FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu User

 
 
LinkBack Thread Tools
 
Old 01-02-2009, 04:17 PM
Frank Cox
 
Default network problem

On Fri, 02 Jan 2009 09:09:29 -0800
Gerhard Magnus wrote:

> Is there an easy fix to this -- short of doing the installation over?
> Thanks for the help!

Assuming that your network card is eth0:

vi /etc/sysconfig/network-scripts/ifcfg-eth0
vi /etc/sysconfig/network-scripts/route-eth0

Make the necessary corrections there and all should be well.

--
MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com
DRY CLEANER BUSINESS FOR SALE ~ http://www.canadadrycleanerforsale.com

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 01-02-2009, 04:22 PM
Gene Heskett
 
Default network problem

On Friday 02 January 2009, Gerhard Magnus wrote:
>I have a small home LAN that I am starting to upgrade from FC9 to FC10.
>As the network is still "hardwired" with ethernet cable and the boxes
>all have static IP addresses I would like to continue using the old
>network service rather than NetworkManager.
>
>After installing FC10 on one of the machines without problems, I stopped
>and disabled NetworkManager and configured the network using the widget
>System -> Administration -> Network from the gnome desktop and filling
>in the "DNS" and "Hosts" information as with FC9. But then I made a typo
>in editing device etho under the "Devices" tab -- I accidentally typed
>in the gateway address instead of 255.255.255.0 in the "Subnet mask"
>field. Now whenever I try correcting this from the "network" widget the
>field reverts back to what I mistakenly typed in before. This is
>apparently why I can't reach the network from this box.
>
>Is there an easy fix to this -- short of doing the installation over?
>Thanks for the help!
>
>Jerry

I think you need to be root to do that and make it stick.

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Mal: "Just get us on the ground!"

Wash: "That part'll happen, pretty definitely."
--"Serenity"

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 01-02-2009, 04:25 PM
"Mikkel L. Ellertson"
 
Default network problem

Gerhard Magnus wrote:
> I have a small home LAN that I am starting to upgrade from FC9 to FC10.
> As the network is still "hardwired" with ethernet cable and the boxes
> all have static IP addresses I would like to continue using the old
> network service rather than NetworkManager.
>
> After installing FC10 on one of the machines without problems, I stopped
> and disabled NetworkManager and configured the network using the widget
> System -> Administration -> Network from the gnome desktop and filling
> in the "DNS" and "Hosts" information as with FC9. But then I made a typo
> in editing device etho under the "Devices" tab -- I accidentally typed
> in the gateway address instead of 255.255.255.0 in the "Subnet mask"
> field. Now whenever I try correcting this from the "network" widget the
> field reverts back to what I mistakenly typed in before. This is
> apparently why I can't reach the network from this box.
>
> Is there an easy fix to this -- short of doing the installation over?
> Thanks for the help!
>
> Jerry
>
I am old school when it comes to network configuration - I would
edit /etc/sysconfig/network-scripts/ifcfg-eth0 and change the values
for NETMASK and GATEWAY there. Then run "service network restart" to
use the new values.

Mikkel
--

Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 05-07-2011, 03:06 PM
AG
 
Default Network problem

On 07/05/11 15:49, Camaleón wrote:

<snip>
(...)

Okay, let's forget momentary the "hosts" file and go on with the network
issue which I think is more important here.


So, I have just done the following:

(1) I altered the /etc/hosts IP address to *.64
(2) ensured that the /etc/network/interface file read "static" rather
than dhcp
(3) rebooted

(...)


Hi Camaleón

See below. Thanks.

Copy/paste what does your "/etc/network/interfaces" look like


# 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 # I have manually specified this
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



and also
post the results of "/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:1936 errors:0 dropped:0 overruns:0 frame:0
TX packets:1864 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1018372 (994.5 KiB) TX bytes:237018 (231.4 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:644 errors:0 dropped:0 overruns:0 frame:0
TX packets:644 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:54042 (52.7 KiB) TX bytes:54042 (52.7 KiB)



"cat /etc/resolv.conf",


$ cat /etc/resolv.conf
domain lan
search lan
nameserver 192.168.1.254

"ping -c 3
192.168.0.1" (or whatever the IP of your router is)


$ 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.74 ms
64 bytes from 192.168.1.254: icmp_req=2 ttl=64 time=0.683 ms
64 bytes from 192.168.1.254: icmp_req=3 ttl=64 time=0.705 ms



and just in case "ip
ro"


$ ip ro
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.64
default via 192.168.1.254 dev eth0

and "dmesg | grep -i eth".


$ dmesg | grep eth
[ 0.178866] 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.014972] 8139too 0000:01:0a.0: eth0: RealTek RTL8139 at 0xec00,
00:90:47:05:a3:07, IRQ 18

[ 10.733628] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 20.752026] eth0: no IPv6 routers present



Greetings,


Thanks


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4DC55FF6.4090702@gmail.com">http://lists.debian.org/4DC55FF6.4090702@gmail.com
 
Old 05-07-2011, 03:39 PM
Camaleón
 
Default Network problem

On Sat, 07 May 2011 16:06:30 +0100, AG wrote:

> On 07/05/11 15:49, Camaleón wrote:

(...)

>> Copy/paste what does your "/etc/network/interfaces" look like
>
> # 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 # I have manually specified this
> 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

