CHaynes112
Occasional Visitor
ISP Modem - Arris NVG448BQ
Router - ASUS GT-AC5300
This setup is running in bridge mode. Previously, I had ADSL2+ and was able to access the Arris modem from behind the ASUS router by entering this command:
ifconfig eth0:0 192.168.254.253 netmask 255.255.255.0
It created a subinterface for eth0 (the WAN port) and assigned it an IP address on the modem subnet. Recently, I upgraded to VDSL2. It took a little while to get bridge mode working as I was unaware that Frontier VDSL2 required VLAN tagging. Once I set the WAN VID to 101, I was able to get bridge mode working again. However, now that the VLAN tag is in the mix, I can no longer access my modem. I assume the basic fuctionality is still there, but I probably need to slightly modify the command mentioned above. The ASUS routing table does show a VLAN101 now. I tried the following commands without any luck...
ifconfig eth0:1 192.168.254.253 netmask 255.255.255.0
ifconfig eth0:101 192.168.254.253 netmask 255.255.255.0
ifconfig vlan101 192.168.254.253 netmask 255.255.255.0
ifconfig vlan101:0 192.168.254.253 netmask 255.255.255.0
I just now noticed that the VLAN101 route shows the MAN interface (as opposed to the WAN interface).
I'm hoping that someone has some suggestions?
Thanks
Router - ASUS GT-AC5300
This setup is running in bridge mode. Previously, I had ADSL2+ and was able to access the Arris modem from behind the ASUS router by entering this command:
ifconfig eth0:0 192.168.254.253 netmask 255.255.255.0
It created a subinterface for eth0 (the WAN port) and assigned it an IP address on the modem subnet. Recently, I upgraded to VDSL2. It took a little while to get bridge mode working as I was unaware that Frontier VDSL2 required VLAN tagging. Once I set the WAN VID to 101, I was able to get bridge mode working again. However, now that the VLAN tag is in the mix, I can no longer access my modem. I assume the basic fuctionality is still there, but I probably need to slightly modify the command mentioned above. The ASUS routing table does show a VLAN101 now. I tried the following commands without any luck...
ifconfig eth0:1 192.168.254.253 netmask 255.255.255.0
ifconfig eth0:101 192.168.254.253 netmask 255.255.255.0
ifconfig vlan101 192.168.254.253 netmask 255.255.255.0
ifconfig vlan101:0 192.168.254.253 netmask 255.255.255.0
I just now noticed that the VLAN101 route shows the MAN interface (as opposed to the WAN interface).
I'm hoping that someone has some suggestions?
Thanks