Joined: 26 Mar 2013 Posts: 1855 Location: Hung Hom, Hong Kong
Posted: Sat Nov 12, 2022 7:16 Post subject: Asus RT-N18U and CTF+FA: "eth%d"? "%d"?
According to the screenshot I attached, am I actually using CTF+FA in Setup->Basic Setup?
Do I need to set "Shortcut Forwarding Engine" to "CTF"? Well, if I set it to "CTF", port-forwarding stopped working.
Also, the system log is showing "_ctf_attach:attach eth%d", NOT "eth1" but "eth%d"! And as I said in another thread and according to ifconfig, my router has no interface named "wl0"! There is no "eth%d" as well!! The wireless interface of Asus RT-N18U is named "eth1".
My bet is: "%d" was not passed the parameter "1"! It's C programming language. There should be a variable not properly set when detecting the wireless interface.
Code:
~# grep ctf /var/log/messages
Jan 1 08:00:12 rt-n18u kern.warn kernel: [ 7.908879] ctf_init:2843 00:23:08 Nov 9 2022 CTF version 1.0 loaded
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 8.111716] attach ctf for eth%d
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 8.114942] _ctf_attach:attach eth%d
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 8.118533] bind ctf to eth if
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 10.974467] _ctf_attach:attach wl0
Jan 1 08:00:21 rt-n18u user.info : [ctf] : fast path forwarding successfully started
Jan 1 08:00:23 rt-n18u user.info : [ctf] : fast path forwarding successfully started
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Sat Nov 12, 2022 10:23 Post subject:
Quote:
nothing critical
just debug output. internally the correct interface will be used
its attached to ethernet and wifi interfaces. they are all named eth%d
Joined: 26 Mar 2013 Posts: 1855 Location: Hung Hom, Hong Kong
Posted: Sat Nov 12, 2022 12:23 Post subject:
the-joker wrote:
Quote:
nothing critical
just debug output. internally the correct interface will be used
its attached to ethernet and wifi interfaces. they are all named eth%d
I asked this question on the 14th of March 2022
...
mystery solved and no point complaining about %d either.
Thanks. Log messages should be clear. "%d"... well....
Is there a command to check that ctf is really binding to eth1? _________________ 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: 1855 Location: Hung Hom, Hong Kong
Posted: Tue Nov 22, 2022 10:15 Post subject:
If you looked at the following log entries, you will see that "_ctf_attach:attach eth%d" happened BEFORE eth0, br0 and vlan was logged as ready("entering promiscuous mode"). Also. for a while, "eth0" was "aux0", right before "attach ctf for eth%d"!
I think ctf_init happened too soon.
Code:
~# grep -i -E 'eth|wl0|ctf|aux' /var/log/messages
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 0.151777] L310: cache controller enabled 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x7a130000
Jan 1 08:00:12 rt-n18u kern.warn kernel: [ 7.925792] ctf_init:2843 02:42:25 Nov 18 2022 CTF version 1.0 loaded
Jan 1 08:00:12 rt-n18u kern.warn kernel: [ 8.106373] aux0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.164.18 (r692288)
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 8.129554] attach ctf for eth%d
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 8.132780] _ctf_attach:attach eth%d
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 8.136374] bind ctf to eth if
Jan 1 08:00:12 rt-n18u kern.warn kernel: [ 8.151181] eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.164.18 (r692288)
Jan 1 08:00:12 rt-n18u kern.info kernel: [ 10.992162] _ctf_attach:attach wl0
Jan 1 08:00:12 rt-n18u kern.warn kernel: [ 10.999075] eth1: Broadcom BCM4360 802.11 Wireless Controller 7.14.164.18 (r692288)
Jan 1 08:00:12 rt-n18u kern.warn kernel: [ 11.219229] aux0: mixed HW and IP checksum settings.
Jan 1 08:00:12 rt-n18u kern.warn kernel: [ 11.224334] eth0: mixed HW and IP checksum settings.
Jan 1 08:00:13 rt-n18u kern.info kernel: [ 13.350851] device eth0 entered promiscuous mode
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.836823] device eth1 entered promiscuous mode
Jan 1 08:00:13 rt-n18u kern.info kernel: [ 13.841740] br0: port 2(eth1) entered forwarding state
Jan 1 08:00:13 rt-n18u kern.info kernel: [ 13.847173] br0: port 2(eth1) entered forwarding state
Jan 1 08:00:18 rt-n18u daemon.warn dnsmasq[976]: warning: interface eth1 does not currently exist
Jan 1 08:00:21 rt-n18u user.info : [ctf] : fast path forwarding successfully started
Jan 1 08:00:23 rt-n18u user.info : [ctf] : fast path forwarding successfully started
Jan 1 08:00:28 rt-n18u user.info : [ctf] : fast path forwarding successfully started
Jan 1 08:00:28 rt-n18u kern.info kernel: [ 28.886673] br0: port 2(eth1) entered forwarding state
Jan 1 08:00:30 rt-n18u daemon.warn dnsmasq[1478]: warning: interface eth1 does not currently exist
Jan 1 08:00:33 rt-n18u user.info : [ctf] : fast path forwarding successfully started
Jan 1 08:00:34 rt-n18u user.info : [ctf] : fast path forwarding successfully started
Nov 22 18:20:51 rt-n18u user.info : [ctf] : fast path forwarding successfully started
Nov 22 18:20:52 rt-n18u user.info : [nas] : start nas for wl0
Nov 22 18:20:52 rt-n18u user.info : [nas] : NAS lan (wl0 interface) successfully started
Nov 22 18:20:53 rt-n18u user.info : [nas] : start nas for wl0
Nov 22 18:20:53 rt-n18u user.info : [nas] : NAS lan (wl0 interface) successfully started
Nov 22 18:20:54 rt-n18u user.info : [ctf] : fast path forwarding successfully started
Nov 22 18:20:57 rt-n18u user.info : [ctf] : fast path forwarding successfully started
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!