2 Aug
2013
2 Aug
'13
4:58 a.m.
Blaine,
Here are some tools that may be helpful to you in the future for troubleshooting:
http://kb3vwg-010.ampr.org/tools/ping/php-ping.php
http://kb3vwg-010.ampr.org/tools/trace/php-trace.php
http://whatismyip.ampr.org/
http://speedtest.ampr.org/
DNS:
dns-mdc.ampr.org (44.60.44.3 kb3vwg-003.ampr.org)
Also, I cannot ping you, but traceroue is working:
traceroute to 44.4.36.1 (44.4.36.1), 30 hops max, 60 byte packets
1 kb3vwg-001.ampr.org (44.60.44.1) 0.480 ms 0.924 ms 0.889 ms
2 k1qv.ampr.org (44.4.36.1) 91.696 ms 95.844 ms 100.637 ms
-Lynwood
KB3VWG
2 Aug
2 Aug
6:30 a.m.
New subject: question regarding amprgw.sysnet.ucsd.edu
Yes it's an interesting problem I seem to be having. I seem to be able
to reach some machines, but not other. I'm starting to suspect some
issue related to filtering, but it's hard to diagnose without another
machine running tcpdump to help.
Right now I'm receiving traffic from 44.0.0.1, as well as the
Internet, and certain machines on net44
The links you provided will be very helpful, I was looking for just
such a thing! I'll be testing those out later when I get the time.
Thanks much,
Blaine, K1QV
Sent from my iPhone
On Aug 1, 2013, at 2:59 PM, "lleachii(a)aol.com" <lleachii(a)aol.com> wrote:
Also, I cannot ping you, but traceroue is working:
7:11 p.m.
New subject: ipip tunnel
Miro LZ4NY,
No problems on my side; is your AMPR firewall blocking ICMP - Echo Reply?
ip route get 44.185.1.1
44.185.1.1 via
109.107.73.62 dev tunl0 src 172.31.255.254
traceroute to 44.185.1.1 (44.185.1.1), 30 hops max, 60 byte packets
1 kb3vwg-001.ampr.org (44.60.44.1) 0.380 ms 0.202 ms 0.108 ms
2 lz4ny.ampr.org (44.185.1.1) 128.304 ms 132.677 ms 137.805 ms
PING 44.185.1.1 (44.185.1.1) 56(84) bytes of data.
64 bytes from 44.185.1.1: icmp_req=1 ttl=63 time=130 ms
64 bytes from 44.185.1.1: icmp_req=2 ttl=63 time=128 ms
64 bytes from 44.185.1.1: icmp_req=3 ttl=63 time=131 ms
64 bytes from 44.185.1.1: icmp_req=4 ttl=63 time=133 ms
--- 44.185.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 128.803/130.923/133.714/1.804 ms
-Lynwood
KB3VWG
9:13 p.m.
New subject: ipip tunnel
Miro LZ4NY,
Please confirm you are using RIP44d version 1.3.
The first release of v1.2 had a CIDR prefix issue.
-Lynwood
KB3VWG
10:07 p.m.
New subject: ipip tunnel
Hi Lynwood,
You have an error in your set up...
ip route get 44.185.1.1
44.185.1.1 via
109.107.73.62 dev tunl0 src 172.31.255.254
This is wrong. It should state :
44.185.1.1 via 109.107.73.62 dev tunl0 src 44.60.44.1
This leads to faulty encapsulation using your public IP as source instead of
the ampr address and will trigger a wrong response route on the target
systems.
73s de YO2LOJ
-----Original Message-----
From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu
[mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of
lleachii(a)aol.com
Sent: Friday, August 02, 2013 15:11
To: 44net(a)hamradio.ucsd.edu
Subject: Re: [44net] ipip tunnel
(Please trim inclusions from previous messages)
_______________________________________________
Miro LZ4NY,
No problems on my side; is your AMPR firewall blocking ICMP - Echo Reply?
ip route get 44.185.1.1
44.185.1.1 via
109.107.73.62 dev tunl0 src 172.31.255.254
traceroute to 44.185.1.1 (44.185.1.1), 30 hops max, 60 byte packets
1 kb3vwg-001.ampr.org (44.60.44.1) 0.380 ms 0.202 ms 0.108 ms
2 lz4ny.ampr.org (44.185.1.1) 128.304 ms 132.677 ms 137.805 ms
PING 44.185.1.1 (44.185.1.1) 56(84) bytes of data.
64 bytes from 44.185.1.1: icmp_req=1 ttl=63 time=130 ms
64 bytes from 44.185.1.1: icmp_req=2 ttl=63 time=128 ms
64 bytes from 44.185.1.1: icmp_req=3 ttl=63 time=131 ms
64 bytes from 44.185.1.1: icmp_req=4 ttl=63 time=133 ms
--- 44.185.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms rtt
min/avg/max/mdev = 128.803/130.923/133.714/1.804 ms
-Lynwood
KB3VWG
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html
10:17 p.m.
New subject: ipip tunnel
Correction, it will encapsulate with 172.31.255.254, but it stil won't work.
-----Original Message-----
From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu
[mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of
Marius Petrescu
Sent: Friday, August 02, 2013 18:08
To: 'AMPRNet working group'
Subject: Re: [44net] ipip tunnel
(Please trim inclusions from previous messages)
_______________________________________________
Hi Lynwood,
You have an error in your set up...
ip route get 44.185.1.1
44.185.1.1 via
109.107.73.62 dev tunl0 src 172.31.255.254
This is wrong. It should state :
44.185.1.1 via 109.107.73.62 dev tunl0 src 44.60.44.1
This leads to faulty encapsulation using your public IP as source instead of
the ampr address and will trigger a wrong response route on the target
systems.
73s de YO2LOJ
4162
days inactive
4163
days old
5 comments
3 participants
participants (3)
-
Blaine Forbort -
lleachii＠aol.com -
Marius Petrescu