Wireless network no IP [RESOLVED]

Rintse

rastus wrote
Rintse wrote2 hours 0% though...
I only just gave it to you, is 2 hours the estimated time to complete? I just ran a scan using that program, took just under 2 minutes. It found six (6) network devices on my network.

Came across the programme on fora 2 hours ago and started running it. Got google plus to prevent getting this forum from getting cluttered?

rastus

Rintse wroteCame across the programme on fora 2 hours ago and started running it. Got google plus to prevent getting this forum from getting cluttered?

Stop it and start it again, it should not take that long.... minutes at most on a home network. I do not know what 'google plus' is. I think.... from looking at the pics you posted, that there is a network problem your end. I don't know exactly what it is right now. I don't think it's the Pi itself.

rastus

I'm just going to turn my router off and run that scanner, BRB.

Back.... like I thought the scan took minutes using information from my PC's network card, nothing from the network. I have to say... network problem your end. Check the configuration of the laptop's wireless card is correct.

Rintse

rastus wroteStop it and start it again, it should not take that long....

I reinstalled the program, ran the portable version, they all seem to take ages. I just tried installing volumio on my Pi again and that works fine. I can get a wireless connection and then access the pi through entering the ip adress.

Have you got any preferred chat services to use then, in response to the google plus thing?

rastus

Rintse wroteI reinstalled the program, ran the portable version, they all seem to take ages. I just tried installing volumio on my Pi again and that works fine. I can get a wireless connection and then access the pi through entering the ip adress.

Have you got any preferred chat services to use then, in response to the google plus thing?

Mmmmmm.... strange. Must be something to do with the Rune software... maybe a older version, maybe?

PS: Chat... not really, haven't used a chat for years.
PSS: I'm not too good with Linux, so you may have to wait for a more experienced Linux user to come along.

Rintse

rastus wrote PS: Chat... not really, haven't used a chat for years.

This should be easily accessible:

https://chatstep.com/#Hifiberry
No password

rastus

One thought.... are you using a Raspberry Pi 3? I've read they have problems with the internal wireless connection.

Rintse

rastus wroteOne thought.... are you using a Raspberry Pi 3? I've read they have problems with the internal wireless connection.

Nope. I have a 2 running 0.4

rastus

