mkresin:

Hey Mauro,

please don't add patches to the bugtracker. Send this patch according to [[https://lede-project.org/docs/guide-developer/the-source-code#submitting_patches|Submitting Patches]] to get your changes included.

If you want to discuss an idea, it would be the best to send a mail to the [[https://lede-project.org/contact#mailing_lists|lede-dev mailing list]].

I've already prepared something similar, which should workaround FS#390 as well. Please have a look at these commits

• lantiq: use xwan network name for xdsl wan
• lantiq: xrx200: use vlan for ethernet wan port

in my [[https://git.lede-project.org/?p=lede/mkresin/staging.git;a=summary|staging repository]].

My first idea was to rename the networks wan/wan6 to ewan/ewan6 and use wan for xdsl/3G/4G connections. But that idea was not that appreciated by the other devs.

It's not yet in master since I see the following problems with the implemention:

• it might be confusing if you want to make a service listen on any wan interface (interface assigned to either wan or xwan)
• the wan network name could be hardcoded somewhere (config_get interface "wan")

The other idea I had, was to use a single network "wan" with multiple interfaces (ucidef_set_interface_wan "$interface_wan" "pppoe eth0.2" ). But when doing it this way, it is not possible to assign individual mac addresses to wan interfaces, since ucidef_set_interface_macaddr "wan" "$wan_mac" would set the same mac address for all interfaces in that network. Furthermore, it wouldn't be possible any longer to bind a service only to one specific wan interface (opposite use case to all wan interfaces are doing the same).

Maybe we can discuss my approach via mail and finish/test what I've done. Would be great to hear your opinion about the corner cases I do see. Might be that I'm seeing issue where no issues are.

mkresin:

With https://git.lede-project.org/cd8b20931ee40a5cdf008e6087b35e7770fc51a1 the wan port is member of the switch can be used as eth0.2 using the default configuration.

I've tried to add a default config for the ethernet wan port as well using a solution similar to yours. But I wasn't able to come up with a solution which all other devs were happy with.

But with the mentioned commit it is now way easier to use the wan port as wan interface, since it is available in LuCI. No need to edit /etc/board.json. To use the ethernet wan port as wan interface apply the following changes to your /e/c/network:

config interface 'wan6'
option ifname 'eth0.2'
option proto 'dhcpv6'


If you are fine with the way it works now, please close the feature request.

ezplanet:

Mathias,

thank you for posting the patches to get the red wan port as eth0.2. I have been using them for several weeks and the interface has been stable since your latest patches for the multicast leak.

With regards to naming the port I guess we can leave this to the choice of the user.