cannot get connectivity using /etc/network/interfaces

Adding /var/log/syslog

This somehow is different that the Syslog shown above.

lemme reformat it so its more readable.

The most interesting ones I guess are the one with SCPlugin-Ifupdown shown

and this one is the most telling

Oct 22 20:03:05 Mugglewille-desktop nm-system-settings: SCPlugin-Ifupdown: No dns-nameserver configured in /etc/network/interfaces

If you want can try putting some more random dns-nameserver in /etc/network/interfaces.

sorry for the double-post as far as syslog is concerned, for the last time I had forgot to give extension, I thought it would make it format it right, apparently it doesn't :(

had a talk with Asac, most probably thought it was just a spelling mistake so changed it from 'dns-nameserver' to 'dns-nameservers' as well.

auto lo
iface lo inet loopback

auth eth1
iface eth1 inet static
    address 192.168.1.3
    netmask 255.255.255.0
    gateway 192.168.1.1
    dns-nameservers 192.168.1.1

Also tried changing dns-nameservers to 61.1.96.69, 61.1.96.71 but still no go.

Then did the sudo killall nm-system-settings

In fact trying to ping 192.168.1.1 gives me the following :-

$ ping -c5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 169.254.4.102 icmp_seq=1 Destination Host Unreachable
From 169.254.4.102 icmp_seq=2 Destination Host Unreachable
From 169.254.4.102 icmp_seq=3 Destination Host Unreachable
From 169.254.4.102 icmp_seq=4 Destination Host Unreachable
From 169.254.4.102 icmp_seq=5 Destination Host Unreachable

$ ping -c5 192.168.1.3
PING 192.168.1.3 (192.168.1.3) 56(84) bytes of data.
From 169.254.4.102 icmp_seq=1 Destination Host Unreachable
From 169.254.4.102 icmp_seq=2 Destination Host Unreachable
From 169.254.4.102 icmp_seq=3 Destination Host Unreachable
From 169.254.4.102 icmp_seq=4 Destination Host Unreachable
From 169.254.4.102 icmp_seq=5 Destination Host Unreachable

This is the same result with both the dns-nameservers.

So the only way is to do nm do whatever it wants to do. :(

is this fixed for you now in karmic?

Hi Alex,
 I still had to run around to get this fixed in karmic. It is fixed for now but don't know whether it will remain the same on next boot or not.

I had to do the following.

Right-click on Network Manager
Edit Connections
In Auto eth1
in IPv4 Settings
Change Method to Automatic (DHCP) addresses only
in DNS servers change from blank to 208.67.222.222
in Search domains change to opendns.com

I want to add another DNS server IP Address, how can I do that ?

Please lemme know if you require any other attachments.

This is a fresh install though, not an upgrade and within an NTFS partition

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]