#79 closed documentation (wontfix)
Network error while booting up network
Reported by: | e.d.grootjans@… | Owned by: | amain |
---|---|---|---|
Priority: | major | Milestone: | milestone: |
Component: | debian/rootfs | Version: | 2.0 |
Severity: | severity 4 | Keywords: | |
Cc: |
Description
WHile booting the router I get the next network error:
. . b43-phy0: Broadcom 4306 WLAN found (core revision 5) Broadcom 43xx driver loaded [ Features: PL, GPIO LED Mask: 0x000f, Firmware-ID: FW13 ] done. . . Setting up networking.... Configuring network interfaces...SIOCSIFADDR: No such device eth0_wan: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device eth0_wan: ERROR while getting interface flags: No such device Failed to bring up eth0_wan. interface eth0_lan does not exist! can't add wlan0 to bridge lanbridge: Operation not supported done. Cleaning up temporary files.... INIT: Entering runlevel: 2 . .
I use the following configuration:
the changed interfaces.lan-wlan-bridge
root@debwrt:/etc/network# cat interfaces.lan-wlan-bridge # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or # /usr/share/doc/ifupdown/examples for more information. auto lo iface lo inet loopback # eth0: port 5 on ethernet switch ( Broadcom 44xx/47xx 10/100BaseT Ethernet - b44 ) # # Note: eth0 is the ethernet device connected to the b44 switch. # The switch creates vlan tags for each seperate configured # vlan. robocfg is used to configure the switch. For security # reasen I would advice not to bind an ip-address to eth0 and # make sure you have no services connect to eth0 and/or # create proper firewall rules. # # eth0 needs to be enabled, otherwise eth0.wan and eth0.lan # VLAN interfaces will be disabled as well. See # /etc/init.d/network_switch were eth0 is enabled and the # switch and VLAN's interfaces are created. # eth0_wan: vlan #0 on eth0 - ports: 0 # auto eth0_wan #iface eth0_wan inet dhcp iface eth0_wan inet static address 192.168.0.251 netmask 255.255.255.0 gateway 192.168.0.254 # eth0_lan: vlan #1 on eth0 - ports: 1,2,3,4 # # part of lanbridge - no ip config needed # wlan0: wireless lan interface ( Broadcom WLAN - b43 ) - kernel 2.6 # # part of lanbridge - no ip config needed # wl0: wireless lan interface ( Broadcom WLAN - wl ) - kernel 2.4 # # part of lanbridge - no ip config needed # lanbridge: eth0_lan ports and wlan0/wl0 bridge # auto lanbridge iface lanbridge inet static bridge-ports eth0_lan wlan0 bridge-stp off bridge-maxwait 0 address 192.168.1.1 netmask 255.255.255.0 # pre-up /etc/init.d/nas start # pre-down /etc/init.d/nas stop # pre-up /etc/init.d/hostapd-mini start # pre-down /etc/init.d/hostapd-mini stop
ifconfig shows:
root@debwrt:/etc/init.d# ifconfig eth0 Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7 errors:0 dropped:0 overruns:0 frame:0 TX packets:232 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1088 (1.0 KiB) TX bytes:21491 (20.9 KiB) Interrupt:4 lanbridge Link encap:Ethernet HWaddr 52:60:ed:6a:c4:f5 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:6600 (6.4 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:100 (100.0 B) TX bytes:100 (100.0 B)
robocfg shows:
root@debwrt:/etc/init.d# robocfg show probing eth1 SIOCETHTOOL: No such device probing eth0 Switch: enabled Port 0(W): 100FD enabled stp: disable vlan: 1 mac: 00:23:5a:5a:a8:8b Port 1(4): DOWN enabled stp: none vlan: 1 mac: 00:00:00:00:00:00 Port 2(3): DOWN enabled stp: none vlan: 1 mac: 00:00:00:00:00:00 Port 3(2): 100FD enabled stp: none vlan: 1 mac: 00:10:dc:3a:bc:1e Port 4(1): DOWN enabled stp: none vlan: 1 mac: 00:00:00:00:00:00 Port 5(C): 100FD enabled stp: none vlan: 1 mac: 00:15:f2:77:d0:c1 VLANs: BCM536x disabled mac_check mac_hash root@debwrt:/etc/init.d#
Attachments (0)
Change History (38)
comment:1 Changed 11 years ago by stappers
- Priority changed from major to trivial
comment:2 Changed 11 years ago by E.D.Grootjans <e.d.grootjans@…>
The problem is that interfaces are not created...
There is no eth0_wan, eth0_lan
and wlan0 can not be added to lanbridge.
See below:
Setting up networking.... eth0_wan: ERROR while getting interface flags: No such device Failed to bring up eth0_wan. interface eth0_lan does not exist! can't add wlan0 to bridge lanbridge: Operation not supported
Errors are generated on the ASUS Router
- so the devices are there
- drivers are loaded; because eth0 works with firstboot
- b43 driver is loaded, see previous start message
eth0_lan and eth0_wan are not created....
See below:
root@debwrt:~# iwconfig lo no wireless extentions wlan0 IEEE 802.11bg ESSID:off/any Mode: managed Access Point: Not-Associated TX-Power=0 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off lanbridge no wireless extentions root@debwrt:~# ifconfig eth0_lan eth0_lan: error fetching interface information: Device not found root@debwrt:~# ifconfig eth0_wan eth0_wan: error fetching interface information: Device not found
comment:3 Changed 11 years ago by stappers
What is the output of these commands
tty
ifconfig -a
and
brctl show
?
comment:4 Changed 11 years ago by E.D.Grootjans <e.d.grootjans@…>
The output:
root@debwrt:~#tty /dev/ttyS0 root@debwrt:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2524 errors:0 dropped:0 overruns:0 frame:0 TX packets:223 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:190628 (186.1 KiB) TX bytes:20867 (20.3 KiB) Interrupt:4 lanbridge Link encap:Ethernet HWaddr 1e:fe:c3:ed:f3:e2 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:75 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:14175 (13.8 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:100 (100.0 B) TX bytes:100 (100.0 B) wlan0 Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@debwrt:~# brctl show bridge name bridge id STP enabled interfaces lanbridge 8000.000000000000 no root@debwrt:~#
comment:5 Changed 11 years ago by stappers
ifconfig -a | grep HWaddr
brctl showmacs lanbridge
And to save me some time on scrolling back and forward in this ticket
robocfg show
again.
comment:6 follow-up: ↓ 7 Changed 11 years ago by E.D.Grootjans <e.d.grootjans@…>
The output:
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. root@debwrt:~# root@debwrt:~# root@debwrt:~# root@debwrt:~# root@debwrt:~# ifconfig -a | grep HWaddr eth0 Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 lanbridge Link encap:Ethernet HWaddr fa:bb:06:81:ac:4b wlan0 Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 root@debwrt:~# brctl showmacs lanbridge port no mac addr is local? ageing timer root@debwrt:~# robocfg show probing eth1 SIOCETHTOOL: No such device probing eth0 Switch: enabled Port 0(W): 100FD enabled stp: disable vlan: 1 mac: 00:23:5a:5a:a8:8b Port 1(4): DOWN enabled stp: none vlan: 1 mac: 00:00:00:00:00:00 Port 2(3): DOWN enabled stp: none vlan: 1 mac: 00:00:00:00:00:00 Port 3(2): 100FD enabled stp: none vlan: 1 mac: 00:10:dc:9a:8e:e2 Port 4(1): DOWN enabled stp: none vlan: 1 mac: 00:00:00:00:00:00 Port 5(C): 100FD enabled stp: none vlan: 1 mac: 00:15:f2:77:d0:c1 VLANs: BCM536x disabled mac_check mac_hash root@debwrt:~# b44 ssb0:0: eth0: powering down PHY
comment:7 in reply to: ↑ 6 Changed 11 years ago by stappers
- Priority changed from trivial to minor
Strange, very strange.
- Both eth0 and wlan0 have the same MAC address
- Bridge lanbridge has no MAC addresses, it should have at least some local MAC addresses
- In the switch is everthing in vlan 1
Please review wiki page BridgedNetwork
That page is a copy from the two year old page http://www.debwrt.net/usage/networking/bridged-network/
What used to work, 24 months ago, seems to have been changed ...
comment:8 Changed 11 years ago by E.D.Grootjans <e.d.grootjans@…>
Between version 1.0 and 2.0 are a lot of changes.
So there is no nas-file, there is no firewall-file etc.
I have looked in the old file system 1.0 and i see in rcS.d:
S38robocfg
S39firewall
S39ifupdown
S40networking
I see S20hostapd-mini in rc2.d, rc3.d, rc4.d en in rc5.d.
In the new debwrt2.0 filesysteem i see in rcS.d:
S39ifupdown
S40networking
GEEN S38robocfg
en in rc2.d t/m rc5.d zie ik GEEN S20hostapd
I think these files are missing ....
--> Correct or is hostapd and robocfg in another way started ???? <---
( I have inserted an echo command in robocfg and i dont see it while booting !!!
(For the K-files its more ore less the same. ...)
comment:9 Changed 11 years ago by E.D.Grootjans <e.d.grootjans@…>
I have added the following links:
root@debwrt:/etc# ln -snf /etc/init.d/robocfg /etc/rcS.d/S38robocfg root@debwrt:/etc# ln -snf /etc/init.d/hostapd /etc/rc2.d/S20hostapd root@debwrt:/etc# ln -snf /etc/init.d/hostapd /etc/rc3.d/S20hostapd root@debwrt:/etc# ln -snf /etc/init.d/hostapd /etc/rc4.d/S20hostapd root@debwrt:/etc# ln -snf /etc/init.d/hostapd /etc/rc5.d/S20hostapd root@debwrt:/etc# ln -snf /etc/init.d/hostapd /etc/rc6.d/K20hostapd root@debwrt:/etc# ln -snf /etc/init.d/hostapd /etc/rc0.d/K20hostapd root@debwrt:/etc# ln -snf /etc/init.d/hostapd /etc/rc1.d/K20hostapd root@debwrt:/etc#
In the robocfg i have :
put 3 lines in
echo "1"
echo "2"
echo "3"
echo "4"
outcommended the
if [ ! $ENABLED -eq 1 ]; then exit 0; fi
and put there an echo $ENABLED
During startup i get:
Activating swapfile swap...done. Cleaning up temporary files.... 1 2 3 4 0 Initializing vlan tagging on b44 ethernet switch: robocfg...Configurating robocfg-switch !!!! done. Setting up networking.... Configuring network interfaces...device eth0_lan entered promiscuous mode device eth0 entered promiscuous mode can't add wlan0 to bridge lanbridge: Operation not supported lanbridge: port 1(eth0_lan) entering learning state lanbridge: port 1(eth0_lan) entering learning state done. Cleaning up temporary files.... INIT: Entering runlevel: 2 Starting enhanced syslogd: rsyslogdlanbridge: port 1(eth0_lan) entering forwarding state . Starting OpenBSD Secure Shell server: sshdsshd (1014): /proc/1014/oom_adj is deprecated, please use /proc/1014/oom_score_adj instead. . Starting advanced IEEE 802.11 management: hostapdb43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) . Starting internet superserver: inetd. Starting Samba daemons: nmbd smbdusb 1-4: reset high speed USB device using ehci_hcd and address 3 . Starting NTP server: ntpd. Starting periodic command scheduler: cron. Debian GNU/Linux 6.0 debwrt ttyS0 debwrt login:
I do a ifconfig -a
root@debwrt:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:17 errors:0 dropped:0 overruns:0 frame:0 TX packets:431 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1450 (1.4 KiB) TX bytes:37604 (36.7 KiB) Interrupt:4 eth0_lan Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14 errors:0 dropped:0 overruns:0 frame:0 TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:942 (942.0 B) TX bytes:3312 (3.2 KiB) eth0_wan Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 inet addr:192.168.0.251 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:161 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:9194 (8.9 KiB) lanbridge Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11 errors:0 dropped:0 overruns:0 frame:0 TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:748 (748.0 B) TX bytes:2796 (2.7 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:59 errors:0 dropped:0 overruns:0 frame:0 TX packets:59 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5616 (5.4 KiB) TX bytes:5616 (5.4 KiB) mon.wlan0 Link encap:UNSPEC HWaddr 00-15-F2-77-D0-C1-B0-E1-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:42 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3639 (3.5 KiB) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@debwrt:~# ifconfig -a | grep HWaddr eth0 Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 eth0_lan Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 eth0_wan Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 lanbridge Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 mon.wlan0 Link encap:UNSPEC HWaddr 00-15-F2-77-D0-C1-B0-C1-00-00-00-00-00-00-00-00 wlan0 Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 root@debwrt:~# NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 robocfg show probing eth1 SIOCETHTOOL: No such device probing eth0 Switch: enabled Port 0(W): DOWN enabled stp: none vlan: 100 mac: 00:00:00:00:00:00 Port 1(4): DOWN enabled stp: none vlan: 101 mac: 00:00:00:00:00:00 Port 2(3): DOWN enabled stp: none vlan: 101 mac: 00:00:00:00:00:00 Port 3(2): 100FD enabled stp: none vlan: 101 mac: 00:10:dc:9a:8e:e2 Port 4(1): DOWN enabled stp: none vlan: 101 mac: 00:00:00:00:00:00 Port 5(C): 100FD enabled stp: none vlan: 1 mac: 00:15:f2:77:d0:c1 VLANs: BCM536x enabled mac_check mac_hash vlan100: 0 5t vlan101: 1 2 3 4 5t root@debwrt:~# brctl showmacs lanbridge port no mac addr is local? ageing timer 1 00:02:44:8c:8b:26 no 90.72 1 00:10:dc:3a:bc:1e no 195.18 1 00:10:dc:9a:8e:e2 no 41.90 1 00:15:f2:77:d0:c1 yes 0.00 root@debwrt:~#
So i think a step ahead but not good yet....
comment:10 Changed 11 years ago by stappers
- Owner changed from amain to stappers
- Priority changed from minor to major
- Status changed from new to accepted
- Type changed from defect to documentation
comment:11 Changed 11 years ago by E.D.Grootjans <e.d.grootjans@…>
Too Enable robofg
I changed Enable from 0 to 1 in the /etc/default directory.
I also changed here dnsmasq from 0 to 1
And changed in /etc/dnsmasq.conf the netwerkrange for dhcp ethernetaddresses.
Result is still the same.
When starting I get:
Cleaning up temporary files.... Initializing vlan tagging on b44 ethernet switch: robocfg...Configurating robocfg-switch !!!! done. Setting up networking.... Configuring network interfaces...device eth0_lan entered promiscuous mode device eth0 entered promiscuous mode can't add wlan0 to bridge lanbridge: Operation not supported lanbridge: port 1(eth0_lan) entering learning state lanbridge: port 1(eth0_lan) entering learning state SIOCADDRT: No such process Failed to bring up lanbridge done. Cleaning up temporary files.... INIT: Entering runlevel: 2 Starting enhanced syslogd: rsyslogdlanbridge: port 1(eth0_lan) entering forwarding state . Starting OpenBSD Secure Shell server: sshdsshd (1014): /proc/1014/oom_adj is deprecated, please use /proc/1014/oom_score_adj instead. . Starting advanced IEEE 802.11 management: hostapdb43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) . Starting internet superserver: inetd. Starting Samba daemons: nmbdNOHZ: local_softirq_pending 08 smbdNOHZ"local_softirq_pending 08 . NOHZ"local_softirq_pending 08 NOHZ"local_softirq_pending 08 NOHZ"local_softirq_pending 08 NOHZ"local_softirq_pending 08 NOHZ"local_softirq_pending 08 NOHZ"local_softirq_pending 08 NOHZ"local_softirq_pending 08 NOHZ"local_softirq_pending 08 Starting NTP server: ntpd. Starting periodic command scheduler: cron. Debian GNU/Linux 6.0 debwrt ttyS0 debwrt login:
I think this error: can't add wlan0 to bridge lanbridge: Operation not supported has something to do with: bridge-ports eth0_lan wlan0 in /etc/network/interfaces.lan-wlan-bridge
The processes are started in the following order:
- robocfg
- ifupdown
- networking
runlevel 2:
- hostapd
Question: do i already have an wlan0 device to bind to lanbridge add the point of starting networking ?
comment:12 Changed 11 years ago by stappers
As far as I known, comes
can't add wlan0 to bridge lanbridge: Operation not supported
from /etc/interfaces, executed during system startup
auto lanbridge iface lanbridge inet static bridge-ports eth0_lan wlan0 bridge-stp off bridge-maxwait 0 address 192.168.1.1 netmask 255.255.255.0
Because you have a serial port, you can play with the network configuration
without loosing connection.
Emulate manually the system network start, do something like
- ifconfig lanbridge down
- brctl delif lanbridge eth0_lan
- brclt delbr lanbridge
- ifconfig eth0_lan down
- ifconfig wlan0 down
- brctl show # should show no bridge definition
- brctl addbr lanbridge
- brctl addif lanbridge eth0_lan
- brctl addif lanbridge wlan0
- ifconfig lanbridge 192.168.1.1 netmask 255.255.255.0
I didn't verify those instructions, because I have not the access to the hardware.
Looking forward for the feedback.
comment:13 Changed 11 years ago by E.D.Grootjans <e.d.grootjans@…>
Add first i did bring the interfaces down and started them up again.
Second I brought the interfaces down and used the scripts to also bring them down an up again.
I did not get the same error: "can't ..." but i don't understand why.
But still i cant get out of the router.
The Wan interface must be address 192.168.0.251 netmask 255.255.255.0
The lan interface must be address 192.168.1.1 netmask 255.255.255.0
I put here my interfaces-file:
root@debwrt:/etc# cat network/interfaces auto lo iface lo inet loopback auto eth0_wan iface eth0_wan inet static address 192.168.0.251 netmask 255.255.255.0 gateway 192.168.0.254 dns-nameservers 192.168.0.6 192.168.0.254 dns-search thuis.priv auto lanbridge iface lanbridge inet static bridge-ports eth0_lan wlan0 bridge-stp off bridge-maxwait 0 address 192.168.1.1 netmask 255.255.255.0
root@debwrt:~# ifconfig lanbridge down lanbridge: port 1(eth0_lan) entering forwarding state root@debwrt:~# brctl delif lanbridge eth0_lan device eth0_lan left promiscuous mode device eth0 left promiscuous mode lanbridge: port 1(eth0_lan) entering disabled state root@debwrt:~# brctl delbr lanbridge netconsole: network logging stopped, interface lanbridge unregistered root@debwrt:~# ifconfig eth0_lan down root@debwrt:~# ifconfig wlan0 down root@debwrt:~# brctl show bridge name bridge id STP enabled interfaces root@debwrt:~# brctl addbr lanbridge root@debwrt:~# brctl addif lanbridge eth0_lan device eth0_lan entered promiscuous mode root@debwrt:~# brctl addif lanbridge wlan0 device wlan0 entered promiscuous mode root@debwrt:~# ifconfig lanbridge 192.168.0.251 netmask 255.255.255.0 root@debwrt:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:435 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:251 (251.0 B) TX bytes:37679 (36.7 KiB) Interrupt:4 eth0_lan Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:25 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:233 (233.0 B) TX bytes:2820 (2.7 KiB) eth0_wan Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 inet addr:192.168.0.251 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:172 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:9700 (9.4 KiB) lanbridge Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 inet addr:192.168.0.251 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:59 errors:0 dropped:0 overruns:0 frame:0 TX packets:59 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5774 (5.6 KiB) TX bytes:5774 (5.6 KiB) mon.wlan0 Link encap:UNSPEC HWaddr 00-15-F2-77-D0-C1-B0-01-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:15:f2:77:d0:c1 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@debwrt:~# brctl show bridge name bridge id STP enabled interfaces lanbridge 8000.0015f277d0c1 no eth0_lan wlan0 root@debwrt:~#
comment:14 Changed 11 years ago by stappers
ifconfig lanbridge 192.168.1.1 netmask 255.255.255.0
then connect to 192.168.1.xx where xx is a configured network device
and xx is larger as 1 and smaller as 255.
comment:15 Changed 11 years ago by stappers
the same check to other way round:
connect from 192.168.1.xx to 192.168.1.1
comment:16 follow-up: ↓ 19 Changed 11 years ago by E.D.Grootjans <e.d.grootjans@…>
I'm one step further.
I can connect with ssh from the device to the outside en visaversa.
I still have the
can't add wlan0 to bridge lanbridge: Operation not supported
ad bootup.
Still a lot off devices have the same HW-address.
I'm now looking if i can make an external connection with wlan0
comment:17 follow-up: ↓ 18 Changed 11 years ago by E.D.Grootjans <e.d.grootjans@…>
I have this error while starting network:
can't add wlan0 to bridge lanbridge: Operation not supported
and
netconsole: network logging stopped, interface mon.wlan0 unregistered
The first one is during start off the networking
The secondone is when i'm about to login.
After login in
I do sometimes 1 time, sometime 2, sometimes 3 times:
brctl show ==> I only see a eth0_lan interface not a wlan0 interface /etc/init.d/hostapd stop /etc/init.d/networking stop /etc/init.d/ifupdown stop /etc/init.d/ifupdown start /etc/init.d/networking start /etc/init.d/hostapd start brctl show
After the last time i have a wlan0
I don't understand why.
Why sometimes one, sometimes 2 sometimes more.....
Can it be in a way that the interfaces are not yet ready and because of that i can not add wlan to lanbridge ????
But I do understand that if I don't have a wlan0 bind to lanbridge
then i can not login by wireless, because i can not connect to the network and get no ip-address.
comment:18 in reply to: ↑ 17 Changed 11 years ago by stappers
Replying to E.D.Grootjans <e.d.grootjans@…>:
Can it be in a way that the interfaces are not yet ready and because of that i can not add wlan to lanbridge ????
Yes, hence this ticket ...
comment:19 in reply to: ↑ 16 Changed 11 years ago by stappers
Replying to E.D.Grootjans <e.d.grootjans@…>:
I'm one step further.
I can connect with ssh from the device to the outside en visaversa.
\o/ Hurray! It is good to have progress.
I still have the
can't add wlan0 to bridge lanbridge: Operation not supportedat bootup.
Welcome to DebWrt, the place where Debian and OpenWrt meet.
Openwrt is about many different hardware devices.
Debian is about free software.
Debwrt's approach is to boot with a minimalistic configuration, /etc/network/interfaces.firstboot.
Which configuration for which internal network switch and further configuration, is the reason that this ticket is open. It is tagged as documentation. Writing down what is needed, is the way to closing this ticket.
Still a lot off devices have the same HW-address.
Please review wiki page BrigdedNetwork?.
I'm now looking if i can make an external connection with wlan0
Most likely will starting hostapd at the right moment, do the trick.
(Please document)
comment:20 Changed 11 years ago by E.D.Grootjans <e.d.grootjans@…>
I have tryed 4 things
- Not startingup hostapd --> same error
- Startingup hostapd and not the networking (mv S40networking K40networking)and after login starting the network. --> wlan is started correctly and added to lanbridge...
- Add a countingscript between ifupdown and networking in rcS.d; and wait 3 min. -> same error
- Start hostapd before networking --> wlan is started correctly and added to lanbridge.
By 2 and 4 hostapd is started BEFORE networking and this is working.
I do not understand why.
comment:21 Changed 11 years ago by e.d.grootjans@…
If have been surching on the internet and found out, and i quote:
That it is no longer posible to add an interface in the managed mode bridge. You should run hostapd first to pure the interface to Master mode.
This is from kernel version 2.6.33.
See also: http://kerneltrap.org/mailarchive/linux-ath5k-devel/2010/3/21/6871733
and http://lists.shmoo.com/pipermail/hostap/2010-January/020958.html
My conclussion is:
You have to run hostapd first (to get it in master mode)
and after that run networking.
So I made the following changes to my box:
(under root)
ln -snf /etc/init.d/robocfg /etc/rcS.d/S38robocfg
ln -snf /etc/init.d/hostapd /etc/rcS.d/S41hostapd
mv /etc/rcS.d/S40networking /etc/rcS.d/S42networking
ln -snf /etc/init.d/hostapd /etc/rc6.d/K20hostapd
ln -snf /etc/init.d/hostapd /etc/rc0.d/K20hostapd
ln -snf /etc/init.d/hostapd /etc/rc1.d/K20hostapd
I have rebooted my box a few times and this is working !!!
comment:22 Changed 11 years ago by stappers
Some notes for later, mostly to avoid a plain
Seen the good update
:-)
Information about a tool for creating symbolic links on init scripts
man update-rc.d
Header of hostapd init script
stappers@inertia:/usr/src/debwrt $ sed --silent '/BEGIN INIT/,/END INIT/p' debian/package/hostapd/debian/hostapd.init ### BEGIN INIT INFO # Provides: hostapd # Required-Start: # Required-Stop: # Should-Start: $network # Should-Stop: # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Advanced IEEE 802.11 management daemon # Description: Userspace IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP # Authenticator ### END INIT INFO stappers@inertia:/usr/src/debwrt $
I think that the
Should-Start: $network
is some how important.
comment:23 Changed 11 years ago by e.d.grootjans@…
From the documentation:
Should-Start: boot_facility_1 [boot_facility_2...]
defines the facilities that if present should start before the service provided by the script. Nevertheless, the script can still start if the listed facilities are missing. This allows for weak dependencies which do not cause the service to fail if a facility is not available. Consider using virtual facility names as described below if adequate.
So This means that network should start BEFORE hostapd is started
I think this needs modification, because off the kernelupdate...
-->> networking must be start AFTER hostapd is started
The correct sequence is:
robocfg
hostapd
networking
comment:24 follow-ups: ↓ 29 ↓ 33 Changed 11 years ago by stappers
To create the various symbolic links in the /etc/rcX.d directories,
there seems to be
insserv
Currently I'm playing with that tool
and encountered some cruft
root@debwrt:~# insserv insserv: warning: script is corrupt or invalid: /etc/init.d/../rc0.d/S03led insserv: warning: script is corrupt or invalid: /etc/init.d/../rc0.d/S99stop-led insserv: warning: script is corrupt or invalid: /etc/init.d/../rc2.d/S99stop-led-flashing insserv: warning: script is corrupt or invalid: /etc/init.d/../rc2.d/S03led insserv: warning: script is corrupt or invalid: /etc/init.d/../rc6.d/S03led insserv: warning: script is corrupt or invalid: /etc/init.d/../rc6.d/S99stop-led insserv: warning: script is corrupt or invalid: /etc/init.d/../rcS.d/S03led insserv: warning: script 'rcS.firstboot' missing LSB tags and overrides insserv: warning: script 'rcS.debian' missing LSB tags and overrides root@debwrt:~#
comment:25 Changed 11 years ago by crodr021@…
did you get your stuff resolved? I managed to hack my stuff up today and get it slightly working from when I opened up my ticket.
comment:26 Changed 11 years ago by e.d.grootjans@…
It works, if you start wlan (hostapd) before networking.
If you need help, Maybe i can help you - let me know
comment:27 Changed 11 years ago by stappers
The next three comments are a mix of code improvement and workaround
n+1: hostapd symlink change, includes a patch
n+2: cruft removal
n+3: full symlink generation
The fourth comment shows the list that e.d.grootjans@... provided earlier.
All is done on the target debwrt hardware ( no "build delay" )
comment:28 Changed 11 years ago by stappers
Delete symlinks for the current hostapd
update-rc.d hostapd remove
Modify the header of /etc/init.d/hostapd as diff
# Provides: hostapd # Required-Start: # Required-Stop: -# Should-Start: $network -# Should-Stop: -# Default-Start: 2 3 4 5 -# Default-Stop: 0 1 6 +# Should-Start: $local_fs +# Should-Stop: $local_fs +# Default-Start: S +# Default-Stop: 0 6 +# X-Start-Before: $network +# X-Stop-After: $network # Short-Description: Advanced IEEE 802.11 management daemon # Description: Userspace IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP # Authenticator
so it should look like
# Provides: hostapd # Required-Start: # Required-Stop: # Should-Start: $local_fs # Should-Stop: $local_fs # Default-Start: S # Default-Stop: 0 6 # X-Start-Before: $network # X-Stop-After: $network # Short-Description: Advanced IEEE 802.11 management daemon # Description: Userspace IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP # Authenticator
Recreate symlinks with
update-rc.d hostapd defaults
comment:29 in reply to: ↑ 24 ; follow-up: ↓ 32 Changed 11 years ago by stappers
Replying to stappers:
and encountered some cruft
insserv: warning: script is corrupt or invalid: /etc/init.d/../rc0.d/S03led insserv: warning: script is corrupt or invalid: /etc/init.d/../rc0.d/S99stop-led insserv: warning: script is corrupt or invalid: /etc/init.d/../rc2.d/S99stop-led-flashing insserv: warning: script is corrupt or invalid: /etc/init.d/../rc2.d/S03led insserv: warning: script is corrupt or invalid: /etc/init.d/../rc6.d/S03led insserv: warning: script is corrupt or invalid: /etc/init.d/../rc6.d/S99stop-led insserv: warning: script is corrupt or invalid: /etc/init.d/../rcS.d/S03led insserv: warning: script 'rcS.firstboot' missing LSB tags and overrides insserv: warning: script 'rcS.debian' missing LSB tags and overrides
rm /etc/rc2.d/S99stop-led-flashing rm /etc/rc{0,2,6,S}.d/S03led rm /etc/rc6.d/S99stop-led rm /etc/init.d/rcS.*i*
comment:30 Changed 11 years ago by stappers
Switch to dependency based booting
dpkg-reconfigure sysv-rc
Generate the symlinks
insserv
( probably allready done with dpkg-reconfigure sysv-rc )
comment:31 Changed 11 years ago by stappers
root@debwrt:/etc/init.d# ls /etc/rcS.d README S07hwclock.sh S12procps S01mountkernfs.sh S07ifupdown-clean S12udev-mtab S01robocfg S07module-init-tools S12urandom S02udev S07mtab.sh S13ifupdown S03mountdevsubfs.sh S08checkfs.sh S14networking S04bootlogd S09mountall.sh S15mountnfs.sh S05hdparm S10mountall-bootclean.sh S16mountnfs-bootclean.sh S05hostname.sh S11mountoverflowtmp S17bootmisc.sh S05hwclockfirst.sh S12ebtables S17screen-cleanup S06checkroot.sh S12hostapd S18stop-bootlogd-single root@debwrt:/etc/init.d#
Note that the order is robocfg, hostapd and networking
comment:32 in reply to: ↑ 29 Changed 11 years ago by stappers
Replying to stappers:
Replying to stappers:
and encountered some cruft
insserv: warning: script is corrupt or invalid: /etc/init.d/../rc0.d/S03led insserv: warning: script is corrupt or invalid: /etc/init.d/../rc2.d/S03led insserv: warning: script is corrupt or invalid: /etc/init.d/../rc6.d/S03led insserv: warning: script is corrupt or invalid: /etc/init.d/../rcS.d/S03ledrm /etc/rc{0,2,6,S}.d/S03led
Since r223 is the led stuff default not included any more.
comment:33 in reply to: ↑ 24 Changed 11 years ago by stappers
- Severity set to severity 4
comment:34 Changed 11 years ago by stappers
Does AsusWl500GPremium#PostInstall solve this ticket?
Please confirm.
comment:35 Changed 11 years ago by anonymous
I did not try this out.
But the startup order is in the correct order.
As far as i can check this out now. It seems to be working.
I did not test with the latest version - because i dont have the time right now.
comment:36 Changed 11 years ago by stappers
No worries, no hurries.
It is the quality of the feedback report that counts.
In r258 is minor change, which might be an enhancement.
comment:37 Changed 11 years ago by amain
- Owner changed from stappers to amain
- Status changed from accepted to assigned
comment:38 Changed 11 years ago by amain
- Resolution set to wontfix
- Status changed from assigned to closed
Closing, lot has changed since debwrt-net package has been added to DebWrt.
Please elaborate. What is the actual problem, besides getting several "No such device messages" for the very same eth0_wan device?