Link and network level in the tcp/ip stack

[Arun]

Correction - read NOT in line : "If your SRV node could NOT forward the ping reply then add a ..."

Niether it is a problem of small subnet nor NIC card. The problem is of routing entries.
 
Just add default route at your node 10.225.162.28, and make the default GW for this route as  192.168.28.0/24 or the connected interface. Your SRV node should pass it to its default gw 192.168.28.1 which should take care of forwarding it to the destination RN. If your SRV node could NOT forward the ping reply then add a specific route there like - "pkt comes from 10.225.162.0 then forward it to 192.168.28.1.
Thanks.

______________________________________________________________
Before printing, think about your ENVIRONMENTAL responsibility.


--- On Sun, 5/8/11, Arun <p26a at yahoo.com> wrote:


From: Arun <p26a at yahoo.com>
Subject: Re: Link and network level in the tcp/ip stack
To: "Erik Nørgaard" <norgaard at locolomo.org>, "Lokadamus" <lokadamus at gmx.de>
Cc: questions at freebsd.org
Received: Sunday, May 8, 2011, 2:00 AM


Niether it is a problem of small subnet not NIC card. The problem is of routing entries.
 
Just add default route at your node 10.225.162.28, and make the default GW for this route as  192.168.28.0/24 or the connected interface. Your SRV node should pass it to its default gw 192.168.28.1 which should take care of forwarding it to the destination RN. If your SRV node could forward the ping reply then add a specific route there like - "pkt comes from 10.225.162.0 then forward it to 192.168.28.1.
Thanks.

______________________________________________________________
Before printing, think about your ENVIRONMENTAL responsibility.



 
 --- On Sun, 5/8/11, Lokadamus <lokadamus at gmx.de> wrote:


From: Lokadamus <lokadamus at gmx.de>
Subject: Re: Link and network level in the tcp/ip stack
To: "Erik Nørgaard" <norgaard at locolomo.org>
Cc: questions at freebsd.org
Received: Sunday, May 8, 2011, 12:22 AM


Am 06.05.2011 23:17, schrieb Erik Nørgaard:
> Hi:
> 
> This is a generic question about may, should and must:
> 
> I have the following setup:
> 
>    192.168.28/24
>  +---------------+
>  |.196         |.1
> SRV        GW--------- RN
>  |.28         |.1
>  +---------------+
>    10.225.162/24
> 
> The server, SRV, has default gateway set to 192.168.28.1, no routing has been configured for the 10.225.162/24 network. The gateway is a router, no NAT or firewall. Yup, we do have this setup, don't ask why.
> 
> Now, the remote node RN pings the server on 192.168.28.196 fine, no problem. Then it pings 10.225.162.28 and get destination unreachable.
> 
> OK, so I did tcpdump first on the 10.225.162.28 interface, and saw icmp echo requests coming in, but no replies going out. Then I did tcpdump on the other interface and got this:
> 
> 13:39:43.233419 arp who-has 192.168.28.1 tell 10.225.162.28
> 
> obviously no reply, wrong network.
> 
Can your SRV (10.225.162.28) ping anything in 192.168.28?
I don't think, because your SRV is looking for its gateway, but never get an answer from it.
It's subnetmask is to small to reach another subnet.

Put another network card in it with an ip of 192.168.28 and all will working.

Sorry for my bad english ;(
> Thanks, Erik
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
> 

_______________________________________________
freebsd-questions at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
_______________________________________________
freebsd-questions at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"