Closed max-b closed 9 years ago
Ok well I have good news and I have bad news.....
The good news is that I think I figured out what's causing this.
The bad news is that once again, it seems to be mtu issues :/ The home node had an mtu of 1446, while the exit server had an mtu of 1438. Once again, I really have no idea how these are both getting determined and then set. If I change the home node's mtu to 1438 to match the exit server, all of a sudden there are no more issues getting ssh connections across the link.
I know that we can figure out what the hell tunneldigger is doing if we go over the code thoroughly enough. Considering it's such an integral part of our project at the moment, I think we may have to just bite that bullet... @papazoga - sound fun? :P
Ok the broker is getting an mtu set in the up_hook which looks like we've statically assigned it. That was dumb. I think I've fixed it with this in the exit node.... https://github.com/sudomesh/exitnode/commit/0d3ef9606f8b89afd5bbe15c3462b41434020e4a
This looks fixed, and I've added an issue to the exit-node repo to add a script for any mtu changed hook.
I'll attach a pcap of me, wireless connected to the 'open2' interface ("peoplesopen.net"), doing a bit of web browsing successfully and then failing to be able to ssh to any servers, both mesh and off the mesh.
Here are the configs from a TP-link wdr4300 which is on the most current firmware/makenode code (as of 7/27/2015), and then below I'll post a set of configs from another of the same device that's running some older code that does seem to be working:
A couple weird things: