RE: [luau] Routing table problems...

2004-01-05 Thread Ben Beeson
Ron,

All fixed now, the cards both work fine ;-)

Ben 




RE: [luau] Routing table problems...

2004-01-05 Thread Ronald Willis
Sorry I didnt catch the beginning of this thread, hope the following hasnt
been recommended...

When ever I build a multihome box I learned from the ISA card days to run
the diagnostic software to confirm whether the card even works for starters,
and run the diagnostics test on each card. The io and irqs for info sake,
would round out my test. Just to get started.

Ron

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Ben Beeson
> Sent: Friday, January 02, 2004 10:56 PM
> To: LUAU
> Subject: Re: [luau] Routing table problems...
>
>
> MonMotha,
>
>   I'll look into this.
>
> VR,
>
> Ben
>
>
> >
> > Another thing you may look at is the networking init script (in
> /etc/init.d)
> > itself.  Most of redhat's scripts provide some way to save the current
> > configuration as the default.  Running the init script with no
> options, using
> > --help, or viewing the file (99.9% chance it's just a "very small shell
> > script"(tm) ) may give ideas.
> >
>
>
> ___
> LUAU mailing list
> [EMAIL PROTECTED]
> http://videl.ics.hawaii.edu/mailman/listinfo/luau
>



Re: [luau] Routing table problems...

2004-01-03 Thread Ben Beeson
Devon,

I finally axed the /etc/sysconfig/network-scripts eth1.route and
ifcfg-eth1 files.  So far that seems to have fixed the problem. 

VR,

Ben 



Re: [luau] Routing table problems...

2004-01-02 Thread Ben Beeson
MonMotha,

I'll look into this.  

VR,

Ben 


> 
> Another thing you may look at is the networking init script (in /etc/init.d) 
> itself.  Most of redhat's scripts provide some way to save the current 
> configuration as the default.  Running the init script with no options, using 
> --help, or viewing the file (99.9% chance it's just a "very small shell 
> script"(tm) ) may give ideas.
> 




Re: [luau] Routing table problems...

2004-01-02 Thread Ben Beeson
Devon,

Tried all that stuff.  Same symptoms when I restart the network. I even
disabled eth1 but that didn't fix it either.  I believe the system is
reading a file somewhere when the network starts.  I'll dig and see if I
can find it.

Thanks,

Ben 





Re: [luau] Routing table problems...

2004-01-02 Thread Deven Phillips
Ben,

In truth, your problem has nothing to do with routing tables at all. It
is the fact that you have two network interfaces configured with IP
addresses on the same subnet. If you were to merely disable the second
NIC on startup, all of your troubles would go away. If this is not an
option, you need to specify which network interface is your gateway
device so that your system does not try to send packets out on your
unused interface. The way to accomplish this is to specify your default
route in this manner:

route add -net 192.56.76.0 netmask 255.255.255.0 dev eth0

intentionally specifying the interface on which to route the traffic.
This is typically done in the /etc/sysconfig/network file by adding a
line:

GATEWAYDEV=eth0

Let me know if this was helpful.

Deven

On Wed, 2003-12-31 at 19:24, Ben Beeson wrote:
> Aloha and Hauoli Makahiki Hou,
> 
>   Today a strange thing happened.  My routing tables got messed up and
> now although I can fix them, they don't stay fixed when the network
> restarts. I can't seem to find any reference to files that hold the
> 'non-volatile' parts of networking info to track down the problem. So
> any help would be greatly appreciated. 
> 
>   My box is RH 9 behind a router/firewall.  This box uses a fixed IP
> address of 192.168.1.21 and .22 (two nics).  Right now only eth0 is
> connected.  The router is IP address 192.168.1.1 on the LAN side. 
> Everything is OK with the router and all the rest of the boxen.  Just
> this one box is giving me trouble. 
> 
> This is what I want it to look like when I am done configuring the box.
> 
> [EMAIL PROTECTED] init.d]# /sbin/route -e
> Kernel IP routing table
> Destination Gateway Genmask Flags   MSS Window  irtt
> Iface
> localhost   *   255.255.255.255 UH0 0  0
> lo
> 192.168.1.0 *   255.255.255.0   U 0 0  0
> eth0
> default router  0.0.0.0 UG0 0  0
> eth0
> [EMAIL PROTECTED] init.d]#
> 
> 
> This is what the routing table looks like when the network restarts
> 
> [EMAIL PROTECTED] init.d]# /sbin/route -e
> Kernel IP routing table
> Destination Gateway Genmask Flags   MSS Window  irtt
> Iface
> 192.168.1.0 *   255.255.255.0   U 0 0  0
> eth1
> 192.168.1.0 *   255.255.255.0   U 0 0  0
> eth1
> 169.254.0.0 *   255.255.0.0 U 0 0  0
> eth1
> 127.0.0.0   *   255.0.0.0   U 0 0  0
> lo
> default router  0.0.0.0 UG0 0  0
> eth1
> [EMAIL PROTECTED] init.d]#
> 
> 
> As you can see most of the entries are eth1, not eth0, and there are a
> few other mistakes in the table that keep the networking stuff from
> functioning correctly.  
> 
> After I rebuild the routing tables by hand, all is OK until the network
> gets restarted.  Why is this, and what can I do to correct it?
> 
> Mahalos in advance,
> 
> Ben 
> 
> 
> 
> 
> ___
> LUAU mailing list
> [EMAIL PROTECTED]
> http://videl.ics.hawaii.edu/mailman/listinfo/luau



