Boson NetSim , anyone face this problem?

lAwBoY

hi, i have install Boson NetSim, but notice one bug in the program, dont noe anyone have this program as well
i use the Boson network to plan my network, but i notice that my pc connected to the e0 of the router unable to ping to the S1 of router 2
the pc can ping e0, s0 of router 1 but not s1 of router 2

PC

---

E0, SO(Router 1) ----S1(Router2)


can anyone help me?

lAwBoY

this are the ip address

pc - 165.10.10.2 /24

Router 1
E0 - 165.10.10.1 /24
S0 - 202.0.0.1 /24

Router 2
S1 - 202.0.0.2 /24

why from pc , i can ping s0 of router 1 but not router 2 s1

lordy

First thing coming to my mind: Does the PC have a default route ?

lAwBoY

lordy wrote:

First thing coming to my mind: Does the PC have a default route ?

i dont noe leh.. but i already set the pc gateway to be the pc E0. so it would work right?

2lazybutsmart

You won't be able to ping s1 of router2 unless you enable routing on both routers. Routing isn't enabled by default just because the machines are called routers. You gotta turn them (RIP, IGRP, etc...) on.

2lbs.

jd_mattos

You have to have some routing protocol like 2lazy said, or set up static routes on the routers.

lAwBoY

2lazybutsmart wrote:

You won't be able to ping s1 of router2 unless you enable routing on both routers. Routing isn't enabled by default just because the machines are called routers. You gotta turn them (RIP, IGRP, etc...) on.

2lbs.

thanks it works now...

2lazybutsmart

Here's a TechNote on configuring RIP.

http://www.techexams.net/techlabs/ccna/lab_1_rip.shtml

What are you using to study with?

lAwBoY

cause i alway thought that since router can ping next hop address without settting the routing protocol, the pc which is connected to E) should be able to ping to the router next hop as well

2lazybutsmart

Well that's why it's important to really understand what a router does when it recieves a packet destined for a remote network:

1- It checks the network address and determines that it's for a remote network (meaning not local).

2- It looks up the routing table for an entry for that network, if it doesn't find one, it will drop the packet. That's when you'll get the "Destination Unreachable" message.

3- If there is an entry for the network, it frames it and sends it out the interface for that network.

4- When the packet comes to it's destination at the remote network, (if your packet was a ping, suppose..) then the reply will have to come back from the destination host/router. This is where most of the confusion arises. If Router B, in your scenario, doesn't have an entry for the network that's connected on E0 of routerA (which it won't by default), then it will drop the packet on it's way back and send you a "Request timed out" message.

A router can ping (reach) everybody "directly" connected. In your case, routerA doesn't have a problem, it's RouterB that doesn't have RouterA's E0 interface directly connected.

2lbs.

QUIX0TIC

Wow... nice explanation 2lbs.

lAwBoY

2lazybutsmart wrote:

Well that's why it's important to really understand what a router does when it recieves a packet destined for a remote network:

1- It checks the network address and determines that it's for a remote network (meaning not local).

2- It looks up the routing for an entry for that network, if it doesn't find one, it will drop the packet. That's when you'll get the "Destination Unreachable" message.

3- If there is an entry for the network, it frames it and sends it out the interface for that network.

4- When the packet comes to it's destination at the remote network, (if your packet was a ping, suppose..) then the reply will have to come back from the destination host/router. This is where most of the confusion arises. If Router B, in your scenario, doesn't have an entry for the network that's connected on E0 of routerA (which it won't by default), then it will drop the packet on it's way back and send you a "Request timed out" message.

A router can ping (reach) everybody "directly" connected. In your case, routerA doesn't have a problem, it's RouterB that doesn't have RouterA's E0 interface directly connected.

2lbs.

thanks.. i fully understand it now
it due to router b that doesnt have routera e0 interface thus droping the reply

QUIX0TIC

You should check if you can initiate debugging on router 2 to see if it is receiving the pings from the PC. That would be able to tell you that you are seeing the ping from the pc but it is dropping the packet on the way back out.

johnnynodough

Here is another bug with Boson Netsim -

Yay! More bugs with Boson Netsim. ISDN configuration, if you type in a dialer list statement wrong, it will take and wont give an invalid command error, puts it in the running config in, and wont let you negate it. You have to reload the router and start from scratch icon_lol.gif