2 Jun
2017
2 Jun
'17
9:09 p.m.
What's happening is that your route is moving to the next one in the
routing table. Now all I have to do is find out why!
It would be helpful to know if ALL your traffic switches to the other
person's address, or whether you still get some traffic for your proper
subnet. There are two routing tables, one indexed by individual address
and one indexed by subnet, and knowing which is being mis-indexed would
help me find the problem.
In the meantime, I've restarted the daemon and you should be good again.
- Brian
On Fri, Jun 02, 2017 at 09:46:29AM -0400, lleachii--- via 44Net wrote:
Brian,
Yep, debugging may be necessary, I'm receiving someone else's traffic again:
2017-06-02 08:04:44.392 0.000 TCP 1.34.202.215:24351 ->
44.62.1.81:16165 1 552 1
2017-06-02 08:05:49.494 0.000 TCP 195.88.209.24:41058 ->
44.62.1.81:3388 1 40 1
- Lynwood
KB3VWG
I restarted the ipip daemon and they went away.
Looks like it's time to debug the routing table maintenance routing.
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net