OESF Portables Forum

Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: gururise on April 08, 2006, 08:12:25 pm

Title: Dns Not Working!
Post by: gururise on April 08, 2006, 08:12:25 pm

Wireless network is working.  I am able to ping any IP address; however, DNS resolution is not working on ALTboot (direct install) image of OZ 3.5.4 of GPE.  

The strange thing is when I boot directly from flash instead of the altboot SD image, DNS works...  Any ideas?

Posted bug #824 (http://bugs.openembedded.org/show_bug.cgi?id=824)

Gururise

Collie SL-5500

Title: Dns Not Working!
Post by: paganoll on April 09, 2006, 04:34:21 am

Quote

The strange thing is when I boot directly from flash instead of the altboot SD image, DNS works...  Any ideas?
Collie SL-5500
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122355\"][{POST_SNAPBACK}][/a][/div]

I have the same problem with Opie but I have seen a "ln -s resolv.conf" (file exists) error at boot. You can add a "cp /media/ROM/etc/resolv.conf /etc" or create a new resolv.conf with "echo nameserver -your DNS server- >/etc/resolv.conf"
In Opie, then file is created configuring the network (settings) every boot.

¿Google translation? Not this time

Title: Dns Not Working!
Post by: CoreDump on April 10, 2006, 06:29:09 am

Quote

Quote

The strange thing is when I boot directly from flash instead of the altboot SD image, DNS works...  Any ideas?
Collie SL-5500
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122355\"][{POST_SNAPBACK}][/a][/div]

I have the same problem with Opie but I have seen a "ln -s resolv.conf" (file exists) error at boot. You can add a "cp /media/ROM/etc/resolv.conf /etc" or create a new resolv.conf with "echo nameserver -your DNS server- >/etc/resolv.conf"
In Opie, then file is created configuring the network (settings) every boot.

¿Google translation? Not this time
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122372\"][{POST_SNAPBACK}][/a][/div]

This has been reported for systems booted off CF or SD. While I did know that there is such a bug when booting from NFS (and I know the reason why it happens), seeing this on SD or CF boots was quite a surprise.

/etc/resolv.conf is a symlink to /var/something/resolv.conf.
As you may or may not know, /var is actually a ramdrive on most machines which gets recreated during bootup. I'll investigate and report back