What is the purpose of including wan6 as a possible alias interface in wan6 configuration? I believe it is a bug, it leads to non-functioning configuration.
This is just for ppl. who have specific needs. E. g. a second IP address for the same interface (one is static another one via DHCP). "Alias" is meant for this usecases. So it's not a bug.
EDIT: A bit of search would have directed you to:
Not accepted. What is the need of having alias to intself (wan6 to wan6)? The link you provided is just a lan1 and lan2 being aliases to lan (eth0).
@wan6 itself is just an alias of @wan (just execute "ifconfig wan"). You can see in your dropdown menu that pppoe-wan has wan and wan6.
ifconfig wan
wan Link encap:Ethernet HWaddr BC:CF:4F:FF:
inet addr:192.168.178.74 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: fe80::cadc:2b1e:93b2:66d0/64 Scope:Link
inet6 addr: 2a02:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/128 Scope:Global
inet6 addr: fd00::cadc:2b1e:93b2:66d0/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:58325 errors:0 dropped:10480 overruns:0 frame:0
TX packets:3513 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:61672945 (58.8 MiB) TX bytes:520023 (507.8 KiB)
Base address:0x1800
Then add just a new interface, select alias interface @wan6 and assign another IP:
ifconfig wan
wan Link encap:Ethernet HWaddr BC:CF:4F:FF:
inet addr:192.168.178.74 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: fe80::cadc:2b1e:93b2:66d0/64 Scope:Link
inet6 addr: 2a02:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/128 Scope:Global
**inet6 addr: fe80::cadc:2b1e:93b2:66d0:ffff/128 Scope:Link**
inet6 addr: fd00::cadc:2b1e:93b2:66d0/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:59938 errors:0 dropped:11288 overruns:0 frame:0
TX packets:3997 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:62045475 (59.1 MiB) TX bytes:623432 (608.8 KiB)
Base address:0x1800
So what is wrong to have just another IP if needed?
Better tell me what this config will produce (your ifconfigs are irrelevant):
config interface 'wan6'
option proto 'dhcpv6'
option device '@wan6'
This does not work obviously. Because I'm referencing the device itself what I'm about to create (just delete wan6 and recreate it. there is no reference for @wan6).
As I said if you have need you can use this alias for another interface referencing @wan6 to assign another IP and then create an new firewall zone and a new lan e. g.
But as it is OpenWrt. Not every option to choose makes sense or does work. You have to know what you are doing. You have this drop down menus everywhere. Esp. in Firewall settings. Still not a bug (IMO).
But you can't use it as an alias to itself, do you agree?
The only way to use this option is to get a non-working configuration. So far it looks like a typical bug to me.
I do not agree. If you delete wan6 interface completely and recreate it you don't have @wan6 alias available as option in the drop down menu. So you would not end up with a broken interface. The alias is available only after wan6 interface is created. Not before! So even if you are a noob you could not choose @wan6 if you are about to create wan6 interface. Beside the fact that wan6 interface is created automatically.
If you decide to reconfigure wan6 interface (you know what you are doing (IMO)).
It's like talking to my 6 y.o. son, I'm sorry.
What will trigger start of wan6 device in case I'm talking about?
Try it youself, it's a simple thing. No need to waste your precious time.
I'm just saying that GUI should avoid showing options which will generate broken or non-functioning configurations.
Well, then we don't understand each other respectivley I have a different defenition of what a bug is.
wan6 is working as intended. @wan6 alias is available for special configurations after wan6 is setup correctly.
Nobody would go into wan6 settings and choose @wan6 alias interface. Nobody would go into wan6 settings and choose pppoe-wan for wan6 just because it is available.
That's I see it with my 6 years.
SHOW ME that scenario! I'm tired wasting my time with your irrelevant links and ifconfigs.
I'll show you my finger as a 6 yo old kid. ^^
What prevents it? Your stubbornness?
Once again, what is that secret scenario which requires wan6-wan6 loop?
The drop down simply lists all defined devices, notably not excluding the one that is currently being configured.
Feel free to open an issue, or even better, fix it and submit a patch/pull request.
3 Likes
1 Like
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.