Based off the output of the munge script, those two addresses take different paths: /sbin/ip route add 44.137.41.96/28 via 89.18.172.156 dev tunl0 onlink /sbin/ip route add 44.137.0.0/16 via 213.222.29.194 dev tunl0 onlink On Sat, Jul 25, 2015 at 12:19 PM, Rob Janssen <pe1chl(a)amsat.org> wrote: > (Please trim inclusions from previous messages) > _______________________________________________ > >> Subject: >> [44net] Iperf server - kk7kx >> From: >> "Assi Friedman" <assi(a)kiloxray.com> >> Date: >> 07/25/2015 05:56 AM >> >> To: >> "'AMPRNet working group'" <44net(a)hamradio.ucsd.edu> >> >> >> Folks: >> I think the direct routes to the various AMPRNet nodes are up and running. >> Iperf is running: >> TCP: iperf -c kk7kx.ampr.org -p 7000 >> UDP: iperf -c kk7kx.ampr.org -p 7000 -u >> Ping and MTR should also respond. >> I do however seem to have an issue with the web page. Does >> http://kk7kx.ampr.org respond from the AMPRNet? >> Thanks, >> Assi >> >> > I think there still are issues. How do you route 44.137.0.0/16 ? > I can now run the iperf from 44.137.0.1 but not from 44.137.41.97 > Same for the webpage. > > Rob > > ------------------------------------------------------------ > Client connecting to kk7kx.ampr.org, TCP port 7000 > TCP window size: 256 KByte (default) > ------------------------------------------------------------ > [ 3] local 44.137.0.1 port 57548 connected with 44.8.0.160 port 7000 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-10.2 sec 6.50 MBytes 5.36 Mbits/sec > > ------------------------------------------------------------ > Client connecting to kk7kx.ampr.org, UDP port 7000 > Sending 1470 byte datagrams > UDP buffer size: 256 KByte (default) > ------------------------------------------------------------ > [ 3] local 44.137.0.1 port 54929 connected with 44.8.0.160 port 7000 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec > [ 3] Sent 893 datagrams > [ 3] Server Report: > [ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec 0.242 ms 0/ 893 (0%) > >