There are two gateway systems with misconfigured routing tables that are attempting to route all of net44 through amprgw instead of using mesh connections. These may have a default route instead of using the correct routing table. Whatever the case, they aren't going to have much luck reaching other net44 hosts. Those gateway operators should check their configurations. - Brian
Last update at Sun Oct 22 06:30:01 2017 PDT [-0700]
gateway inner src #errs indx error type ---------------- ---------------- ----- ---- ------------------------------- 79.0.254.164 44.134.96.1 5408 [ 8] dropped: encap to encap 173.230.244.130 44.68.41.1 1349 [ 8] dropped: encap to encap
Il 22/10/2017 15:42, Brian Kantor ha scritto:
There are two gateway systems with misconfigured routing tables that are attempting to route all of net44 through amprgw instead of using mesh connections. These may have a default route instead of using the correct routing table. Whatever the case, they aren't going to have much luck reaching other net44 hosts. Those gateway operators should check their configurations.
- Brian
Last update at Sun Oct 22 06:30:01 2017 PDT [-0700]
gateway inner src #errs indx error type
79.0.254.164 44.134.96.1 5408 [ 8] dropped: encap to encap 173.230.244.130 44.68.41.1 1349 [ 8] dropped: encap to encap
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Hi everyone, gw 79.0.254.164 has been out of control until today 01/11/17 because of my job injury that actually blocked me in the system's monitoring and supervision activities. The system seems to work on a regular basis today. I ask courtesy to Brian and colleagues to report any abnormalities that should arise on the system from today. 73 de IW8PGT
-
Brian Kantor -
Francesco Ciacco