Page 1 of 3 1 23
Reply
Thread Tools
dreixel is offline dreixel
2010-01-14 , 09:08
Posts: 22 | Thanked: 6 times | Joined on Dec 2009 @ Utrecht, the Netherlands
#1
(created a new thread because this wasn't noticed in the PR1.1 release thread)

After updating to 2.2009.51-1 I can no longer get any data from a WLAN WPA with PEAP MSCHAPv2 connection, which worked fine just before the update (it's even from where I downloaded the update). I can still connect fine, but not load webpages or anything. Anyone else having trouble with protected WLANs in general, or more specifically with these settings?

I don't see anything in the changelog that could justify this...
Last edited by dreixel; 2010-01-14 at 14:37.
 
AlexDT is offline AlexDT
2010-01-14 , 09:18
Posts: 58 | Thanked: 24 times | Joined on Jan 2010 @ Rotterdam - Netherlands, the
#2
I'll try when I am to school today.
Last edited by AlexDT; 2010-01-14 at 09:24.
 
dreixel is offline dreixel
2010-01-14 , 09:23
Posts: 22 | Thanked: 6 times | Joined on Dec 2009 @ Utrecht, the Netherlands
#3
Btw, this is the implementation of security chosen for eduroam at my Uni.
 
silviumc is offline silviumc
2010-01-14 , 09:44
Posts: 25 | Thanked: 13 times | Joined on Jan 2010 @ Bucharest, Romania
#4
I have a different problem, but still related to networking. Does this update install any kind of firewall? I'm a bit of a noob with N900.. I see there's no iptables on it to list firewall rules.

Can someone check if USB networking works as before the update?
I have this problem:
The device does not respond to pings anymore, neither on the IP associated to the USB interface (192.168.2.15) nor to localhost (127.0.0.1).
What works are pings to the PC (192.168.2.14) from the device.
 

The Following User Says Thank You to silviumc For This Useful Post:
Ph0b is offline Ph0b
2010-01-14 , 09:57
Posts: 10 | Thanked: 5 times | Joined on Oct 2009 @ Paris
#5
I'm using a WLAN WPA with PEAP MSCHAPv2 connection without any issue here. And I have already flashed my device with the PR 1.1 release.
 
spanner's Avatar
spanner is offline spanner
2010-01-14 , 09:58
Posts: 253 | Thanked: 184 times | Joined on Nov 2009 @ Bristol, UK
#6
Originally Posted by silviumc View Post
The device does not respond to pings anymore, neither on the IP associated to the USB interface (192.168.2.15) nor to localhost (127.0.0.1).
What works are pings to the PC (192.168.2.14) from the device.
Apologies to all for replying to an off-topic post. But did you try (in an xterm):

cat /proc/sys/net/ipv4/icmp_echo_ignore_all

I don't have PR1.1 yet, but in the 2009.44 firmware this was set to '0', meaning "respond to pings".
If you see a value of '1' it means that ping responses have been intentionally disabled.
Last edited by spanner; 2010-01-14 at 10:03.
 

The Following User Says Thank You to spanner For This Useful Post:
silviumc is offline silviumc
2010-01-14 , 10:13
Posts: 25 | Thanked: 13 times | Joined on Jan 2010 @ Bucharest, Romania
#7
Yes, that was it, /proc/sys/net/ipv4/icmp_echo_ignore_all is now 1.

Sorry, for the offtopic question, I thought it was related to the subject. Your answer proves that is wasn't. Thanks.
 
dreixel is offline dreixel
2010-01-14 , 14:36
Posts: 22 | Thanked: 6 times | Joined on Dec 2009 @ Utrecht, the Netherlands
#8
Update: it's not only for PEAP, it's all WLAN in general, there is no DNS. Seems to be the same as in http://talk.maemo.org/showthread.php?t=40425.

This solution worked for me: http://talk.maemo.org/showpost.php?p...0&postcount=43
Last edited by dreixel; 2010-01-14 at 14:44.
 

The Following User Says Thank You to dreixel For This Useful Post:
AlexDT is offline AlexDT
2010-01-14 , 17:25
Posts: 58 | Thanked: 24 times | Joined on Jan 2010 @ Rotterdam - Netherlands, the
#9
I just checked at school. No poblem.
 
eezo is offline eezo
2010-01-17 , 22:14
Posts: 22 | Thanked: 6 times | Joined on Dec 2009
#10
I have a similar issue with WPA2, PEAP and MSCHAPv2. Whatever I try, it just doesn't seem to work out. It looks like my N900 just disconnects itself for some reason. The only thing I see is a message about some failed authenticating, which imho is not what's in the logs:

[18397.719909] wl1251: 154 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[18397.720275] wl1251: firmware booted (Rev 6.0.4.156)
[18398.985534] wl1251: down
[18402.637023] gprs0: detached
[18411.649353] wl1251: 154 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[18411.665008] wl1251: firmware booted (Rev 6.0.4.156)
[18412.868347] wl1251: down
[18415.782104] wl1251: 154 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[18415.797851] wl1251: firmware booted (Rev 6.0.4.156)
[18416.470642] wlan0: authenticate with AP <MACid>
[18416.473571] wlan0: authenticated
[18416.473602] wlan0: associate with AP <MACid>
[18416.477783] wlan0: RX AssocResp from <MACid> (capab=0x431 status=0 aid=17)
[18416.477783] wlan0: associated
[18417.536193] wlan0: roaming signal from driver, sending LOWSIGNAL
[18418.662567] wlan0: roaming signal from driver, sending HIGHSIGNAL
[18420.043060] wlan0: deauthenticating by local choice (reason=3)
[18420.290283] wl1251: down
 
Reply
Page 1 of 3 1 23

« Previous Thread | Next Thread »

 
Forum Jump


All times are GMT. The time now is 06:36.

Contact Us - Home - Archive - Top