Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 7 May 2011 13:30:01 -0700 (PDT)
From:      Arun <>
To:        =?iso-8859-1?Q?Erik_N=F8rgaard?= <>, Lokadamus <>
Subject:   Re: Link and network level in the tcp/ip stack
Message-ID:  <>
In-Reply-To: <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Niether it is a problem of small subnet not NIC card. The problem is of rou=
ting entries.
Just add default route at your=A0node, and make the default G=
W for this route as =A0192.168.28.0/24 or the connected interface. Your SRV=
 node should pass it to its default gw 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=A010.225.=
162.0 then forward it to

Before printing, think about your ENVIRONMENTAL responsibility.

=A0--- On Sun, 5/8/11, Lokadamus <> wrote:

From: Lokadamus <>
Subject: Re: Link and network level in the tcp/ip stack
To: "Erik N=F8rgaard" <>
Received: Sunday, May 8, 2011, 12:22 AM

Am 06.05.2011 23:17, schrieb Erik N=F8rgaard:
> Hi:
> This is a generic question about may, should and must:
> I have the following setup:
>=A0 =A0 192.168.28/24
>=A0 +---------------+
>=A0 |.196=A0 =A0 =A0 =A0=A0=A0|.1
> SRV=A0 =A0 =A0 =A0 GW--------- RN
>=A0 |.28=A0 =A0 =A0 =A0=A0=A0|.1
>=A0 +---------------+
>=A0 =A0 10.225.162/24
> The server, SRV, has default gateway set to, 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 fine, no probl=
em. Then it pings and get destination unreachable.
> OK, so I did tcpdump first on the interface, and saw icmp e=
cho 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 tell
> obviously no reply, wrong network.
Can your SRV ( ping anything in 192.168.28?
I don't think, because your SRV is looking for its gateway, but never get a=
n 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 workin=

Sorry for my bad english ;(
> Thanks, Erik
> _______________________________________________
> mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o=

_______________________________________________ mailing list
To unsubscribe, send any mail to "

Want to link to this message? Use this URL: <>