Originally Posted by NikolaiM

Sending discover...
Lease failed:
zeroconf: address selected is 169.254.173.8
zeroconf: state is Active/Announce, Link-local address 169.254.173.8
bogus packet, option fields too long: Read past the packet length when getting option 0x1 (308 >= 308)

and there are many of the above error with different options quoted instead of 0x1

then

/etc/udhcpc/default.script: exec: line 7: /etc/udhcpc/default.zeroconf: not found

then starts:

sending discover...

etc

Originally Posted by rebhana

It doesn't really fit in this thread, but since you raised the issue: vpnc worked out of the box for me, despite the above issues. After reading your description, I thought I should clean up issue 1), and I
modified the /etc/vpnc/vpnc-script so that it would no longer use the generic behavior, but the maemo one, by changing

Code:

elif [ -e /etc/osso-af-init ]; then                                        
        MODIFYRESOLVCONF=modify_resolvconf_maemo                           
        RESTORERESOLVCONF=restore_resolvconf_maemo

I also did

Code:

echo "nameserver 127.0.0.1" > /etc/resolv.conf
echo "nameserver 127.0.0.1" > /etc/vpnc/resolv.conf-backup

to have everything in order, following your previous suggestions. But after a VPN session, it now no longer returned to the state it was in before, i.e. I lost my WLAN connection despite having seemingly correct resolv.conf files (instead of emptied ones). Don't understand...

Originally Posted by egoshin

"line 7" is OK but the rest is very bad. It looks like you get a wrong data from DHCP server. For exam "bogus packet, option fields too long" points to invalid UDP packet from DHCP server...

Try connect to WLAN in some another place, please. It would be a fast test that issue is in device or in WLAN router.

EDIT: BTW, multiple "sending discover" points to somethink wrong with DHCP server or connection to it. It usualy responds on first request... may be second. But multiple ... there is a problem with WiFi network setup, and based on your description that only DNS doesn't work - the problem inside WiFi network, not in N900.

Originally Posted by egoshin

WLAN loss has nothing with DNS. You hit something else. What do you mean "loss" - your N900 disconnected WLAN? Or you just can't ping host.wlan.yourdomain because it host.wlan.youdomain
is unknown?

EDIT: Try connect VLAN again and disconnect (no modifications of any resolve.conf), it looks like it helps. Sorry, I can't setup vpnc connection now and test.

EDIT2: After second look I think it has sense to you stop debugging vpnc-script and return it to usual one or just reinstall vpnc. Sorry, but it is difficult to debug via conference thread. I had no time to do it (I use Cisco VPN from time to time, on business trip), so - please stop debugging it.

Originally Posted by jsbigs

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!