[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-ppc
Subject:    RE: connecting to internet via network
From:       Jason Staloff <jason-lppc () citroen ! oldcity ! dca ! net>
Date:       2000-07-04 15:57:13
[Download RAW message or body]


Umm, do you folks have in your /etc/sysconfig/network file a statement:

GATEWAYDEV=eth0

I found on my PC linux box that this was missing. The machine always booted up fine, \
perhaps because it sets the gateway to eth0 during some earlier boot stage, but \
/etc/rc.d/init.d/network restart prevented me from getting outside. I fixed the \
missing st atement, and now it works fine.

Jason

PS here are my copies of the two files:

/etc/sysconfig/network
HOSTNAME=bug
DOMAINNAME=staloff.org
NETWORKING=yes
FORWARD_IPV4=false
GATEWAY=192.168.0.1
GATEWAYDEV=eth0

/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
IPADDR=192.168.0.6
NETMASK=255.255.255.240

You may have NETWORK and BROADCAST statements in ifcfg-eth0 too, but they aren't \
necessary as they can be calculated by looking at the IPADDR and the NETMASK.

Jason


On Tue, 4 Jul 2000, Tate Stephen SA wrote:

> Jason, Keary,
> 
> Last night I tried to finish setting the parameters that you all suggested
> and using the network restart script to reduce time but this did not work. I
> could ping the machien itself and I could ping the gateway machine but non
> of the DNS worked so I could not see the outside world.
> 
> I have just booted the machine from cold and decided to have another session
> at connecting to the outside world. This time the system works and
> recognises the G4 as the gateway and I can connect without modifying any of
> the scripts :)
> 
> I have just read the message below so I will try and network restart the
> machine when I get home and see if that stops the system working. As there
> was no joy in restarting the system last night I have a feeling that this
> will stop the network from working again.
> 
> I do not have linuxconf installed is this the reason why the system does not
> work ?
> 
> Steve Tate
> ps the system is a 3400 powerbook with linuxppc 2000 and the standard
> kernel.
> 
> 
> > Keary,
> > 
> > If your machine boots up all right, then your network and ifcfg-eth0 files
> > should be fine.
> > 
> > When the machine boots, it brings up the networking system by calling
> > /etc/rc.d/init.d/network and passing it the argument "start" instead of
> > restart. What happens if you boot up, then /etc/rc.d/init.d/network stop,
> > then /etc/rc.d/init.d/network start?
> > 
> > I'm not sure why running the same script should succeed at boot time but
> > not afterward. The network script does refer to linuxconf in the reload
> > case statement, but not in restart. Restart is very simple, just stop and
> > start. Do you have Linuxconf install
> > ed? What happens if you use the reload argument?
> > 
> > Jason
> > 
> > 
> > 
> > On Mon, 3 Jul 2000, Keary Suska wrote:
> > 
> > > 
> > > > OK it's time to get some more detail. Did restarting
> > /etc/rc.d/init.d/network
> > > > cause errors to be printed to the screen or to /var/log/messages? If
> > so, what
> > > > errors?
> > > 
> > > No--no errors reported in either.
> > > 
> > > > What changes did you make to which files? Email me your
> > /etc/sysconfig/network
> > > > and your /etc/sysconfig/network-scripts/ifcfg-eth0.
> > > > Also send me the output of ifconfig before and after restarting
> > network.
> > > > 
> > > > After the network restart, can you ping the 7200's own IP address from
> > itself?
> > > > 
> > > > You say the machine wouldn't respond to pings... is the machine you're
> > pinging
> > > > from on the same IP network as your linux box's new IP address? (For
> > example,
> > > > 10.0.0.1 is not on the same IP network as 10.0.0.200 if the subnet
> > mask is
> > > > 255.255.255.128, even t
> > > > hough they may be connected to the same ethernet hub.)
> > > 
> > > Let me begin by re-stating that there is absolutely nothing wrong with
> > my
> > > network configuration whatsoever. It works perfectly. The problem is
> > that if
> > > I call /etc/rc.d/init.d/network restart, even if I had made *no* changes
> > to
> > > a fully functioning, perfectly working network config, the script brings
> > > down the entire networking system and the machine won't even respond to
> > > pings which likely indicates that the entire TCP/IP substructure is
> > down. If
> > > I reboot, everything is returned to normal. Which, I assume, indicates
> > that
> > > there is nothing wrong with my network config, yes?
> > > 
> > > So then, why is the /etc/rc.d/init.d/network script downing the network
> > when
> > > it is called with "restart"?
> > > 
> > > -K
> > > 
> > > --
> > > "... and here comes the ice-pick, in the forehead!"
> > > - Frank Zappa, _Fembot in a Wet T-Shirt_
> > > 
> > > > From: Jason Staloff <jason-lppc@citroen.oldcity.dca.net>
> > > > Date: Mon, 3 Jul 2000 20:21:01 -0400 (EDT)
> > > > To: Keary Suska <aksuska@insideflyer.com>
> > > > Cc: "LinuxPPC (user)" <linuxppc-user@lists.linuxppc.org>
> > > > Subject: Re: connecting to internet via network
> > > > 
> > > > 
> > > > Hi Keary,
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Jason
> > > > 
> > > > 
> > > > On Mon, 3 Jul 2000, Keary Suska wrote:
> > > > 
> > > > > 
> > > > > I am familiar with the Sys V init somewhat, although I have not
> > thoroughly
> > > > > researched the sections that boot the network and associated systems.
> > The
> > > > > books I have read recommend rebooting when making certain changes,
> > but what
> > > > > you recommend sounds better to me.
> > > > > 
> > > > > So I took your advice, and when I had to make changes I executed the
> > init
> > > > > script as indicated above and the networking system was trashed. The
> > machine
> > > > > would not even respond to pings. Once I rebooted, everything was
> > hunky-dory.
> > > > > Just to make sure I didn't do anything wrong, after having *not* made
> > any
> > > > > changes whatsoever from a known working network config (need to have
> > a
> > > > > control for my little experiment), I executed
> > /etc/rc.d/init.d/network
> > > > > restart. Once again, networking was trashed and I had to reboot to
> > get it
> > > > > back online.
> > > > > 
> > > > > Could you tell me why your recommendation doesn't work, as I am not
> > familiar
> > > > > enough with the Sys V init system? I am on LPPC2k/7200/120.
> > > > > 
> > > > > > From: Jason Staloff <jason-lppc@citroen.oldcity.dca.net>
> > > > > > Date: Thu, 29 Jun 2000 19:11:06 -0400 (EDT)
> > > > > > 
> > > > > > No, please don't reboot your machine to change network settings. If
> > you do,
> > > > > > your super-cool LPPC Mac will be no better than a Windows box!   :-)
> > > > > > 
> > > > > > After editing /etc/sysconfig/network and
> > > > > > /etc/sysconfig/network-scripts/ifcfg-eth0, you should use the most
> > excellent
> > > > > > System V init system to reload the networking system with the new
> > values:
> > > > > > 
> > > > > > /etc/rc.d/init.d/network restart
> > > > > > 
> > > > > > If you don't understand how the Sys V init system works, you should
> > learn
> > > > > > about it. In addition to giving you an idea of the elegant
> > philosophy behind
> > > > > > Unix, it will make your administration tasks easier. You can learn
> > from a
> > > > > > Unix
> > > > > > book such as Essential Sy
> > > > > > stem Administration (O-Reilly) or just read the scripts yourself if
> > you know
> > > > > > some bash.
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > > 
> > 
> > 
> > 
> 


** Sent via the linuxppc-user mail list. See http://lists.linuxppc.org/


[prev in list] [next in list] [prev in thread] [next in thread]