14 Jun
2016
14 Jun
'16
4:57 p.m.
On Tue, Jun 14, 2016 at 4:33 PM, lleachii--- via 44Net <
44net(a)hamradio.ucsd.edu> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
The reason your AMPR traffic does not yet work - is because you haven't
yet created an IPENCAP tunnel to listen on cnmac0 that will decapsulate the
IP traffic and forward/bridge/NET/etc. it to the network located at cnmac2.
At this point, you're still looking at the encapsulated IPENCAP traffic
with the additional Public IP header included. The tunnel interface strips
this header - and your traffic will be ready for your local 44 subnet.
Thanks again for the response, Lynwood. I'm not sure this is completely
accurate, however: in the tunnel configuration I created in my last email,
for instance, I saw unencapsulated RIP traffic being delivered to to gif
interface I created. For example, consider this output from tcpdump:
# tcpdump -vni gif0
...
20:30:33.727242 44.0.0.1.520 > 224.0.0.9.520: [no udp cksum] RIPv2-resp
[items 25]: [password ***redacted***] {44.131.8.0/255.255.255.0->212.56.100.200
tag 0004}(1) {44.131.7.0/255.255.255.0->92.237.131.1 tag 0004}(1) {
44.130.240.6/255.255.255.255->52.76.212.50 tag 0004}(1)[|rip] (ttl 64, id
0, len 532)
...
#
From this point, I would expect to be able to 'ping 44.44.107.1' (my 44net
interface) from an external, Internet connected host and at least see an
ICMP
echo request. However, doing so from a random machine, I see neither an
unencapsulated ICMP echo request packet on gif0, nor an encapsulated
packet on cnmac0.
Trying to 'traceroute 44.44.107.1' from a machine on the Internet shows hops
until I get to the amprgw at UCSD, and then nothing. Should I expect to see
those
make it to my router?
Hopefully, someone can provide you information on IPENCAP in BSD (once you
receive it, consider making a BSD page on the Wiki
site).
I will be happy to!
One of the apparent differences between BSD and Linux is that folks seem to
be adding multiple point-to-point tunnels between machines onto a single
virtual
tunnel interface. With BSD, it appears the easiest thing to do *may* be
create
a separate 'gif' interface for each tunnel. I was hoping to find a way to
avoid
that, but I come up with anything. If someone knows, please do let me know.
Thanks!
- Dan C.