Frank (hondagx35) will come along in a few hours and figure this out (in less time than I've taken), I'll be watching this space. If you figure it out yourself, please come back and tell me what the problem was Rintse. Sorry I couldn't be of more help.

Rintse

rastus wroteFrank (hondagx35) will come along in a few hours and figure this out (in less time than I've taken), I'll be watching this space. If you figure it out yourself, please come back and tell me what the problem was Rintse. Sorry I couldn't be of more help.

Absolutely no problem! A massive thank you for your time anyway. I'll keep messing about!

Rintse

Rintse wrote
rastus wroteFrank (hondagx35) will come along in a few hours and figure this out (in less time than I've taken), I'll be watching this space. If you figure it out yourself, please come back and tell me what the problem was Rintse. Sorry I couldn't be of more help.
Absolutely no problem! A massive thank you for your time anyway. I'll keep messing about!

Just tried flashing v0.3 again and this time I can get a connection set up. I would still like to be on the latest version though..

Rintse

Just to create some order out of the chaos that is this thread:

I'm running runeaudio v0.4 on a raspberry Pi 2.
I ran volumio for multiple weeks.
I can get everything set up on cable.
I can set up a connection through the web interface.
I don't get an IP from the router on the wireless connection.
The web interface gives me this overview:

Name: wlan0
Type: wireless
Status: connected
Associated SSID: Ziggo89289
Assigned IP: none
Speed: 72 Mb/s

I still don't get an IP when I assign one manually. (I double checked the default gateway etc.)
I can ping my wired connection.
I can not ping the wireless connection.
I can not tracert the wireless connection.
I am able to get a working wireless connection on v0.3.

hondagx35

Hi Rintse,

Rintse wroteName: wlan0
Type: wireless
Status: connected
Associated SSID: Ziggo89289
Assigned IP: none
Speed: 72 Mb/s

This doesn't you anything.
What about posting your debug data as mentioned on the "Post a reply" page?

I have multiple devices (RP2 and RP3) running on wifi only without any issues.
So it seems to work in general.

To get even more debug information you can try to search the journal:

journalctl

Frank

Rintse

hondagx35 wroteWhat about posting your debug data as mentioned on the "Post a reply" page?

Fresh install -> set up wifi network (still no ip) -> reboot -> debug

http://pastebin.com/qVmLayK7

Rintse

hondagx35 wroteTo get even more debug information you can try to search the journal:

journalctl

I don't know what's relevant here, so here's the entire thing.
http://pastebin.com/bB8nnxxk

hondagx35

Hi Rintse,

from the logs i can see that the driver and firmware get loaded.
The only thing you should mention is that these RTL dongles are not well supported by linux.

[ 6.832546] r8712u: module is from the staging directory, the quality is unknown, you have been warned.

Please check:

systemctl status netctl-auto@wlan0

and also try

systemctl restart netctl-auto@wlan0
systemctl status netctl-auto@wlan0
journalctl -u netctl-auto@wlan0

Frank

Rintse

It all works fine on other versions and other players like volumio, I suppose my adapter could be unstable, but it's not like its impossible to get it to work.

hondagx35 wrote

systemctl status netctl-auto@wlan0

Frank

gives:

netctl-auto@wlan0.service - Automatic wireless network connection using netctl profiles
Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2016-04-29 21:25:46 CEST; 51s ago
Docs: man:netctl.special(7)
CGroup: /system.slice/system-netctl\x2dauto.slice/netctl-auto@wlan0.service
└─1661 wpa_supplicant -q -B -P /run/wpa_supplicant_wlan0.pid -i wlan0 -D nl80211,wext -c/run/network/wpa_supplicant_wlan0.conf -W

Apr 29 21:25:46 runeaudio systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Apr 29 21:25:46 runeaudio netctl-auto[1642]: Included profile 'Jabba the Hutt'
Apr 29 21:25:46 runeaudio netctl-auto[1642]: Included profile 'Ziggo89289'
Apr 29 21:25:46 runeaudio wpa_actiond[1663]: Starting wpa_actiond session for interface 'wlan0'
Apr 29 21:25:46 runeaudio systemd[1]: Started Automatic wireless network connection using netctl profiles.

After restart, nothing seems to change in that.

I don't know what to do with the other command.

hondagx35

Hi,

It all works fine on other versions and other players like volumio, I suppose my adapter could be unstable, but it's not like its impossible to get it to work.

The older versions and volumio use different kernels.

I don't know what to do with the other command.

Execute it in the console and post the output.
Mine looks like this:

root@runeaudio(ro):~# journalctl -u netctl-auto@wlan0
-- Logs begin at Mon 2016-02-22 15:40:15 CET, end at Fri 2016-04-29 22:47:07 CEST. --
Feb 22 15:40:17 runeaudio systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Feb 22 15:40:17 runeaudio netctl-auto[229]: Included profile 'NETGEAR'
Feb 22 15:40:17 runeaudio netctl-auto[229]: Included profile 'SpeedportDG6NDH'
Feb 22 15:40:18 runeaudio wpa_actiond[287]: Starting wpa_actiond session for interface 'wlan0'
Feb 22 15:40:18 runeaudio systemd[1]: Started Automatic wireless network connection using netctl profiles.
Feb 22 15:40:20 runeaudio wpa_actiond[287]: Interface 'wlan0' connected to network 'NETGEAR'
Feb 22 15:40:20 runeaudio dhcpcd[355]: DUID 00:01:00:01:1c:72:2b:ea:06:92:c5:a0:0d:d6
Feb 22 15:40:20 runeaudio dhcpcd[355]: wlan0: IAID 02:c5:d1:f0
Feb 22 15:40:21 runeaudio dhcpcd[355]: wlan0: rebinding lease of 192.168.0.40
Feb 22 15:40:21 runeaudio dhcpcd[355]: wlan0: probing address 192.168.0.40/24
Feb 22 15:40:25 runeaudio dhcpcd[355]: wlan0: leased 192.168.0.40 for 864000 seconds
Feb 22 15:40:25 runeaudio dhcpcd[355]: wlan0: adding route to 192.168.0.0/24
Feb 22 15:40:25 runeaudio dhcpcd[355]: wlan0: adding default route via 192.168.0.1
Feb 22 15:40:26 runeaudio dhcpcd[355]: forked to background, child pid 553

You can see the dhcpcd service which gets the IP address from the router.

Frank

Rintse

hondagx35 wroteExecute it in the console and post the output.

Oh I must have copied it wrongly somehow, I didn't get output last time.

Mine says this:

-- Logs begin at Mon 2016-02-22 15:40:16 CET, end at Sat 2016-04-30 15:27:42 CEST. --
Feb 22 15:40:17 runeaudio systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Feb 22 15:40:18 runeaudio netctl-auto[205]: Included profile 'Jabba the Hutt'
Feb 22 15:40:18 runeaudio netctl-auto[205]: Included profile 'Ziggo89289'
Feb 22 15:40:19 runeaudio wpa_actiond[261]: Starting wpa_actiond session for interface 'wlan0'
Feb 22 15:40:19 runeaudio systemd[1]: Started Automatic wireless network connection using netctl profiles.
Apr 30 15:22:13 runeaudio systemd[1]: Stopping Automatic wireless network connection using netctl profiles...
Apr 30 15:22:13 runeaudio netctl-auto[1032]: /usr/bin/netctl-auto: line 222: kill: (261) - No such process
Apr 30 15:22:15 runeaudio systemd[1]: Stopped Automatic wireless network connection using netctl profiles.
Apr 30 15:22:15 runeaudio systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Apr 30 15:22:15 runeaudio netctl-auto[1058]: Included profile 'Jabba the Hutt'
Apr 30 15:22:15 runeaudio netctl-auto[1058]: Included profile 'Ziggo89289'
Apr 30 15:22:15 runeaudio wpa_actiond[1081]: Starting wpa_actiond session for interface 'wlan0'
Apr 30 15:22:15 runeaudio systemd[1]: Started Automatic wireless network connection using netctl profiles.
Apr 30 15:25:04 runeaudio systemd[1]: Stopping Automatic wireless network connection using netctl profiles...
Apr 30 15:25:04 runeaudio netctl-auto[1190]: /usr/bin/netctl-auto: line 222: kill: (1081) - No such process
Apr 30 15:25:05 runeaudio systemd[1]: Stopped Automatic wireless network connection using netctl profiles.
Apr 30 15:25:05 runeaudio systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Apr 30 15:25:05 runeaudio netctl-auto[1219]: Included profile 'Jabba the Hutt'
Apr 30 15:25:05 runeaudio netctl-auto[1219]: Included profile 'Ziggo89289'
Apr 30 15:25:06 runeaudio wpa_actiond[1240]: Starting wpa_actiond session for interface 'wlan0'
Apr 30 15:25:06 runeaudio systemd[1]: Started Automatic wireless network connection using netctl profiles.
Apr 30 15:26:32 runeaudio systemd[1]: Stopping Automatic wireless network connection using netctl profiles...
Apr 30 15:26:32 runeaudio netctl-auto[1308]: /usr/bin/netctl-auto: line 222: kill: (1240) - No such process
Apr 30 15:26:33 runeaudio systemd[1]: Stopped Automatic wireless network connection using netctl profiles.
Apr 30 15:26:33 runeaudio systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Apr 30 15:26:33 runeaudio netctl-auto[1335]: Included profile 'Jabba the Hutt'
Apr 30 15:26:33 runeaudio netctl-auto[1335]: Included profile 'Ziggo89289'
Apr 30 15:26:34 runeaudio wpa_actiond[1359]: Starting wpa_actiond session for interface 'wlan0'
Apr 30 15:26:34 runeaudio systemd[1]: Started Automatic wireless network connection using netctl profiles.
lines 8-30/30 (END)
Apr 30 15:22:13 runeaudio netctl-auto[1032]: /usr/bin/netctl-auto: line 222: kill: (261) - No such process
Apr 30 15:22:15 runeaudio systemd[1]: Stopped Automatic wireless network connection using netctl profiles.
Apr 30 15:22:15 runeaudio systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Apr 30 15:22:15 runeaudio netctl-auto[1058]: Included profile 'Jabba the Hutt'
Apr 30 15:22:15 runeaudio netctl-auto[1058]: Included profile 'Ziggo89289'
Apr 30 15:22:15 runeaudio wpa_actiond[1081]: Starting wpa_actiond session for interface 'wlan0'
Apr 30 15:22:15 runeaudio systemd[1]: Started Automatic wireless network connection using netctl profiles.
Apr 30 15:25:04 runeaudio systemd[1]: Stopping Automatic wireless network connection using netctl profiles...
Apr 30 15:25:04 runeaudio netctl-auto[1190]: /usr/bin/netctl-auto: line 222: kill: (1081) - No such process
Apr 30 15:25:05 runeaudio systemd[1]: Stopped Automatic wireless network connection using netctl profiles.
Apr 30 15:25:05 runeaudio systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Apr 30 15:25:05 runeaudio netctl-auto[1219]: Included profile 'Jabba the Hutt'
Apr 30 15:25:05 runeaudio netctl-auto[1219]: Included profile 'Ziggo89289'
Apr 30 15:25:06 runeaudio wpa_actiond[1240]: Starting wpa_actiond session for interface 'wlan0'
Apr 30 15:25:06 runeaudio systemd[1]: Started Automatic wireless network connection using netctl profiles.
Apr 30 15:26:32 runeaudio systemd[1]: Stopping Automatic wireless network connection using netctl profiles...
Apr 30 15:26:32 runeaudio netctl-auto[1308]: /usr/bin/netctl-auto: line 222: kill: (1240) - No such process
Apr 30 15:26:33 runeaudio systemd[1]: Stopped Automatic wireless network connection using netctl profiles.
Apr 30 15:26:33 runeaudio systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Apr 30 15:26:33 runeaudio netctl-auto[1335]: Included profile 'Jabba the Hutt'
Apr 30 15:26:33 runeaudio netctl-auto[1335]: Included profile 'Ziggo89289'
Apr 30 15:26:34 runeaudio wpa_actiond[1359]: Starting wpa_actiond session for interface 'wlan0'
Apr 30 15:26:34 runeaudio systemd[1]: Started Automatic wireless network connection using netctl profiles.

for convenience:
http://pastebin.com/wDWhHUJd

hondagx35

Hi,

in your log files is nothing special to see.

Last thing you can try is:

dhcpcd

root@runeaudio(ro):~# dhcpcd
dev: loaded udev
DUID 00:01:00:01:1c:72:2b:ea:06:92:c5:a0:0d:d6
wlan0: IAID 02:c5:d1:f0
eth0: waiting for carrier
wlan0: soliciting a DHCP lease
wlan0: offered 192.168.0.40 from 192.168.0.1
wlan0: leased 192.168.0.40 for 864000 seconds
wlan0: changing route to 192.168.0.0/24
wlan0: changing default route via 192.168.0.1
forked to background, child pid 3747

I would try an other wifi dongle.

Frank

« Previous Page Next Page »