Iburst to Iburst problems

[Leno]

Every now and again i cannot access my other iburst connection, pings time out and traceroutes dont make it... Both connections can access internet fine...

Tracing route to xxx.ath.cx [196.2.114.xx]
over a maximum of 30 hops:

1 89 ms 83 ms 63 ms wbs-196-2-100-1.wbs.co.za [196.2.100.1]
2 106 ms 87 ms 78 ms 192.168.0.97
3 101 ms 85 ms 88 ms 192.168.0.104
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.

Private range ip's being used on backbone??? Come on...!

 

[riverdusty]

Yes, We do not try explain how iBurst network is setup. They're probably too cheep to buy their own block of IPs so they've got us on some local system piggy backing on some bigger ISP (explains the weird MTU).
You'll find that someones router is probably blocking your pings along the way. It'll be something silly like that.
You could try set up some sort of dynamic DNS on both systems so that the request to find each system leaves the iburst local network 'thing' they've got going to find each other. I do that with my iBurst's and it works for me. I use no-ip.

 

[OoMk0o5i3]

I had a case where the my packets got "trapped" between 2 ip's and just hopping between them until the TTL was zero. iBurst have some serious routing issues...

 

[Leno]

Yes, We do not try explain how iBurst network is setup. They're probably too cheep to buy their own block of IPs so they've got us on some local system piggy backing on some bigger ISP (explains the weird MTU).
You'll find that someones router is probably blocking your pings along the way. It'll be something silly like that.
You could try set up some sort of dynamic DNS on both systems so that the request to find each system leaves the iburst local network 'thing' they've got going to find each other. I do that with my iBurst's and it works for me. I use no-ip.

I do have dynamic dns (hence the .ath.cx host name)

Still nothing today, I can vnc now, but nothing else.... (port blocking or some nat?)

Have double checked my linksys, but i can access fine on 3g and from oversea's

Has anyone tried to report issues like routing to their support desk, i normally get a blank responce from help desks on these type of problems...

 

[who.is.michael]

I do have dynamic dns (hence the .ath.cx host name)

Still nothing today, I can vnc now, but nothing else.... (port blocking or some nat?)

Have double checked my linksys, but i can access fine on 3g and from oversea's

Has anyone tried to report issues like routing to their support desk, i normally get a blank responce from help desks on these type of problems...

Hi Leno

Not sure if this will be of help to you - my issue was resolved when I changed the recommended MTU of 1352 to the default 1942.

Regards


M