17 Jan
2013
17 Jan
'13
9:53 p.m.
Dear Bob VE3TOK (and thanks to VE3ZDA and N2NOV),
Your entry is on my route table, I'm using rip44d (not encap), so my
updates are live. The IP of my gateway is correct in the Portal. I use
the -a switch to remove my own route (and have updated it to the correct
IP); and I still receive rip44d updates over AMPR (showing that I have
not lost connectivity to the Main AMPRGW).
From testing connectivity to your subnet, I have determined that my
44GW is operational; and that some gateways may not have yet updated
their encap.
Thanks for your help; I waited a few days to to be sure that was not the
case; as I know all stations do not have dynamic routing updates, I'll
wait longer next time.
73,
Lynwood
KB3VWG
http://44.60.44.10/tools
@kb3vwg-015:~$ ping 44.135.85.1 -c 10
PING 44.135.85.1 (44.135.85.1) 56(84) bytes of data.
From 44.135.85.30: icmp_seq=7 Source Quench
From 44.135.85.30: icmp_seq=8 Source Quench
From 44.135.85.30: icmp_seq=9 Source Quench
From 44.135.85.30: icmp_seq=10 Source Quench
--- 44.135.85.1 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9003ms
@kb3vwg-015:~$ traceroute 44.135.85.30
traceroute to 44.135.85.30 (44.135.85.30), 30 hops max, 60 byte packets
1 kb3vwg-001.ampr.org (44.60.44.1) 0.724 ms 0.238 ms 0.218 ms
2 linux.ve3mch.ampr.org (44.135.85.151) 51.890 ms 55.835 ms 60.720 ms
3 port.ve3mch.ampr.org (44.135.85.30) 63.642 ms 62.613 ms 66.477 ms
@kb3vwg-015:~$ ping 44.135.85.30 -c 5
PING 44.135.85.30 (44.135.85.30) 56(84) bytes of data.
64 bytes from 44.135.85.30: icmp_req=1 ttl=39 time=53.9 ms
64 bytes from 44.135.85.30: icmp_req=2 ttl=39 time=51.8 ms
64 bytes from 44.135.85.30: icmp_req=3 ttl=39 time=87.4 ms
64 bytes from 44.135.85.30: icmp_req=4 ttl=39 time=52.7 ms
64 bytes from 44.135.85.30: icmp_req=5 ttl=39 time=51.9 ms
--- 44.135.85.30 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 51.899/59.607/87.406/13.919 ms
18 Jan
18 Jan
12:23 a.m.
New subject: Gateways Unreachable after Dynamic IP Update
I just tried again a couple of minutes ago and at first I couldn't ping
you (started with 44.60.44.10) and tried several other 44 ip addresses
you mentioned and suddenly something opened up at you end and I could
ping all your addresses incl. 44.60.44.10
This was around 7.16 PM EST.
73,
Bob VE3TOK
On 13-01-17 04:53 PM, lleachii(a)aol.com wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Dear Bob VE3TOK (and thanks to VE3ZDA and N2NOV),
Your entry is on my route table, I'm using rip44d (not encap), so my
updates are live. The IP of my gateway is correct in the Portal. I use
the -a switch to remove my own route (and have updated it to the
correct IP); and I still receive rip44d updates over AMPR (showing
that I have not lost connectivity to the Main AMPRGW).
From testing connectivity to your subnet, I have determined that my
44GW is operational; and that some gateways may not have yet updated
their encap.
Thanks for your help; I waited a few days to to be sure that was not
the case; as I know all stations do not have dynamic routing updates,
I'll wait longer next time.
73,
Lynwood
KB3VWG
http://44.60.44.10/tools
@kb3vwg-015:~$ ping 44.135.85.1 -c 10
PING 44.135.85.1 (44.135.85.1) 56(84) bytes of data.
From 44.135.85.30: icmp_seq=7 Source Quench
From 44.135.85.30: icmp_seq=8 Source Quench
From 44.135.85.30: icmp_seq=9 Source Quench
From 44.135.85.30: icmp_seq=10 Source Quench
--- 44.135.85.1 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9003ms
@kb3vwg-015:~$ traceroute 44.135.85.30
traceroute to 44.135.85.30 (44.135.85.30), 30 hops max, 60 byte packets
1 kb3vwg-001.ampr.org (44.60.44.1) 0.724 ms 0.238 ms 0.218 ms
2 linux.ve3mch.ampr.org (44.135.85.151) 51.890 ms 55.835 ms 60.720 ms
3 port.ve3mch.ampr.org (44.135.85.30) 63.642 ms 62.613 ms 66.477 ms
@kb3vwg-015:~$ ping 44.135.85.30 -c 5
PING 44.135.85.30 (44.135.85.30) 56(84) bytes of data.
64 bytes from 44.135.85.30: icmp_req=1 ttl=39 time=53.9 ms
64 bytes from 44.135.85.30: icmp_req=2 ttl=39 time=51.8 ms
64 bytes from 44.135.85.30: icmp_req=3 ttl=39 time=87.4 ms
64 bytes from 44.135.85.30: icmp_req=4 ttl=39 time=52.7 ms
64 bytes from 44.135.85.30: icmp_req=5 ttl=39 time=51.9 ms
--- 44.135.85.30 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 51.899/59.607/87.406/13.919 ms
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html
5:37 p.m.
New subject: Gateways Unreachable after Dynamic IP Update
Dear Bob VE3TOK and Don VE3ZDA,
Bob, I can confirm that 44.60.44.10, 11 and 12 had an MTU (1480)
mismatch with my 44Router 98.252.61.22/44.60.44.1 (1500). That was fixed
around the time you specified.
I receive the following RIP44 announcement for you from 44.0.0.1, it is
in my 44routing table:
44.135.85.0/24 via 69.165.175.62 dev tunl0 onlink window 840
Don, without a reference to your GW WAN IP or 44subnet address, I'm
unable to test or confirm anything here (I recall a file on the old
gateway service that included gateway notes - but those notes can only
be referenced on the portal by WAN IP). Yes, I am certain my end is
encapsulating, as I have not lost connection to AMPRGW nor VE3TOK. I see
IP-in-IP datagrams thru routers I'm in control of between 98.252.61.22
and the tunnel interface - addressed to AMPRGW and VE3TOK.
Feel free to check your 44net connection via:
From anywhere
http://kb3vwg-010.ampr.org/tools/ping/php-ping.php
http://kb3vwg-010.ampr.org/tools/trace/php-trace.php
On AMPR
http://whatismyip.ampr.org
nslookup server 44.60.44.3
dns-mdc.ampr.org
(looks up 44.in-addr.arpa and ampr.org. for all Internet hosts and is
ICANN recursive for 44.0.0.0/8 hosts).
At this time, I am left to assume that I am not reaching valid IPs, or
the router of the other 44endpoint has not updated their routing table.
73,
Lynwood
8:18 p.m.
New subject: Gateways Unreachable after Dynamic IP Update
My address is 44.135.90.2 encap 70.52.124.227
After I had tried from my end I then went to ve3mch (Bob) and got the same
result, no ping. That is why I asked about encap..
Don
On Fri, Jan 18, 2013 at 12:37 PM, <lleachii(a)aol.com> wrote:
(Please trim inclusions from previous messages)
______________________________**_________________
Dear Bob VE3TOK and Don VE3ZDA,
Bob, I can confirm that 44.60.44.10, 11 and 12 had an MTU (1480) mismatch
with my 44Router 98.252.61.22/44.60.44.1 (1500). That was fixed around
the time you specified.
I receive the following RIP44 announcement for you from 44.0.0.1, it is in
my 44routing table:
44.135.85.0/24 via 69.165.175.62 dev tunl0 onlink window 840
Don, without a reference to your GW WAN IP or 44subnet address, I'm unable
to test or confirm anything here (I recall a file on the old gateway
service that included gateway notes - but those notes can only be
referenced on the portal by WAN IP). Yes, I am certain my end is
encapsulating, as I have not lost connection to AMPRGW nor VE3TOK. I see
IP-in-IP datagrams thru routers I'm in control of between 98.252.61.22 and
the tunnel interface - addressed to AMPRGW and VE3TOK.
Feel free to check your 44net connection via:
From anywhere
http://kb3vwg-010.ampr.org/**tools/ping/php-ping.php<http://kb3vwg-010.a…
http://kb3vwg-010.ampr.org/**tools/trace/php-trace.php<http://kb3vwg-010…
On AMPR
http://whatismyip.ampr.org
nslookup server 44.60.44.3
dns-mdc.ampr.org
(looks up 44.in-addr.arpa and ampr.org. for all Internet hosts and is
ICANN recursive for 44.0.0.0/8 hosts).
At this time, I am left to assume that I am not reaching valid IPs, or the
router of the other 44endpoint has not updated their routing table.
73,
Lynwood
______________________________**___________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/**mailman/listinfo/44net<http://hamradio.ucsd.e…
http://www.ampr.org/donate.**html <http://www.ampr.org/donate.html>
8:32 p.m.
New subject: Gateways Unreachable after Dynamic IP Update
Hi Lynwood,
I can confirm the behavior described by Don...
I can ping ve3zda.ampr.org without problems.
As for 44.60.44.1, 44.60.44.10, 44.60.44.11 and 44.60.44.12, ping goes out
via encap interface but there's no response on the ipip tunnel.
My system: 44.182.21.1/89.122.215.236
73,
Marius, yo2loj
7 Apr
7 Apr
12:41 p.m.
New subject: Gateways Unreachable after Dynamic IP Update
On 13-01-18 04:32 PM, Marius Petrescu wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Hi Lynwood,
I can confirm the behavior described by Don...
I can ping ve3zda.ampr.org without problems.
As for 44.60.44.1, 44.60.44.10, 44.60.44.11 and 44.60.44.12, ping goes out
via encap interface but there's no response on the ipip tunnel.
My system: 44.182.21.1/89.122.215.236
73,
Marius, yo2loj
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html
complete HD failure on this end....setting up from scratch again, arrgh!
my backup was too old to be very useful...I'm thinking of using the
linux stack again for our link? it's 44.135.32.201
(linux.ve1jot.ampr.org) port 10095, but I'm ok with any axudp port
needed...I'll wait till you reply before I mess with it, hi hi!
Cheerio,
John
12:51 p.m.
New subject: Gateways Unreachable after Dynamic IP Update
On 13-04-07 08:41 AM, jj wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On 13-01-18 04:32 PM, Marius Petrescu wrote:
oops...went to the list....darn autocomplete! pse ignore
(Please trim inclusions from previous messages)
_______________________________________________
Hi Lynwood,
I can confirm the behavior described by Don...
I can ping ve3zda.ampr.org without problems.
As for 44.60.44.1, 44.60.44.10, 44.60.44.11 and 44.60.44.12, ping
goes out
via encap interface but there's no response on the ipip tunnel.
My system: 44.182.21.1/89.122.215.236
73,
Marius, yo2loj
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html
complete HD failure on this end....setting up from scratch again,
arrgh! my backup was too old to be very useful...I'm thinking of using
the linux stack again for our link? it's 44.135.32.201
(linux.ve1jot.ampr.org) port 10095, but I'm ok with any axudp port
needed...I'll wait till you reply before I mess with it, hi hi!
Cheerio,
John
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html
4038
days inactive
4118
days old
6 comments
5 participants
participants (5)
-
Bob Tenty -
Don Moore -
jj -
lleachii＠aol.com -
Marius Petrescu