Hi Pong,
Here's the result of the sh ip route command on both zebra.
ROUTER1:
router1# sh ip route
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
B - BGP, > - selected route, * - FIB route
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
B - BGP, > - selected route, * - FIB route
K>* 10.0.0.0/24 is directly connected, eth1
K * 127.0.0.0/8 is directly connected, lo
C>* 127.0.0.0/8 is directly connected, lo
K>* 169.254.0.0/16 is directly connected, eth2
R>* 172.16.0.0/24 [120/2] via 192.168.2.6, eth2, 00:16:35
K * 192.168.0.0/22 is directly connected, eth2
C>* 192.168.0.0/22 is directly connected, eth2
K * 192.168.1.0/24 is directly connected, eth0
C>* 192.168.1.0/24 is directly connected, eth0
C>* 192.168.3.0/24 is directly connected, eth1
K * 127.0.0.0/8 is directly connected, lo
C>* 127.0.0.0/8 is directly connected, lo
K>* 169.254.0.0/16 is directly connected, eth2
R>* 172.16.0.0/24 [120/2] via 192.168.2.6, eth2, 00:16:35
K * 192.168.0.0/22 is directly connected, eth2
C>* 192.168.0.0/22 is directly connected, eth2
K * 192.168.1.0/24 is directly connected, eth0
C>* 192.168.1.0/24 is directly connected, eth0
C>* 192.168.3.0/24 is directly connected, eth1
ROUTER 2:
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
B - BGP, > - selected route, * - FIB route
B - BGP, > - selected route, * - FIB route
K * 127.0.0.0/8 is directly connected, lo
C>* 127.0.0.0/8 is directly connected, lo
K>* 169.254.0.0/16 is directly connected, eth1
K * 172.16.0.0/24 is directly connected, eth0
C>* 172.16.0.0/24 is directly connected, eth0
K * 192.168.0.0/22 is directly connected, eth1
C>* 192.168.0.0/22 is directly connected, eth1
C>* 127.0.0.0/8 is directly connected, lo
K>* 169.254.0.0/16 is directly connected, eth1
K * 172.16.0.0/24 is directly connected, eth0
C>* 172.16.0.0/24 is directly connected, eth0
K * 192.168.0.0/22 is directly connected, eth1
C>* 192.168.0.0/22 is directly connected, eth1
With your statements below, could you please help me how should I correct the problem?
--------------start------------------
based on your linux routes,
the reason why router2 will not be able to reach the subnets
192.168.3.0/24 and 192.168.1.0/24 is because it will not forward
the packets to router1 due to the fact that it thinks those 2 subnets
are directly attached via its route to 192.168.0.0/22 --> eth1.
the reason why router2 will not be able to reach the subnets
192.168.3.0/24 and 192.168.1.0/24 is because it will not forward
the packets to router1 due to the fact that it thinks those 2 subnets
are directly attached via its route to 192.168.0.0/22 --> eth1.
-------------end--------------------
Thanks again,
Sonny
Pong <[EMAIL PROTECTED]> wrote:
hey sonny,
On Thu, 5 Aug 2004 [EMAIL PROTECTED] wrote:
> I tried using 'show ip route' inside zebra but no such command can be found so
> I use MRLG mentioned in this URL
> http://www-106.ibm.com/developerworks/linux/library/l-emu/ but when I
> tried to execute 'show ip route' nothing appeared in the web console.
connect to the main zebra router process and issue 'show ip route' there.
if you connect to the rip router process, the command will not be found.
the main zebra router process consolidates all routes received from the
dynamic routing protocols it handles such as RIP.
>
> Here's the result of the 'route' command in the linux box (router1):
>
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.3.0 * 255.255.255.0 U 0 0 0 eth1
> 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
> 192.168.0.0 * 255.255.252.0 U 0 0 0 eth2
> 169.254.0.0 * 255.255.0.0 U 0 0 0 eth2
> 127.0.0.0 * 255.0.0.0 U 0 0 0 lo
>
> Here's the result of the route command in the linux box (router2):
>
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 172.16.0.0 * 255.255.255.0 U 0 0 0 eth0
> 192.168.0.0 * 255.255.252.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
>
>
based on your linux routes,
the reason why router2 will not be able to reach the subnets
192.168.3.0/24 and 192.168.1.0/24 is because it will not forward
the packets to router1 due to the fact that it thinks those 2 subnets
are directly attached via its route to 192.168.0.0/22 --> eth1.
pong
--
Philippine Linux Users' Group (PLUG) Mailing List
[EMAIL PROTECTED] (#PLUG @ irc.free.net.ph)
Official Website: http://plug.linux.org.ph
Searchable Archives: http://marc.free.net.ph
.
To leave, go to http://lists.q-linux.com/mailman/listinfo/plug
.
Are you a Linux newbie? To join the newbie list, go to
http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
-- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
