Date: Wed, 14 Jan 2004 22:24:11 +1100 From: Tony Frank <tfrank@optushome.com.au> To: "Nicol?s de Bari Embr?z G. R." <nbari@unixmexico.com> Cc: freebsd-isp@freebsd.org Subject: Re: Routing Networks Message-ID: <20040114112411.GA4492@marvin.home.local> In-Reply-To: <52975.148.243.211.1.1074063556.squirrel@mail.unixmexico.com> References: <52975.148.243.211.1.1074063556.squirrel@mail.unixmexico.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi there, On Wed, Jan 14, 2004 at 12:59:16AM -0600, Nicol?s de Bari Embr?z G. R. wrote: > 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 ? Easy option is to ensure that a static route is configured on the Linux server to route 192.168.10.0/24 to 192.168.1.1 (your server IP) > 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. Given this restriction, the best option might be to ensure that anything received on FreeBSD server from 192.168.10.0 subnet is passed through NAT to appear to originate from the FreeBSD server IP (192.168.1.1) This would allow traffic initiated from LAN A to talk to LAN B but typically would not allow LAN B to initiate traffic to LAN A. Unfortunately I have not used ipnat at all so cannot help in that aspect. With ipfw/natd I would have two natd instances and use ipfw rules to send packets to different divert sockets based on the IP address. Regards, Tony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040114112411.GA4492>