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? :-?
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
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:
On Sat 07 May 2011 at 15:39:27 +0000, Camaleón wrote:
> 1/ Restart the network service: /etc/init.d/networking restart
Which may or not work. It doesn't here on one machine with a hotplugged
wlan0 interface. Which is why a warning is given. ifdown/ifup should be
sufficient. Also, the command /etc/init.d/networking does not offer a
restart option.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110507171701.GZ13057@desktop">http://lists.debian.org/20110507171701.GZ13057@desktop
05-07-2011, 05:34 PM
Klistvud
Network problem
Dne, 07. 05. 2011 18:48:31 je AG napisal(a):
/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
Seems OK to me.
cat /etc/resolv.conf:
$ sudo cat /etc/resolv.conf
sudo: unable to resolve host valhalla
# Generated by NetworkManager
Seems a total mess. Which is no wonder at all -- it's been generated by
the notorious NetworkMangler!
AFAIK you just need one line inthere, namely:
nameserver 192.168.1.254
(or whatever nameserver you think you should put there).
Just for a test, try commenting out all other lines in your
/etc/resolv.conf, leaving just the 'nameserver 192.168.1.254' line.
Then: service stop network-manager
Then: cat /etc/resolv.conf again just to check that Network Manager
hasn't written rubbish inthere again
I have a strong suspicion Network Manager is messing things up for you.
If you can restart your networking (or reboot) *without* letting
Network Manager mangle your resolv.conf again, you could actually get
connectivity.
I think.
Perhaps by making /etc/resolv.conf read-only or something...?
(temporarily, just to see if it works)
Also, you mention you're using a february CD for your installs? Was
that just before Squeeze entered stable? I would strongly recommend you
download a more recent netinstall (or other) CD before trying a
reinstall.
--
Cheerio,
Klistvud
http://bufferoverflow.tiddlyspot.com
Certifiable Loonix User #481801 Please reply to the list, not to
me.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1304789657.23908.1@compax">http://lists.debian.org/1304789657.23908.1@compax
05-07-2011, 05:43 PM
Brian
Network problem
On Sat 07 May 2011 at 17:48:31 +0100, AG wrote:
[Snip]
> 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,
[Snip again]
> cat /etc/resolv.conf:
> $ sudo cat /etc/resolv.conf
> sudo: unable to resolve host valhalla
> # Generated by NetworkManager
I have never used NetworkManager. I know little about it. But I do know
it does not play with ifupdown kindly. Both cannot be used together to
manage interfaces.
Yours (becoming more intrigued),
Brian.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110507174344.GA13057@desktop">http://lists.debian.org/20110507174344.GA13057@desktop
05-07-2011, 06:15 PM
Camaleón
Network problem
On Sat, 07 May 2011 17:48:31 +0100, AG wrote:
> On 07/05/11 17:26, Camaleón wrote:
(...)
>>> 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:
Wait, wait... your IP is the one you configured so there is nothing
broken. The problem now is that you cannot access the web but that's
another different issue.
> So ... what now?
>
> Yours helplessly lost
Now you have to make another tests, but you need to configure your
network with the static layout to try this :-)
Once you restore the static IP, run "dig @8.8.8.8 google.com" and put
here the output.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.05.07.18.15.25@gmail.com">http://lists.debian.org/pan.2011.05.07.18.15.25@gmail.com
07-04-2012, 11:20 AM
Tiziana Manfroni
network problem
Hi, I have a server with two card network, one in public network
(193.204.165.*) and other in private network(192.168.114.*).
When I connect from host on public network (193.204.165.*) or another
private network (192.168.115.) to server it's all ok, but for example, if
I connect from a host with IP address 192.168.114.30 in 'ssh -vvv www@193.204.165.224' the output is "ssh:
connect to 193.204.165.224 port 22: no route to host". When I connect with 'ssh
-vvv www@192.168.114.60' I see "www@192.168.114.60's password:" I have this
network problem for all services on server (http, https, mail) and not for only
ssh. This server works on RHEL6.3. The service NetworkManager is disable,
only service network is on.
This is my configuration file:
/etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE="eth1"
ONBOOT=yes
HWADDR=00:1D:0F:C3:42:F2
TYPE=Ethernet
BOOTPROTO=none
IPADDR=193.204.165.224
NETMASK=255.255.255.0
DNS1=193.204.165.131
DNS2=193.205.139.10
IPV6INIT=no
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
07-04-2012, 11:51 AM
Ed Greshko
network problem
On 07/04/2012 07:20 PM, Tiziana Manfroni wrote:
> Hi, I have a server with two card network, one in public network (193.204.165.*)
> and other in private network(192.168.114.*).
> When I connect from host on public network (193.204.165.*) or another private
> network (192.168.115.) to server it's all ok, but for example, if I connect from a
> host with IP address 192.168.114.30 in 'ssh -vvv www@193.204.165.224' the output is
> "ssh: connect to 193.204.165.224 port 22: no route to host". When I connect with
> 'ssh -vvv www@192.168.114.60' I see "www@192.168.114.60's password:" I have this
> network problem for all services on server (http, https, mail) and not for only
> ssh. This server works on RHEL6.3. The service NetworkManager is disable, only
> service network is on.
>
> This is my configuration file:
> /etc/sysconfig/network-scripts/ifcfg-eth1
> DEVICE="eth1"
> ONBOOT=yes
> HWADDR=00:1D:0F:C3:42:F2
> TYPE=Ethernet
> BOOTPROTO=none
> IPADDR=193.204.165.224
> NETMASK=255.255.255.0
> DNS1=193.204.165.131
> DNS2=193.205.139.10
> IPV6INIT=no
>
> /etc/sysconfig/network-scripts/ifcfg-eth2
> DEVICE="eth2"
> HWADDR=00:24:01:32:06:C7
> TYPE=Ethernet
> BOOTPROTO=none
> IPADDR=192.168.114.60
> NETMASK=255.255.255.0
> DNS1=193.204.165.131
> DNS2=193.205.139.10
> IPV6INIT=no
> ONBOOT=yes
>
> /etc/sysconfig/network
> NETWORKING=yes
> HOSTNAME=web.mat.uniroma3.it
> GATEWAY=193.204.165.1
>
> /etc/resolv.conf
> search mat.uniroma3.it
> nameserver 193.204.165.131
> nameserver 193.205.139.10
>
>
> Any idea?
>
For the system with IP address 192.168.114.30 what is the output of netstat -nr ?
--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
07-04-2012, 12:04 PM
Tiziana Manfroni
network problem
For the system with IP address 192.168.114.30 what is the output of netstat -nr ?
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.114.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth0
0.0.0.0 192.168.114.1 0.0.0.0 UG 0 0 0
eth0
--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
07-04-2012, 12:17 PM
Oleg Cherkasov
network problem
On 04. juli 2012 14:04, Tiziana Manfroni wrote:
For the system with IP address 192.168.114.30 what is the output of
netstat -nr ?
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.114.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth0
0.0.0.0 192.168.114.1 0.0.0.0 UG 0 0 0
eth0
Follow the initial introduction I think IPv4 forwarding is missing, so
try to enable it:
sysctl -w net.ipv4.ip_forward=1
Oleg
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
07-04-2012, 12:20 PM
Ed Greshko
network problem
On 07/04/2012 08:04 PM, Tiziana Manfroni wrote:
>> For the system with IP address 192.168.114.30 what is the output of netstat -nr ?
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.114.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
> 0.0.0.0 192.168.114.1 0.0.0.0 UG 0 0 0 eth0
OK....
There is no specific route to 193.204.165.0 network.
So, that means the packets are sent to the default route 192.168.114.1. What kind of
device is that?
--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Network problem
