PODA fiber optics or VDSL support (PPPoE over VLAN)

NethSecurity
1

Czech providers of PODA fiber optics internet or VDSL internet (similar in Germany) provide connectivity with PPPoE over a VLAN.

This is not supported out of the box in the web UI in Nethsecurity and has to be manually configured over uci or editing the config files. (Add a VLAN and use the VLAN for WAN with PPPoE instead of the eth1)

The result of manually configuring is here:

image
image1559Ă—838 80 KB

Would be nice to support this very common option (PPPoE over a VLAN for WAN connectivity) out of the box.
Just in Czech republic are 4.2 million households/connections with this setup.

1 Like
2

It’s totally possible to configure a PPPoE over VLAN: I did it on my firewall last week.

Follow this steps:

  1. Create the VLAN device: Network interfaces — NethSecurity documentation
  2. Configure a PPPoE WAN on it
3 Likes
3

My company also provides me with free FTTH connectivity with VLAN tagging, so I’m very familiar with this setup.

I can confirm that configuring PPPoE over VLAN on NethSecurity is absolutely possible and, as pointed out by Giacomo Sanchietti, it can be done directly from the GUI in about 2 minutes — no need to manually edit UCI settings or configuration files.

It’s a straightforward procedure, fully supported from the web interface, and works perfectly for FTTH deployments using VLAN tagging like the one described.

1 Like
4

Spotted with blindness…

I’m familiar with creating a VLAN in the Nethsecurity UI.

but howto change the wan from ethx to the vlan?

I also know the PPPoE part in the wan setting.

5

didn’t find the wan setting to the vlan in Firewall - Zones and policies.

neither in Network - Interfaces and devices.

I’m used to the OpenWRT way to get it done, maybe I’m making something wrong.

  1. Create VLAN - OK

how? :slight_smile:

I know how to configure PPPoE on the default WAN which is the network interface without the vlan…

6

I can’t upload a screencast.

  1. Create a VLAN (Click on the “Create VLAN device” button on top of the page)

image
image551Ă—514 15.4 KB

  1. Click on “Configure”

image
image1605Ă—132 8.34 KB

  1. Choose a name for the interface, select “WAN” as Zone, select “PPPoE” as protocol, enter PPPoE credentials

image
image537Ă—842 26.5 KB

5 Likes
7

wow - that’s easy

didn’t get this trick

thank you

1 Like
8

immagine
immagine321Ă—263 7.57 KB

1 Like
9

Thanks! I was actually looking to replace the physical WAN interface (eth0) with a tagged VLAN interface (eth0.xxx), rather than just adding a secondary VLAN interface to the existing WAN.

That was my mistake—both methods work, but I decided to follow the approach of replacing eth0 with eth0.xxx directly. I believe this is the default behavior on Turris OS and OpenWRT.

That said, there’s no issue with simply adding a tagged VLAN to the WAN for PPPoE; it just didn’t occur to me at the time.

1 Like