no internet with static IP in intrepid

**hahahan** · November 10th, 2008

Can you ping any hard address like $>ping 64.233.161.83?
If so it will help to add a nameserver to your /etc/resolv.conf file like

$>sudo echo "nameserver xxx.xxx.xxx.xxx" > /etc/resolv.conf .Where xxx.xxx...is the address of a valid nameserver.

**jonobr** · November 10th, 2008

Mikesmithv,

aren't a netmask of "24" and "255.255.255.0" the same thing?
Is this only presnetation or something more sinister?

**wilberfan** · November 11th, 2008

Well, I thought robertbc's post was going to do the trick! It DOES allow me to successfully set up a manual, wired connection, but when I reboot, the "Auto eth0" setting takes over again.

I've even tried DELETING the lil' *******...unchecking the automatic start box, but it rises from the dead every time, at each reboot.

What would be causing that behavior? Do I need to be making those changes as root, or...? (If so, how would I do that?)

**jamb** · November 15th, 2008

Originally Posted by waffen

The workaround is disable the NetworkManager and setup by hand the params in /etc/network/interfaces and the DNS, in my internet search I can see is a possible bad function in the NetworkManager present in the Ubuntu 8.10 Betas and not solved yet...

I had kind of weird experience, with DNS and static IP's but now it fails again with the latest upgraded Intrepid packges. Anyway in my setup I found a workaround by modifying only /etc/resolv.conf.

I have done further investigations, add the 'nameserver' directive to /etc/resolve.conf, which solved the problem in my setup.
Hardy does not have this problem...

http://ubuntuforums.org/showthread.p...42#post6186742

**mccartyj** · November 20th, 2008

namserver 192.168.1.1 (the IP of my router) worked for me. Thanks for the help!

Now does anyone know how to get CIFS to work again in 8.10?

**Roasted** · November 21st, 2008

Is static IP's officially fixed in Intrepid? Or is this still a problem?

**kevinfishburne** · November 23rd, 2008

It's still an issue as far as I can tell. Ubuntu should dump Network Manager completely and use something else. Network Manager has been terrible from the beginning in nearly every aspect. Its main problem, other than failing to provide functionality that its GUI suggests is there, is its unpredictability. Enough ranting, though. :/

I'm running a clean install of Ubuntu 8.10 Desktop AMD64, with no modifications other than installing all updates, uninstalling some unneeded apps, and modifying the exports and fstab files. My LAN has a DHCP server, but this PC is a server and needs a static IP.

While I can create additional network profiles, any modification to the default "auto eth0" profile is undone after a reboot. There appears to be no way to set a profile as default, apply any of the existing profiles, or configure hierarchy/precedence between them. It's also interesting that the Network Manager is now under the Preferences menu and doesn't require root access, which makes me think that Ubuntu uses /etc/network/interfaces pre-login and Network Manger's junk settings post-login.

Is it just me, or is this totally insane? As bad as Network Manager was in previous releases, this one seems to have a serious lack of functionality and is a step backward in many respects (lack of control and intuitiveness being the main ones). I just feel like I'm missing something obvious that will make everything better, but that feeling is slipping away as the process of elimination reveals that new Network Manager truly is worthless. :/ I'm ranting again...