7 Aug
2015
7 Aug
'15
9:30 a.m.
TNX Nigel for the news! It seems that no error and no loss
are registered... however the tracks for ir0rm-7.ampr.org
stops at ucsd.edu.
This means that my host is not reachable?
gus
Traceroute from Seattle-SRV1.HamWAN.net
Source IP address is 44.24.241.98.
Use DNS
Hostname Loss Received Sent Min Avg Max
0 Resolver error: No error returned but no answers given. Resolver
error: No error returned but no answers given. 3 209.189.201.199 0 1 1 1
1 1
1 switch.seattle-er1.hamwan.net 0.00% 166 166 0 0 1
2 209.189.196.65 0.00% 166 166 0 1 2
3 ge0-0-0-0-thbr06.threshinc.net 0.00% 166 166 0 1 3
4 six.llnw.net 0.00% 166 166 0 2 15
5 tge2-2.fr3.sjc.llnw.net 0.00% 166 166 18 19 38
6 ve5.fr4.sjc.llnw.net 0.00% 166 166 18 24 33
8 dc-svl-agg4--paix-px1-10g.cenic.net 0.00% 165 165 20 20 23
9 dc-lax-agg6--svl-agg4-100ge.cenic.net 0.00% 165 165 27 28 29
10 dc-riv-agg4--lax-agg6-100ge.cenic.net 0.00% 165 165 32 32 34
11 dc-sdg-agg4--riv-agg4-10ge.cenic.net 0.00% 165 165 40 40 41
12 dc-ucsd-1--sdg-agg4.cenic.net 0.00% 165 165 39 40 65
13 nodem-core--mx0-30ge.ucsd.edu 0.00% 165 165 40 54 273
14 ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu
0.00% 165 165 40 40 53
On 08/07/2015 04:03 PM, Nigel Vander Houwen wrote:
(Please trim inclusions from previous messages)
_______________________________________________
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
>