On 07/05/11 17:26, Camaleón wrote:
On Sat, 07 May 2011 16:49:07 +0100, AG wrote:
On 07/05/11 16:39, Camaleón wrote:
(...)
Let's see... on a running system, once you edit the "/etc/network/
interfaces" file you also have to:
1/ Restart the network service: /etc/init.d/networking restart
2/ Up the network interface: ifup eth0
3/ Check that all is fine: /sbin/ifconfig
(this is not needed after you restart the machine)
Try it and send the results. The rest of the files look normal so let's
focus on this.
Here are the results of those three commands:
$ sudo /etc/init.d/networking restart
sudo: unable to resolve host
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(...)
Once you resolve the networking problem, you should look from where is
coming that "sudo" error... Is it happening for any "sudo" command you
type? :-?
$ /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:90:47:05:a3:07
inet addr:192.168.1.40 Bcast:192.168.1.255
Mask:255.255.255.0 inet6 addr: fe80::290:47ff:fe05:a307/64
Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10700 errors:0 dropped:0 overruns:0 frame:0 TX
packets:10113 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8424815 (8.0 MiB) TX bytes:1223781 (1.1 MiB)
Interrupt:18 Base address:0xec00
(...)
Hey, that seems to be the right one :-)
The IP address is now consistent.
Now is this likely to hold when I reboot so that I can access the Net?
(...)
Sure, and if not something is very badly broken. Restart the machine to
be sure and if the IP address changes again, review your syslog.
I guess something is "very badly broken" then. After rebooting, the
blessed problems start all over again and I cannot access the web at
all. The following are all copied before applying Brian's #dhclient
eth0 trick:
This is the syslog report (again snipped for the time):
May 7 17:30:26 valhalla kernel: [ 1.030564] 8139too 0000:01:0a.0:
eth0: RealTek RTL8139 at 0xec00, 00:90:47:05:a3:07, IRQ 18
May 7 17:30:26 valhalla kernel: [ 11.189082] eth0: link up, 100Mbps,
full-duplex, lpa 0x41E1
May 7 17:30:28 valhalla NetworkManager[1542]: SCPluginIfupdown:
guessed connection type (eth0) = 802-3-ethernet
May 7 17:30:28 valhalla NetworkManager[1542]: SCPlugin-Ifupdown:
update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet,
id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e
May 7 17:30:28 valhalla NetworkManager[1542]: SCPlugin-Ifupdown:
adding eth0 to iface_connections
May 7 17:30:28 valhalla NetworkManager[1542]: SCPlugin-Ifupdown:
adding iface eth0 to well_known_interfaces
May 7 17:30:28 valhalla NetworkManager[1542]: SCPlugin-Ifupdown:
devices added (path:
/sys/devices/pci0000:00/0000:00:04.0/0000:01:0a.0/net/eth0, iface: eth0)
May 7 17:30:28 valhalla NetworkManager[1542]: <info> (eth0): carrier is ON
May 7 17:30:28 valhalla NetworkManager[1542]: <info> (eth0): new
Ethernet device (driver: '8139too' ifindex: 2)
May 7 17:30:28 valhalla NetworkManager[1542]: <info> (eth0): exported
as /org/freedesktop/NetworkManager/Devices/0
May 7 17:30:35 valhalla kernel: [ 21.232032] eth0: no IPv6 routers
present
$ /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:90:47:05:a3:07
inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::290:47ff:fe05:a307/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:414 errors:0 dropped:0 overruns:0 frame:0
TX packets:322 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:376637 (367.8 KiB) TX bytes:90428 (88.3 KiB)
Interrupt:18 Base address:0xec00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:604 errors:0 dropped:0 overruns:0 frame:0
TX packets:604 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:58752 (57.3 KiB) TX bytes:58752 (57.3 KiB)
/etc/network/interfaces:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
#iface eth0 inet dhcp
address 192.168.1.40
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.254
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 158.43.240.4
dns-search org
cat /etc/resolv.conf:
$ sudo cat /etc/resolv.conf
sudo: unable to resolve host valhalla
# Generated by NetworkManager
Ping: $ ping -c 3 192.168.1.254
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
64 bytes from 192.168.1.254: icmp_req=1 ttl=64 time=1.22 ms
64 bytes from 192.168.1.254: icmp_req=2 ttl=64 time=0.706 ms
64 bytes from 192.168.1.254: icmp_req=3 ttl=64 time=0.671 ms
--- 192.168.1.254 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.671/0.866/1.222/0.253 ms
ip ro: $ ip ro
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.40
default via 192.168.1.254 dev eth0
and finally, $ dmesg | grep eth
[ 0.178867] ACPI Error: Method parse/execution failed
[\_SB_.MEM_._CRS] (Node f4c370c0), AE_AML_BUFFER_LIMIT
(20110112/psparse-536)
[ 0.178875] ACPI Error: Method execution failed [\_SB_.MEM_._CRS]
(Node f4c370c0), AE_AML_BUFFER_LIMIT (20110112/uteval-103)
[ 1.030564] 8139too 0000:01:0a.0: eth0: RealTek RTL8139 at 0xec00,
00:90:47:05:a3:07, IRQ 18
[ 11.189082] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 21.232032] eth0: no IPv6 routers present
I am now going to apply Brian's trick which will probably change my IP
address again, as noted in /sbin/ifconfig:
$ /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:90:47:05:a3:07
inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::290:47ff:fe05:a307/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:474 errors:0 dropped:0 overruns:0 frame:0
TX packets:368 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:382587 (373.6 KiB) TX bytes:97169 (94.8 KiB)
Interrupt:18 Base address:0xec00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:802 errors:0 dropped:0 overruns:0 frame:0
TX packets:802 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:83818 (81.8 KiB) TX bytes:83818 (81.8 KiB)
And yes, sudo still cannot resolve the hostname.
But at least now I can access the Net so I can post this.
At this point in time I am sorely tempted to reinstall from my February
netinstall disc but I am not sure which package I should be avoiding
when I upgrade. Any ideas?
Also, if it is of any relevance, these are the services I am currently
running (according to "services" in Gnome/ Administration:
alsa-utils
anacron
atd
cpufrequtils
cron
cups
exim4
fancontrol
firestarter
fuse
gdm3
ipupdown-clean
kerneloops
loadcpufreq
nfs-common
polipo
portmap
pulseaudio
rsync
rsyslog
sudo
tor
So ... what now?
Yours helplessly lost
AG
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4dc577df.7070...@gmail.com
