OpenWRT VLAN ID for VDSL

SauRoNZA

SauRoNZA

Honorary Master
Joined
Jul 6, 2010
Messages
61,473
Reaction score
23,199
Location
Cape Town
So Telkom quietly switched me to VDSL this evening and didn't tell me about it and then everything fell apart when I couldn't PPPoE even though I could sync just fine.

I have this setup...

Technicolor TG589 (Mweb Unlocked) as Modem >>>> OpenWRT Router + Access Point (does PPPoE) >>>> LAN

Now resetting the Technicolor and then populating the VLAN ID 835 eventually sorted out the connection directly from the Modem...but it's a terribly **** router so I would like to use it as nothing more than a Bridged Modem.

But for the life of me I cannot figured out how to implement the VLAN ID 835 on the WAN Interface of the OpenWRT.

Has anyone done this in SA by any chance? Every config I see online seems to be doing something very different for different reasons.
 
You should be able to go to the "Switch" menu under "Network", then change the VLAN ID of the WAN port (often port 0, it is with my 1043ND) from 2 (my wan interface is eth0.2) to 835 (this should likely change the interface name to eth0.835, I guess), then set the dropdown for that VLAN/port to "Tagged", so that any packets leaving this interface will be tagged with the 835 VLAN id (and have the vlan header stripped for any packets entering the router via that interface).

This *should* work, I think. Take a backup first, though!
 
That's just the problem I'm having...the WAN port doesn't show up on the Switch list at all only the local LAN stuff.

So I ended up messing around in the manual terminal configuration but now actually just reset it back to the TP-Link firmware to see if I can make that work so long.

One would think the VLAN ID should be added on the actual modem, much like ATM settings normally are.
 
Mmmm, I'm honestly not sure how the VLAN's would work across the VDSL modem.

Can you tell me what model of router you are using for OpenWRT? It might be the case that you have two independent network interfaces on the CPU, with WAN attached to one, and a switch chip attached to the other for LAN, rather than a single network interface connected to a switch chip, with the WAN being on a VLAN.

If this is the case, I believe that you should still be able to configure a VLAN on the WAN interface, it will just be done differently.
 
Thanks Rogan.

It's the TP-Link N600 (WDR-3500).

But I just gave up now and simply had the bloody Mweb Router dial the PPPoE connection and then assign the WAN IP directly to the TP-Link behind it so it can still do the Routing without any Double NAT dramas.

Maybe I'll have more energy for it later, or break out my Mikrotik again.
 
Bah that seemed like a good solution except that even though it assigns the WAN IP to the OpenWRT Router it intercepts it and SSH goes to the Technicolor instead.

I wonder if I can just disable NAT completely on the piece of ****.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X