24 Jul
2015
24 Jul
'15
3:16 p.m.
Subject:
Re: [44net] Iperf server for public use
From:
Brian <n1uro(a)n1uro.ampr.org>
Date:
07/24/2015 02:46 AM
To:
AMPRNet working group <44net(a)hamradio.ucsd.edu>
Rob;
On Thu, 2015-07-23 at 22:46 +0200, Rob Janssen wrote:
Hi Brian,
With your system I have a different issue... when I ping n1uro.ampr.org from 44.137.40.2
which
has an IPIP tunnel on 89.18.172.156 I can ping you without problem, but when I ping from
other
addresses like 44.137.0.1 or 44.137.41.97 I get no reply.
Those addresses are supposed to be handled via the tunnel for 44.137.0.0/16 which has
external
address 213.222.29.194 and is also registered in the portal.
They are also reachable on the internet directly (BGP announced)
What can be the problem? Did you add some handling of BGP routed subnets that now fails
because
of the dual connectivity we have? Or is it the issue that I hunted some time ago (and
never really
tracked down) where there appears to be systematic packet loss in RIP announcements that
makes
certain subnets disappear completely or make them flapping?
(I tried to suppress that by increasing EXPTIME to 7200 in ampr-ripd.c)
Rob
>This means it failed!
>And not from UDP either. I have the same result. It does not work.
>Others who can reach kk7kx?
>
>Assi, what kind of return routes do you have? Do you route everything back via UCSD
>or do you have a proper tunnel mesh?
I concur:
n1uro@n1uro:~$ iperf -c kk7kx.ampr.org -p 7000
connect failed: Connection timed out