The above looks okay.

>> and also
>> post the results of "/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:1936 errors:0 dropped:0 overruns:0 frame:0 TX
> packets:1864 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1018372 (994.5 KiB) TX bytes:237018 (231.4 KiB)
> Interrupt:18 Base address:0xec00

(...)

Here there's a problem. Your IP address does not match with the one you
defined in the "interfaces" file.

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.

Also, after running the above 3 commands, review the syslog ("grep -i
eth0 /var/log/syslog")

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.15.39.27@gmail.com">http://lists.debian.org/pan.2011.05.07.15.39.27@gmail.com
 
Old 05-07-2011, 03:40 PM
Klistvud
 
Default Network problem

Dne, 07. 05. 2011 17:06:30 je AG napisal(a):

# dns-* options are implemented by the resolvconf package, if
installed

dns-nameservers 158.43.240.4


Can the above line from your /etc/network/interfaces be conflicting
with the:



nameserver 192.168.1.254


in your /etc/resolv.conf ?

Unfortunately, I'm not network-savvy enough to say anything about that.
Perhaps others can comment?



--
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: 1304782842.28162.5@compax">http://lists.debian.org/1304782842.28162.5@compax
 
Old 05-07-2011, 03:49 PM
AG
 
Default Network problem

On 07/05/11 16:39, Camaleón wrote:

On Sat, 07 May 2011 16:06:30 +0100, AG wrote:


On 07/05/11 15:49, Camaleón wrote:

(...)


Copy/paste what does your "/etc/network/interfaces" look like

# 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 # I have manually specified this
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

The above looks okay.


and also
post the results of "/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:1936 errors:0 dropped:0 overruns:0 frame:0 TX
packets:1864 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1018372 (994.5 KiB) TX bytes:237018 (231.4 KiB)
Interrupt:18 Base address:0xec00

(...)

Here there's a problem. Your IP address does not match with the one you
defined in the "interfaces" file.

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 valhalla
Running /etc/init.d/networking restart is deprecated because it may not
enable again some interfaces ... (warning).

Reconfiguring network interfaces...Stopping the Firestarter firewall....
Starting the Firestarter firewall....
done.

$ sudo ifup eth0
sudo: unable to resolve host valhalla
Stopping the Firestarter firewall....
Starting the Firestarter firewall....

$ /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

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:983 errors:0 dropped:0 overruns:0 frame:0
TX packets:983 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:79512 (77.6 KiB) TX bytes:79512 (77.6 KiB)


The IP address is now consistent.

Now is this likely to hold when I reboot so that I can access the Net?


Also, after running the above 3 commands, review the syslog ("grep -i
eth0 /var/log/syslog")


I did, and here is the output (I trimmed it to the last lines consistent
with the current time):


May 7 16:43:13 valhalla NetworkManager[1550]: <info> (eth0): carrier
now OFF (device state 1)
May 7 16:43:13 valhalla dhclient: receive_packet failed on eth0:
Network is down
May 7 16:43:29 valhalla NetworkManager[1550]: <info> (eth0): carrier
now ON (device state 1)
May 7 16:43:29 valhalla kernel: [ 5878.118829] eth0: link up, 100Mbps,
full-duplex, lpa 0x41E1
May 7 16:43:40 valhalla kernel: [ 5888.800028] eth0: no IPv6 routers
present


Thanks (as always!)

AG


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4DC569F3.4010703@gmail.com">http://lists.debian.org/4DC569F3.4010703@gmail.com
 
Old 05-07-2011, 04:26 PM
Camaleón
 
Default Network problem

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.

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.16.26.39@gmail.com">http://lists.debian.org/pan.2011.05.07.16.26.39@gmail.com
 
Old 05-07-2011, 04:42 PM
Brian
 
Default Network problem

On Sat 07 May 2011 at 17:40:42 +0200, Klistvud wrote:

> Dne, 07. 05. 2011 17:06:30 je AG napisal(a):
>
>> # dns-* options are implemented by the resolvconf package, if
>> installed
>> dns-nameservers 158.43.240.4
>
> Can the above line from your /etc/network/interfaces be conflicting with
> the:
>
>> nameserver 192.168.1.254
>
> in your /etc/resolv.conf ?
>
> Unfortunately, I'm not network-savvy enough to say anything about that.
> Perhaps others can comment?

There will be no conflict because the dns-nameservers and dns-search
lines are only acted on (the entries are put into /etc/resolv.conf) if
the resolvconf package is installed, which I do not think it is.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110507164246.GX13057@desktop">http://lists.debian.org/20110507164246.GX13057@desktop
 
Old 05-07-2011, 04:44 PM
Brian
 
Default Network problem

On Sat 07 May 2011 at 16:06:30 +0100, AG wrote:

> # The primary network interface
> allow-hotplug eth0
> iface eth0 inet static
> #iface eth0 inet dhcp
> address 192.168.1.40 # I have manually specified this
> netmask 255.255.255.0

Something and nothing. From interfaces(5)

> Lines starting with `#' are ignored. Note that end-of-line comments are
> NOT supported, comments must be on a line of their own.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110507164452.GY13057@desktop">http://lists.debian.org/20110507164452.GY13057@desktop
 

Thread Tools




All times are GMT. The time now is 12:05 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org