[MLB-WIRELESS] Strange routing issues on 10.10.129.64/28 (GHO-North-5.8/HVC??)

[David Nuttall]

Hi Robert,

Things are going OK till you get to JLP at Heidelberg.  (10.10.81.33 is 
the incoming interface from Box Hill)

After that is where it goes bad.

If it goes direct to GHO (10.10.80.5) all is good.
If it goes via HVC (10.10.2.225) it gets lost.

1)  Looking at OSPF at JLP right now, it wants to send traffic to 
10.10.129.64/28 via HVC with a cost of 20!  There is a cost of 10 from 
JLP to HVC.  That suggests 10.10.129.64/28 is directly connected to HVC 
with a cost of 10 on it's interface.

2)  I pinged all of the addresses in 10.10.129.64/28 from JLP and a 
response came back from 10.10.129.70 on the HVC interface.  Time was 1 mS.

3)  So it looks like you are right, 10.10.129.64/28 is on both HVC and GHO.

4)  A couple of guesses....  Maybe an attempt to directly link HVC with 
GHO after JIA died?  Maybe JIA was bridging HVC and GHO?  Someone will know!

Dave.


On 5/03/2012 11:39 AM, Robert Haines wrote:
> Hi Andrew,
>
> We're using the Ubiquiti's basic internal router at present (WIFI as 
> WAN and LAN as internal network). We've tried it as a strait station 
> with identical results.
>
> I think it has something to do with 10.10.129.70, an interface on the 
> HVC node which isn't connected to the network it should be (a 
> duplicate subnet...??) I don't know, I am unable to troubleshoot this 
> any further from where I am.
>
> The best I can come up with is this:
>
> --------------
>
> This is what it looks like when it is working....
>
> (from my place - KPK 10.10.96.123)
>
> Tracing route to 10.10.129.69 over a maximum of 30 hops
>
>   1 <1 ms <1 ms <1 ms  xxx.xxx.xxx.xxx
>
>   2     4 ms     7 ms     2 ms  10.10.96.113
>
>   3     6 ms     8 ms     4 ms  10.10.97.49
>
>   4     6 ms    16 ms     8 ms  10.10.97.68
>
>   5    12 ms    17 ms     7 ms  10.10.81.33
>
>   6    14 ms    10 ms    28 ms  10.10.80.5
>
>   7    15 ms    23 ms    14 ms  10.10.131.66
>
>   8    12 ms    13 ms    15 ms  10.10.129.69
>
>  Trace complete.
>
>  --------------
>
> This is what it looks like when it is not....
>
> tracert 10.10.129.69
>
> Tracing route to 10.10.129.69 over a maximum of 30 hops
>
>    1 <1 ms <1 ms <1 ms  xxx.xxx.xxx.xxx
>
>   2     7 ms     9 ms    18 ms  10.10.96.113
>
>   3     6 ms     4 ms     3 ms  10.10.97.49
>
>   4     6 ms    14 ms    15 ms  10.10.97.68
>
>   5    14 ms    12 ms    11 ms  10.10.81.33
>
>   6    12 ms    10 ms    14 ms  10.10.2.225
>
>   7  10.10.2.225  reports: Destination host unreachable.
>
> Trace complete.
>
> -------
>
> Rob.
>
>
> _______________________________________________
> Melbwireless mailing list
> Melbwireless at lists.wireless.org.au
> http://lists.wireless.org.au/mailman/listinfo/melbwireless
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wireless.org.au/pipermail/melbwireless/attachments/20120306/df2eb928/attachment.html>