I have also noticed that traceroutes through the amprgw router don't seem to work, although the destination host is reachable. I have yet to spend much time on figuring out why this is. - Brian
On Fri, May 05, 2017 at 11:35:40PM +0100, M6XCV (Mike) wrote:
I think this is because you are trying to send via the gateway.
I am not sure why, but I have tried using the gateway to access the internet and my packets go missing. I assumed it should work, however the fact that it did not was not something I thought it was worth investigating as I am BGP routed. If are trying to reach me through the main gateway then perhaps it is worth asking Brian to look in to it?
For the record, I attempted to ping you and my outbound seems fine. https://u4477715.ct.sendgrid.net/wf/click?upn=MJaTQVDJZogYIZySndf7y-2BCWLgZM... 668edee920.pcap
I can ping 44.0.0.1. Traceroutes also show my packets reach the gateway but go no further. I added a static route for 8.8.8.8 encapped via the gateway and it gave me this.
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 onsite.notmike.uk (44.131.14.129) 0.412 ms 0.392 ms 0.382 ms 2 Gateway.AS206671 (44.131.14.254) 9.972 ms 9.989 ms 9.988 ms 3 amprgw.sysnet.ucsd.edu (169.228.66.251) 158.942 ms 158.981 ms 159.397 ms 4 * * * 5 * * *
I suspect a firewall rule, however there are A records under ampr.org for all of my IP addresses.
Thanks, Mike, M6XCV