Hi,
Pinging 44.0.0.1 will not work, since the ucsd gateway does NOT respond to ping from tunnels, only from the internet.
The easiest way to test the tunnels is to set up a tunnel by hand to a known peer, and test using that peer.
Marius, YO2LOJ
(Please trim inclusions from previous messages) _______________________________________________ On Tue, Jun 14, 2016 at 1:23 PM, lleachii--- via 44Net 44net@hamradio.ucsd.edu wrote:
I see your list of Ethernet interfaces...but where's your IPENCAP tunnel interface?
What commands are you using to set your IPENCAP interface Up?
Lynwood,
Thanks for the note. Setting up the IPENCAP interface is the thingI haven't figured out yet. :-)
Here is an example of what I've tried:# ifconfig gif0 create # ifconfig gif0 tunnel 23.30.150.141 169.228.66.251 netmask 255.255.255.254 # route add -host 169.228.66.251 23.30.150.142 add host 169.228.66.251: gateway 23.30.150.142 # ifconfig gif0 inet 23.30.150.141 169.228.66.251 netmask 255.255.255.254 # ifconfig gif0 gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 priority: 0 groups: gif tunnel: inet 23.30.150.141 -> 169.228.66.251 inet 23.30.150.141 --> 169.228.66.251 netmask 0xfffffffe # route add 44/8 23.30.150.141 add net 44/8: gateway 23.30.150.141 # netstat -rn -f inet Routing tables
Internet: Destination Gateway Flags Refs Use Mtu Prio Iface default 23.30.150.142 UGS 4 48 - 8 cnmac0 23.30.150.136/29 23.30.150.141 UC 1 0 - 4 cnmac0 23.30.150.141 44:d9:e7:9f:a7:64 UHLl 0 77 - 1 cnmac0 23.30.150.142 4a:1d:70:de:c3:5a UHLc 2 9 - 4 cnmac0 23.30.150.143 23.30.150.141 UHb 0 0 - 1 cnmac0 44/8 23.30.150.141 UGS 0 33 - 8 gif0 44.44.107/24 44.44.107.1 C 0 0 - 4 cnmac2 44.44.107.1 44:d9:e7:9f:a7:66 UHLl 0 0 - 1 cnmac2 44.44.107.255 44.44.107.1 Hb 0 0 - 1 cnmac2 127/8 127.0.0.1 UGRS 0 0 32768 8 lo0 127.0.0.1 127.0.0.1 UHl 0 0 32768 1 lo0 169.228.66.251 23.30.150.142 UGHSP 0 11 - 8 cnmac0 169.228.66.251 23.30.150.141 UHP 0 0 - 8 gif0 192.168/16 192.168.129.1 UGS 3 3 - 8 cnmac1 192.168.129/24 192.168.129.4 UC 1 0 - 4 cnmac1 192.168.129.1 24:a4:3c:05:57:b5 UHLc 1 2 - 4 cnmac1 192.168.129.4 44:d9:e7:9f:a7:65 UHLl 0 7 - 1 cnmac1 192.168.129.255 192.168.129.4 UHb 0 0 - 1 cnmac1 224/4 127.0.0.1 URS 0 24 32768 8 lo0 #
Let's suppose I try to ping something based on this.# ping -I 44.44.107.1 -c 5 44.0.0.1 PING 44.0.0.1 (44.0.0.1): 56 data bytes --- 44.0.0.1 ping statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss #
However, it appears these are being forwarded. In another windowI ran 'tcpdump -vni gif0' and see this output:
# tcpdump -vni gif0 tcpdump: listening on gif0, link-type LOOP 17:54:23.704315 44.44.107.1 > 44.0.0.1: icmp: echo request (id:17cb seq:0) [icmp cksum ok] (ttl 255, id 47502, len 84) 17:54:24.715928 44.44.107.1 > 44.0.0.1: icmp: echo request (id:17cb seq:1) [icmp cksum ok] (ttl 255, id 47611, len 84) 17:54:25.710780 44.44.107.1 > 44.0.0.1: icmp: echo request (id:17cb seq:2) [icmp cksum ok] (ttl 255, id 16830, len 84) 17:54:26.705734 44.44.107.1 > 44.0.0.1: icmp: echo request (id:17cb seq:3) [icmp cksum ok] (ttl 255, id 34739, len 84) 17:54:27.710742 44.44.107.1 > 44.0.0.1: icmp: echo request (id:17cb seq:4) [icmp cksum ok] (ttl 255, id 32354, len 84) ^C 5 packets received by filter 0 packets dropped by kernel #
And running 'tcpdump -vni cnmac0 proto ipencap' in yet another windowI see the following:
# tcpdump -vni cnmac0 proto ipencap tcpdump: listening on cnmac0, link-type EN10MB 17:56:16.647503 23.30.150.141 > 169.228.66.251: 44.44.107.1 > 44.0.0.1: icmp: echo request (id:1ace seq:0) (ttl 255, id 7822, len 84) (ttl 64, id 27590, len 104) 17:56:17.658425 23.30.150.141 > 169.228.66.251: 44.44.107.1 > 44.0.0.1: icmp: echo request (id:1ace seq:1) (ttl 255, id 22527, len 84) (ttl 64, id 20077, len 104) 17:56:18.653338 23.30.150.141 > 169.228.66.251: 44.44.107.1 > 44.0.0.1: icmp: echo request (id:1ace seq:2) (ttl 255, id 63017, len 84) (ttl 64, id 22814, len 104) 17:56:19.648295 23.30.150.141 > 169.228.66.251: 44.44.107.1 > 44.0.0.1: icmp: echo request (id:1ace seq:3) (ttl 255, id 24579, len 84) (ttl 64, id 13778, len 104) 17:56:20.653301 23.30.150.141 > 169.228.66.251: 44.44.107.1 > 44.0.0.1: icmp: echo request (id:1ace seq:4) (ttl 255, id 31869, len 84) (ttl 64, id 32539, len 104) ^C 21 packets received by filter 0 packets dropped by kernel #
But, no responses are receieved. Perhaps I'm just not pinging theright thing? Trying to ping '44.44.107.1' from an external address does not see incoming packets, either.
Thanks for any help! 73 de AC2OI, - Dan C.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net