From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 15:15:02 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8109816A4D0 for ; Wed, 14 Jan 2004 15:15:02 -0800 (PST) Received: from ns1.unixmexico.net (ns1.unixmexico.net [69.10.138.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 944A943D5D for ; Wed, 14 Jan 2004 15:14:56 -0800 (PST) (envelope-from nbari@unixmexico.com) Received: (qmail 71559 invoked by uid 85); 14 Jan 2004 23:19:18 -0000 Received: from nbari@unixmexico.com by ns1.unixmexico.net by uid 82 with qmail-scanner-1.16 (hbedv: 6.22.0.1/6.22.0.6. Clear:. Processed in 0.359774 secs); 14 Jan 2004 23:19:18 -0000 Received: from ns1.unixmexico.net (HELO mail.unixmexico.com) ([69.10.138.161]) (envelope-sender ) by ns1.unixmexico.net (qmail-ldap-1.03) with SMTP for ; 14 Jan 2004 23:19:18 -0000 Received: from 200.23.123.104 (SquirrelMail authenticated user nbari@unixmexico.com) by mail.unixmexico.com with HTTP; Wed, 14 Jan 2004 17:19:18 -0600 (CST) Message-ID: <1784.200.23.123.104.1074122358.squirrel@mail.unixmexico.com> Date: Wed, 14 Jan 2004 17:19:18 -0600 (CST) From: =?iso-8859-1?Q?Nicol=E1s_de_Bari_Embr=EDz_G._R.?= To: freebsd-net@freebsd.org, freebsd-questions@freebsd.org, freebsd-isp@freebsd.org User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Solution to Routing Networks X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2004 23:15:02 -0000 Hi all thanks for all your answers. The solution that i found was to add to my ipnat.rules this lines: map dc1 192.168.10.0/24 -> 0/32 portmap tcp/udp auto map dc1 192.168.10.0/24 -> 0/32 and to my rc.conf this : static_routes="linux" route_linux="192.168.0.0/16 192.168.1.3" regards. Hi all, I need some help routing or making Nat on a LAN. I have something like this: I N T E R N E T ----------------- ^ ^ | | fxp0 public IP public IP | | FreeBSD server LINUX server | | dc0 192.168.10.1 | dc1 192.168.1.1 ^ 192.168.1.3 ^ | ^ | | | | | | ---------------- | Switch/Hub | ---------------- | | ------------------ ----------------- | LAN A | | LAN B | | 192.168.10.2-254 | | 192.168.1.4-100 | ------------------ ----------------- I have running a FreeBSD server as a gateway and DHCP, the server share the Internet to all the computers on LAN A (192.168.10.0/24). The server have 3 network cards: fxp0 is public IP. dc0 is the gateway for the LAN A "192.168.10.1". dc1 has IP 192.168.1.1 ( need help with this ). Right now i am just using fxp0 and dc0 so any computer on the LAN A "192.168.10.2-254" can have Internet, my ipnat.rules file looks like this: -- map fxp0 192.168.10.1/24 -> 0/32 portmap tcp/udp auto map fxp0 192.168.10.1/24 -> 0/32 -- until that point everything just work OK. There is another network, I will call it LAN B, this LAN make the same thing that i am doing with the FreeBSD Server, but instead it uses LINUX, the m achine have 2 network cars. eth0 has a public IP. eth1 is the gateway for the LAN B "192.168.1.3" Both networks are connected to the same switch/hub, but now i need that the computers of LAN A can see "ping" computers on LAN B. If I configure the third nick "dc1" on the FreeBSD server to have an IP on the range of LAN B for example with ip 192.168.1.1, then I can see all the computers from both LAN's, I can ping, telnet, ssh etc. to both 192.168.10.X and 192.168.1.X. networks "standing on the FreeBSD server." What i want to do is that a computer on LAN A with an IP on the range of 192.168.10.2-254 can ping, telnet, ssh, etc. to a computer on LAN B "192.168.1.X". How can i solve this problem, is this is a route or Nat problem ? There is one more issue, I can't touch the LINUX SERVER I can just be a client or join the LAN by configure a nic with a IP on the range of 192.168.1.0/24. I have been trying to fix this with static routes but i am not having luck. Any help will be apreciated. regards. -- nbari@unixmexico.com key ID 1EF56FDC -- nbari@unixmexico.com key ID 1EF56FDC -- nbari@unixmexico.com key ID 1EF56FDC