From owner-freebsd-questions@FreeBSD.ORG Sat May 7 22:41:18 2011 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AA7B1065670 for ; Sat, 7 May 2011 22:41:18 +0000 (UTC) (envelope-from norgaard@locolomo.org) Received: from mail.locolomo.org (97.pool85-48-194.static.orange.es [85.48.194.97]) by mx1.freebsd.org (Postfix) with ESMTP id F08B68FC08 for ; Sat, 7 May 2011 22:41:17 +0000 (UTC) Received: from gamma.local (unknown [189.152.251.113]) by mail.locolomo.org (Postfix) with ESMTPSA id 591381C0841; Sun, 8 May 2011 00:41:12 +0200 (CEST) Message-ID: <4DC5CA83.6080009@locolomo.org> Date: Sat, 07 May 2011 17:41:07 -0500 From: =?ISO-8859-1?Q?Erik_N=F8rgaard?= User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Arun References: <214923.99033.qm@web111721.mail.gq1.yahoo.com> In-Reply-To: <214923.99033.qm@web111721.mail.gq1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Lokadamus , questions@freebsd.org Subject: Re: Link and network level in the tcp/ip stack X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 May 2011 22:41:18 -0000 On 7/5/11 4:12 PM, Arun wrote: > 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. Hi: There can only be one default gateway, anything else doesn't make sense. I did try adding a specific route on SRV for RN such that pings arriving on 10.225.162.28 would be responded correctly. But, then RN can no longer reach 192.168.28.196. No surprise there really. So, why do we have this setup? Well, some services like ssh that is used for administration must arrive on 192.168.28/24 where as the commercial service has a dedicated network on 10.225.162/24 and to ensure availability and bandwidth we cannot accept to have ssh coming in on that network. I should add that this is a Red Hat Linux, I ask here since the FBSD implementation of the tcp/ip stack is considered the reference implementation. So the question is which behaviour is correct, recommended or accepted? Stripping the link layer and reply according to the network layer, or keeping the link layer? Thanks, Erik