From owner-freebsd-questions@FreeBSD.ORG Mon Nov 20 17:07:29 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F12F916A508 for ; Mon, 20 Nov 2006 17:07:29 +0000 (UTC) (envelope-from lane@joeandlane.com) Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id A77CB444CE for ; Mon, 20 Nov 2006 16:46:57 +0000 (GMT) (envelope-from lane@joeandlane.com) Received: from [66.47.111.183] (helo=joeandlane.com) by elasmtp-dupuy.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1GmCI5-0003zM-8n for freebsd-questions@freebsd.org; Mon, 20 Nov 2006 11:46:41 -0500 Received: from joeandlane.com (localhost.localnet.local [127.0.0.1]) by joeandlane.com (8.13.8/8.13.1) with ESMTP id kAKGnaeN046040 for ; Mon, 20 Nov 2006 10:49:36 -0600 (CST) (envelope-from lane@joeandlane.com) Received: from localhost (localhost [[UNIX: localhost]]) by joeandlane.com (8.13.8/8.13.1/Submit) id kAKGnaQl046039 for freebsd-questions@freebsd.org; Mon, 20 Nov 2006 10:49:36 -0600 (CST) (envelope-from lane@joeandlane.com) From: Lane To: freebsd-questions@freebsd.org Date: Mon, 20 Nov 2006 10:49:36 -0600 User-Agent: KMail/1.9.3 References: <4561D4A6.10702@proficuous.com> In-Reply-To: <4561D4A6.10702@proficuous.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611201049.36275.lane@joeandlane.com> X-CD-SOLUTIONS-MailScanner-Information: Please contact the ISP for more information X-CD-SOLUTIONS-MailScanner: Found to be clean X-CD-SOLUTIONS-MailScanner-From: lane@joeandlane.com X-ELNK-Trace: e56a4b6ca9bdfda11aa676d7e74259b7b3291a7d08dfec79200374bd7a82ade20f67e8a44f56f196350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.47.111.183 Subject: Re: ping send to problem, what am i missing 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: Mon, 20 Nov 2006 17:07:30 -0000 On Monday 20 November 2006 10:15, Aaron Martinez wrote: > I'm trying to get some routing working from my freebsd 6.1 machine that > i thought should be extremely easy, but not having any luck. When > trying to ping the destination address (192.168.5.6) i get : "ping: > sendto: Invalid argument" > > the net goes like so: freebsd6.1----linux router-----another linux > router---openbsd machine (running openvpn) > > the corresponding routing tables are as such: > > freebsd6.1: > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 192.168.3.94 UGS 1 121441 fxp0 > 127.0.0.1 127.0.0.1 UH 0 0 lo0 > 192.168.3.64/27 link#1 UC 0 0 fxp0 > 192.168.3.94 00:40:f4:76:3d:d3 UHLW 2 106622 fxp0 1154 > 192.168.4.1/32 192.168.4.5 UGS 0 2042 tun0 > 192.168.4.5 192.168.4.6 UH 1 0 tun0 > 192.168.5 192.168.0.66 UGS 0 154 fxp0 > > > I manually added the 192.168.5 route using the following command (please > correct me if i did it incorrectly > > route -n add 192.168.5/24 192.168.0.66 > > > first linux router: > Kernel IP routing table > Destination Gateway Genmask Flags MSS Window irtt > Iface > 192.168.3.32 0.0.0.0 255.255.255.224 U 40 0 0 > eth0 > 192.168.3.96 0.0.0.0 255.255.255.224 U 40 0 0 > eth2 > 192.168.3.64 0.0.0.0 255.255.255.224 U 40 0 0 > eth1 > 192.168.3.160 0.0.0.0 255.255.255.224 U 40 0 0 > eth4 > 192.168.3.128 0.0.0.0 255.255.255.224 U 40 0 0 > eth3 > 0.0.0.0 192.168.3.62 0.0.0.0 UG 40 0 0 > eth0 > > > second linux router: > Kernel IP routing table > Destination Gateway Genmask Flags MSS Window irtt > Iface > 192.168.3.32 0.0.0.0 255.255.255.224 U 40 0 0 > eth3 > 192.168.3.96 192.168.3.34 255.255.255.224 UG 40 0 0 > eth3 > 192.168.3.64 192.168.3.34 255.255.255.224 UG 40 0 0 > eth3 > 192.168.3.160 192.168.3.34 255.255.255.224 UG 40 0 0 > eth3 > 192.168.3.128 192.168.3.34 255.255.255.224 UG 40 0 0 > eth3 > 192.168.2.0 0.0.0.0 255.255.255.0 U 40 0 0 > eth2 > 192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 > eth1 > 192.168.0.0 0.0.0.0 255.255.255.0 U 40 0 0 > eth0 > 0.0.0.0 0.0.0.0 0.0.0.0 U 40 0 0 > dsl1 > > > openbsd machine: > Routing tables > > Internet: > Destination Gateway Flags Refs Use Mtu > Interface > default 192.168.0.254 UGS 5 516934 - rl0 > 127/8 127.0.0.1 UGRS 0 0 33224 lo0 > 127.0.0.1 127.0.0.1 UH 1 125 33224 lo0 > 192.168.0/24 link#1 UC 2 0 - rl0 > 192.168.0.2 00:d0:b7:8f:51:41 UHLc 0 5 - rl0 > 192.168.0.254 00:e0:18:90:17:f1 UHLc 1 0 - rl0 > 192.168.4/24 192.168.4.2 UGS 0 2042 - tun0 > 192.168.4.2 192.168.4.1 UH 1 0 - tun0 > 192.168.5/24 192.168.5.2 UGS 0 3411 - tun1 > 192.168.5.2 192.168.5.1 UH 1 5 - tun1 > 224/4 127.0.0.1 URS 0 0 33224 lo0 > > > i can successfully ping the 192.168.0.66 host with no problems, so i'm > guessing that most of my routes are fine, i am a little suspect however > about the route i manually put in. I can also ping the 192.168.5.6 > address FROM the openbsd machine. All firewalls between these machines > ARE disabled. i DO have ip forwarding enabled on the OPENBSD machine: > # sysctl -a | grep > forward > > net.inet.ip.forwarding=1 > > > I can't figure what's going on here any help would be terribly > appreciated. Any more info that is needed just ask. > > thanks in advance, > > Aaron > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" Aaron, It looks like the FreeBSD and the OpenBSD machines are vpn tunnelling through the linux routers, right? If that is the case then you really shouldn't have to mess around with manual routing tables, at all. You should be looking at the OpenVPN configuration. If I was working on this problem, I'd first shut down openvpn and verify that FreeBSD and OpenBSD can talk along their default routes (it looks like they each have only one nic, so the default routes will be used). Next, after I am able to verify clear communication from both sides, I'd start working on the OpenVPN configuration. When configured correctly the openvpn server will push an appropriate route to the client, and presto! VPN. lane