That's why I personally just disable all firewalls and just configure acls in
vulnerable services themselves.
Don't let mysql listen on anything but local host, server secured lol.
--
Matt Westfall
President & CIO
ECAN Solutions, Inc.
804.592.1672
On August 22, 2019 11:46:44 AM EDT, Roman M
22.08.2019, 18:46, "Roman Mamedov" :
> On Thu, 22 Aug 2019 13:07:21 +
> "Matt Westfall" wrote:
>
>> So perhaps your ISP is wonking with tor traffic as suggested.
>
> We happened to meet in a Telegram group chat and after some more discussion
> the cause turned out to be firewall rules on th
On Thu, 22 Aug 2019 13:07:21 +
"Matt Westfall" wrote:
> So perhaps your ISP is wonking with tor traffic as suggested.
We happened to meet in a Telegram group chat and after some more discussion
the cause turned out to be firewall rules on the relay machine itself.
--
With respect,
Roman
__
Great, and many thanks - that explains it: if the bursting-timespan is 1 sec
only only I obviously can't see that bandwidth bursting with my resolution of
10 sec measurements.
‐‐‐ Original Message ‐‐‐
On Thursday, 22. August 2019 05:02, teor wrote:
> Hi,
>
> > On 20 Aug 2019, at 20:2
I can traceroute to your ipv6 address:
traceroute to 2a03:e2c0:bc7::2 (2a03:e2c0:bc7::2), 30 hops max, 80 byte
packets
1 2001:559:800c:1900::5a01 (2001:559:800c:1900::5a01) 0.356 ms 0.345
ms 0.449 ms
2 2001:558:180:1c::1 (2001:558:180:1c::1) 0.317 ms 0.435 ms 0.429
ms
3 2001:558:18
Here's all the info you need to setup IPv6 in Debian:
root@ateam:~# ifconfig
eno1: flags=4163 mtu 1500
inet 50.238.252.6 netmask 255.255.255.252 broadcast 50.238.252.7
inet6 2001:559:800c:1900::5a02 prefixlen 126 scopeid 0x0
root@ateam:/etc/network# pwd
/etc/network
root@ateam:/e
IPv6 at the OS Side is not difficult whatsoever.
My node is running IPv6, I have 2Gbps Comcast Fiber.
It's literally no different than configuring IPv4 other than its
hexidecimal and a lot more digits :-D
Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
8
On Thu, 22 Aug 2019 21:23:03 +1000
teor wrote:
> Your relay's IPv6 address is not reachable from the directory authorities:
> https://metrics.torproject.org/rs.html#details/CE5ED345398CC02D573347C2F238F80B18E680EE
>
> All 6 directory authorities on IPv6 can't reach your relay on IPv6:
> https://
Hi,
> On 22 Aug 2019, at 20:00, Станислав wrote:
>
> 22.08.2019, 06:57, "teor" :
>>
>>
>>> On 21 Aug 2019, at 23:38, armik...@gmail.com wrote:
>>>
>>> hi.in relay stopped working ipv6.address is correct all pings, including
>>> tor to the servers, but relay does not work.before that it wor
22.08.2019, 06:57, "teor" :
> Hi,
>
>> On 21 Aug 2019, at 23:38, armik...@gmail.com wrote:
>>
>> hi.in relay stopped working ipv6.address is correct all pings, including
>> tor to the servers, but relay does not work.before that it worked perfectly
>> 2 months.
>
> Please tell us your relay's
Hi Paul,
> On 22 Aug 2019, at 14:26, Paul Templeton wrote:
>
>> It can be hard to set up IPv6 for a relay, we're working on a grant to make
>> it easier.
>
> It could be helpful to do a request/survey to relay operators to find out
> their experiences.
> That is those who have ipv6 configured
> It can be hard to set up IPv6 for a relay, we're working on a grant to make
> it easier.
It could be helpful to do a request/survey to relay operators to find out their
experiences.
That is those who have ipv6 configured what was the process and if there were
any problems in the process.
For
12 matches
Mail list logo
