Active Topics

 


Reply
Thread Tools
Posts: 3,428 | Thanked: 2,856 times | Joined on Jul 2008
#51
Originally Posted by noobmonkey View Post
Screw criptic - i can figure it out lol! - downloading it on 2g now!!
You don't need to download VI.. it's already on your device.

Just start with:

Code:
vi /etc/maemo-dhcp.d/60_vpnc
Use "i" to enter insert mode. Then paste his code into it. Then press ESC. Then Shift+ZZ.
__________________
If I've helped you or you use any of my packages feel free to help me out.
-----------------------------------------------------------------------------------
Maintaining:
pyRadio - Pandora Radio on your N900, N810 or N800!
 

The Following User Says Thank You to fatalsaint For This Useful Post:
Posts: 75 | Thanked: 41 times | Joined on Jan 2010 @ Suffolk, UK
#52
I thought I had te same error. I updated whilst at work on my lunch break but once home I couldn't connect to my home network. I deleted it, re-booted and setup the wifi again but still no joy.... that is, until i noticed my battery was quite low. I connected the phone into my laptop to charge (note, the laptop was currently connected to my home wifi perfectly!!) and then while it was charging I tried to connect again and this time, it connected fine. Once the phone was more than half charged, I removed the USB cable, disconnected from the wifi, and then tried to connect again. It did.
I'm wondering maybe some functions are disabled if battery is just too low? If not, then maybe just an odd little issue!
 
Posts: 172 | Thanked: 27 times | Joined on Oct 2009 @ San Francisco, CA
#53
Okay, per this thread:

http://talk.maemo.org/showthread.php...288#post470288

