On Tue, 27 Aug 2002, Blake C. Thornton wrote:
>
> > On Mon, 26 Aug 2002, Blake C. Thornton wrote:
> >
> > > > > I need some network help. I haven't seen this happen before.
> > > > >
> > > > > I am trying to set up networking on a system without DHCP. My sysadmin
> > > > > gave me an IP address for my linux box (redhat 7.3). So, I edited:
> > > > >
> > > > > /etc/hosts
> > > > > 127.0.0.1 localhost.localdomain localhost
> > > > > 165.134.123.88 localhost.localdomain
> > > > >
> > > > > /etc/sysconfig/network
> > > > > NETWORKING=yes
> > > > > HOSTNAME=localhost.localdomain
> > > > > FORWARD_IPV4=false
> > > > > GATEWAY=165.134.1.254
> > > > >
> > > > > /etc/sysconfig/network-scripts
> > > > > DEVICE=eth0
> > > > > IPADDR=165.134.123.88
> > > > > NETMASK=165.134.123.0
> > > > this looks suspicious probably should be something like 255.255.255.0
> > > >
> > > > > ONBOOT=yes
> > > > >
> > >
> > > Sorry, I mistyped when copying. Here is what i have (and still can't
> > > connect or ping anything):
> > >
> > > /etc/sysconfig/network-scripts/ifcfg-eth0
> > > DEVICE=eth0
> > > IPADDR=165.134.123.88
> > > NETWORK=165.134.123.0
> > > NETMASK=255.255.255.0
> > > ONBOOT=yes
> > >
> > > Sorry, any other ideas?
> >
> > Yup...if you want to see the rest of the network, not to mention the rest
> > of the net, change your netmask to 255.255.0.0.
> >
>
> Very good - this did it.
>
> I also used the suggestion to use redhat-config-network and used the
> correct netmask as above. Not sure I understand why, but I'll read the
> network admin guide sometime and get it.
>
> Thanks!
The reason that changing the netmask worked is this.
Your system IP: 165.134.123.88
^^^
Your gateway IP: 165.134.1.254
^
Class C netmask: 255.255.255.0
Class B netmask: 255.255.0.0
The third octet (third set of numbers) was different, between the two
addresses...basically placing your network addresses into a class B
network.
By using a Class C netmask, your system was limited to seeing only other
addresses in the 165.134.123 network, without a router in place (which
also would have to have a 165.134.123 address).
By using the Class B netmask, your system was able to see other addresses
in the full 165.134 network, giving you a much wider range. Because you
could now see the entire 165.134 network, the gateway, in the 165.134.1
network, became visible, and network traffic could properly be routed
to/from your machine.
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
