I have a question to the sysops running gateways in Europe.
Lately, my subnets (44.182.21.0/24, 44.182.20.0/24 and 44.182.21.253 using gw 89.122.215.236 and yo2loj.go.ro) seem to have been lockout from different regions like Germany, Poland, Portugal and Bulgaria, while access from 44.182.21.1/32 still works.
Is this intentional or just a configuration issue?
Marius, YO2LOJ
On Mon, Apr 29, 2019 at 02:38:53PM +0300, Marius Petrescu wrote:
I have a question to the sysops running gateways in Europe.
Lately, my subnets (44.182.21.0/24, 44.182.20.0/24 and 44.182.21.253 using gw 89.122.215.236 and yo2loj.go.ro) seem to have been lockout from different regions like Germany, Poland, Portugal and Bulgaria, while access from 44.182.21.1/32 still works.
Is this intentional or just a configuration issue?
Marius, YO2LOJ
Marius, attempting to traceroute to 89.122.215.236 from San Diego does not get any further than Germany, with the last response being from 193.159.167.174, a host with no rDNS entry, but whose subnet, according to RIPE, is a transit network allocated to Deutsche Telekom AG. - Brian
Tnx. Brian,
This may be an issue , but I can actually ping the gateways of those subnets, so traffic actually passes. Maybe it is an ipip filtering or something. But then again, it works with US gateways...
(Btw, it is funny, Deutsche Telekom is the operator of 89.122.215.236, since they took over our national former state owned operator).
On 29.04.2019 15:01, Brian Kantor wrote:
On Mon, Apr 29, 2019 at 02:38:53PM +0300, Marius Petrescu wrote:
I have a question to the sysops running gateways in Europe.
Lately, my subnets (44.182.21.0/24, 44.182.20.0/24 and 44.182.21.253 using gw 89.122.215.236 and yo2loj.go.ro) seem to have been lockout from different regions like Germany, Poland, Portugal and Bulgaria, while access from 44.182.21.1/32 still works.
Is this intentional or just a configuration issue?
Marius, YO2LOJ
Marius, attempting to traceroute to 89.122.215.236 from San Diego does not get any further than Germany, with the last response being from 193.159.167.174, a host with no rDNS entry, but whose subnet, according to RIPE, is a transit network allocated to Deutsche Telekom AG.
- Brian
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
You can check at http://ping.sp.ampr.org or http://trace.sp.ampr.org (from Poland - 44.165.44.165) - more http://sp.ampr.org.
From 44.165.44.9:
sq2frb@mega:~$ nmap -sP 44.182.21.0/24 Starting Nmap 7.40 ( https://nmap.org ) at 2019-04-29 14:07 CEST Nmap scan report for yo2tm.ampr.org (44.182.21.1) Host is up (0.045s latency). Nmap scan report for server.yo2loj.ampr.org (44.182.21.2) Host is up (0.087s latency). Nmap scan report for ap.yo2lgp.ampr.org (44.182.21.145) Host is up (0.11s latency). Nmap scan report for router2.yo2loj.ampr.org (44.182.21.253) Host is up (0.050s latency). Nmap scan report for router.yo2loj.ampr.org (44.182.21.254) Host is up (0.10s latency). Nmap done: 256 IP addresses (5 hosts up) scanned in 5.46 seconds
sq2frb@mega:~$ nmap -sP 44.182.20.0/24 Starting Nmap 7.40 ( https://nmap.org ) at 2019-04-29 14:08 CEST Nmap scan report for yo2llq.ampr.org (44.182.20.35) Host is up (0.095s latency). Nmap scan report for yo2lic.ampr.org (44.182.20.42) Host is up (0.095s latency). Nmap scan report for yo2lqm.ampr.org (44.182.20.45) Host is up (0.094s latency). Nmap done: 256 IP addresses (3 hosts up) scanned in 7.14 seconds
pon., 29 kwi 2019 o 14:06 Marius Petrescu marius@yo2loj.ro napisał(a):
Tnx. Brian,
This may be an issue , but I can actually ping the gateways of those subnets, so traffic actually passes. Maybe it is an ipip filtering or something. But then again, it works with US gateways...
(Btw, it is funny, Deutsche Telekom is the operator of 89.122.215.236, since they took over our national former state owned operator).
On 29.04.2019 15:01, Brian Kantor wrote:
On Mon, Apr 29, 2019 at 02:38:53PM +0300, Marius Petrescu wrote:
I have a question to the sysops running gateways in Europe.
Lately, my subnets (44.182.21.0/24, 44.182.20.0/24 and 44.182.21.253 using gw 89.122.215.236 and yo2loj.go.ro) seem to have been lockout
from
different regions like Germany, Poland, Portugal and Bulgaria, while access from 44.182.21.1/32 still works.
Is this intentional or just a configuration issue?
Marius, YO2LOJ
Marius, attempting to traceroute to 89.122.215.236 from San Diego does not get any further than Germany, with the last response being from 193.159.167.174, a host with no rDNS entry, but whose subnet, according to RIPE, is a transit network allocated to Deutsche Telekom AG. - Brian
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Tnx Andrej,
Somehow, after a few days of not working, everything seems to be normal again :-)
Coincidence? :-)
On 29.04.2019 15:30, Andrzej via 44Net wrote:
You can check at http://ping.sp.ampr.org or http://trace.sp.ampr.org (from Poland - 44.165.44.165) - more http://sp.ampr.org.
From 44.165.44.9:
sq2frb@mega:~$ nmap -sP 44.182.21.0/24 Starting Nmap 7.40 ( https://nmap.org ) at 2019-04-29 14:07 CEST Nmap scan report for yo2tm.ampr.org (44.182.21.1) Host is up (0.045s latency). Nmap scan report for server.yo2loj.ampr.org (44.182.21.2) Host is up (0.087s latency). Nmap scan report for ap.yo2lgp.ampr.org (44.182.21.145) Host is up (0.11s latency). Nmap scan report for router2.yo2loj.ampr.org (44.182.21.253) Host is up (0.050s latency). Nmap scan report for router.yo2loj.ampr.org (44.182.21.254) Host is up (0.10s latency). Nmap done: 256 IP addresses (5 hosts up) scanned in 5.46 seconds
sq2frb@mega:~$ nmap -sP 44.182.20.0/24 Starting Nmap 7.40 ( https://nmap.org ) at 2019-04-29 14:08 CEST Nmap scan report for yo2llq.ampr.org (44.182.20.35) Host is up (0.095s latency). Nmap scan report for yo2lic.ampr.org (44.182.20.42) Host is up (0.095s latency). Nmap scan report for yo2lqm.ampr.org (44.182.20.45) Host is up (0.094s latency). Nmap done: 256 IP addresses (3 hosts up) scanned in 7.14 seconds
pon., 29 kwi 2019 o 14:06 Marius Petrescu marius@yo2loj.ro napisał(a):
Tnx. Brian,
This may be an issue , but I can actually ping the gateways of those subnets, so traffic actually passes. Maybe it is an ipip filtering or something. But then again, it works with US gateways...
(Btw, it is funny, Deutsche Telekom is the operator of 89.122.215.236, since they took over our national former state owned operator).
On 29.04.2019 15:01, Brian Kantor wrote:
On Mon, Apr 29, 2019 at 02:38:53PM +0300, Marius Petrescu wrote:
I have a question to the sysops running gateways in Europe.
Lately, my subnets (44.182.21.0/24, 44.182.20.0/24 and 44.182.21.253 using gw 89.122.215.236 and yo2loj.go.ro) seem to have been lockout
from
different regions like Germany, Poland, Portugal and Bulgaria, while access from 44.182.21.1/32 still works.
Is this intentional or just a configuration issue?
Marius, YO2LOJ
Marius, attempting to traceroute to 89.122.215.236 from San Diego does not get any further than Germany, with the last response being from 193.159.167.174, a host with no rDNS entry, but whose subnet, according to RIPE, is a transit network allocated to Deutsche Telekom AG. - Brian
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Andrzej -
Brian Kantor -
Marius Petrescu