Re: [44net] Iperf server for public use

I am seeing the exact same thing with brian as well. Last week he was able to ping me 44.56.6.1-3 is what I had him test, but I am not able to ping him, but others I can. I can't see his services on the 44 net either. I also see some people using the 44 network for asterisk repeaters. I can not ping them inside the network at all. I can see them outside but not inside. Are there just a lot of people not routing right? I mean if I am on the 44 network and can't reach them but I can in the public, that just doesn't sound right to me. Corey. N3FE > On Jul 25, 2015, at 3:12 PM, Rob Janssen <pe1chl(a)amsat.org> wrote: > > (Please trim inclusions from previous messages) > _______________________________________________ >> Subject: >> Re: [44net] Iperf server for public use >> From: >> "Marc, LX1DUC" <lx1duc(a)laru.lu> >> Date: >> 07/24/2015 09:44 PM >> >> To: >> AMPRNet working group <44net(a)hamradio.ucsd.edu> >> >> >> I have a BGP feed and the IPIP mesh (loaded from API). >> >> These are the relevant routing entries for 44.137.40.2. >> >> # DST-ADDRESS PREF-SRC GATEWAY DISTANCE >> 0 ADb 0.0.0.0/0 46.29.abc.xyz 250 >> 1 A S 44.137.0.0/16 ampr-213.222.de... 210 >> 2 Db 44.137.0.0/16 46.29.abc.xyz 250 >> 3 A S 44.137.40.2/32 ampr-89.18.def.ghi 210 >> >> Rule #0 and #2 are BGP routes, rule #1 and #3 are static rules added via script parsing API output. >> >> As you can see I prefer IPIP routes over BGP. >> >> Traceroute looks fine: >> >> marconi:~# traceroute -I 44.137.40.2 >> traceroute to 44.137.40.2 (44.137.40.2), 30 hops max, 60 byte packets >> 1 lx0bgp-18.ampr.org (44.161.204.1) 0.390 ms 0.493 ms 0.652 ms >> 2 tunnels.lx0bgp.ampr.org (44.161.230.255) 7.681 ms 7.743 ms 7.878 ms >> 3 sys2.pe1chl.ampr.org (44.137.40.2) 24.655 ms 24.666 ms 25.041 ms >> >> 73 de Marc, LX1DUC > > Hi Marc, > > I can ping you OK from both systems. What you tried above is via tunnel, and e.g. to 44.137.0.1 can > be via BGP or Tunnel. Both will work. > > But when I ping Brian N1URO from 44.137.0.1 I see the outgoing traffic via tunnel and I never see a > reply coming back. No idea what is wrong. It cannot be a firewall at my end because I would see the > reply when tracing (tshark operates before the filter). > > Interesting is that he can ping me. And I can communicate with many systems, both those that use > tunnels and those that have direct BGP routing. No idea where the issue is. > > Rob >