not able to ping from one n/w to another using linux box installed with zebra
hi,
we had installed zebra(ver 0.93b) on linux kernel(2.4.19). after all the procedures involved in the installing process, configuring interface parameters for eth0 and eth1. we are not able to ping from the router. we are using 3 pcs one is configured for zebra(linux box) another as host one more the server. the problem is we are not able to ping from the server to the host pc through the linuxbox. what should be done, plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz help out. thanz , abirami |
Re: not able to ping from one n/w to another using linux box installed with zebra
Quote:
so=> HOST----------linuxbox----------SERVER if yes, can both HOST and SERVER ping the linuxbox? => if yes, can you post your routing table pls? also give us some details about your network topology (adresses, NICs,...) |
Thanx for ur time
Actually i'm newbie to zebra routers. I've configured zebra on linux machine. The routing table (ip route command)shows the following details:- 192.168.1.0/24 dev eth0 scope link 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.35 169.254.0.0/16 dev eth0 scope link 127.0.0.0/8 dev lo scope link Now, we are able to ping from the router(linux box) to the server and the host but we are not able to ping from the host to the server through the router what has to be done to make it ping? Thanx in advance for your help Regards Abirami |
could you also give me:
-the ip addresses of all pc's involved -type the "route" command and send the output |
Thanks for ur response,
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.0.0 192.168.0.35 255.255.255.0 UG 0 0 0 eth1 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.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 0.0.0.0 0.0.0.0 U 0 0 0 eth0 we tried all possible things,but still we are not able to ping from host(192.168.0.39) to server(192.168.1.1) through our linuxbox(configured to zebra) having eth0 interface(192.168.1.102) and eth1 interface(192.168.0.35). thanx, abirami |
A few problems:
first: 192.168.0.0 192.168.0.35 255.255.255.0 UG 0 0 0 eth1 => this line tells the box to send all traffic for 192.168 to 192.168.0.35 how can it do that if it doesnt know where it is? I'd just remove that line. second: you have a subnet called 192.168.1.0 and one called 192.168.0.0 thing is, 192.168.1.0 is actually a subnet of 192.168.0.0, so if you redirect all traffic for 192.168.0.0 to a certain ethernet card, you are actually redirecting the traffic for 192.168.1.0 as well. You shouldn't be using 192.168.0.0 and 192.168.1.0 on a network together. try using 192.168.1.0 and 192.168.2.0. your routing table will look like 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 eth0 (this line is wherever the internet is) |
hi symen,
thanz a lot, u r idea worked out. now, we are able to ping. can u just give us a idea how to test the performance and functionality of RIP, OSPF ,BGP protocols using zebra (our linux router box). once again thanz for ur reply, bye, abirami. |
eh, no, I don't know anything about that ;)
|
All times are GMT -5. The time now is 02:59 AM. |