Re: [luau] Routing table problems...

2004-01-01 Thread MonMotha
To my knowledge, RH stores its routing tables in /etc/sysconfig/route, or at 
least some file in /etc/sysconfig.  I'm not quite sure on the syntax though. 
Anyway, playing around in sysconfig may shed some light on the subject.  I'm 
sure redhat also has a tool to tweak them with a fancy frontend.


Another thing you may look at is the networking init script (in /etc/init.d) 
itself.  Most of redhat's scripts provide some way to save the current 
configuration as the default.  Running the init script with no options, using 
--help, or viewing the file (99.9% chance it's just a "very small shell 
script"(tm) ) may give ideas.



--MonMotha




[luau] Routing table problems...

2003-12-31 Thread Ben Beeson
Aloha and Hauoli Makahiki Hou,

Today a strange thing happened.  My routing tables got messed up and
now although I can fix them, they don't stay fixed when the network
restarts. I can't seem to find any reference to files that hold the
'non-volatile' parts of networking info to track down the problem. So
any help would be greatly appreciated. 

My box is RH 9 behind a router/firewall.  This box uses a fixed IP
address of 192.168.1.21 and .22 (two nics).  Right now only eth0 is
connected.  The router is IP address 192.168.1.1 on the LAN side. 
Everything is OK with the router and all the rest of the boxen.  Just
this one box is giving me trouble. 

This is what I want it to look like when I am done configuring the box.

[EMAIL PROTECTED] init.d]# /sbin/route -e
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt
Iface
localhost   *   255.255.255.255 UH0 0  0
lo
192.168.1.0 *   255.255.255.0   U 0 0  0
eth0
default router  0.0.0.0 UG0 0  0
eth0
[EMAIL PROTECTED] init.d]#


This is what the routing table looks like when the network restarts

[EMAIL PROTECTED] init.d]# /sbin/route -e
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt
Iface
192.168.1.0 *   255.255.255.0   U 0 0  0
eth1
192.168.1.0 *   255.255.255.0   U 0 0  0
eth1
169.254.0.0 *   255.255.0.0 U 0 0  0
eth1
127.0.0.0   *   255.0.0.0   U 0 0  0
lo
default router  0.0.0.0 UG0 0  0
eth1
[EMAIL PROTECTED] init.d]#


As you can see most of the entries are eth1, not eth0, and there are a
few other mistakes in the table that keep the networking stuff from
functioning correctly.  

After I rebuild the routing tables by hand, all is OK until the network
gets restarted.  Why is this, and what can I do to correct it?

Mahalos in advance,

Ben