BCM4321 connected but no internet

[donald]

The screenshot shows only b,g...,select "automatic 20/40 mhz" in the router wifi settings.
and because a icon does not reveal much information,.again:
If you ping your router, success y/n
ping 8.8.8.8 success y/n
which messages do you get, if any?

In Network manager disconnect wifi, open a terminal, type:
tail -f /var/log/messages > hit enter
now reconnect wifi, any suspicious messages? (in the terminal window)

[brokenman]

From a console please type: xpns-tool

This will launch the porteus network setup tool. This will verify if it is a DNS problem. It pings router, gateway and DNS during the checks.

[knixter]

Results of xpns-tool

root@porteus:~# xpns-tool
device="eth1" junk="" EXIT="_Select"
EXIT="OK"
Successfully initialized wpa_supplicant
eth1: Trying to associate with c0:56:27:ad:8c:f0 (SSID='Cisco6329' freq=2422 MHz)
eth1: Association request to the driver failed
eth1: Associated with c0:56:27:ad:8c:f0
eth1: WPA: Key negotiation completed with c0:56:27:ad:8c:f0 [PTK=CCMP GTK=CCMP]
eth1: CTRL-EVENT-CONNECTED - Connection to c0:56:27:ad:8c:f0 completed [id=0 id_str=]
Activating pns-tool settings
eth1: CTRL-EVENT-DISCONNECTED bssid=c0:56:27:ad:8c:f0 reason=3 locally_generated=1
eth1: CTRL-EVENT-TERMINATING
EXIT="OK"
root@porteus:~#

[knixter]

Results of pingroot@porteus:~# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted


root@porteus:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8 ) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted

[knixter]

I switched the router setting but "N" still doesn't show up
Results of tail -f /var/log/message
sorry for the length but I don't know what to look for

