RE: [luau] Routing table problems...
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...
Ron, All fixed now, the cards both work fine ;-) Ben
Re: [luau] Routing table problems...
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...
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...
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...
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...
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
Re: [luau] routing- linksys
I agree with jeff here. The simplest way to configure a linksys router is via the web browswer interface. 1st set your IP to 192.168.1.2 or something on the same net as the router is by default. 2nd point your browser to 192.168.1.1 Login using the password supplied by linksys (admin) i think w/o username. 3rd Change the IP of the router to be on your 10.0.0.x network. CHANGE THE PASSWORD!!! 4th change the IP of your machine back to what it was on the 10.0.0.x net, or use DHCP as Elaine mentioned. If not using DHCP, set your gateway as the router's IP, Set DNS if not already done and check your connectivity with pings or browsers. dean On Sat, 2002-08-31 at 13:00, Jeff Mings wrote: Why don't you just change the IP of the Linksys router? It's VERY easy to do with the browser interface. -Jeff Randall Oshita wrote: yes, but you have to be more specific on how you have your network setup, you have to tell the router how to get from one subnet to the other. what kind of router do you have? Julio + I'm adding a Linksys router (based on 192) to a network with the 10 series. Subnet : 255.255.255.0; subnet class within the ip is the same for all workstations as well, 10.0.0.# . Gateway will be the router : 192. Doesn't look like the linksys can be told how to get from one subnet to another. I'm looking to see if a Linux box will provide me with a solution. Would be nice to see it work with the Linksys, that way I know what to look for when I setup a Linux box. Thanks. Randall ___ LUAU mailing list [EMAIL PROTECTED] http://videl.ics.hawaii.edu/mailman/listinfo/luau ___ LUAU mailing list [EMAIL PROTECTED] http://videl.ics.hawaii.edu/mailman/listinfo/luau
Re: [luau] routing- linksys
Thats correct. To leave the Linksys router on its default settings will lead to disaster. Having a 192 internel LAN network setting is one thing, allowing access to internet at any point in that network just opens yourself up to hackers. Change your IP settings and password ASAP. - Original Message - From: Jeff Mings [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, August 31, 2002 1:00 PM Subject: Re: [luau] routing- linksys Why don't you just change the IP of the Linksys router? It's VERY easy to do with the browser interface. -Jeff Randall Oshita wrote: yes, but you have to be more specific on how you have your network setup, you have to tell the router how to get from one subnet to the other. what kind of router do you have? Julio + I'm adding a Linksys router (based on 192) to a network with the 10 series. Subnet : 255.255.255.0; subnet class within the ip is the same for all workstations as well, 10.0.0.# . Gateway will be the router : 192. Doesn't look like the linksys can be told how to get from one subnet to another. I'm looking to see if a Linux box will provide me with a solution. Would be nice to see it work with the Linksys, that way I know what to look for when I setup a Linux box. Thanks. Randall ___ LUAU mailing list [EMAIL PROTECTED] http://videl.ics.hawaii.edu/mailman/listinfo/luau ___ LUAU mailing list [EMAIL PROTECTED] http://videl.ics.hawaii.edu/mailman/listinfo/luau
RE: [luau] routing- linksys
I agree with jeff here. The simplest way to configure a linksys router is via the web browswer interface. 1st set your IP to 192.168.1.2 or something on the same net as the router is by default. 2nd point your browser to 192.168.1.1 Login using the password supplied by linksys (admin) i think w/o username. 3rd Change the IP of the router to be on your 10.0.0.x network. CHANGE THE PASSWORD!!! 4th change the IP of your machine back to what it was on the 10.0.0.x net, or use DHCP as Elaine mentioned. If not using DHCP, set your gateway as the router's IP, Set DNS if not already done and check your connectivity with pings or browsers. dean + Thanks. You guys reinforced what I knew. I didn't know the Linksys could go to 10 series. When I changed the linksys to 10 all its internal settings for forwarding, DMZ etc.. turned to 10 as well. Thanks. Randall
Re: [luau] routing
On Saturday 31 August 2002 12:20 am, Randall Oshita wrote: yes, but you have to be more specific on how you have your network setup, you have to tell the router how to get from one subnet to the other. what kind of router do you have? Julio Can you share between or connect a workstation on a '10' series IP with a workstation or router on a '192' series IP? How? Thanks Randall
RE: [luau] routing
yes, but you have to be more specific on how you have your network setup, you have to tell the router how to get from one subnet to the other. what kind of router do you have? Julio + I'm adding a Linksys router (based on 192) to a network with the 10 series. Subnet : 255.255.255.0; subnet class within the ip is the same for all workstations as well, 10.0.0.# . Gateway will be the router : 192. Doesn't look like the linksys can be told how to get from one subnet to another. I'm looking to see if a Linux box will provide me with a solution. Would be nice to see it work with the Linksys, that way I know what to look for when I setup a Linux box. Thanks. Randall
RE: [luau] routing
On Sat, 31 Aug 2002 12:51:38 -1000, Randall Oshita [EMAIL PROTECTED] said: I'm adding a Linksys router (based on 192) to a network with the 10 series. Subnet : 255.255.255.0; subnet class within the ip is the same for all workstations as well, 10.0.0.# . Gateway will be the router : 192. Doesn't look like the linksys can be told how to get from one subnet to another. I'm looking to see if a Linux box will provide me with a solution. Randall- I'd suggest plugging an uplink cable from the 10.0.0.0 network into the WAN port of the Linksys router. Make sure you know whether or not you need a cross-over cable. I'll explain that further if needed. Linksys automatically assigns the internal LAN the 192.168.1.0/24 network scheme, so you should plug the 192 network segment into the designated LAN port of the router. This 192.168.1.0 scheme can be changed if needed, but this default should be fine for this situation. This solution also works great if your ISP stems from the 10 network, and access to the Internet is needed for the 192 network. You would need to setup DHCP on the 192.168.1.0 network workstations, though. With DHCP, you wouldn't need to set up the gateway address on those computers. (That might've been the problem.) Make sure your router is also set to be a DHCP server! The accompanying manual tells you how. Leave the current setup on the 10.0.0.0 network as it was before you installed the Linksys router. That should work. If not, I'm proactively assuming the next adversity might be that uplink/cross-over cable. If you need an explanation for that, please feel free to ask. -elayne
