Accessing the config page

[Leonichol]

Hi All,

I have used VM for the past two years at two addresses (20mb Ambits), and at both I have had the same problem - as soon as I connect the supplied Netgear router, I can no longer access the modem config page. Internet access and such remains fine.

When I connect a system directly to the modem, I can once again view the page at http://192.168.100.1. This is the case with the Netgear at complete factory settings.

Anyone got any ideas?

Thanks.

[bomber_g]

It's because the modem is acting in bridged mode

you'll probably find that if you disconnect the coax, you'll still be able to log into the modem from behind your router.

the question really is - Why would you want to log into your modem in the first place?

[Leonichol]

Then how do other people access it from behind their routers?

Taking the coax out would defeat the purpose - I wish to monitor signal levels. Can't really do that without a coax!

[Jon T]

What are you using for the IP range on your LAN? (drop to a command promt, type "ipconfig"(no quotes), tell us what you get for ip address, subnet mask and default gateway.

When you request the modem's diagnostics/config page, the bridge sniffs it's own address and rather than passing them on to the UBR it responds itself.

So for some reason i think your likely to have an IP range conflict, the cable modem doesn't seem to be receiving the request for http://192.168.100.1



..................Standing by to be corrected by Broadbandings though!

[Ignitionnet]

Nothing to correct Jon!

[Jon T]

Originally Posted by Broadbandings

Nothing to correct Jon!

Thanks, didn't think so, but I didn't know if anything had changed from how it used to be.

[Leonichol]

Currently in the 192.168.2.x range - with devices littered all over it.

Nothing running in .1.x;

Originally Posted by Output from a slightly more sophisticated router

eth0 Link encap:Ethernet HWaddr 00:xx:xx:xx:xx:xx
inet addr:86.13.xx.xx Bcast:255.255.255.255 Mask:255.255.252.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:27235332 errors:0 dropped:0 overruns:0 frame:0
TX packets:16719275 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1713444697 (1634.0 Mb) TX bytes:1290107203 (1230.3 Mb)
Interrupt:12 Base address:0x8000

eth1 Link encap:Ethernet HWaddr 00:xx:xx:xx:xx:xx
inet addr:192.168.2.1 Bcast:192.168.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16773473 errors:0 dropped:0 overruns:0 frame:0
TX packets:26433808 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1299459513 (1239.2 Mb) TX bytes:425209536 (405.5 Mb)
Interrupt:5 Base address:0xc400

Originally Posted by Windows client

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : xx
Link-local IPv6 Address . . . . . : fe80::4c3c:18a0:f21:a40e%12
IPv4 Address. . . . . . . . . . . : 192.168.2.3
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.2.1

[Jon T]

Your using a 255.255.0.0 subnet, this is going to stop the 192.168.100.1 request being passed through to the router.

Basically by using a 255.255.0.0 subnet, your telling the router that the first two octets of the IP address intentify the network, and the last two describe hosts on your network. In your case, when you call up 192.168.100.1, your router is not passing the request on to it's WAN port because it thinks the device is on the LAN side of your network.

[Leonichol]

For peets sake, can't believe I didn't spot that - even after staring at the routing table for an hour!

Cheers Jon