7 Aug
2015
7 Aug
'15
10:03 a.m.
All,
For your information, my colleague Tom was kind enough to write a tool that should let you
run traceroutes from our network. If you can’t reach us via 44-net, you’ll obviously need
to access via public internet.
http://trace.hamwan.net/ <http://trace.hamwan.net/>
Feel free to use it to test if you’re reachable from BGP announced subnets like ours.
Nigel
K7NVH
> On Aug 7, 2015, at 06:51, lleachii--- via 44Net <44net(a)hamradio.ucsd.edu>
wrote:
>
> (Please trim inclusions from previous messages)
> _______________________________________________
>
> Gus,
>
> I had errors and collisions before I reviewed my configuration. Now that's
everything properly configured, I don't see them.
>
> It may be helpful to note the only TWO reasons the collision and error count
increases on a tunnel interface:
>
>
>
> If the next hop of the encapsulated packet is the same tunnel interface: ipip.c line
437.
>
> If the path MTU of the next hop for the encapsulated packet is less than 68:ipip.c
line 447.
>
>
>
>
> - Lynwood
>
>
>
> -----Original Message-----
> note that (I'm not aware why) on the tunl0 interface there are
> many errors/collisions on the TX tunnel side.
>
>
>