I removed vpnc gui and vpnc (didn't need it as I got OpenVPN to work), then went through the following steps:

1. Install 'rootsh' package
2. Open X Terminal
3. Enter 'sudo gainroot'
4. Enter 'mv /etc/udhcpc/libicd_network_ipv4.script.dpkg-dist /etc/udhcpc/libicd_network_ipv4.script'

rebooted, re-connected to LAN and...back in business!! Thank you Maemo community!

And regarding my fear of flashing and voiding my warranty, it was moot anyway as I've reflashed a couple of times earlier trying to get Knots2 working.

Cheers!
 

The Following 4 Users Say Thank You to jsbigs For This Useful Post:
Posts: 25 | Thanked: 87 times | Joined on Nov 2009
#54
Originally Posted by villo View Post
I think we can safely presume there is going to be another update at some point in the future...
Villo, I think you should learn to flash your device if you play with software from development repository:
http://wiki.maemo.org/Updating_the_tablet_firmware
 
Posts: 23 | Thanked: 5 times | Joined on Jan 2010 @ bay area ca
#55
I am having the same problem. Update went fine but when try to connect to wifi which was working before is not working. Tried several othe APs same issue. Tried rebooting, removing the battery it says unable to connect one or other account. Gmail/Gtalk does not work , skype says it is online.
Other issue : When I try to restore setting to original facotry setting says enter unlock code. I did not set this int he first place. I used ATT sim in the Nokia. How in the hell this release passed. Nokia is really testing the paitence of their loyals by screwing like this.
Any solution please?
 
Posts: 152 | Thanked: 41 times | Joined on Dec 2009 @ Sydney
#56
I had a wifi problem too. I thought it was just me and concluded I must have edited /etc/dnsmasq.conf and thus the upgrade didn't overwrite that file cause it had changed, but I needed the changes it seems.

http://talk.maemo.org/showthread.php?t=40425

In a nut shell.

The N900 uses dnsmasq [why a small devices uses a DNS/DHCP server designed for servers is beyond me]
And in it's config it lists it's resolv files it uses to look up DNS servers.

So with that, let's see what dnsmasq wants to look up

Code:
Nokia-N900-42-11:~# grep resolv /etc/dnsmasq.conf
# somewhere other that /etc/resolv.conf
resolv-file=/var/run/resolv.conf
resolv-file=/tmp/resolv.conf.wlan0
resolv-file=/tmp/resolv.conf.ppp0
resolv-file=/tmp/resolv.conf.lo
resolv-file=/tmp/resolv.conf.gprs
# /etc/resolv.conf
# If you don't want dnsmasq to read /etc/resolv.conf or any other
#no-resolv
# If you don't want dnsmasq to poll /etc/resolv.conf or other resolv\
Right cool. I know from experience, before the update that the /tmp/resolv* files were created when a connection was made. So let's have a look at those files, they should list an IP of your DNS server.


Code:
Nokia-N900-42-11:~# cat /tmp/resolv*
cat: can't open '/tmp/resolv*': No such file or directory.
Hmmmm that is odd, the update has changed things...

Let's try the other file, it must using that now....

Code:
Nokia-N900-42-11:~# cat /var/run/resolv.conf
cat: can't open '/var/run/resolv.conf': No such file or directory.

Oh dear. We have a problem Houston.

Code:
Nokia-N900-42-11:~# ls /var/run/resolv*
/var/run/resolv.conf.wlan0
Hmmmm bugger.

Ok to fix this we need to tell dnsmasq about this.
Change the below in /etc/dnsmasq.conf from:

Code:
# somewhere other that /etc/resolv.conf
resolv-file=/var/run/resolv.conf
resolv-file=/tmp/resolv.conf.wlan0
resolv-file=/tmp/resolv.conf.ppp0
resolv-file=/tmp/resolv.conf.lo
resolv-file=/tmp/resolv.conf.gprs
To:

Code:
# somewhere other that /etc/resolv.conf
resolv-file=/var/run/resolv.conf
resolv-file=/var/run/resolv.conf.wlan0
resolv-file=/var/run/resolv.conf.ppp0
resolv-file=/var/run/resolv.conf.lo
resolv-file=/var/run/resolv.conf.gprs
resolv-file=/tmp/resolv.conf.wlan0
resolv-file=/tmp/resolv.conf.ppp0
resolv-file=/tmp/resolv.conf.lo
resolv-file=/tmp/resolv.conf.gprs
And restart dnsmasq

Code:
/etc/init.d/dnsmasq restart
Now it all should be working.
You are done. For anyone curious more about this.....



I dug around and found the culprit.

I first checked the dhcp client.

Code:
Nokia-N900-42-11:~#grep var  /etc/udhcpc/*
/etc/udhcpc/default.bound:RESOLV_CONF="/var/run/resolv.conf"
/etc/udhcpc/default.renew:RESOLV_CONF="/var/run/resolv.conf"
Hmm mthat looks right.

Digging further into it configs dir I found:

Code:
/etc/udhcpc/libcd_network_ipv4.script
Which references /etc/maemo-dhcp.d/


Code:
Nokia-N900-42-11:~# grep -i resolv /etc/maemo-dhcp.d/50_ipv4_network_setup
RESOLV_CONF="/var/run/resolv.conf.$interface"
          if egrep "^nameserver[\t ]*${ns}" $RESOLV_CONF > /dev/null
              echo -n > $RESOLV_CONF.tmp
              [ -n "$domain" ] && echo domain $domain >> $RESOLV_CONF.tmp
                echo nameserver $i >> $RESOLV_CONF.tmp
              mv $RESOLV_CONF.tmp $RESOLV_CONF


This is the issue:
Code:
RESOLV_CONF="/var/run/resolv.conf.$interface"
Had it been:

Code:
RESOLV_CONF="/var/run/resolv.conf"
We would be fine, but then concurrent connections may argue over the same file and corrupt it.

So where does this come from:

Code:
Nokia-N900-42-11:~# dpkg -S /etc/maemo-dhcp.d/50_ipv4_network_setup
libicd-network-ipv4: /etc/maemo-dhcp.d/50_ipv4_network_setup
Which looking at its description is a core package for the udhcp client.
 

The Following 3 Users Say Thank You to DaveQB For This Useful Post:
Posts: 23 | Thanked: 5 times | Joined on Jan 2010 @ bay area ca
#57
Any update on this? Is there a workaround or fix for this?

Thanks.
 
Posts: 152 | Thanked: 41 times | Joined on Dec 2009 @ Sydney
#58
I remember editing my /etc/dnsmasq.conf file, so dpkg would not have overwritten it as it was not the same file that was originally there.

I found a /etc/dnsmasq.conf.dpkg-dist file that was correct with the resolv lines.
Anyone with my issue can simply copy it over.
 
Posts: 23 | Thanked: 5 times | Joined on Jan 2010 @ bay area ca
#59
There seems to be a no solution to this problem as I resetted to the factory setting (BTW it still keeps the user data ) and still no change in wifi behaviour. I was not active member of the maemo community and now I became member to log this issue. Is there any maemo expert who can help on this to really enable the wireless back on this device. Thank you very much.
 
Posts: 116 | Thanked: 147 times | Joined on Jan 2010
#60
Originally Posted by jsbigs View Post
Okay, per this thread:

http://talk.maemo.org/showthread.php...288#post470288

I removed vpnc gui and vpnc (didn't need it as I got OpenVPN to work), then went through the following steps:

1. Install 'rootsh' package
2. Open X Terminal
3. Enter 'sudo gainroot'
4. Enter 'mv /etc/udhcpc/libicd_network_ipv4.script.dpkg-dist /etc/udhcpc/libicd_network_ipv4.script'

rebooted, re-connected to LAN and...back in business!! Thank you Maemo community!

And regarding my fear of flashing and voiding my warranty, it was moot anyway as I've reflashed a couple of times earlier trying to get Knots2 working.

Cheers!
I too could not browse the web through my home wifi after the update. Narrowed it down to DNS resolution problem before coming here because I could browse by IP. I had previously installed/uninstalled vpnc prior to the update, and the above solution worked for me. Thanks. (extras , ahh!!!!!)

@DaveQB: I ran through the checks you walked through, and my /etc/dnsmasq.conf was good after the update and didn't need the changes you indicated, so I tried the above solution.
 
Reply


 
Forum Jump


All times are GMT. The time now is 22:02.