Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Mon Oct 17, 2022 7:05 Post subject: Broadcom: wireless interface names ethX vs wlX
Why is my only physical wireless interface NOT named "wl0", but "eth1"? Is it a bug?
I suspect DD-WRT always assumes that wireless interface names begin with "wl".
Looking at the system log, [nas] and _ctf_ claimed to work with wl0 not eth1, while dnsmasq said there was no eth1! Well..
Code:
# grep -E 'eth1|ctf|wl' /var/log/messages
Jan 1 08:00:12 rt-n18u kern.warn kernel: [ 7.905913] ctf_init:2843 03:16:08 Oct 13 2022 CTF version 1.0 loaded
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 8.107908] attach ctf for eth%d
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 8.111125] _ctf_attach:attach eth%d
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 8.114731] bind ctf to eth if
Jan 1 08:00:12 rt-n18u kern.warn kernel: [ 10.845902] wl: module license 'Proprietary' taints kernel.
Jan 1 08:00:12 rt-n18u kern.warn kernel: [ 10.902794] wl_module_init: passivemode set to 0x0
Jan 1 08:00:12 rt-n18u kern.warn kernel: [ 10.907713] wl_module_init: txworkq set to 0x1
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 10.976311] _ctf_attach:attach wl0
Jan 1 08:00:12 rt-n18u kern.warn kernel: [ 10.983239] eth1: Broadcom BCM4360 802.11 Wireless Controller 7.14.164.18 (r692288)
Jan 1 08:00:13 rt-n18u user.info : [bridge] : interface eth1 successfully added to bridge br0
Jan 1 08:00:13 rt-n18u kern.info kernel: [ 13.752742] device eth1 entered promiscuous mode
Jan 1 08:00:13 rt-n18u kern.info kernel: [ 13.769087] br0: port 2(eth1) entered forwarding state
Jan 1 08:00:13 rt-n18u kern.info kernel: [ 13.774513] br0: port 2(eth1) entered forwarding state
Jan 1 08:00:18 rt-n18u daemon.warn dnsmasq[977]: warning: interface eth1 does not currently exist
Jan 1 08:00:27 rt-n18u user.info : [wland] : daemon successfully stopped
Jan 1 08:00:27 rt-n18u user.info : [wland] : successfully started
Jan 1 08:00:27 rt-n18u daemon.warn dnsmasq[1419]: warning: interface eth1 does not currently exist
Jan 1 08:00:28 rt-n18u kern.info kernel: [ 28.802354] br0: port 2(eth1) entered forwarding state
Oct 17 15:01:51 rt-n18u user.info : [nas] : start nas for wl0
Oct 17 15:01:51 rt-n18u user.info : [nas] : NAS lan (wl0 interface) successfully started
Oct 17 15:01:53 rt-n18u user.info : [nas] : start nas for wl0
Oct 17 15:01:53 rt-n18u user.info : [nas] : NAS lan (wl0 interface) successfully started
Code:
# ifconfig -a | grep Link | cut -f 1 -d \ ;
aux0
br0
ctf0
eth0
eth1
lo
teql0
vlan1
vlan2
# ip link show | grep -v ether
1: lo: <LOOPBACK,MULTICAST,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: teql0: <NOARP> mtu 1500 qdisc noop state DOWN qlen 100
link/void
3: ctf0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
4: aux0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN qlen 1000
5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN qlen 1000
6: vlan1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP qlen 1000
7: vlan2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
8: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UNKNOWN qlen 1000
9: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Mon Oct 17, 2022 7:31 Post subject:
That's not a bug per say, on Broadcom at least mine eth1/eth2 are the physical wireless interfaces, 2.4GHz being (eth1) wl0 and 5GHz (eth2) wl1 -- VAP being eth2 wl1.1 in my case.
Look at the networking page and it becomes clearer what what.
As for the CTF -- it applies only for WAN <-> LAN connections, that's the default and intended design, but, guess what, you have a bridge where all the interfaces are under including your wireless interface, so by side effect CTF attaches to the WAN/LAN which is under the bridge increasing it's performance by doing what it CFT does and your wifi interface is just a side effect of being bridged along with the rest.
Joined: 08 May 2018 Posts: 14220 Location: Texas, USA
Posted: Mon Oct 17, 2022 9:33 Post subject:
As I said in my reply in the other thread, this has always been the case. Awaiting response from BrainSlayer to my reply about the other issue. I was trying to find the code where this crossover meets IRT the webUI access filter and went cross-eyed yesterday. Anyhow, we'll see what's what soon enough. Film at 11. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Mon Oct 17, 2022 10:14 Post subject: It's all because of bad, inconsistent labels and names!
To both the-joker and kernel-panic69:
If and only if the only physical wireless interface in my Asus RT-N18U was just named "wl0" in ifconifg, I and possibly many other users wouldn't have met so many strange problems, and saved a lot of time debugging, testing and messaging.
I could have use that amount of time watching porn movies... well... I could have done something more productive to the world. Meow...
It's all because of bad, inconsistent labels and names!
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Mon Oct 17, 2022 10:21 Post subject:
the-joker wrote:
If ifs and buts were candy and nuts, we all would have a merry xmas.
Anyway stop pretending you love it -- admit it!
Only because I had that amount of leisure time... but watching light-emitting screens are bad for human eyes. It's like staring at winter snow in a sunny day! You all should be careful about it.
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Mon Oct 17, 2022 10:31 Post subject:
the-joker wrote:
Ah, sorry, drink, blink and re-read my previous post, I hit post too soon.
The only concerns with snow generally is the color of it, if its yellow dont eat it. I dont spend a large amount of time staring at the snow, not anymore anyway my twitch medication is working much better, 500Mg of fuckoffpills twice a day
Cheers (tea not wine nor beer) to good health, including good eyes!! _________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
According to this link (http://www.dd-wrt.com/wiki/index.php/Iptables_command), the interfaces are ...
vlan0 is the 4 LAN ports (K24 Only)
vlan1 is the WAN port (K24 Only) or the 4 LAN ports (K26 and K3.x) (ppp0 is the WAN interface when PPPoE is used)
vlan2 is the WAN port (K26 and K3.x)
eth1 is the WIFI
eth2-3 is the WIFI (Dual Radio routers)
br0 is a bridge connecting the 4 LAN and the WIFI together
and everything else related (many other files peppered around source code) that relies exclusively on default vendor wlX Broadcom side including the driver itself, since driver is closed source I suggest you complain to Broadcom.
And then enjoy the bugs that will result.
This is my last entry on these posts about the subject which is already fast becoming a pet peeve type thread.
IMHO my stance is I will not support this for the sake of something that is and has been an issue across all Linux distros since the dawn of time so that one single user and the only user who cares about this DD-WRT side can feel better about something meaningless and that breaks nothing.
you love it -- admit it!