No static IP on Ubuntu Intrepid 8.10

Bug #292824 reported by jokker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After upgrading from Hardy to Intrepid, /etc/network/interfaces was ignored, no matter what I tried, this file was ignored by Intrepid. I ended with a dynamic IP address. I thought it was related to the upgrade, so I reinstall everything and kept my /home. Same problem, no static IP possible but this time /etc/network/interfaces was empty, only the loopback was present, but I still had connection / internet through dhcp. This particular machine and 2 others MUST be in static IP (I only use dhcp on my 2 laptops). So I edited /etc/network/interfaces like this:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address 192.168.0.22
        netmask 255.255.255.0
        network 192.168.0.0
        broadcast 192.168.0.255
        gateway 192.168.0.1

auto eth1
iface eth1 inet static
        address 192.168.0.21
        netmask 255.255.255.0
        network 192.168.0.0
        broadcast 192.168.0.255
        gateway 192.168.0.1

But after a reboot (to test the settings completely) no access to internet, though I could still ping the router, DNS I thought!

I edited /etc/resolv.conf, but everything was already there !!!!!:

# Generated by NetworkManager
nameserver 68.105.28.12
nameserver 68.105.29.12
nameserver 68.105.28.11

(checked and compared to my modem interface, these above are OK DNS IPs)

I tried to remove NetworkManager from rc.d but it did not change anything, so I restore NetworkManager defaults in rc.d

So at this point I had the correct IP settings, but no DNS working... Seemed like this time /etc/network/interfaces was no longer ignored but /etc/resolv.conf now is !!!!!

So right now I'm back to DHCP, I commented all about eth0 and eth1 in /etc/network/interfaces and restarted... Everything works beside the fact that I have wrong IP addresses for both NICs.

I feel like I'm going crazy, I spent the last 72 hours practically day and night on this, I NEED THIS MACHINE TO WORK since I use it as a server (ssh, apache, ftp, VPN, samba, cups, NFS) and guess what... Everything is setup with IP, not hostnames... That means all the servers are down. So far this is the worst experience I had with Ubuntu, "the number one distro" people say...

Thanks for your help

description: updated
Revision history for this message
Daniel Hollocher (chogydan) wrote :

try removing the package network-manager*

I think there are problems with nm and static ips.

Revision history for this message
jokker (david-las-solanas) wrote :

I thank you for your help but that was a very very bad idea, let me explain...
After sudo aptitude remove network-manager*, I uncommented all about eth0 and eth1 in my very good interfaces file then rebooted... NO internet, no dns, but eth0 and eth1 worked and had correct static IPs, so no change... I tried to reinstall network-manager but without DNS I had to download it for another machine, a laptop with Sabayon Linux (very good distro byt the way) and then reinstall it through scp to go back to zero, so you can scratch that solution, it does not do any good.

Revision history for this message
jokker (david-las-solanas) wrote :

EDIT=
If you have wrong IP setting, it seems like you need to enter them manually in system - preferences - network connection... then in the nm-applet on the top bar right click on it and uncheck "enable connection" then recheck it: IT WORKS as long as you do not restart your machine. For some reason it works better than # /etc/init.d/networking restart or even # ifup ethx
That's my solution for now, I hope to get a fix very soon.

description: updated
Revision history for this message
Daniel Hollocher (chogydan) wrote :

well, you could have just set your interfaces back to dhcp again, couldn't you? Anyway, sorry that you are having so much trouble.

personally, I think you should go back to hardy. Anyway, good luck.

Revision history for this message
jokker (david-las-solanas) wrote :

If I go back to DHCP my IP address will be *.51 or *.52 I set only 2 IPs for dhcp and they are for my laptops, and no I do not want to change all my router's settings, because then I will have to change a lot more things on all my stations (and even more than that). This machine must be *.22 It's a long story... I think I will go back to hardy because this is really a mess and I have a backup, but I still want to give it a try, Intrepid "looks" good. Thank for your help.
Is there anybody working on this bug already? How can I know?

Revision history for this message
jokker (david-las-solanas) wrote :

Any news on this ?

Revision history for this message
jokker (david-las-solanas) wrote :

I'm now sure this bug comes for the new network-manager that comes with Ubuntu Intrepid 8.10
But I can't find a way to fix it.

description: updated
Revision history for this message
Alexander Sack (asac) wrote :

I think this is rather a question than a bug?

static interfaces are supported in general. there are a few bugs surrounding auto startup and configuring them as system connections open. However, things in /etc/network/interfaces are not managed by NM, so when those dont come up its a different issue.

Changed in network-manager:
status: Confirmed → Invalid
Revision history for this message
jokker (david-las-solanas) wrote :

This is not a question but a bug which, by the way, just got fixed with the last kernel update !

Revision history for this message
jokker (david-las-solanas) wrote :

Not fixed, and I repeat, this is NOT a question. I uninstalled network-manager and edited interfaces, because I need a bridge with 4 virtual interfaces. I still do not have DNS working, resolv.conf is properly edited as well

Revision history for this message
asacbug (asacbug) wrote :

/etc/NetworkManager/nm-system-settings.conf

please attach that.

Revision history for this message
jokker (david-las-solanas) wrote :

I do not even have a /etc/NetworkManager folder. Please keep in mind that I completely purged this crappy application

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.