In the 1st post he's setup the Zyxel LAN as 192.168.1.1 on the default interface.
That means the web interface is reachable on 192.168.1.1
It has a 2nd bridge interface which is 192.168.2.1 by default.
I've never changed the bridge interface and it has always worked.
I always setup my Zyxel LAN to 192.168.1.1
I left the Zyxel bridge as 192.168.2.1
My Asus LAN was 192.168.1.2 with its DHCP at 192.168.1.10 - 192.168.1.253
That's how probably a dozen or more users on these forums have set it up.
The OP appears to have done similar.
No idea why it isn't working but I would be tempted to factory reset both devices and start over. It shouldn't be this difficult.
Physical wiring/connections maybe?
How many cables do you have in your modem and what port(s) do they plug into on your router?
And which port/connection is configured in your custom bridge interface?
The instructions that are linked (
https://kitz.co.uk/routers/zyxel_VMG8324-B10A_bridge.htm) look slightly flawed to me...
2. Connecting the two devicesShows Modem-Lan4 connected to Router-WAN
but then
5. Getting line stats from the Modem when in Bridged Modeshows Modem-Lan1 connected to 2nd Router-WAN (which implies to me that the modem is acting as a router too???)
and Modem-Lan4
now connected to 2nd Router-Lan port
and in the final section
Configure VMG8324 access from the LAN to get line statsit is not clear to me if you require both ethernet cables to remain in place?
It goes on to configure MODEM-Lan1 as the bridge port - does this mean the Lan1 that is connected to the routers WAN port? I really dont know! I suspect it means the MODEM-Lan port that is connected to the Router-Lan... not the WAN connection? but who knows?
I just quickly tried to follow these instructions using just a single cable between Modem and Router and it did not seem possible to me. The interface on my router has absolutely no way to communicate to the custom bridge on 192.168.2.1... the routers WAN port is, for all intents and purposes connected to the internet via the modem... it has to have an external IP in order to get the internet.
I was able to fudge something together using 2 cables... but that seems silly... why duplicate cables?
My modem is on 192.168.1.1 - even in bridged mode, if I plug into any of the LAN ports it will serve up a 192.168.1.x address to any DHCP client and allow me to use the GUI.
In my router setup (router is 192.168.0.1) I have 2 interfaces on the WAN port... 1 is the default/normal PPPoE interface that receives an external IP address from my ISP and the other I just gave a static IP in the modems range (192.168.1.2). Now anything that plugs into the router (will receive a 192.168.0.x IP) can see 192.168.1.1.
And the only way I can see everything on the same subnet
just working without any messing about as Jaydub seems to suggest is if you do
not use the WAN port on the router - but I suspect this will then be double NATed?
As it is, if your modem is in bridged mode then your modem is not NATing - it is simply bridging!
Your problem is that you need a routing device to exist on both subnets, in order to route your requests for the GUI from one subnet to the other.
The linked instructions appear to be trying to do this subnet-routing on the modem - which seems logically to be the wrong place... I would have my router doing all of my routing... indeed, I want my modem to do nothing more than be a modem!
You can always just plugin to the modem when you need to see stats!!