Connect to vlan2 on wan port ? (solved)

[g1dtf]

I have a vdsl modem with a management interface on vlan2 (192.168.1.250). I can access the interface via a PC connected directly to the modems single LAN port but dont know how to config my N66U (Rmerlin 374.43_2) to access the interface via the N66U when the modem is connected to its WAN port and supplying the vdsl connection and the PC connected to one of the 4 LAN ports. The N66U is in default config with a LAN IP of 192.168.1.1.

Switch: enabled gigabit
Port 0: 100FD enabled stp: none vlan: 2 jumbo: off mac: 10:e8:78:a7:93:11
Port 1: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 1c:87:2c:44:32:ab
Port 2: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 3: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 0c:f9:c0:31:6c:f0
Port 4: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 8: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 50:46:5d:6d:41:78
VLANs: BCM53115 enabled mac_check mac_hash
1: vlan1: 1 2 3 4 8t
2: vlan2: 0 8u


eth0 Link encap:Ethernet HWaddr 50:46:5D:6D:41:78
inet addr:169.254.248.181 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1508 Metric:1
RX packets:28564357 errors:0 dropped:0 overruns:0 frame:0
TX packets:28396142 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:972103020 (927.0 MiB) TX bytes:242679946 (231.4 MiB)
Interrupt:4 Base address:0x2000

eth1 Link encap:Ethernet HWaddr 50:46:5D:6D:41:78
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19002779 errors:0 dropped:0 overruns:0 frame:2891365
TX packets:17983309 errors:43 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:691450887 (659.4 MiB) TX bytes:2263032560 (2.1 GiB)
Interrupt:3 Base address:0x8000
eth2 Link encap:Ethernet HWaddr 50:46:5D:6D:41:7C
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1475587 errors:0 dropped:0 overruns:0 frame:2290312
TX packets:4414299 errors:9 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:190318483 (181.5 MiB) TX bytes:4283807740 (3.9 GiB)
Interrupt:5 Base address:0x8000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:102392 errors:0 dropped:0 overruns:0 frame:0
TX packets:102392 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10637030 (10.1 MiB) TX bytes:10637030 (10.1 MiB)
ppp0 Link encapoint-to-Point Protocol
inet addr:80.229.2.124 P-t-P:195.166.130.250 Mask:255.255.255.255
UP POINTOPOINT RUNNING MULTICAST MTU:1492 Metric:1
RX packets:24302079 errors:0 dropped:0 overruns:0 frame:0
TX packets:22218011 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:3982658246 (3.7 GiB) TX bytes:1247003816 (1.1 GiB)
vlan1 Link encap:Ethernet HWaddr 50:46:5D:6D:41:78
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:4167639 errors:0 dropped:0 overruns:0 frame:0
TX packets:6094259 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:927167837 (884.2 MiB) TX bytes:3303123033 (3.0 GiB)

I'm hoping its just a config issue that is blocking my connection to the vlan2 interface when going via the N66U.

 

[g1dtf]

From what I have read from various sources the Lan and Wan interfaces are spit internally on the N66 to vlan1 for LAN and vlan2 for WAN and hence the vlan1 1 2 3 4 8t and vlan2 0 8u config settings. It may therefor be better to try to change the management interface on the modem from vlan2 to vlan20 or something similar. It may be due to how the router handles vlan2 internally that I cannot access the vlan2 tagged management interface on the modem via the WAN port on the N66U. Does anyone know what the consequences would be in altering the vlan2 0 8u setting to vlan2 0t 8u or vlan2 0t 8t as I dont want to mess too much and lose my internet connection due to messed up WAN settings.

 

[coldwizard]

I have a vdsl modem with a management interface on vlan2 (192.168.1.250). I can access the interface via a PC connected directly to the modems single LAN port but dont know how to config my N66U (Rmerlin 374.43_2) to access the interface via the N66U when the modem is connected to its WAN port and supplying the vdsl connection and the PC connected to one of the 4 LAN ports. The N66U is in default config with a LAN IP of 192.168.1.1.


I'm hoping its just a config issue that is blocking my connection to the vlan2 interface when going via the N66U.

Your problem is using the same network for the management interface on vdsl modem and the LAN on the N66U (both on 192.168.1.x). Change the LAN network on the N66U to something else like 192.168.9.1

 

[g1dtf]

Your problem is using the same network for the management interface on vdsl modem and the LAN on the N66U (both on 192.168.1.x). Change the LAN network on the N66U to something else like 192.168.9.1

Will the PC connected to the LAN port need to be Vlan aware (set to vlan2) or will it be utagged on the Lan ports. I did initially have the modem set to 172.16.2.250 but again got no access to it via the N66.

 

[ColinTaylor]

What is the make and model number of your VDSL modem?

You keep talking about VLAN 2 on the modem. Can the VLAN requirement be disabled?

 

[g1dtf]

Its Netgear DM200 flashed with OpenWRT and set as a transparent vdsl2 bridge. Whilst in bridge mode it has been programmed to allow access to the management console on vlan2 (eth0.2). Its working great as a modem but I am struggling to get a config that allows me to access the console via the N66U to get line stats etc. Hope this explains a little what I am trying to do.

 

