Mikkel:

Ok - I went in and looked at the file you mentioned.  I think it's
identical to what you said it should be.  In the past, as I did this last
time, I usually use the control panel under X to set the interface
up.  Here is the file:

DEVICE=eth1
ONBOOT=yes
BOOTPROTO=none
BROADCAST=192.168.1.255
NETWORK=192.168.1.0
NETMASK=255.255.255.0
IPADDR=192.168.1.1
USERCTL=no

Here is what route -n is showing:

/etc/sysconfig/network-scripts: route -n
Kernel IP routing table
Destination  Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.1  0.0.0.0         255.255.255.255 UH    0      0        0 eth1
192.168.1.0  0.0.0.0         255.255.255.0   U     0      0        0 eth1
24.218.80.0  0.0.0.0         255.255.252.0   U     0      0        0 eth0
127.0.0.0    0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0      24.218.80.1     0.0.0.0         UG    0      0        0 eth0

See anything conspicuous?

- Mike


On Sat, 22 Apr 2000, Mikkel L. Ellertson wrote:

> At 04:47 PM 4/22/00 -0400, you wrote:
> >Mikkel:
> >
> >Maybe you can help me interpret what I'm seeing.  I'm not very good with
> >this stuff (yet), so I appreciate any help you can throw my way.  You
> >mentioned something about a route not being set up.  Please understand
> >that I did everything exactly the way as I did with my Red Hat 6.1
> >machine, so possibly Red Hat is no longer setting something by default
> >that they did before?  Below are the steps you mentioned:
> >
>       SNIP
> 
> >The packets do appear to be on eth0.  Is this correct?  I honestly don't
> >really understand when you mention about the route not being set up
> >correctly, so possibly you can reply with a short explanantion, or point
> >me to a resource that would help explain it?  Any help is really
> >appreciated.  Thanks.
> >
> >- Mike
> >
> Yes, the packets are going out the wrong interface.  I think the problem is
> in /etc/sysconfig/network-scripts/ifcfg-eth1.  It should look something
> like:
> 
> DEVICE=eth1
> IPADDR=192.168.1.1
> NETMASK=255.255.255.0
> NETWORK=192.168.1.0
> BROADCAST=192.168.1.255
> ONBOOT=yes
> BOOTPROTO=none
> USERCTL=no
> 
> You can add the route manually to test things out with:
> 
> route add -net 192.168.1.0 netmask 255.255.255.0 eth1
> 
> If you still have trouble, send the output of route -n.
> 
> Mikkel
> 
> --
>     Do not meddle in the affairs of dragons,
>  for you are crunchy and taste good with ketchup.
> 
> 
> 


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to