From owner-freebsd-questions@FreeBSD.ORG Sun Jan 25 14:50:23 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB03D838 for ; Sun, 25 Jan 2015 14:50:23 +0000 (UTC) Received: from potato.growveg.org (potato.growveg.org [62.49.247.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 43E36CED for ; Sun, 25 Jan 2015 14:50:23 +0000 (UTC) Received: from john by potato.growveg.org with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1YFNyA-000A1A-EA for freebsd-questions@freebsd.org; Sun, 25 Jan 2015 14:15:18 +0000 Date: Sun, 25 Jan 2015 14:15:18 +0000 From: John To: freebsd-questions@freebsd.org Subject: real IP and rfc1918 IP on the same machine - how? Message-ID: <20150125141518.GA23664@potato.growveg.org> Mail-Followup-To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: John X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: john@potato.growveg.org X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 14:50:23 -0000 hello freebsd-questions, I have a workstation with two NICs - one wired (real IP address on a /28) and one wireless, which I want to configure to use the protected wireless LAN on 192.168.100.0/24. I want the internet to route through real IP address, and I want access to the wireless LAN. I don't want to route out to the internet through the wireless LAN, I just need to be able to contact the machines within it. The wireless LAN itself has its own gateway, which is not this machine but a wifi access point. How can I configure the ath0 interface so it sees the wireless LAN but doesn't break routing to the outside world on this machine? Both interfaces will have static IPs. I have tried statically assigning ath0 (wireless interface) to 192.168.100.100 255.255.255.0 , em0 interface to [real IP] and default gateway to the real IP of the gateway, but once I bring the interfaces up I cannot access the real IP of the default gateway. can anyone help? thanks, -- John