[ColinTaylor]

OK It looks like you posted the same question in the OpenWRT forum. So I'll wait to see what happens there.

 

[g1dtf]

I posted here as its probably a config issue on the N66U (Rmerlin) and not the OpenWRT on the DM500 as I can connect to the management interface from a PC connected directly to the DM500 Lan port but not via the N66U.

 

[g1dtf]

Can anyone explain what the difference would be between vlan20 0t 8u and vlan20 0t 8t with regards to tagging. My aim is to connect to a tagged vlan20 on the wan port with an untagged device on the network if thats possible.

 

[coldwizard]

Will the PC connected to the LAN port need to be Vlan aware (set to vlan2) or will it be utagged on the Lan ports. I did initially have the modem set to 172.16.2.250 but again got no access to it via the N66.

The reason the two networks must be different is how routing is handled. If the PC thinks the address is on the local network, it sends a ARP broadcast on the local network for the device, no reply means device is offline. If the PC thinks the address is on a different network, it forwards the traffic to the gateway router (the N66).

I have no good ideas about the second problem, why the N66 is not passing the traffic to the modem.
Did you do something to make the PC vlan aware when connected directly to the modem? Look at any difference between routing tables "netstat -rn" on the PC connected to the modem and on the N66 router itself.

 

[g1dtf]

The vlan20 IP on the DM500 modem i am trying to connect to on the WAN port is now 192.168.5.1. These are the commands I have used .

robocfg vlan 20 ports "0t 8t"
vconfig add eth 0 20
ifconfig vlan20 192.168.5.254 netmask 255.255.255.0 up

I can now ping the modem on 192.168.5.1 using the above settings but I cannot get anything from http://192.168.5.1/cgi-bin/luci. A tracert to 192.168.5.1 stops at 192.168.1.1 (the N66U IP)
This is my current ifconfig.

ASUSWRT-Merlin RT-N66U_3.0.0.4 Sun Aug 6 00:10:38 UTC 2017
admin@RT-N66U-4178:/tmp/home/root# ifconfig
br0 Link encap:Ethernet HWaddr 50:46:5D:6D:41:78
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22235 errors:0 dropped:0 overruns:0 frame:0
TX packets:8412 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4584210 (4.3 MiB) TX bytes:1622017 (1.5 MiB)

eth0 Link encap:Ethernet HWaddr 50:46:5D:6D:41:78
inet addr:169.254.248.181 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1108742 errors:0 dropped:0 overruns:0 frame:0
TX packets:1141313 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1319115785 (1.2 GiB) TX bytes:1421045407 (1.3 GiB)
Interrupt:4 Base address:0x2000

eth1 Link encap:Ethernet HWaddr 50:46:5D:6D:41:78
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:171704 errors:0 dropped:0 overruns:0 frame:20936
TX packets:136407 errors:2 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:137046368 (130.6 MiB) TX bytes:17618957 (16.8 MiB)
Interrupt:3 Base address:0x8000

eth2 Link encap:Ethernet HWaddr 50:46:5D:6D:41:7C
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8519 errors:0 dropped:0 overruns:0 frame:94588
TX packets:27049 errors:2 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1153989 (1.0 MiB) TX bytes:17628293 (16.8 MiB)
Interrupt:5 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:974 errors:0 dropped:0 overruns:0 frame:0
TX packets:974 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:104287 (101.8 KiB) TX bytes:104287 (101.8 KiB)

ppp0 Link encapoint-to-Point Protocol
inet addr:80.229.2.124 P-t-P:195.166.130.252 Mask:255.255.255.255
UP POINTOPOINT RUNNING MULTICAST MTU:1492 Metric:1
RX packets:43791 errors:0 dropped:0 overruns:0 frame:0
TX packets:57266 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:11305233 (10.7 MiB) TX bytes:42756060 (40.7 MiB)

vlan1 Link encap:Ethernet HWaddr 50:46:5D:6D:41:78
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:127088 errors:0 dropped:0 overruns:0 frame:0
TX packets:859630 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15593201 (14.8 MiB) TX bytes:1275998234 (1.1 GiB)

vlan20 Link encap:Ethernet HWaddr 50:46:5D:6D:41:78
inet addr:192.168.5.254 Bcast:192.168.5.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Do i also need to setup a bridge interface for it with brctl

 

[g1dtf]

It seems I now cannot ping the modem on 192.168.5.1 but can ping the vlan20 ip 192.168.5.254

 

[g1dtf]

I have finally found a config that works. The management interface of the DM200 is now set to vlan20 with an IP of 192.168.1.250. The N66U is set to 192.168.1.1 and I issued rthe folloing commands to setup vlan 20 on its WAN port.

robocfg vlan 20 ports "0t 8t"
vconfig add eth0 20
ifconfig vlan20 up
brctl addif br0 vlan20

I can now access the management interface of the DM200 modem fron any connected device by using "http://192.168.1.250/cgi-bin/luci. I now need to find out how to make the settings persist a reboot for which I think I need a script.

Thanks everyone for your input and I will open another thread with regards to making the vlan settings persist as it is not just relevent to this individual setup issue and any answers may help others who need help with scripts.