Dec 30 08:36:00 porteus NetworkManager[1241]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Dec 30 08:36:00 porteus NetworkManager[1241]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Dec 30 08:36:00 porteus NetworkManager[1241]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Dec 30 08:36:00 porteus NetworkManager[1241]: <info> (eth1): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 30 08:36:00 porteus NetworkManager[1241]: <info> Activation (eth1/wireless): connection 'Cisco6329' has security, and secrets exist. No new secrets needed.
Dec 30 08:36:00 porteus NetworkManager[1241]: <info> Config: added 'ssid' value 'Cisco6329'
Dec 30 08:36:00 porteus NetworkManager[1241]: <info> Config: added 'scan_ssid' value '1'
Dec 30 08:36:00 porteus NetworkManager[1241]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Dec 30 08:36:00 porteus NetworkManager[1241]: <info> Config: added 'psk' value '<omitted>'
Dec 30 08:36:00 porteus NetworkManager[1241]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Dec 30 08:36:00 porteus NetworkManager[1241]: <info> Config: set interface ap_scan to 1
Dec 30 08:36:00 porteus NetworkManager[1241]: <info> (eth1): supplicant interface state: inactive -> scanning
Dec 30 08:36:01 porteus NetworkManager[1241]: <info> (eth1): supplicant interface state: scanning -> associating
Dec 30 08:36:01 porteus NetworkManager[1241]: <info> (eth1): supplicant interface state: associating -> 4-way handshake
Dec 30 08:36:01 porteus NetworkManager[1241]: <info> (eth1): supplicant interface state: 4-way handshake -> completed
Dec 30 08:36:01 porteus NetworkManager[1241]: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Cisco6329'.
Dec 30 08:36:01 porteus NetworkManager[1241]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 30 08:36:01 porteus NetworkManager[1241]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Dec 30 08:36:01 porteus NetworkManager[1241]: <info> (eth1): device state change: config -> ip-config (reason 'none') [50 70 0]
Dec 30 08:36:01 porteus NetworkManager[1241]: <info> Activation (eth1) Beginning DHCPv4 transaction (timeout in 45 seconds)
Dec 30 08:36:01 porteus NetworkManager[1241]: <info> dhcpcd started with pid 1647
Dec 30 08:36:01 porteus NetworkManager[1241]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Dec 30 08:36:01 porteus dhcpcd[1647]: version 6.0.5 starting
Dec 30 08:36:01 porteus NetworkManager[1241]: <info> (eth1): DHCPv4 state changed nbi -> preinit
Dec 30 08:36:01 porteus dhcpcd[1647]: eth1: rebinding lease of 192.168.2.6
Dec 30 08:36:06 porteus dhcpcd[1647]: eth1: leased 192.168.2.6 for infinity
Dec 30 08:36:06 porteus dhcpcd[1647]: eth1: adding host route to 192.168.2.6 via 127.0.0.1
Dec 30 08:36:06 porteus dhcpcd[1647]: eth1: adding route to 192.168.2.0/24
Dec 30 08:36:06 porteus avahi-daemon[1142]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.2.6.
Dec 30 08:36:06 porteus avahi-daemon[1142]: New relevant interface eth1.IPv4 for mDNS.
Dec 30 08:36:06 porteus avahi-daemon[1142]: Registering new address record for 192.168.2.6 on eth1.IPv4.
Dec 30 08:36:06 porteus NetworkManager[1241]: <info> (eth1): DHCPv4 state changed preinit -> bound
Dec 30 08:36:06 porteus NetworkManager[1241]: <info> address 192.168.2.6
Dec 30 08:36:06 porteus NetworkManager[1241]: <info> prefix 24 (255.255.255.0)
Dec 30 08:36:06 porteus NetworkManager[1241]: <info> gateway 192.168.2.1
Dec 30 08:36:06 porteus NetworkManager[1241]: <info> nameserver '192.168.2.1'
Dec 30 08:36:06 porteus NetworkManager[1241]: <info> domain name 'Belkin'
Dec 30 08:36:06 porteus NetworkManager[1241]: <info> Activation (eth1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Dec 30 08:36:06 porteus NetworkManager[1241]: <info> Activation (eth1) Stage 5 of 5 (IPv4 Commit) started...
Dec 30 08:36:06 porteus avahi-daemon[1142]: Withdrawing address record for 192.168.2.6 on eth1.
Dec 30 08:36:06 porteus avahi-daemon[1142]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.2.6.
Dec 30 08:36:06 porteus avahi-daemon[1142]: Interface eth1.IPv4 no longer relevant for mDNS.
Dec 30 08:36:06 porteus avahi-daemon[1142]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.2.6.
Dec 30 08:36:06 porteus avahi-daemon[1142]: New relevant interface eth1.IPv4 for mDNS.
Dec 30 08:36:06 porteus avahi-daemon[1142]: Registering new address record for 192.168.2.6 on eth1.IPv4.
Dec 30 08:36:06 porteus dhcpcd[1647]: eth1: removing IP address 192.168.2.6/24
Dec 30 08:36:06 porteus dhcpcd[1647]: eth1: removing route to 192.168.2.0/24
Dec 30 08:36:07 porteus NetworkManager[1241]: <info> (eth1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Dec 30 08:36:07 porteus NetworkManager[1241]: <info> Activation (eth1) Stage 5 of 5 (IPv4 Commit) complete.
Dec 30 08:36:07 porteus NetworkManager[1241]: <info> (eth1): device state change: secondaries -> activated (reason 'none') [90 100 0]
Dec 30 08:36:07 porteus NetworkManager[1241]: <info> NetworkManager state is now CONNECTED_GLOBAL
Dec 30 08:36:07 porteus NetworkManager[1241]: <info> Policy set 'Cisco6329' (eth1) as default for IPv4 routing and DNS.
Dec 30 08:36:07 porteus NetworkManager[1241]: <info> Activation (eth1) successful, device activated.
Dec 30 08:36:07 porteus dbus[779]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Dec 30 08:36:07 porteus dbus[779]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

[donald]

Hi knixter
What i can see is that you're associated with your router but
not authenticated.
Check with:

Code: Select all

guest@localhost:~$ grep "eth1: authenticated" /var/log/messages

(Most likely, without result)
Wrong credentials / encryption key settings?
also
please post the output of

Code: Select all

root@localhost:~# route -n

and

Code: Select all

cat /etc/resolv.conf

and

Code: Select all

root@localhost:~# ifconfig eth1

thanks

[knixter]

Happy New Year, again thanks for your time
Here are the last commands

root@porteus:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
192.168.2.0 0.0.0.0 255.255.255.0 U 9 0 0 eth1
192.168.2.3 127.0.0.1 255.255.255.255 UGH 302 0 0 lo
root@porteus:~# cat /etc/resolv.conf
# Generated by NetworkManager
domain Belkin
search Belkin
nameserver 192.168.2.1
root@porteus:~# ifconfig eth1
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.3 netmask 255.255.255.0 broadcast 192.168.2.255
ether e0:91:f5:5e:b5:4b txqueuelen 1000 (Ethernet)
RX packets 40 bytes 3760 (3.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 9954
TX packets 67 bytes 4581 (4.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 base 0xc000

root@porteus:~#


I had to run grep "eth1: authenticated" /var/log/messages, without the " " marks and it generated a couple of pages, below is a sample from the end of it
(edit, rebooted as "always fresh" and this is what I got


root@porteus:~# grep eth1: authenticated /var/log/messages
grep: authenticated: No such file or directory
/var/log/messages:Jan 2 05:32:30 porteus dhcpcd[1542]: eth1: soliciting an IPv6 router
/var/log/messages:Jan 2 05:32:30 porteus dhcpcd[1542]: eth1: soliciting a DHCP lease
/var/log/messages:Jan 2 05:32:31 porteus dhcpcd[1542]: eth1: offered 192.168.2.4 from 192.168.2.1
/var/log/messages:Jan 2 05:32:36 porteus dhcpcd[1542]: eth1: leased 192.168.2.4 for infinity
/var/log/messages:Jan 2 05:32:36 porteus dhcpcd[1542]: eth1: adding host route to 192.168.2.4 via 127.0.0.1
/var/log/messages:Jan 2 05:32:36 porteus dhcpcd[1542]: eth1: adding route to 192.168.2.0/24
/var/log/messages:Jan 2 05:32:36 porteus dhcpcd[1542]: eth1: removing IP address 192.168.2.4/24
/var/log/messages:Jan 2 05:32:36 porteus dhcpcd[1542]: eth1: removing route to 192.168.2.0/24
root@porteus:~#

[aus9]

Hi

I am still none the wiser so can't help with Slackware stuff but can you explain why I sometimes see Cisco and now also Belkin.
Are you trying to connect to a Cisco or to a Belkin or do you have 2 routers and are choosing which one to connect to?

[knixter]

I have no idea why Belkin shows up, did Always fresh" boot and reran the commands and it showed the same. There is not a "Belkin" network around me at all
(edit)
I almost totally forgot, it's a Belkin router with the network renamed to Cisco.
That was done to prevent confusion when the kids showed up after we bought the new router
that shouldn't make a difference, right??

[donald]

@knixter
--> I had to run grep...without the " " marks <--
The quotes are right, i wanted to see if there is a message like this:
(Note: my wifi is wlan0, yours eth1)
root@porteus:/home/guest# grep "wlan0: authenticated" /var/log/messages
Jan 2 11:07:41 porteus kernel: [ 1049.558124] wlan0: authenticated

If you get no result the string isn't found, which in turn means you're not
authenticated.-- but why?
routing is ok
resolv.conf is ok
ifconfig looks ok
Nothing stands out to me as wrong or missing.
...I'm running out of ideas...
oh,wait:
root@porteus:/home/guest# grep "key_mgmt" /var/log/messages
do you see WPA-PSK or something different / nothing?
PSK = pre shared key.

[knixter]

This is what I got
root@porteus:~# grep "key_mgmt" /var/log/messages
Jan 2 07:51:08 porteus NetworkManager[1147]: <info> Config: added 'key_mgmt' value 'WPA-PSK'

Not sure if it's important but I am logged in as "root". It seems Porteus was installed that way

[brokenman]

Output shows the 'wl' kernel module loaded. Have you tried blacklisting this yet?

Code: Select all

mkdir -p /mnt/sdXy/porteus/rootcopy/etc/modprobe.d
echo "blacklist wl" >> /mnt/sdXy/porteus/rootcopy/etc/modprobe.d/broadcom_blacklist.conf

sdXy is you partition where porteus is installed.

Then reboot.

[knixter]

Just tried it, seemed worse then with the "wl"

root@porteus:~# dmesg | grep b43
[ 10.743050] b43-phy0: Broadcom 4321 WLAN found (core revision 11)
[ 10.757993] b43-phy0: Found PHY: Analog 5, Type 4 (N), Revision 1
[ 10.758004] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2055, Revision 4, Version 0
[ 10.767693] b43 ssb0:0: Direct firmware load for b43/ucode11.fw failed with error -2
[ 10.767718] b43 ssb0:0: Direct firmware load for b43/ucode11.fw failed with error -2
[ 10.767997] b43 ssb0:0: Direct firmware load for b43-open/ucode11.fw failed with error -2
[ 10.768022] b43 ssb0:0: Direct firmware load for b43-open/ucode11.fw failed with error -2
[ 10.768024] b43-phy0 ERROR: Firmware file "b43/ucode11.fw" not found
[ 10.768026] b43-phy0 ERROR: Firmware file "b43-open/ucode11.fw" not found

[brokenman]

Ok then I suggest updating the firmware from here:
https://www.broadcom.com/support/802.11

and blacklisting the following kernel modules:
b44 b43 b43legacy ssb brcmsmac bcma

[knixter]

That was the first place I looked for a driver ( I did recheck ), a couple of distros ago. They do not have one for my chipset listed

(edit)
14e4:4329
BCM4321