Thanks for taking a look.
Eeeps said,
Quote:
|
The netmask that Virgin is providing looks wrong and this causes your router to believe it can access that website directly without going via Virgins gateway at 81.109.124.1.
|
My apologies, but this may be a result of cut'n'paste gathering over a few days. A fresh set today shows the net mask to be in the same block as the Wan IP, which I think is where it should be and may have caused confusion.
A release and renew on my router returns with the same settings and the tracert fails at the same point.
WAN IP 81.110.180.82
Subnet Mask 255.0.0.0
Gateway 81.110.180.1
Static Routing Table,
Destination IP Subnet Mask Gateway Metric Interface
192.168.0.0 255.255.255.0 0.0.0.0 0 br0
81.0.0.0 255.0.0.0 0.0.0.0 0 eth2.2
0.0.0.0 0.0.0.0 81.110.180.1 1 eth2.2
Tracing route to
www.barco.com [81.247.254.134]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 cpc69054-oxfd25-2-0-cust81.4-3.cable.virginm.net [81.110.180.82] reports:
Destination host unreachable.
Trace complete.
Switching the Superhub to router mode obviously gives a different Wan IP, though still an 81.xx, but I can see no similar net mask info in the extensive advanced settings page on the Superhub. And of course I can reach the site.
General Maximus,
Quote:
|
The interesting thing is that even though you say it works fine in router mode, it is in router mode that your trace route fails.
|
Just to be clear, it works with the Superhub in router mode, but not in modem mode with my router as well.