I have installed the a1comms (imacarpet) transparent bridge firmware on my Netgear DM200. The bridge is working great with my Asus N66U router but cannot seem to work out how to access the management interface which is on VLAN2. The network config is. -
I have tried connecting a PC directly to the DM200 with the IP set to 172.16.2.254 but get no response using http://172.16.2.250. I am looking for help in how to config the PC or the N66U to allow me to access the management interface which should be on VLAN2 with an IP of 172.16.2.250.
Without a switch between the two, I’d approach it by changing your OpenWrt switch config to not use VLAN 2 as it does now (changing it to VLAN 10 or something), then adding a VLAN 2 interface on the management subnet (tagged on the switch port the other device is attached to). Then you can use ssh to port forward.
Edit: looks like you’ve got some of that already. Forwarding can be challenging if you can’t install static routes on the upstream device. Seeing your switch config would help.
I suggest not to change the LAN IP, but to follow @jeff's advice instead: add a VLAN2 management interface on the Asus N66U after getting rid of any previous use of VLAN2.
Cant change any config on the DM200 whilst its in bridge mode as I have no access which is why I am trying to config the N66U to access the management interface on it thats been setup as default on VLAN2 with the config I first posted. I will start by changing the current default setting I posted to vlan2: 0t 8t on the N66U. As I have never used VLAN I should not have any previous use of VLAN2. The Lan IP of the N66U is currently set to 192.168.1.1 with all connected devices on 192.168.1.x.
You are using VLANs, even if you haven't configured them. Switches use VLANs internally to segregate ("wire") traffic. It looks like Merlin, like OpenWrt, uses VLAN 1 and VLAN 2 in the switch for LAN vs. WAN traffic. If you want to use VLAN 2 for another purpose, you'll need to change that configuration.
I also don't see any VLAN 2 interface on your Asus router, nor any interface with 172.16.2.250 assigned. The self-assigned 169.254.248.181 on eth0 is puzzling, though I don't know how Merlin handles its interfaces.
I dont know if this will help at all but this is a segment of the readme.md from the github firmware that I built and installed on the DM200.
This firmware when built and flashed to the Netgear DM200, will make it operate in a transparent bridge mode, where it will auto-configure to either ADSL or VDSL, depending on what is detected on the line.
Networking Setup
The internet connection from the ISP is always bridged directly to the ethernet port, untagged (you don't need to specify VLAN 101 for FTTC, this is handled internally), allowing you to do PPPoE or just DHCP directly on your ethernet router, depending on the connection type from your ISP.
Management Interface (VLAN 2)
As well as the connection bridge, we also expose a management network on VLAN 2, allowing you to access connection status, or manage the modem (SSH, Luci, firmware flash, etc).
Modem network settings for VLAN 2 :
IP Address: 172.16.2.250
Network Mask: 255.255.255.0
Expected router IP: 172.16.2.254
Services exposed:
SSH (port 22): root@172.16.2.250
Web:
Status Overview page: http://172.16.2.250/
Status JSON feed: http://172.16.2.250/cgi-bin/luci/a1comms/status/json
Luci Web Admin Panel: http://172.16.2.250/cgi-bin/luci
A drawing of your connections would help, as would a link to the firmware that you've installed. Right now I am very confused as to where you expect there to be the 172.16 address and fromwhere you expect to be able to access it.
The firmware was built from the following github page.
Basically I have the DM200 modem setup with the above firmware as a Transparent vdsl bridge connected to my line and Its single Lan port connected to the WAN port on the N66U. All devices are then either wired to the N66U lan ports or wireless and currently all set to 192.168.1.x range. My next test will be to alter the router and connected devices to 172.16.2.x range to see what happens when I try to access the DM200 management interface on 172.16.2.250.
When I tried the direct connection from DM200 to PC I did not have any settings on the PC to access a tagged Vlan as not exactly sure how to do it. I have not as yet submitted anything to github as thought its most probably just my setup being a newbie to rthis and not really an issue with the firmware.
My laptop had the Vlan setting in its drivers and I managed to get that to connect to the DM200 management interface on Vlan2 so all that remains now is to try and get a config that allows a connection via the N66U.
but that assumes that eth0 is a real interface not connected to the wan port via the switch. I also added that interface into the firewall zone containing wan.
Most of the time this works....