[SLE] Routing w/ a Webramp
I have a Webramp 200i that is hooked to my Linux box. The 200i's IP is 192.168.0.250 and the Linux box is 192.168.0.79. I added the ...250 as my gateway in YAST and I have checked for the listing for route -n : 0.0.0.0 192.168.0.250 255.255.255.0 UG eth0 (I think, have to do it from memory) I can ping the webramp and open its config in Netscape but no trafic goes out, I get a Network Unreachable error. Am I missing something? <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type> <META content="MSHTML 5.00.2614.3500" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face=Arial size=2>I have a Webramp 200i that is hooked to my Linux box. The 200i's IP is 192.168.0.250 and the Linux box is 192.168.0.79. I added the ...250 as my gateway in YAST and I have checked for the listing for route -n : </FONT></DIV> <DIV><FONT face=Arial size=2>0.0.0.0 192.168.0.250 255.255.255.0 UG eth0</FONT></DIV> <DIV><FONT face=Arial size=2>(I think, have to do it from memory) I can ping the webramp and open its config in Netscape but no trafic goes out, I get a Network Unreachable error. Am I missing something?</FONT></DIV> <DIV> </DIV></BODY>
Patrick K Moorman wrote:
I have a Webramp 200i that is hooked to my Linux box. The 200i's IP is 192.168.0.250 and the Linux box is 192.168.0.79. I added the ...250 as my gateway in YAST and I have checked for the listing for route -n : 0.0.0.0 192.168.0.250 255.255.255.0 UG eth0 (I think, have to do it from memory) I can ping the webramp and open its config in Netscape but no trafic goes out, I get a Network Unreachable error. Am I missing something?
Are your masks set up right? As I see it, your Linux box knows how to reach all hosts in network 192.168.0, because it is in the same network. So you don't have to add another host-route. As long as your mask is set to 255.255.255.0 you're allright. If your Linux box and the 200i have different masks, it might not work, because one of the addresses may very well be network- or broadcast-addressess. Also, if your 200i is routing in stead of masquerading, you'll get these errors also, because network 192.168 is not routable. See if the 200i is routing. If so, change that to masquerading, or enable the NAT setting. This all is said assuming the 200i is a router, I haven't even heard of it, so I might be *way* off here! Good luck! Rogier Maas -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (2)
-
icarus@guldennet.nl
-
khadji@pld.com