Re: [44net] New Linux Boot Scripts for Testing

OK, I think I discovered the issue... only the following IPs are available: 44.60.44.3 (DNS) 44.60.44.10 (HTTP) 44.60.44.14 (a PC, should be able to ping) I've found an anomaly on my Gateway...where 44 the IP assigned to tunl0 encapsulates using the real destination in the outer header (instead of AMPRGW). Going to another 44 IPENCAP tunnel works fine. In fact, all IPs assigned to my AMPR Gateway cannot reach non 44 addresses in the proper manner... Any ideas? ----------- on tunl0 OUTER - Internet Protocol Version 4, Src: 192.168.10.2 (192.168.10.2), ****Dst: 8.8.8.8 (8.8.8.8)**** INNER - Internet Protocol Version 4, Src: 44.60.44.2 (44.60.44.2), Dst: 8.8.8.8 (8.8.8.8) ----------- on eth1 (44.60.44.1) user@kb3vwg-001:~$ ping 8.8.8.8 -I eth1 PING 8.8.8.8 (8.8.8.8) from 44.60.44.1 eth1: 56(84) bytes of data. From 44.60.44.1 icmp_seq=1 Destination Host Unreachable From 44.60.44.1 icmp_seq=2 Destination Host Unreachable From 44.60.44.1 icmp_seq=3 Destination Host Unreachable From 44.60.44.1 icmp_seq=4 Destination Host Unreachable From 44.60.44.1 icmp_seq=5 Destination Host Unreachable From 44.60.44.1 icmp_seq=6 Destination Host Unreachable (I should note, I see no traffic on the wire, meaning my GW is giving the response to 44.60.44.1) ----------- Downstream device (44.60.44.14) user@kb3vwg-014:~$ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8 <http://8.8.8.8>: icmp_req=1 ttl=54 time=87.4 ms 64 bytes from 8.8.8.8 <http://8.8.8.8>: icmp_req=2 ttl=54 time=87.3 ms 64 bytes from 8.8.8.8 <http://8.8.8.8>: icmp_req=3 ttl=54 time=86.8 ms 64 bytes from 8.8.8.8 <http://8.8.8.8>: icmp_req=4 ttl=54 time=88.6 ms -----------