From owner-freebsd-questions@FreeBSD.ORG Mon Nov 20 16:42:44 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 44C8216A412 for ; Mon, 20 Nov 2006 16:42:44 +0000 (UTC) (envelope-from ml@proficuous.com) Received: from mail.proficuous.com (www.proficuous.com [209.240.79.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6AAC43F64 for ; Mon, 20 Nov 2006 16:33:39 +0000 (GMT) (envelope-from ml@proficuous.com) Received: from [192.168.3.68] (unknown [192.168.3.68]) by mail.proficuous.com (Postfix) with ESMTP id 0EEEAA8ACEF; Mon, 20 Nov 2006 10:33:29 -0600 (CST) Message-ID: <4561D8DD.90208@proficuous.com> Date: Mon, 20 Nov 2006 10:33:33 -0600 From: Aaron Martinez User-Agent: Thunderbird 1.5.0.8 (X11/20061112) MIME-Version: 1.0 To: Jerry McAllister References: <4561D4A6.10702@proficuous.com> <20061120162512.GB38498@gizmo.acns.msu.edu> In-Reply-To: <20061120162512.GB38498@gizmo.acns.msu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org 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 16:42:44 -0000 Jerry McAllister wrote: > On Mon, Nov 20, 2006 at 10:15:34AM -0600, 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" >> > > Well, since it seems that 'ping' is the one that is complaining, > you might include exactly the ping command that you have been > typing in your post. (Or have you actually been trying to use > the 'sendto' directly in a program - if so send that information). > > ////jerry > ping 192.168.5.6 as well as /sbin/ping 192.168.5.6 traceroute gives me a similar responese: /usr/sbin/traceroute 192.168.5.6 traceroute to 192.168.5.6 (192.168.5.6), 64 hops max, 40 byte packets traceroute: sendto: Invalid argument 1 traceroute: wrote 192.168.5.6 40 chars, ret=-1 *traceroute: sendto: Invalid argument traceroute: wrote 192.168.5.6 40 chars, ret=-1 *traceroute: sendto: Invalid argument traceroute: wrote 192.168.5.6 40 chars, ret=-1 Aaron > >> 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" >>