From owner-freebsd-net@FreeBSD.ORG Sun Jan 18 03:45:23 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 C643616A4CE for ; Sun, 18 Jan 2004 03:45:23 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C3BC43D4C for ; Sun, 18 Jan 2004 03:45:22 -0800 (PST) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i0IBjJAB001498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 18 Jan 2004 14:45:19 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i0IBjIHU001497; Sun, 18 Jan 2004 14:45:18 +0300 (MSK) Date: Sun, 18 Jan 2004 14:45:17 +0300 From: Gleb Smirnoff To: Andrew Thomas Message-ID: <20040118114517.GA1360@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Andrew Thomas , freebsd-net@freebsd.org References: <20040118073042.51571.qmail@web60506.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040118073042.51571.qmail@web60506.mail.yahoo.com> User-Agent: Mutt/1.5.4i cc: freebsd-net@freebsd.org Subject: Re: MPD server not routing 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: Sun, 18 Jan 2004 11:45:23 -0000 On Sat, Jan 17, 2004 at 11:30:42PM -0800, Andrew Thomas wrote: A> I'm trying to get mpd working as a simple vpn server. I'm doing A> this on a 4.9-STABLE machine of a week or so ago. No matter what A> I do, packets will not route to the client. The login is fine, A> the server machine has gateway enabled=YES (and in fact works OK <==skip==> For me mpd works well on STABLE system. I suppose, you should examine your firewall configuration, and NAT, if there is one. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Sun Jan 18 07:39:01 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 C414816A4CE; Sun, 18 Jan 2004 07:39:01 -0800 (PST) Received: from ftp.bjpu.edu.cn (ftp.bjpu.edu.cn [202.112.78.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75E3F43D48; Sun, 18 Jan 2004 07:38:38 -0800 (PST) (envelope-from delphij@frontfree.net) Received: by ftp.bjpu.edu.cn (Postfix, from userid 426) id E913252D4; Sun, 18 Jan 2004 23:38:35 +0800 (CST) Received: from beastie.frontfree.net (beastie.frontfree.net [218.107.145.7]) by ftp.bjpu.edu.cn (Postfix) with ESMTP id A4BD55299; Sun, 18 Jan 2004 23:38:35 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 426) id 6A0651195B; Sun, 18 Jan 2004 23:38:34 +0800 (CST) Received: from phantasm205 (unknown [221.216.129.200]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by beastie.frontfree.net (Postfix) with ESMTP id CEA0D11552; Sun, 18 Jan 2004 23:38:32 +0800 (CST) Message-ID: <054301c3ddd9$24070f30$0401a8c0@phantasm205> From: "Xin LI" To: "Andre Oppermann" References: <042601c3dcb0$de90c410$0401a8c0@phantasm205> <400976AA.169D1440@freebsd.org> <01ae01c3dd27$2f459c20$0401a8c0@phantasm205> <40098084.E2FA06B0@freebsd.org> Date: Sun, 18 Jan 2004 23:38:34 +0800 Organization: Phantasm Studio MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.0 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 cc: freebsd-net@FreeBSD.org Subject: Re: Newbie question: is net.inet.ip.fastforwarding intended for routersonly? 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: Sun, 18 Jan 2004 15:39:01 -0000 It's FreeBSD 5.2-RELEASE, the uname is: FreeBSD servers.frontfree.net 5.2-RELEASE FreeBSD 5.2-RELEASE #19: Sun Jan 11 04:22:44 CST 2004 delphij@servers.frontfree.net:/usr/obj/usr/src/sys/SERVERS i386 I think peter's rev. 1.5 of sys/netinet/ip_fastfwd.c is not a functional change? Do you need my kernel configuration or any other information as well? Thanks in advance. Xin LI ----- Original Message ----- From: "Andre Oppermann" To: "Xin LI" Cc: Sent: Sunday, January 18, 2004 2:35 AM Subject: Re: Newbie question: is net.inet.ip.fastforwarding intended for routersonly? > What exact version of FreeBSD are you running? I must admit that I > was only able to do limited tests with ipfilter. IPFW I could test > to the full extent. The more information I get from you the better > I can track down where the problem is. From owner-freebsd-net@FreeBSD.ORG Sun Jan 18 10:52:35 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 B680316A4CE for ; Sun, 18 Jan 2004 10:52:35 -0800 (PST) Received: from server34.totalchoicehosting.com (server34.totalchoicehosting.com [69.50.194.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A6A843D39 for ; Sun, 18 Jan 2004 10:52:28 -0800 (PST) (envelope-from niranjan@monsoonrain.net) Received: from cpanel by server34.totalchoicehosting.com with local (Exim 4.24) id 1AiI24-0003ZM-LG; Sun, 18 Jan 2004 11:52:24 -0700 Received: from localhost (localhost [127.0.0.1]) by www.monsoonrain.net (IMP) with HTTP for ; Sun, 18 Jan 2004 13:52:24 -0500 Message-ID: <1074451944.400ad5e888ba4@www.monsoonrain.net> Date: Sun, 18 Jan 2004 13:52:24 -0500 From: niranjan@monsoonrain.net To: nil000@cse.unsw.edu.au References: <4009C0D5.2070209@cse.unsw.edu.au> In-Reply-To: <4009C0D5.2070209@cse.unsw.edu.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 X-Originating-IP: 127.0.0.1 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server34.totalchoicehosting.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [32001 32001] / [47 12] X-AntiAbuse: Sender Address Domain - monsoonrain.net cc: freebsd-net@freebsd.org Subject: Re: PPPoE problem: "Too many LQR packets lost" 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: Sun, 18 Jan 2004 18:52:35 -0000 Quoting nil000@cse.unsw.edu.au: > Since my ADSL connection was moved at my ISP's end from one set of > equipment (norte shasta?) to another (unisphere?), I've been having > problems with my PPPoE sessions. > > With "enable lqr" in my ppp.conf, the connection terminates after a few > mintues with "Too many LQR packets lost". I've included log output > below. According to these posts, > Yes, despite the original intent of the RFC, LQM is not commonly used for link state detection and most implementations rely on LCP echoes with knobs for setting the deadcount and loopcount parameters. (counters that dictate when the lcp echo fsm should declare link as dead or link as looped) > Short of actually fixing this LQR negotiation issue (?), might the > suggestion of a ppp.conf option to force LCP echo usage be good? > Yes. I am surprized it doesn't already have that option since thats a more common scenario. Alternately you could use another pppoe implementation, perhaps the one based on pppd/netgraph. BTW, the lcp.c patch suggested by someone else is not the correct approach. There also seems to be a problem with the way the FreeBSD kernel PPP implementation handles LQR and you can see it in the log below. (The unisphere at the other end isn't perfect either and has its own issues!) regards, niranjan [log start] > Jan 3 21:28:11 nn ppp[69401]: Phase: Using interface: tun0 > Jan 3 21:28:11 nn ppp[69401]: Phase: deflink: Created in closed state > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: default: set device > PPPoE:ed0:internode > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: default: set speed sync > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: default: set mru 1492 > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: default: set mtu 1492 > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: default: set ctsrts off > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: default: enable lqr (1) FreeBSD config enables LQR... > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: default: add default HISADDR > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: default: set timeout 0 > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: default: set redial 0 0 > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: internode: set authname > nil000@bogus.internode.on.net > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: internode: set authkey > ******** > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: internode: enable dns > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: internode: nat enable yes > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: internode: nat log yes > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: internode: nat same_ports yes > Jan 3 21:28:11 nn ppp[69401]: tun0: Command: internode: nat > unregistered_only yes > Jan 3 21:28:12 nn ppp[69402]: tun0: LCP: FSM: Using "deflink" as a > transport > Jan 3 21:28:12 nn ppp[69402]: tun0: LCP: deflink: State change Initial > --> Closed > Jan 3 21:28:12 nn ppp[69402]: tun0: LCP: deflink: State change Closed > --> Stopped > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: deflink: RecvConfigReq(137) > state = Stopped > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: MRU[4] 1492 > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: MAGICNUM[6] 0x3d9db2a2 > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: deflink: SendConfigReq(1) > state = Stopped > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: MRU[4] 1492 > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: MAGICNUM[6] 0xbdf7d851 > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: QUALPROTO[8] proto c025, > interval 30000ms (2) FreeBSD requests LQR in the config request > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: deflink: SendConfigAck(137) > state = Stopped > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: MRU[4] 1492 > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: MAGICNUM[6] 0x3d9db2a2 > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: deflink: LayerStart > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: deflink: State change Stopped > --> Ack-Sent > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: deflink: RecvConfigRej(1) > state = Ack-Sent > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: QUALPROTO[8] proto c025, > interval 30000ms (3) Other end did not like LQR and rejected it > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: deflink: SendConfigReq(2) > state = Ack-Sent > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: MRU[4] 1492 > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: MAGICNUM[6] 0xbdf7d851 > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: deflink: RecvConfigAck(2) > state = Ack-Sent > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: MRU[4] 1492 > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: MAGICNUM[6] 0xbdf7d851 > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: deflink: State change Ack-Sent > --> Opened (4) FreeBSD now sends a config without LQR > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: deflink: LayerUp > Jan 3 21:28:13 nn ppp[69402]: tun0: LQM: deflink: Will send ECHO LQR > every 30.00 secs (5) and then decides that it still wants to use LQR... > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: deflink: SendEchoRequest(0) > state = Opened > Jan 3 21:28:13 nn ppp[69402]: tun0: LCP: deflink: RecvEchoReply(0) > state = Opened > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: RecvConfigReq(2) > state = Opened > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: LayerDown > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: MAGICNUM[6] 0x82a38e1b > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: SendConfigReq(3) > state = Opened > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: MRU[4] 1492 > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: MAGICNUM[6] 0x2f84cfe2 > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: QUALPROTO[8] proto c025, > interval 30000ms (6) and tells the other end again that it wants to use LQR... > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: SendConfigNak(2) > state = Opened > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: MRU[4] 1492 > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: State change Opened > --> Req-Sent > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: RecvConfigAck(3) > state = Req-Sent > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: MRU[4] 1492 > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: MAGICNUM[6] 0x2f84cfe2 > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: QUALPROTO[8] proto c025, > interval 30000ms > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: State change Req-Sent > --> Ack-Rcvd (7) other end has no intention of supporting LQR but still acks it.. obviously, at a later time LQR is going to yell "Link Down".. > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: RecvConfigReq(3) > state = Ack-Rcvd > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: MRU[4] 1492 > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: MAGICNUM[6] 0x82a38e1b > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: SendConfigAck(3) > state = Ack-Rcvd > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: MRU[4] 1492 > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: MAGICNUM[6] 0x82a38e1b > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: State change Ack-Rcvd > --> Opened > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: LayerUp > Jan 3 21:28:15 nn ppp[69402]: tun0: LQM: deflink: Will send LQR every > 30.00 secs > Jan 3 21:28:15 nn ppp[69402]: tun0: LQM: deflink: Output: > Jan 3 21:28:15 nn ppp[69402]: tun0: LQM: Magic: 2f84cfe2 > LastOutLQRs: 00000000 > Jan 3 21:28:15 nn ppp[69402]: tun0: LQM: LastOutPackets: 00000000 > LastOutOctets: 00000000 > Jan 3 21:28:15 nn ppp[69402]: tun0: LQM: PeerInLQRs: 00000000 > PeerInPackets: 00000008 > Jan 3 21:28:15 nn ppp[69402]: tun0: LQM: PeerInDiscards: 00000000 > PeerInErrors: 00000000 > Jan 3 21:28:15 nn ppp[69402]: tun0: LQM: PeerInOctets: 000000b0 > PeerOutLQRs: 00000001 > Jan 3 21:28:15 nn ppp[69402]: tun0: LQM: PeerOutPackets: 00000009 > PeerOutOctets: 000000fe > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: FSM: Using "deflink" as a > transport > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: State change Initial > --> Closed > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: LayerStart. > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: SendConfigReq(1) > state = Closed > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: IPADDR[6] 192.168.234.239 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: COMPPROTO[6] 16 VJ slots > with slot compression > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: PRIDNS[6] 192.231.203.3 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: SECDNS[6] 255.255.255.255 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: State change Closed > --> Req-Sent > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: RecvConfigReq(1) > state = Req-Sent > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: IPADDR[6] 150.101.197.97 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: SendConfigAck(1) > state = Req-Sent > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: IPADDR[6] 150.101.197.97 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: State change > Req-Sent --> Ack-Sent > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: RecvProtocolRej(4) > state = Opened > Jan 3 21:28:15 nn ppp[69402]: tun0: LCP: deflink: -- Protocol 0x80fd > (Compression Control Protocol) was rejected! > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: RecvConfigRej(1) > state = Ack-Sent > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: COMPPROTO[6] 16 VJ slots > with slot compression > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: SendConfigReq(2) > state = Ack-Sent > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: IPADDR[6] 192.168.234.239 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: PRIDNS[6] 192.231.203.3 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: SECDNS[6] 255.255.255.255 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: RecvConfigNak(2) > state = Ack-Sent > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: IPADDR[6] 150.101.195.224 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: IPADDR[6] changing address: > 192.168.234.239 --> 150.101.195.224 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: PRIDNS[6] 192.231.203.132 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: SECDNS[6] 192.231.203.3 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: Primary nameserver set to > 192.231.203.132 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: Secondary nameserver set to > 192.231.203.3 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: SendConfigReq(3) > state = Ack-Sent > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: IPADDR[6] 150.101.195.224 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: PRIDNS[6] 192.231.203.132 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: SECDNS[6] 192.231.203.3 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: RecvConfigAck(3) > state = Ack-Sent > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: IPADDR[6] 150.101.195.224 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: PRIDNS[6] 192.231.203.132 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: SECDNS[6] 192.231.203.3 > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: State change > Ack-Sent --> Opened > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: deflink: LayerUp. > Jan 3 21:28:15 nn ppp[69402]: tun0: IPCP: myaddr 150.101.195.224 > hisaddr = 150.101.197.97 > Jan 3 21:28:16 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(1) > state = Opened > Jan 3 21:28:16 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(1) > state = Opened > Jan 3 21:28:26 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(2) > state = Opened > Jan 3 21:28:26 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(2) > state = Opened > Jan 3 21:28:37 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(3) > state = Opened > Jan 3 21:28:37 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(3) > state = Opened > Jan 3 21:28:46 nn ppp[69402]: tun0: LQM: deflink: Output (again): > Jan 3 21:28:46 nn ppp[69402]: tun0: LQM: Magic: 2f84cfe2 > LastOutLQRs: 00000000 > Jan 3 21:28:46 nn ppp[69402]: tun0: LQM: LastOutPackets: 00000000 > LastOutOctets: 00000000 > Jan 3 21:28:46 nn ppp[69402]: tun0: LQM: PeerInLQRs: 00000000 > PeerInPackets: 00000013 > Jan 3 21:28:46 nn ppp[69402]: tun0: LQM: PeerInDiscards: 00000000 > PeerInErrors: 00000000 > Jan 3 21:28:46 nn ppp[69402]: tun0: LQM: PeerInOctets: 000001b5 > PeerOutLQRs: 00000001 > Jan 3 21:28:46 nn ppp[69402]: tun0: LQM: PeerOutPackets: 00000013 > PeerOutOctets: 00000209 > Jan 3 21:28:47 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(4) > state = Opened > Jan 3 21:28:47 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(4) > state = Opened > Jan 3 21:28:57 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(5) > state = Opened > Jan 3 21:28:57 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(5) > state = Opened > Jan 3 21:29:07 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(6) > state = Opened > Jan 3 21:29:07 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(6) > state = Opened > Jan 3 21:29:16 nn ppp[69402]: tun0: LQM: deflink: Output (again): > Jan 3 21:29:16 nn ppp[69402]: tun0: LQM: Magic: 2f84cfe2 > LastOutLQRs: 00000000 > Jan 3 21:29:16 nn ppp[69402]: tun0: LQM: LastOutPackets: 00000000 > LastOutOctets: 00000000 > Jan 3 21:29:16 nn ppp[69402]: tun0: LQM: PeerInLQRs: 00000000 > PeerInPackets: 00000016 > Jan 3 21:29:16 nn ppp[69402]: tun0: LQM: PeerInDiscards: 00000000 > PeerInErrors: 00000000 > Jan 3 21:29:16 nn ppp[69402]: tun0: LQM: PeerInOctets: 000001e2 > PeerOutLQRs: 00000001 > Jan 3 21:29:16 nn ppp[69402]: tun0: LQM: PeerOutPackets: 00000017 > PeerOutOctets: 00000271 > Jan 3 21:29:18 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(7) > state = Opened > Jan 3 21:29:18 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(7) > state = Opened > Jan 3 21:29:28 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(8) > state = Opened > Jan 3 21:29:28 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(8) > state = Opened > Jan 3 21:29:38 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(9) > state = Opened > Jan 3 21:29:38 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(9) > state = Opened > Jan 3 21:29:47 nn ppp[69402]: tun0: LQM: deflink: Output (again): > Jan 3 21:29:47 nn ppp[69402]: tun0: LQM: Magic: 2f84cfe2 > LastOutLQRs: 00000000 > Jan 3 21:29:47 nn ppp[69402]: tun0: LQM: LastOutPackets: 00000000 > LastOutOctets: 00000000 > Jan 3 21:29:47 nn ppp[69402]: tun0: LQM: PeerInLQRs: 00000000 > PeerInPackets: 00000019 > Jan 3 21:29:47 nn ppp[69402]: tun0: LQM: PeerInDiscards: 00000000 > PeerInErrors: 00000000 > Jan 3 21:29:47 nn ppp[69402]: tun0: LQM: PeerInOctets: 0000020f > PeerOutLQRs: 00000001 > Jan 3 21:29:47 nn ppp[69402]: tun0: LQM: PeerOutPackets: 0000001b > PeerOutOctets: 000002d9 > Jan 3 21:29:48 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(10) > state = Opened > Jan 3 21:29:48 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(10) > state = Opened > Jan 3 21:29:59 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(11) > state = Opened > Jan 3 21:29:59 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(11) > state = Opened > Jan 3 21:30:09 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(12) > state = Opened > Jan 3 21:30:09 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(12) > state = Opened > Jan 3 21:30:17 nn ppp[69402]: tun0: LQM: deflink: Output (again): > Jan 3 21:30:17 nn ppp[69402]: tun0: LQM: Magic: 2f84cfe2 > LastOutLQRs: 00000000 > Jan 3 21:30:17 nn ppp[69402]: tun0: LQM: LastOutPackets: 00000000 > LastOutOctets: 00000000 > Jan 3 21:30:17 nn ppp[69402]: tun0: LQM: PeerInLQRs: 00000000 > PeerInPackets: 0000001c > Jan 3 21:30:17 nn ppp[69402]: tun0: LQM: PeerInDiscards: 00000000 > PeerInErrors: 00000000 > Jan 3 21:30:17 nn ppp[69402]: tun0: LQM: PeerInOctets: 0000023c > PeerOutLQRs: 00000001 > Jan 3 21:30:17 nn ppp[69402]: tun0: LQM: PeerOutPackets: 0000001f > PeerOutOctets: 00000341 > Jan 3 21:30:19 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(13) > state = Opened > Jan 3 21:30:19 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(13) > state = Opened > Jan 3 21:30:29 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(14) > state = Opened > Jan 3 21:30:29 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(14) > state = Opened > Jan 3 21:30:48 nn ppp[69402]: tun0: LQM: deflink: Output (again): > Jan 3 21:30:48 nn ppp[69402]: tun0: LQM: Magic: 2f84cfe2 > LastOutLQRs: 00000000 > Jan 3 21:30:48 nn ppp[69402]: tun0: LQM: LastOutPackets: 00000000 > LastOutOctets: 00000000 > Jan 3 21:30:48 nn ppp[69402]: tun0: LQM: PeerInLQRs: 00000000 > PeerInPackets: 00000022 > Jan 3 21:30:48 nn ppp[69402]: tun0: LQM: PeerInDiscards: 00000000 > PeerInErrors: 00000000 > Jan 3 21:30:48 nn ppp[69402]: tun0: LQM: PeerInOctets: 00000352 > PeerOutLQRs: 00000001 > Jan 3 21:30:48 nn ppp[69402]: tun0: LQM: PeerOutPackets: 00000023 > PeerOutOctets: 000003f9 > Jan 3 21:30:50 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(15) > state = Opened > Jan 3 21:30:50 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(15) > state = Opened > Jan 3 21:31:00 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(16) > state = Opened > Jan 3 21:31:00 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(16) > state = Opened > Jan 3 21:31:10 nn ppp[69402]: tun0: LCP: deflink: RecvEchoRequest(17) > state = Opened > Jan 3 21:31:10 nn ppp[69402]: tun0: LCP: deflink: SendEchoReply(17) > state = Opened > Jan 3 21:31:19 nn ppp[69402]: tun0: LQM: deflink: Too many LQR packets > lost > Jan 3 21:31:19 nn ppp[69402]: tun0: LCP: deflink: LayerDown > Jan 3 21:31:19 nn ppp[69402]: tun0: LCP: deflink: State change Opened > --> Starting (8) end of link.... > Jan 3 21:31:19 nn ppp[69402]: tun0: IPCP: deflink: LayerDown: > 150.101.195.224 > Jan 3 21:31:19 nn ppp[69402]: tun0: IPCP: deflink: State change Opened > --> Starting > Jan 3 21:31:19 nn ppp[69402]: tun0: IPCP: deflink: LayerFinish. > Jan 3 21:31:19 nn ppp[69402]: tun0: IPCP: Connect time: 184 secs: 334 > octets in, 92 octets out > Jan 3 21:31:19 nn ppp[69402]: tun0: IPCP: 5 packets in, 1 packets out > Jan 3 21:31:19 nn ppp[69402]: tun0: IPCP: total 2 bytes/sec, peak 58 > bytes/sec on Sat Jan 3 21:30:35 2004 > Jan 3 21:31:19 nn ppp[69402]: tun0: IPCP: deflink: State change > Starting --> Initial > Jan 3 21:31:19 nn ppp[69402]: tun0: LCP: deflink: LayerFinish > Jan 3 21:31:19 nn ppp[69402]: tun0: LCP: deflink: State change Starting > --> Initial > Jan 3 21:31:19 nn ppp[69402]: tun0: Chat: deflink: Reconnect try 1 of 0 > [end] From owner-freebsd-net@FreeBSD.ORG Sun Jan 18 13:23:29 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 B303316A4CE for ; Sun, 18 Jan 2004 13:23:29 -0800 (PST) Received: from smtp001.mail.ukl.yahoo.com (smtp001.mail.ukl.yahoo.com [217.12.11.32]) by mx1.FreeBSD.org (Postfix) with SMTP id 4AE2A43D1F for ; Sun, 18 Jan 2004 13:23:25 -0800 (PST) (envelope-from sylvain_lemasson@yahoo.fr) Received: from unknown (HELO TOMPOUCE) (sylvain?lemasson@80.9.3.177 with login) by smtp001.mail.ukl.yahoo.com with SMTP; 18 Jan 2004 21:23:23 -0000 Message-ID: <000a01c3de09$6468fd60$b1030950@TOMPOUCE> From: "Lemasson Sylvain" To: "freebsd net" , "freebsd config" Date: Sun, 18 Jan 2004 22:23:53 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: can not ping my freebsd from the network 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: Sun, 18 Jan 2004 21:23:29 -0000 I have configured freebsd to access internet by ppp . It works well. I = am able to ping other machine but the other machine can not ping me. I = have no firewall and the option kernel_secure is set to false. I do not = understand why I am not reachable on the network. Sylvain Lemasson From owner-freebsd-net@FreeBSD.ORG Sun Jan 18 16:26:18 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 1CA1316A4CE; Sun, 18 Jan 2004 16:26:18 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7207243D39; Sun, 18 Jan 2004 16:26:16 -0800 (PST) (envelope-from cristjc@comcast.net) Received: from blossom.cjclark.org (c-24-6-186-224.client.comcast.net[24.6.186.224]) by comcast.net (sccrmhc12) with ESMTP id <20040119002615012002kcb8e>; Mon, 19 Jan 2004 00:26:15 +0000 Received: from blossom.cjclark.org (localhost. [127.0.0.1]) by blossom.cjclark.org (8.12.9p2/8.12.8) with ESMTP id i0J0QD43048621; Sun, 18 Jan 2004 16:26:13 -0800 (PST) (envelope-from cristjc@comcast.net) Received: (from cjc@localhost) by blossom.cjclark.org (8.12.9p2/8.12.9/Submit) id i0J0QCgm048620; Sun, 18 Jan 2004 16:26:12 -0800 (PST) (envelope-from cristjc@comcast.net) X-Authentication-Warning: blossom.cjclark.org: cjc set sender to cristjc@comcast.net using -f Date: Sun, 18 Jan 2004 16:26:12 -0800 From: "Crist J. Clark" To: Sten Daniel S?rsdal Message-ID: <20040119002612.GA48581@blossom.cjclark.org> References: <0AF1BBDF1218F14E9B4CCE414744E70F5D97FF@exchange.wanglobal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0AF1BBDF1218F14E9B4CCE414744E70F5D97FF@exchange.wanglobal.net> User-Agent: Mutt/1.4.1i X-URL: http://people.freebsd.org/~cjc/ cc: freebsd-hackers@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: ip_input - chksum - why is it done so early in ip_input? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Crist J. Clark" List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2004 00:26:18 -0000 On Sat, Jan 17, 2004 at 12:50:04AM +0100, Sten Daniel S?rsdal wrote: > > Apologies for the cross-post, i wasnt sure if this was hackers or net material. > > I've often wondered why ip checksumming is done on every incoming > packet and not only on the packets that need to be delivered locally. > It looks like a very expensive way of doing it, especially on high > PPS. Basically all hosts do checksumming so why not just pass the bad > packet on, making the forward process alot cheaper (cpu wise)? It is done this way because the standards demand that it be done this way. RFC1812 says, 4.2.2.5 Header Checksum: RFC 791 Section 3.1 As stated in Section [5.2.2], a router MUST verify the IP checksum of any packet that is received, and MUST discard messages containing invalid checksums. The router MUST NOT provide a means to disable this checksum verification. Keeping a single host from polluting the whole network, and only its LAN, with bad packets is considered worth the cost of every router doing the check. FWIW, this is one of the few places a standard demands that you not even provide the option to disable a feature. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org From owner-freebsd-net@FreeBSD.ORG Sun Jan 18 20:12:38 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 AE41C16A4CE for ; Sun, 18 Jan 2004 20:12:38 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id CE94743D48 for ; Sun, 18 Jan 2004 20:12:36 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 26879 invoked from network); 19 Jan 2004 04:12:36 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 19 Jan 2004 04:12:36 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sun, 18 Jan 2004 22:12:34 -0600 (CST) From: Mike Silbersack To: CHOI Junho In-Reply-To: <20040115.224407.41715339.cjh@kr.FreeBSD.org> Message-ID: <20040118220617.P5672@odysseus.silby.com> References: <20040113.225411.74714267.cjh@kr.FreeBSD.org> <20040115.224407.41715339.cjh@kr.FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: FreeBSD -> Windows HTTP TCP performance 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: Mon, 19 Jan 2004 04:12:38 -0000 On Thu, 15 Jan 2004, CHOI Junho wrote: > For those who interested, I made packet dump file: > > http://www.kr.freebsd.org/~cjh/misc/freebsd-net/ > > Best thing is do tcpdump at client machine but I have no admin > permission, so failed. > > -- > CHOI Junho KFUG I can read these fine, Andre must be going through some web proxy that corrupts them. :) All of the computers in the dumps are on a LAN, right? There seems to be quite a bit of packet loss going on, from what I can see. This is most certainly the cause of low throughput; we'd need tcpdumps from both ends to really determine if there's some suboptimal tcp interaction between w2k and freebsd. (From a single side of the connection, we can't even be sure if retransmissions are getting through, etc.) Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Sun Jan 18 22:28:57 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 DE24D16A4CE for ; Sun, 18 Jan 2004 22:28:57 -0800 (PST) Received: from daemon.kr.FreeBSD.org (daemon.kr.freebsd.org [61.78.53.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4619743D31 for ; Sun, 18 Jan 2004 22:28:56 -0800 (PST) (envelope-from cjh@kr.FreeBSD.org) Received: from localhost (gradius [211.44.63.164]) by daemon.kr.FreeBSD.org (Postfix) with ESMTP id F3A0A1A6CE; Mon, 19 Jan 2004 15:27:30 +0900 (KST) Date: Mon, 19 Jan 2004 15:27:32 +0900 (KST) Message-Id: <20040119.152732.55788233.cjh@kr.FreeBSD.org> To: silby@silby.com From: CHOI Junho In-Reply-To: <20040118220617.P5672@odysseus.silby.com> References: <20040114.143113.74684785.cjh@kr.FreeBSD.org> <20040115.224407.41715339.cjh@kr.FreeBSD.org> <20040118220617.P5672@odysseus.silby.com> Organization: Korea FreeBSD Users Group X-URL: http://www.kr.FreeBSD.org/~cjh X-Mailer: Mew version 4.0.62 on Emacs 21.3.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: FreeBSD -> Windows HTTP TCP performance 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: Mon, 19 Jan 2004 06:28:58 -0000 After more investigation, I realized the problem is on the router side. I think the problem is solved... Thanks. From: Mike Silbersack Subject: Re: FreeBSD -> Windows HTTP TCP performance Date: Sun, 18 Jan 2004 22:12:34 -0600 (CST) > > On Thu, 15 Jan 2004, CHOI Junho wrote: > > > For those who interested, I made packet dump file: > > > > http://www.kr.freebsd.org/~cjh/misc/freebsd-net/ > > > > Best thing is do tcpdump at client machine but I have no admin > > permission, so failed. > > > > -- > > CHOI Junho KFUG > > I can read these fine, Andre must be going through some web proxy that > corrupts them. :) > > All of the computers in the dumps are on a LAN, right? There seems to be > quite a bit of packet loss going on, from what I can see. This is most > certainly the cause of low throughput; we'd need tcpdumps from both ends > to really determine if there's some suboptimal tcp interaction between w2k > and freebsd. (From a single side of the connection, we can't even be sure > if retransmissions are getting through, etc.) > > Mike "Silby" Silbersack -- CHOI Junho KFUG FreeBSD Project Web Data Bank Key fingerprint = 1369 7374 A45F F41A F3C0 07E3 4A01 C020 E602 60F5 From owner-freebsd-net@FreeBSD.ORG Sun Jan 18 22:36:17 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 7464A16A4CE; Sun, 18 Jan 2004 22:36:17 -0800 (PST) Received: from daemon.kr.FreeBSD.org (daemon.kr.freebsd.org [61.78.53.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BE5B43D2F; Sun, 18 Jan 2004 22:36:15 -0800 (PST) (envelope-from cjh@kr.FreeBSD.org) Received: from localhost (gradius [211.44.63.164]) by daemon.kr.FreeBSD.org (Postfix) with ESMTP id 4FD121A744; Mon, 19 Jan 2004 15:34:50 +0900 (KST) Date: Mon, 19 Jan 2004 15:34:52 +0900 (KST) Message-Id: <20040119.153452.10362034.cjh@kr.FreeBSD.org> To: freebsd-net@freebsd.org From: CHOI Junho Organization: Korea FreeBSD Users Group X-URL: http://www.kr.FreeBSD.org/~cjh X-Mailer: Mew version 4.0.62 on Emacs 21.3.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-performance@freebsd.org Subject: mbuf tuning 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: Mon, 19 Jan 2004 06:36:17 -0000 Hi, What is general guidelines of mbuf cluster tunables? I usually use kern.ipc.nmbclusters="65536" in /boot/loader.conf.local. But it has limits on concurrent TCP sessions, under my /etc/sysctl.conf configuration: net.inet.tcp.sendspace=65536 net.inet.tcp.recvspace=65536 With above parameters, about 1000 connection was the maximum. Of course if I set 1/2 value for tcp buffer(32768), maximum connection is doubled. But I want more. Increasing kern.ipc.nmbclusters caused frequent kernel panic under 4.7/4.8/4.9. How can I set more nmbclusters value with 64K tcp buffers? Or is any dependency for mbufclusters value? (e.g. RAM size, kern.maxusers value or etc) p.s. RAM is 2G, Xeon 2.0G x 1 or 2 machines. -- CHOI Junho KFUG FreeBSD Project Web Data Bank Key fingerprint = 1369 7374 A45F F41A F3C0 07E3 4A01 C020 E602 60F5 From owner-freebsd-net@FreeBSD.ORG Sun Jan 18 23:12:15 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 9769016A4CE for ; Sun, 18 Jan 2004 23:12:15 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id E439443D1F for ; Sun, 18 Jan 2004 23:12:10 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 59749 invoked from network); 19 Jan 2004 07:12:09 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 19 Jan 2004 07:12:09 -0000 X-pair-Authenticated: 209.68.2.70 Date: Mon, 19 Jan 2004 01:12:08 -0600 (CST) From: Mike Silbersack To: CHOI Junho In-Reply-To: <20040119.153452.10362034.cjh@kr.FreeBSD.org> Message-ID: <20040119010832.E85911@odysseus.silby.com> References: <20040119.153452.10362034.cjh@kr.FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org cc: freebsd-performance@freebsd.org Subject: Re: mbuf tuning 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: Mon, 19 Jan 2004 07:12:15 -0000 On Mon, 19 Jan 2004, CHOI Junho wrote: > Hi, > > What is general guidelines of mbuf cluster tunables? I usually use There are no good guidelines other than "don't set it too high." Andre and I have talked about some ideas on how to make mbuf usage more dynamic, I think that he has something in the works. But at present, once you hit the wall, that's it. One way to reduce mbuf cluster usage is to use sendfile where possible. Data sent via sendfile does not use mbuf clusters, and is more memory efficient. If you run 5.2 or above, it's *much* more memory efficient, due to change Alan Cox recently made. Apache 2 will use sendfile by default, so if you're running apache 1, that may be one reason for an upgrade. > Increasing kern.ipc.nmbclusters caused frequent kernel panic > under 4.7/4.8/4.9. How can I set more nmbclusters value with 64K tcp > buffers? Or is any dependency for mbufclusters value? (e.g. RAM size, > kern.maxusers value or etc) > > p.s. RAM is 2G, Xeon 2.0G x 1 or 2 machines. You probably need to bump up KVA_PAGES to fit in all the extra mbuf clusters you're allocating. Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Sun Jan 18 23:21:05 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 5370416A4CE for ; Sun, 18 Jan 2004 23:21:05 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 28A5143D45 for ; Sun, 18 Jan 2004 23:21:04 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 61005 invoked from network); 19 Jan 2004 07:21:03 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 19 Jan 2004 07:21:03 -0000 X-pair-Authenticated: 209.68.2.70 Date: Mon, 19 Jan 2004 01:21:01 -0600 (CST) From: Mike Silbersack To: rw@codeburst.co.uk In-Reply-To: <200401162336.XAA04091@starburst.demon.co.uk> Message-ID: <20040119011745.D85911@odysseus.silby.com> References: <200401162336.XAA04091@starburst.demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Ken Faiczak cc: freebsd-net@freebsd.org Subject: Re: forged tsecr giving -ve numbers in rtt calculation causing retran 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: Mon, 19 Jan 2004 07:21:05 -0000 On Fri, 16 Jan 2004, Richard Wendland wrote: > I'd hazard a guess that you are seeing zero, not forged, TSECRs. > Windows sets TSECR zero on SYN-ACK when it does a passive open. This is > established Windows behaviour for several years, and there is a reading > of RFC1323 that might justify this. Hm, wasn't this accounted for in rev 1.174 / 1.107.2.31? From Matt's commit log: --- ... FreeBSD sends a timestamp with the SYN, W2K returns a timestamp of 0 in the SYN+ACK causing FreeBSD to calculate an insane SRTT and RTT, resulting in a maximal retransmit timeout (60 seconds). ... This commit works around the W2K bug. --- Of course, that doesn't account for other non-zero strange values. I guess the timestamp code needs a lot of work. :( Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 01:07:56 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 222B916A4CE for ; Mon, 19 Jan 2004 01:07:56 -0800 (PST) Received: from einet.bg (sonata3.bginter.net [217.79.32.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E70343D2F for ; Mon, 19 Jan 2004 01:07:53 -0800 (PST) (envelope-from tie@einet.bg) Received: from root by einet.bg with scanned-ok (Exim 4.21) id 1AiVOI-0008WK-VS for freebsd-net@freebsd.org; Mon, 19 Jan 2004 11:08:14 +0200 Received: from [217.79.34.250] (helo=filipov) by einet.bg with smtp (Exim 4.21) id 1AiUOA-0007kI-Tj; Mon, 19 Jan 2004 10:04:02 +0200 Message-ID: <00af01c3de62$efaf4bf0$6e00a8c0@filipov> From: "Emil Filipov" To: "Gleb Smirnoff" References: <009401c3dc3c$1fa680e0$6e00a8c0@filipov> <20040116144135.GA92854@cell.sick.ru> <00aa01c3dc4b$1275e500$6e00a8c0@filipov> <20040117184423.GA99268@cell.sick.ru> Date: Mon, 19 Jan 2004 10:04:59 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-net@freebsd.org Subject: Re: PPPOE server with pppoed and mppe 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: Mon, 19 Jan 2004 09:07:56 -0000 Hi, G> How much Mbytes/sec have you got with MPPE? I get about 70-80 kbytes/s, while without encrytion the speed is 150-160 kbytes/s (and that's my hardware limit). A friend of mine tested my configuration in a LAN and got no decrease in the performance with encryption added. I am going to try to exclude the VLAN and VDSL parts (over which my connection goes) and see what happens. It seems that no one has seen this problem before, so it must be something specific for my configuration. I'll post a follow-up as soon as I discover the problem. Thanks for the cooperation though :) Regards, Emil Filipov From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 01:34:48 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 DDB0816A4CE for ; Mon, 19 Jan 2004 01:34:48 -0800 (PST) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id 1D57543D1D for ; Mon, 19 Jan 2004 01:34:45 -0800 (PST) (envelope-from dinesh@alphaque.com) Received: (qmail 78936 invoked by uid 0); 19 Jan 2004 09:34:40 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 19 Jan 2004 09:34:40 -0000 Received: from localhost (localhost.alphaque.com [127.0.0.1]) by prophet.alphaque.com (8.12.10/8.12.9) with ESMTP id i0J9YPx3001411 for ; Mon, 19 Jan 2004 17:34:25 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Mon, 19 Jan 2004 17:34:25 +0800 (MYT) From: Dinesh Nair To: freebsd-net@freebsd.org Message-ID: <20040119171546.T312-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: netgraph questions on ng_tee, ng_iface, ng_socket 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: Mon, 19 Jan 2004 09:34:49 -0000 hey all, am beginning to learn on how to manipulate netgraph nodes. i've read archie cobbs' paper at http://www.daemonnews.org/200003/netgraph.html and it provided a good backgrounder on using netgraph. i'm now playing around with ng_socket, ng_tee, ng_one2many and ng_iface to accomplish round robin routing for a freebsd box with two interfaces going to two ISPs. what i intent to achieve in principle is to have packets going out alternately over each of the two interfaces with source ip address set to the appropriate interface so the reply packets come back in properly. i looked at the examples which archie gave in the daemonnews paper, and am a little stumped at the behaviour of the whole thing. this could be due to my lack of understanding of the whole thing. what i want do is similar to this: i presently have two NICs on the box, fxp0 (192.168.0.5) and aue0 (10.1.1.25). both fxp0 and aue0 go out to different ISPs. currently, default route is thru ISP1 on fxp0, i.e. defroute to 192.168.0.1. what i want to do is to round robin outgoing packets across both ISP links, i.e. one packet out on fxp0 then the next out on aue0 and then the next out on fxp0 ad nauseaum. of course, packets going out on fxp0 will have a src address of 192.168.0.5 and packets going out on aue0 will have a src address of 10.1.1.25. create a new interface (presumably using ng_iface). give this iface an ip address, set the default route thru this iface (ng0). then, using ng_one2many, chain ng0 to both fxp0 and aue0. an example to do this for ethernet frames is given in the ng_one2many(4) man page, however i want to do it for IP packets with the underlying src address being changed where appropriate. i need some understanding on what exactly ng_iface achieves, as it makes a reference to the hook inet being connected to something. however, connecting the ng_iface hook inet to ng_ether's upper or lower doesnt make any sense because ng_ether itself does not do an encasulation of the IP packet into an ethernet frame. or am i wrong here, and just configuring it wrongly ? any pointers/explanations would sure help a lot. thanx in advance. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 02:24:21 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 E5B9816A4CE; Mon, 19 Jan 2004 02:24:21 -0800 (PST) Received: from daemon.kr.FreeBSD.org (daemon.kr.freebsd.org [61.78.53.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2910F43D49; Mon, 19 Jan 2004 02:24:20 -0800 (PST) (envelope-from cjh@kr.FreeBSD.org) Received: from localhost (gradius [211.44.63.164]) by daemon.kr.FreeBSD.org (Postfix) with ESMTP id 87F631A6EB; Mon, 19 Jan 2004 19:22:53 +0900 (KST) Date: Mon, 19 Jan 2004 19:22:57 +0900 (KST) Message-Id: <20040119.192257.34695172.cjh@kr.FreeBSD.org> To: silby@silby.com From: CHOI Junho In-Reply-To: <20040119010832.E85911@odysseus.silby.com> References: <20040119.153452.10362034.cjh@kr.FreeBSD.org> <20040119010832.E85911@odysseus.silby.com> Organization: Korea FreeBSD Users Group X-URL: http://www.kr.FreeBSD.org/~cjh X-Mailer: Mew version 4.0.62 on Emacs 21.3.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-performance@freebsd.org Subject: Re: mbuf tuning 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: Mon, 19 Jan 2004 10:24:22 -0000 From: Mike Silbersack Subject: Re: mbuf tuning Date: Mon, 19 Jan 2004 01:12:08 -0600 (CST) > There are no good guidelines other than "don't set it too high." Andre > and I have talked about some ideas on how to make mbuf usage more dynamic, > I think that he has something in the works. But at present, once you hit > the wall, that's it. > > One way to reduce mbuf cluster usage is to use sendfile where possible. > Data sent via sendfile does not use mbuf clusters, and is more memory > efficient. If you run 5.2 or above, it's *much* more memory efficient, > due to change Alan Cox recently made. Apache 2 will use sendfile by > default, so if you're running apache 1, that may be one reason for an > upgrade. I am using custom version of thttpd. It allocates mmap() first(builtin method of thttpd), and it try to use sendfile() if mmap() fails(out of mmap memory). It really works good in normal status but the problem is that sendfile buffer is also easy to flood. I need more sendfile buffers but I don't know how to increase sendfile buffers either(I think it's hidden sysctl but it was more difficult to tune than nmbclusters). With higher traffic, thttpd sometimes stuck at "sfbufa" status when I run top(I guess it's "sendfile buffer allocation" status). 5.2 is fair good quality in my desktop but I have no experience in production environment. I'll consider it once 5.x enters -STABLE tree, but not now. Apache2 is one of my targets. How much better than apache-1.3.x in static file service? > > Increasing kern.ipc.nmbclusters caused frequent kernel panic > > under 4.7/4.8/4.9. How can I set more nmbclusters value with 64K tcp > > buffers? Or is any dependency for mbufclusters value? (e.g. RAM size, > > kern.maxusers value or etc) > > > > p.s. RAM is 2G, Xeon 2.0G x 1 or 2 machines. > > You probably need to bump up KVA_PAGES to fit in all the extra mbuf > clusters you're allocating. Can you tell me in more detail? > Mike "Silby" Silbersack Thanks, -- CHOI Junho KFUG FreeBSD Project Web Data Bank Key fingerprint = 1369 7374 A45F F41A F3C0 07E3 4A01 C020 E602 60F5 From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 02:33:56 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 2156B16A4CE; Mon, 19 Jan 2004 02:33:56 -0800 (PST) Received: from relay.macomnet.ru (relay.macomnet.ru [195.128.64.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73A1E43D4C; Mon, 19 Jan 2004 02:33:53 -0800 (PST) (envelope-from maxim@macomnet.ru) Received: from news1.macomnet.ru (gog401zp@news1.macomnet.ru [195.128.64.14]) by relay.macomnet.ru (8.12.10/8.12.10) with ESMTP id i0JAWGhg3588493; Mon, 19 Jan 2004 13:32:16 +0300 (MSK) Date: Mon, 19 Jan 2004 13:32:16 +0300 (MSK) From: Maxim Konovalov To: CHOI Junho In-Reply-To: <20040119.192257.34695172.cjh@kr.FreeBSD.org> Message-ID: <20040119132741.O42397@news1.macomnet.ru> References: <20040119.153452.10362034.cjh@kr.FreeBSD.org> <20040119.192257.34695172.cjh@kr.FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org cc: freebsd-performance@freebsd.org Subject: Re: mbuf tuning 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: Mon, 19 Jan 2004 10:33:56 -0000 On Mon, 19 Jan 2004, 19:22+0900, CHOI Junho wrote: > From: Mike Silbersack > Subject: Re: mbuf tuning > Date: Mon, 19 Jan 2004 01:12:08 -0600 (CST) > > > There are no good guidelines other than "don't set it too high." Andre > > and I have talked about some ideas on how to make mbuf usage more dynamic, > > I think that he has something in the works. But at present, once you hit > > the wall, that's it. > > > > One way to reduce mbuf cluster usage is to use sendfile where possible. > > Data sent via sendfile does not use mbuf clusters, and is more memory > > efficient. If you run 5.2 or above, it's *much* more memory efficient, > > due to change Alan Cox recently made. Apache 2 will use sendfile by > > default, so if you're running apache 1, that may be one reason for an > > upgrade. > > I am using custom version of thttpd. It allocates mmap() first(builtin > method of thttpd), and it try to use sendfile() if mmap() fails(out of > mmap memory). It really works good in normal status but the problem is > that sendfile buffer is also easy to flood. I need more sendfile > buffers but I don't know how to increase sendfile buffers either(I > think it's hidden sysctl but it was more difficult to tune than > nmbclusters). With higher traffic, thttpd sometimes stuck at "sfbufa" > status when I run top(I guess it's "sendfile buffer allocation" > status). man 2 sendfile, man 7 tuning are a good start. In 5.2 you can monitor sendfile buffers usage via kern.ipc.nsfbufs* sysctls or netstat(1). [...] -- Maxim Konovalov, maxim@macomnet.ru, maxim@FreeBSD.org From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 03:07:31 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 814A816A4CE for ; Mon, 19 Jan 2004 03:07:31 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 172A443D3F for ; Mon, 19 Jan 2004 03:07:30 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i0JB7PCf091263 for ; Mon, 19 Jan 2004 12:07:26 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: net@freebsd.org From: Poul-Henning Kamp Date: Mon, 19 Jan 2004 12:07:25 +0100 Message-ID: <91262.1074510445@critter.freebsd.dk> Subject: Multihomed UDP server 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: Mon, 19 Jan 2004 11:07:31 -0000 Simple question: Very simple UDP server daemon. Many clients (connect(2)'ing a socket for each is not an option) Multihomed machine. What's the simple trick to replying with the same source-IP as the client used as destination-IP ? Notice I said "simple", monitoring the routetable or polling the interface configuration does not count as "simple". It seems to me that if there is no simple way to do this, it's about time we added it... As I see it, we need recvfromto() and sendtofrom(). Any takers ? Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 03:39:22 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 E09CD16A4CE for ; Mon, 19 Jan 2004 03:39:22 -0800 (PST) Received: from relay.macomnet.ru (relay.macomnet.ru [195.128.64.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A86843D1F for ; Mon, 19 Jan 2004 03:39:21 -0800 (PST) (envelope-from maxim@macomnet.ru) Received: from news1.macomnet.ru (jg998fn6@news1.macomnet.ru [195.128.64.14]) by relay.macomnet.ru (8.12.10/8.12.10) with ESMTP id i0JBdKhg3618490; Mon, 19 Jan 2004 14:39:20 +0300 (MSK) Date: Mon, 19 Jan 2004 14:39:20 +0300 (MSK) From: Maxim Konovalov To: Poul-Henning Kamp In-Reply-To: <91262.1074510445@critter.freebsd.dk> Message-ID: <20040119143315.N81347@news1.macomnet.ru> References: <91262.1074510445@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: net@freebsd.org Subject: Re: Multihomed UDP server 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: Mon, 19 Jan 2004 11:39:23 -0000 On Mon, 19 Jan 2004, 12:07+0100, Poul-Henning Kamp wrote: > Simple question: > > Very simple UDP server daemon. > > Many clients (connect(2)'ing a socket for each is not an option) > > Multihomed machine. > > What's the simple trick to replying with the same source-IP as the > client used as destination-IP ? Probably bin/58012 worth to look (Multihomed tftpd enhancement). Yes, it relies on protocol but still. [...] -- Maxim Konovalov, maxim@macomnet.ru, maxim@FreeBSD.org From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 03:58: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 F0EFC16A4CE for ; Mon, 19 Jan 2004 03:58:02 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A793D43D45 for ; Mon, 19 Jan 2004 03:58:01 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i0JBw0Cf092246; Mon, 19 Jan 2004 12:58:00 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: Maxim Konovalov From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 19 Jan 2004 14:39:20 +0300." <20040119143315.N81347@news1.macomnet.ru> Date: Mon, 19 Jan 2004 12:58:00 +0100 Message-ID: <92245.1074513480@critter.freebsd.dk> cc: net@freebsd.org Subject: Re: Multihomed UDP server 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: Mon, 19 Jan 2004 11:58:03 -0000 In message <20040119143315.N81347@news1.macomnet.ru>, Maxim Konovalov writes: >On Mon, 19 Jan 2004, 12:07+0100, Poul-Henning Kamp wrote: > >> Simple question: >> >> Very simple UDP server daemon. >> >> Many clients (connect(2)'ing a socket for each is not an option) >> >> Multihomed machine. >> >> What's the simple trick to replying with the same source-IP as the >> client used as destination-IP ? > >Probably bin/58012 worth to look (Multihomed tftpd enhancement). Yes, >it relies on protocol but still. But that's not a general solution, and it certainly doesn't solve the problem for my application. I'm considering ways to make sendmsg(2)/recvmsg(2) DTRT, and my current candidate is give them a flag bit which says "msg_name has both addresses". -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 04:27:09 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 BA47316A4CE for ; Mon, 19 Jan 2004 04:27:09 -0800 (PST) Received: from mail.butovo-online.ru (mail.b-o.ru [212.5.78.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13C0F43D1D for ; Mon, 19 Jan 2004 04:27:08 -0800 (PST) (envelope-from resident@b-o.ru) Received: from [192.168.92.185] (helo=192.168.92.185) by mail.butovo-online.ru with esmtp (Exim 4.24) id 1AiYbI-000CPZ-9m for freebsd-net@freebsd.org; Mon, 19 Jan 2004 15:33:52 +0300 Date: Mon, 19 Jan 2004 15:28:25 +0300 From: Andrew Riabtsev X-Mailer: The Bat! (v1.62i) Business X-Priority: 3 (Normal) Message-ID: <14414573064.20040119152825@b-o.ru> To: freebsd-net@freebsd.org In-Reply-To: <20040119171546.T312-100000@prophet.alphaque.com> References: <20040119171546.T312-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: netgraph questions on ng_tee, ng_iface, ng_socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Andrew Riabtsev List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2004 12:27:09 -0000 Hi all, Monday, January 19, 2004, 12:34:25 PM, you wrote: DN> hey all, skiped DN> i need some understanding on what exactly ng_iface achieves, as it makes a DN> reference to the hook inet being connected to something. however, DN> connecting the ng_iface hook inet to ng_ether's upper or lower doesnt make DN> any sense because ng_ether itself does not do an encasulation of the IP DN> packet into an ethernet frame. or am i wrong here, and just configuring it DN> wrongly ? DN> any pointers/explanations would sure help a lot. thanx in advance. Connecting ng_iface:inet and ng_ether:upper/lower do nothing, well, it do something but not what you are waiting for, i think. As wrotes in man ng_iface: This node type supports the following hooks: inet Transmission and reception of IP packets. ng_iface works with IP-packets, but ng_ether works with ethernet frames, so connecting it together require at least transformation module between IP-packets and ether-frames. -- Andrew mailto:resident@b-o.ru From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 04:30:26 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 369C016A4CE for ; Mon, 19 Jan 2004 04:30:26 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E48443D3F for ; Mon, 19 Jan 2004 04:30:21 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i0JCUICf092688; Mon, 19 Jan 2004 13:30:19 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: "Randall R. Stewart (home)" From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 19 Jan 2004 06:13:25 CST." <400BC9E5.8010609@stewart.chicago.il.us> Date: Mon, 19 Jan 2004 13:30:18 +0100 Message-ID: <92687.1074515418@critter.freebsd.dk> cc: net@freebsd.org Subject: Re: Multihomed UDP server 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: Mon, 19 Jan 2004 12:30:26 -0000 In message <400BC9E5.8010609@stewart.chicago.il.us>, "Randall R. Stewart (home) " writes: >>>On Mon, 19 Jan 2004, 12:07+0100, Poul-Henning Kamp wrote: >>>>Simple question: >>>> >>>>Very simple UDP server daemon. >>>> >>>>Many clients (connect(2)'ing a socket for each is not an option) >>>> >>>>Multihomed machine. >>>> >>>>What's the simple trick to replying with the same source-IP as the >>>>client used as destination-IP ? >> >>I'm considering ways to make sendmsg(2)/recvmsg(2) DTRT, and my >>current candidate is give them a flag bit which says "msg_name has >>both addresses". Following the code it seems that it is in fact possible to do with sendmsg(2)/recvmsg(2) already, and my test shows that at least the receive side works. I challenge anybody to point out where this is mentioned in the docs, and once people give up I'll tell how to do it :-) >Poul: > >One of the problems I think that is fundamental to BSD and >multi-homing is the lack of supports for multiple-default routes. I agree. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 04:30:26 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 CC38616A4CE for ; Mon, 19 Jan 2004 04:30:26 -0800 (PST) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBAC343D45 for ; Mon, 19 Jan 2004 04:30:22 -0800 (PST) (envelope-from mike@sentex.net) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smtp3.sentex.ca (8.12.10/8.12.10) with ESMTP id i0JCUKU7067409; Mon, 19 Jan 2004 07:30:20 -0500 (EST) (envelope-from mike@sentex.net) Received: from BLUELAPIS.sentex.ca (cage.simianscience.com [64.7.134.1]) by smtp2.sentex.ca (8.12.10/8.12.10) with SMTP id i0JCUKld029689; Mon, 19 Jan 2004 07:30:21 -0500 (EST) (envelope-from mike@sentex.net) From: Mike Tancsa To: niranjan@monsoonrain.net Date: Mon, 19 Jan 2004 07:30:22 -0500 Message-ID: <99jn005llhvp8bpnaabpqq02kht74lcnth@4ax.com> References: <4009C0D5.2070209@cse.unsw.edu.au> <1074451944.400ad5e888ba4@www.monsoonrain.net> In-Reply-To: <1074451944.400ad5e888ba4@www.monsoonrain.net> X-Mailer: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable cc: freebsd-net@freebsd.org Subject: Re: PPPoE problem: "Too many LQR packets lost" 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: Mon, 19 Jan 2004 12:30:26 -0000 On Sun, 18 Jan 2004 13:52:24 -0500, in sentex.lists.freebsd.net you wrote: > >BTW, the lcp.c patch suggested by someone else is not the correct=20 >approach. It would be great to see a proper config option disable it. However, I dont see any such patches. In the mean time, it works for me. Otherwise pppoe is pretty broken in that there is no link state detection. ---Mike From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 05:29:07 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 151E116A4CE for ; Mon, 19 Jan 2004 05:29:07 -0800 (PST) Received: from smtp3.adl2.internode.on.net (smtp3.adl2.internode.on.net [203.16.214.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id E60F843D39 for ; Mon, 19 Jan 2004 05:29:03 -0800 (PST) (envelope-from nil000@cse.unsw.edu.au) Received: from nn.lam.net.au (ppp193-121.lns1.syd3.internode.on.net [150.101.193.121])i0JDT0qR069877; Mon, 19 Jan 2004 23:59:01 +1030 (CST) Received: from cse.unsw.edu.au (localhost [127.0.0.1]) by nn.lam.net.au (Postfix) with ESMTP id C163A15FFF8; Tue, 20 Jan 2004 00:28:46 +1100 (EST) Message-ID: <400BDB8D.4070807@cse.unsw.edu.au> Date: Tue, 20 Jan 2004 00:28:45 +1100 From: nil000@cse.unsw.edu.au User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031020 X-Accept-Language: en-us, en MIME-Version: 1.0 To: niranjan@monsoonrain.net References: <4009C0D5.2070209@cse.unsw.edu.au> <1074451944.400ad5e888ba4@www.monsoonrain.net> In-Reply-To: <1074451944.400ad5e888ba4@www.monsoonrain.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: PPPoE problem: "Too many LQR packets lost" 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: Mon, 19 Jan 2004 13:29:07 -0000 niranjan@monsoonrain.net wrote: [ ... ] > >>Short of actually fixing this LQR negotiation issue (?), might the >>suggestion of a ppp.conf option to force LCP echo usage be good? >> > > > Yes. I am surprized it doesn't already have that option since thats > a more common scenario. Alternately you could use another pppoe > implementation, perhaps the one based on pppd/netgraph. > > BTW, the lcp.c patch suggested by someone else is not the correct > approach. > > There also seems to be a problem with the way the FreeBSD kernel PPP > implementation handles LQR and you can see it in the log below. (The > unisphere at the other end isn't perfect either and has its own > issues!) > > regards, > niranjan > Thanks for your analysis Niranjan. Could you please elaborate on what you meant about the lcp.c patch not being the correct approach? I think Mike has tested it in multiple situations, and it has worked well for a guy in the same situation down here too. cheers, nik From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 07:33:36 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 725F816A4CE for ; Mon, 19 Jan 2004 07:33:36 -0800 (PST) Received: from smtp0.libero.it (smtp0.libero.it [193.70.192.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B68C43D1F for ; Mon, 19 Jan 2004 07:33:33 -0800 (PST) (envelope-from ml.ventu@flashnet.it) Received: from soth.ventu (151.38.126.218) by smtp0.libero.it (7.0.020-DD01) id 3F6F1CE7021D8ED1 for freebsd-net@freebsd.org; Mon, 19 Jan 2004 16:33:32 +0100 Received: from mailer (xanatar.ventu [10.1.2.6]) by soth.ventu (8.12.6p3/8.12.6) with SMTP id i0JFXUDE050449 for ; Mon, 19 Jan 2004 16:33:31 +0100 (CET) (envelope-from ml.ventu@flashnet.it) Message-Id: <200401191533.i0JFXUDE050449@soth.ventu> To: freebsd-net@freebsd.org Priority: Normal X-Mailer: Post Road Mailer for OS/2 (Green Edition Ver 3.0) Date: Mon, 19 Jan 2004 16:33:31 EST From: Andrea Venturoli X-Spam-Score: 5.274 (*****) DATE_IN_FUTURE_06_12,MSGID_FROM_MTA_SHORT X-Scanned-By: MIMEDefang 2.39 Subject: Two ISP lines X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Andrea Venturoli List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2004 15:33:36 -0000 Ok, I asked already asked something similar to this in the past, but it's not the same thing... maybe it's a trivial question... If I had two lines to the Internet: how would I use both? Could I just provide two default routes? How? What algorithm would be used to choose among the two? What if one failed? bye & Thanks av. From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 09:59:22 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 CB4B216A4CE for ; Mon, 19 Jan 2004 09:59:22 -0800 (PST) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id 6DDDE43D31 for ; Mon, 19 Jan 2004 09:59:16 -0800 (PST) (envelope-from dinesh@alphaque.com) Received: (qmail 90140 invoked by uid 0); 19 Jan 2004 17:59:12 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 19 Jan 2004 17:59:12 -0000 Received: from localhost (localhost.alphaque.com [127.0.0.1]) by prophet.alphaque.com (8.12.10/8.12.9) with ESMTP id i0JHovx3002290; Tue, 20 Jan 2004 01:50:57 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Tue, 20 Jan 2004 01:50:57 +0800 (MYT) From: Dinesh Nair To: Andrea Venturoli In-Reply-To: <200401191533.i0JFXUDE050449@soth.ventu> Message-ID: <20040120014934.Q312-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: Two ISP lines 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: Mon, 19 Jan 2004 17:59:22 -0000 On Mon, 19 Jan 2004, Andrea Venturoli wrote: > lines to the Internet: how would I use both? Could I just provide two > default routes? How? What algorithm would be used to choose among the > two? What if one failed? seems to be the topic of the week over at freebsd-questions. short end of the stick is, freebsd as it is today does not do multipath routing, so you cant add a default route to two gateways for round robin usage. however, there was a multipath patch for 4-STABLE some months back, though for the life of me, i don't know where it's archived anymore. check -questions archives for this thread. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 09:59:23 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 2B87216A4CF for ; Mon, 19 Jan 2004 09:59:23 -0800 (PST) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id C05A343D41 for ; Mon, 19 Jan 2004 09:59:16 -0800 (PST) (envelope-from dinesh@alphaque.com) Received: (qmail 90146 invoked by uid 0); 19 Jan 2004 17:59:14 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 19 Jan 2004 17:59:14 -0000 Received: from localhost (localhost.alphaque.com [127.0.0.1]) by prophet.alphaque.com (8.12.10/8.12.9) with ESMTP id i0JHTNx3002208; Tue, 20 Jan 2004 01:29:23 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Tue, 20 Jan 2004 01:29:23 +0800 (MYT) From: Dinesh Nair To: Andrew Riabtsev In-Reply-To: <14414573064.20040119152825@b-o.ru> Message-ID: <20040120012819.I312-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: netgraph questions on ng_tee, ng_iface, ng_socket 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: Mon, 19 Jan 2004 17:59:23 -0000 On Mon, 19 Jan 2004, Andrew Riabtsev wrote: > DN> connecting the ng_iface hook inet to ng_ether's upper or lower doesnt make > DN> any sense because ng_ether itself does not do an encasulation of the IP > DN> packet into an ethernet frame. or am i wrong here, and just configuring it > DN> wrongly ? > > Connecting ng_iface:inet and ng_ether:upper/lower do nothing, well, it > do something but not what you are waiting for, i think. i know, hence was asking if there was something i could do, even if it meant writing an extension to ng_ether to create a new netgraph type. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 11:02:35 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 59F8416A4CE for ; Mon, 19 Jan 2004 11:02:35 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 011A043D8E for ; Mon, 19 Jan 2004 11:01:31 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.10/8.12.10) with ESMTP id i0JJ1VFR061883 for ; Mon, 19 Jan 2004 11:01:31 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i0JJ1UvJ061877 for freebsd-net@freebsd.org; Mon, 19 Jan 2004 11:01:30 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 19 Jan 2004 11:01:30 -0800 (PST) Message-Id: <200401191901.i0JJ1UvJ061877@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Subject: Current problem reports assigned to you 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: Mon, 19 Jan 2004 19:02:35 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/07/11] kern/54383 net NFS root configurations without dynamic p 1 problem total. From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 11:13:59 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 BE5EB16A4CE for ; Mon, 19 Jan 2004 11:13:59 -0800 (PST) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FD4943D60 for ; Mon, 19 Jan 2004 11:13:53 -0800 (PST) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.31.45.197]) by comcast.net (rwcrmhc11) with ESMTP id <2004011919135201300b4mh2e>; Mon, 19 Jan 2004 19:13:52 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost.crodrigues.org [127.0.0.1])i0JJDrZX057688; Mon, 19 Jan 2004 14:13:53 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)i0JJDqoH057674; Mon, 19 Jan 2004 14:13:52 -0500 (EST) (envelope-from rodrigc) Date: Mon, 19 Jan 2004 14:13:52 -0500 From: Craig Rodrigues To: Dinesh Nair Message-ID: <20040119191352.GA52975@crodrigues.org> References: <200401191533.i0JFXUDE050449@soth.ventu> <20040120014934.Q312-100000@prophet.alphaque.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040120014934.Q312-100000@prophet.alphaque.com> User-Agent: Mutt/1.4.1i cc: freebsd-net@freebsd.org Subject: Re: Two ISP lines 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: Mon, 19 Jan 2004 19:13:59 -0000 On Tue, Jan 20, 2004 at 01:50:57AM +0800, Dinesh Nair wrote: > there was a multipath patch for 4-STABLE some months back, though for the > life of me, i don't know where it's archived anymore. Are you referring to these patches? http://lists.freebsd.org/pipermail/freebsd-hackers/2003-July/001843.html -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 11:34:40 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 022F716A4CE for ; Mon, 19 Jan 2004 11:34:40 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88D2D43D53 for ; Mon, 19 Jan 2004 11:34:27 -0800 (PST) (envelope-from max@love2party.net) Received: from [212.227.126.205] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AifAI-00018y-00 for freebsd-net@freebsd.org; Mon, 19 Jan 2004 20:34:26 +0100 Received: from [217.227.150.10] (helo=vampire.homelinux.org) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1AifAI-0001CZ-00 for freebsd-net@freebsd.org; Mon, 19 Jan 2004 20:34:26 +0100 Received: (qmail 28694 invoked from network); 19 Jan 2004 19:38:45 -0000 Received: from unknown (HELO fbsd52.laiers.local) (192.168.4.88) by 192.168.4.1 with SMTP; 19 Jan 2004 19:38:45 -0000 From: Max Laier To: Dinesh Nair , Andrea Venturoli Date: Mon, 19 Jan 2004 20:34:22 +0100 User-Agent: KMail/1.5.4 References: <20040120014934.Q312-100000@prophet.alphaque.com> In-Reply-To: <20040120014934.Q312-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401192034.22796.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:e28873fbe4dbe612ce62ab869898ff08 cc: freebsd-net@freebsd.org Subject: Re: Two ISP lines 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: Mon, 19 Jan 2004 19:34:40 -0000 On Monday 19 January 2004 18:50, Dinesh Nair wrote: > On Mon, 19 Jan 2004, Andrea Venturoli wrote: > > lines to the Internet: how would I use both? Could I just provide two > > default routes? How? What algorithm would be used to choose among the > > two? What if one failed? > > seems to be the topic of the week over at freebsd-questions. short end > of the stick is, freebsd as it is today does not do multipath routing, > so you cant add a default route to two gateways for round robin usage. > however, there was a multipath patch for 4-STABLE some months back, > though for the life of me, i don't know where it's archived anymore. > > check -questions archives for this thread. take a look at secuirty/pf (from ports) it can make use of more than one uplink. It provides round-robin and source-hash load balancing and you can define even finer policy routing with it. It works currently for 5.x only, for a 4.x version check KAME. -- Best regards, | max@love2party.net Max Laier | ICQ #67774661 http://pf4freebsd.love2party.net/ | mlaier@EFnet From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 12:03:11 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 F1D8F16A4CE for ; Mon, 19 Jan 2004 12:03:11 -0800 (PST) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D43B43D92 for ; Mon, 19 Jan 2004 12:02:44 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost.nic.fr [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id i0JK2TDa058755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Mon, 19 Jan 2004 15:02:39 -0500 (EST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id i0JK2SJZ058752; Mon, 19 Jan 2004 15:02:28 -0500 (EST) (envelope-from wollman) Date: Mon, 19 Jan 2004 15:02:28 -0500 (EST) From: Garrett Wollman Message-Id: <200401192002.i0JK2SJZ058752@khavrinen.lcs.mit.edu> To: "Poul-Henning Kamp" In-Reply-To: <92245.1074513480@critter.freebsd.dk> References: <20040119143315.N81347@news1.macomnet.ru> <92245.1074513480@critter.freebsd.dk> X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.37 cc: net@FreeBSD.ORG Subject: Re: Multihomed UDP server 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: Mon, 19 Jan 2004 20:03:12 -0000 < said: > I'm considering ways to make sendmsg(2)/recvmsg(2) DTRT, and my > current candidate is give them a flag bit which says "msg_name has > both addresses". Um, they already do the right thing. That's what the IP_RECVDESTADDR option (and its dual whose name I forget right now) is all about. -GAWollman From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 12:06:44 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 48EE216A4CE for ; Mon, 19 Jan 2004 12:06:44 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A798143DA0 for ; Mon, 19 Jan 2004 12:05:55 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i0JK5kCf098297; Mon, 19 Jan 2004 21:05:47 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: Garrett Wollman From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 19 Jan 2004 15:02:28 EST." <200401192002.i0JK2SJZ058752@khavrinen.lcs.mit.edu> Date: Mon, 19 Jan 2004 21:05:46 +0100 Message-ID: <98296.1074542746@critter.freebsd.dk> cc: net@FreeBSD.ORG Subject: Re: Multihomed UDP server 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: Mon, 19 Jan 2004 20:06:44 -0000 In message <200401192002.i0JK2SJZ058752@khavrinen.lcs.mit.edu>, Garrett Wollman writes: >< said: > >> I'm considering ways to make sendmsg(2)/recvmsg(2) DTRT, and my >> current candidate is give them a flag bit which says "msg_name has >> both addresses". > >Um, they already do the right thing. That's what the IP_RECVDESTADDR >option (and its dual whose name I forget right now) is all about. Yeah, I found that out. Now, where on the earth is that documented ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 12:44:47 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 6682916A4CE for ; Mon, 19 Jan 2004 12:44:47 -0800 (PST) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9F2243D1D for ; Mon, 19 Jan 2004 12:44:45 -0800 (PST) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 2CD251FF91D; Mon, 19 Jan 2004 21:44:44 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 740661FF90C; Mon, 19 Jan 2004 21:44:42 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 246FE153CA; Mon, 19 Jan 2004 20:44:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 19D4815380; Mon, 19 Jan 2004 20:44:34 +0000 (UTC) Date: Mon, 19 Jan 2004 20:44:34 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Poul-Henning Kamp In-Reply-To: <98296.1074542746@critter.freebsd.dk> Message-ID: References: <98296.1074542746@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: net@FreeBSD.ORG cc: Garrett Wollman Subject: Re: Multihomed UDP server 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: Mon, 19 Jan 2004 20:44:47 -0000 On Mon, 19 Jan 2004, Poul-Henning Kamp wrote: > In message <200401192002.i0JK2SJZ058752@khavrinen.lcs.mit.edu>, Garrett Wollman > writes: > >< said: > > > >> I'm considering ways to make sendmsg(2)/recvmsg(2) DTRT, and my > >> current candidate is give them a flag bit which says "msg_name has > >> both addresses". > > > >Um, they already do the right thing. That's what the IP_RECVDESTADDR actually it is IP_RECVDSTADDR (no E). > >option (and its dual whose name I forget right now) is all about. > > Yeah, I found that out. Now, where on the earth is that documented ? You mean for FreeBSD or in ISBN 0-13-490012-X ? For FreeBSD it is man 4 ip: --- cite --- If the IP_RECVDSTADDR option is enabled on a SOCK_DGRAM socket, the recvmsg(2) call will return the destination IP address for a UDP data- gram. The msg_control field in the msghdr structure points to a buffer that contains a cmsghdr structure followed by the IP address. The cmsghdr fields have the following values: --- cite --- -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/ From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 12:45:58 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 5A02F16A4CE for ; Mon, 19 Jan 2004 12:45:58 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id D20A743D53 for ; Mon, 19 Jan 2004 12:45:56 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i0JKjnCf098635; Mon, 19 Jan 2004 21:45:54 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: "Bjoern A. Zeeb" From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 19 Jan 2004 20:44:34 GMT." Date: Mon, 19 Jan 2004 21:45:49 +0100 Message-ID: <98634.1074545149@critter.freebsd.dk> cc: net@FreeBSD.ORG cc: Garrett Wollman Subject: Re: Multihomed UDP server 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: Mon, 19 Jan 2004 20:45:58 -0000 In message , "Bjo ern A. Zeeb" writes: >You mean for FreeBSD or in ISBN 0-13-490012-X ? > >For FreeBSD it is man 4 ip: > >--- cite --- > If the IP_RECVDSTADDR option is enabled on a SOCK_DGRAM socket, the > recvmsg(2) call will return the destination IP address for a UDP data- > gram. The msg_control field in the msghdr structure points to a buffer > that contains a cmsghdr structure followed by the IP address. The > cmsghdr fields have the following values: >--- cite --- That really belongs on udp(4) more than ip(4)... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 13:20:08 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 9358E16A4CE; Mon, 19 Jan 2004 13:20:08 -0800 (PST) Received: from park.rambler.ru (park.rambler.ru [81.19.64.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BB0443D54; Mon, 19 Jan 2004 13:20:01 -0800 (PST) (envelope-from is@rambler-co.ru) Received: from is (is.park.rambler.ru [81.19.64.102]) by park.rambler.ru (8.12.6/8.12.6) with ESMTP id i0JLJsAY009298; Tue, 20 Jan 2004 00:19:54 +0300 (MSK) (envelope-from is@rambler-co.ru) Date: Tue, 20 Jan 2004 00:19:54 +0300 (MSK) From: Igor Sysoev X-Sender: is@is To: CHOI Junho In-Reply-To: <20040119.192257.34695172.cjh@kr.FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org cc: freebsd-performance@freebsd.org Subject: Re: mbuf tuning 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: Mon, 19 Jan 2004 21:20:08 -0000 On Mon, 19 Jan 2004, CHOI Junho wrote: > From: Mike Silbersack > Subject: Re: mbuf tuning > Date: Mon, 19 Jan 2004 01:12:08 -0600 (CST) > > > There are no good guidelines other than "don't set it too high." Andre > > and I have talked about some ideas on how to make mbuf usage more dynamic, > > I think that he has something in the works. But at present, once you hit > > the wall, that's it. > > > > One way to reduce mbuf cluster usage is to use sendfile where possible. > > Data sent via sendfile does not use mbuf clusters, and is more memory > > efficient. If you run 5.2 or above, it's *much* more memory efficient, > > due to change Alan Cox recently made. Apache 2 will use sendfile by > > default, so if you're running apache 1, that may be one reason for an > > upgrade. > > I am using custom version of thttpd. It allocates mmap() first(builtin > method of thttpd), and it try to use sendfile() if mmap() fails(out of > mmap memory). It really works good in normal status but the problem is > that sendfile buffer is also easy to flood. I need more sendfile > buffers but I don't know how to increase sendfile buffers either(I > think it's hidden sysctl but it was more difficult to tune than > nmbclusters). With higher traffic, thttpd sometimes stuck at "sfbufa" > status when I run top(I guess it's "sendfile buffer allocation" > status). In 4.x you have to rebuild the kernel with options NSFBUFS=16384 It equals to (512 + maxusers * 16) by default. By the way, why do you want to use the big net.inet.tcp.sendspace and net.inet.tcp.recvspace ? It makes a sense for Apache but thttpd can easy work with the small buffers, say, 16K or even 8K. > > > Increasing kern.ipc.nmbclusters caused frequent kernel panic > > > under 4.7/4.8/4.9. How can I set more nmbclusters value with 64K tcp > > > buffers? Or is any dependency for mbufclusters value? (e.g. RAM size, > > > kern.maxusers value or etc) > > > > > > p.s. RAM is 2G, Xeon 2.0G x 1 or 2 machines. > > > > You probably need to bump up KVA_PAGES to fit in all the extra mbuf > > clusters you're allocating. > > Can you tell me in more detail? >From LINT: --- # # Change the size of the kernel virtual address space. Due to # constraints in loader(8) on i386, this must be a multiple of 4. # 256 = 1 GB of kernel address space. Increasing this also causes # a reduction of the address space in user processes. 512 splits # the 4GB cpu address space in half (2GB user, 2GB kernel). # options KVA_PAGES=260 --- Default KVA_PAGES are 256. Igor Sysoev http://sysoev.ru/en/ From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 16:26:13 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 2B15816A4CE for ; Mon, 19 Jan 2004 16:26:13 -0800 (PST) Received: from starburst.demon.co.uk (adsl-02-240.abel.net.uk [193.109.51.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78DE143D1D for ; Mon, 19 Jan 2004 16:26:10 -0800 (PST) (envelope-from richard@starburst.demon.co.uk) Received: (from richard@localhost) by starburst.demon.co.uk (8.8.7/8.8.7) id AAA09260; Tue, 20 Jan 2004 00:27:49 GMT From: Richard Wendland Message-Id: <200401200027.AAA09260@starburst.demon.co.uk> To: silby@silby.com (Mike Silbersack) Date: Tue, 20 Jan 2004 00:27:48 +0000 (GMT) In-Reply-To: <20040119011745.D85911@odysseus.silby.com> from "Mike Silbersack" at Jan 19, 2004 01:21:01 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: Ken Faiczak cc: freebsd-net@freebsd.org Subject: Re: forged tsecr giving -ve numbers in rtt calculation causing retran X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: richard@wendland.org.uk List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 00:26:13 -0000 > Hm, wasn't this accounted for in rev 1.174 / 1.107.2.31? From Matt's > commit log: True. My notes must have been from an older version. Sorry. > Of course, that doesn't account for other non-zero strange values. I > guess the timestamp code needs a lot of work. :( This does suggest Ken is seeing TSecr messed up in some other way than simple zeroing. I'd expect this to be a pretty rare event, and perhaps my suggestion that the 64 sec TCPTV_REXMTMAX limit be implemented correctly is a good enough solution on its own for a rare event. It should certainly avoid the insane -450000000 tp->t_rxtcur Ken has seen. It's simple to implement, does what was probably originally intended, and also protects from bizarre problems with non-timestamp option SRTT calculation. Full validation of TSecr would be nice, but perhaps excessive for something that should not happen. A 64 second RTO may discourage such strangeness :) Richard -- Richard Wendland richard@wendland.org.uk From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 18:38:17 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 0C46A16A4CE for ; Mon, 19 Jan 2004 18:38:17 -0800 (PST) Received: from server34.totalchoicehosting.com (server34.totalchoicehosting.com [69.50.194.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id C29FB43D5E for ; Mon, 19 Jan 2004 18:38:15 -0800 (PST) (envelope-from niranjan@monsoonrain.net) Received: from cpanel by server34.totalchoicehosting.com with local (Exim 4.24) id 1AilmL-0004Tn-3J; Mon, 19 Jan 2004 19:38:09 -0700 Received: from localhost (localhost [127.0.0.1]) by www.monsoonrain.net (IMP) with HTTP for ; Mon, 19 Jan 2004 21:38:08 -0500 Message-ID: <1074566288.400c9490e7f04@www.monsoonrain.net> Date: Mon, 19 Jan 2004 21:38:08 -0500 From: niranjan@monsoonrain.net To: nil000@cse.unsw.edu.au MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 X-Originating-IP: 127.0.0.1 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server34.totalchoicehosting.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [32001 32001] / [47 12] X-AntiAbuse: Sender Address Domain - monsoonrain.net cc: freebsd-net@freebsd.org Subject: Re: PPPoE problem: "Too many LQR packets lost" 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: Tue, 20 Jan 2004 02:38:17 -0000 nil000@cse.unsw.edu.au wrote: > > Thanks for your analysis Niranjan. Could you please elaborate on what > you meant about the lcp.c patch not being the correct approach? I think > Mike has tested it in multiple situations, and it has worked well for a > guy in the same situation down here too. > > cheers, > > nik > Hi Nik, The comment was from the perspective of a long term cleanup of the LQM code. For instance, lqr.c currently assumes that you can either enable LQR or LCP echoes, but not both at the same time. The RFCs, however, do not disallow this scenario and LCP echoes have other uses beyond link quality monitoring. If Mike's patch offers a short term solution for your needs, go for it! (Although, I am wondering, how it would be different, if you simply did not enable LQR in ppp.conf. lqr_Setup() in lqr.c sets LQM_ECHO by default. If LQM_LQR is not set, the code will fall back to sending LCP echoes.. see SendLqrReport()...I haven't looked at this version of PPP in the greatest detail, so its possible there is a clause somewhere preventing this...) Regards, Niranjan From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 22:31:38 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 C0AF016A4CE for ; Mon, 19 Jan 2004 22:31:38 -0800 (PST) Received: from coconut.itojun.org (coconut.itojun.org [219.101.47.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB95C43D1D for ; Mon, 19 Jan 2004 22:31:37 -0800 (PST) (envelope-from itojun@itojun.org) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id EC399B2; Tue, 20 Jan 2004 15:31:33 +0900 (JST) To: freebsd-net@freebsd.org X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 From: itojun@iijlab.net Date: Tue, 20 Jan 2004 15:31:33 +0900 Sender: itojun@itojun.org Message-Id: <20040120063133.EC399B2@coconut.itojun.org> cc: rrs@cisco.com Subject: timersub/timeradd/timercmp 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: Tue, 20 Jan 2004 06:31:38 -0000 could anyone let me know why timersub/add/cmp are disabled in the kernel? they were introduced in 4.4BSD, and (non-)availability of these macro makes it difficult for kame/rrs to deal with multiple *BSDs. (guessing: are you trying to enforce the use of timespec in the kernel?) itojun From owner-freebsd-net@FreeBSD.ORG Mon Jan 19 23:56:14 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 7898716A4CE for ; Mon, 19 Jan 2004 23:56:14 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 44DE743D54 for ; Mon, 19 Jan 2004 23:56:12 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 87331 invoked from network); 20 Jan 2004 07:56:10 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 20 Jan 2004 07:56:10 -0000 X-pair-Authenticated: 209.68.2.70 Date: Tue, 20 Jan 2004 01:56:09 -0600 (CST) From: Mike Silbersack To: CHOI Junho In-Reply-To: <20040119.192257.34695172.cjh@kr.FreeBSD.org> Message-ID: <20040120015356.N39477@odysseus.silby.com> References: <20040119.153452.10362034.cjh@kr.FreeBSD.org> <20040119.192257.34695172.cjh@kr.FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org cc: freebsd-performance@freebsd.org Subject: Re: mbuf tuning 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: Tue, 20 Jan 2004 07:56:14 -0000 On Mon, 19 Jan 2004, CHOI Junho wrote: > I am using custom version of thttpd. It allocates mmap() first(builtin > method of thttpd), and it try to use sendfile() if mmap() fails(out of > mmap memory). It really works good in normal status but the problem is > that sendfile buffer is also easy to flood. I need more sendfile > buffers but I don't know how to increase sendfile buffers either(I > think it's hidden sysctl but it was more difficult to tune than > nmbclusters). With higher traffic, thttpd sometimes stuck at "sfbufa" > status when I run top(I guess it's "sendfile buffer allocation" > status). > > 5.2 is fair good quality in my desktop but I have no experience in > production environment. I'll consider it once 5.x enters -STABLE tree, > but not now. > > Apache2 is one of my targets. How much better than apache-1.3.x in > static file service? thttpd using sendfile will certainly run circles around apache2, apache2 is still pre-fork. Under 4.x, you're going to have to tune the sfbufs by trial and error, but doing so will be worth it. Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 00:47:28 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 92CC216A4CE for ; Tue, 20 Jan 2004 00:47:28 -0800 (PST) Received: from mail.butovo-online.ru (mail.b-o.ru [212.5.78.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8533443D1D for ; Tue, 20 Jan 2004 00:47:27 -0800 (PST) (envelope-from resident@b-o.ru) Received: from [192.168.92.185] (helo=192.168.92.185) by mail.butovo-online.ru with esmtp (Exim 4.24) id 1AireK-000D7y-0s; Tue, 20 Jan 2004 11:54:16 +0300 Date: Tue, 20 Jan 2004 11:48:44 +0300 From: Andrew Riabtsev X-Mailer: The Bat! (v1.62i) Business X-Priority: 3 (Normal) Message-ID: <1602380953.20040120114844@b-o.ru> To: Dinesh Nair In-Reply-To: <20040120012819.I312-100000@prophet.alphaque.com> References: <20040120012819.I312-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re[2]: netgraph questions on ng_tee, ng_iface, ng_socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Andrew Riabtsev List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 08:47:28 -0000 Hi, Dinesh, Monday, January 19, 2004, 8:29:23 PM, you wrote: DN> On Mon, 19 Jan 2004, Andrew Riabtsev wrote: >> DN> connecting the ng_iface hook inet to ng_ether's upper or lower doesnt make >> DN> any sense because ng_ether itself does not do an encasulation of the IP >> DN> packet into an ethernet frame. or am i wrong here, and just configuring it >> DN> wrongly ? >> >> Connecting ng_iface:inet and ng_ether:upper/lower do nothing, well, it >> do something but not what you are waiting for, i think. DN> i know, hence was asking if there was something i could do, even if it DN> meant writing an extension to ng_ether to create a new netgraph type. You could try to write netgraph module that makes same thing with packets and frame as functions ether_(input/output) in net/if_ethersubr.c. Thats all that come in my mind. -- Andrew mailto:resident@b-o.ru From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 01:19:00 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 0A7E516A4CE for ; Tue, 20 Jan 2004 01:19:00 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4063443D39 for ; Tue, 20 Jan 2004 01:18:58 -0800 (PST) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i0K9HWAB010853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jan 2004 12:17:33 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i0K9HW4V010852; Tue, 20 Jan 2004 12:17:32 +0300 (MSK) Date: Tue, 20 Jan 2004 12:17:32 +0300 From: Gleb Smirnoff To: Andrew Riabtsev Message-ID: <20040120091732.GB10731@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Andrew Riabtsev , Dinesh Nair , freebsd-net@freebsd.org References: <20040120012819.I312-100000@prophet.alphaque.com> <1602380953.20040120114844@b-o.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <1602380953.20040120114844@b-o.ru> User-Agent: Mutt/1.5.4i cc: Dinesh Nair cc: freebsd-net@freebsd.org Subject: Re: netgraph questions on ng_tee, ng_iface, ng_socket 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: Tue, 20 Jan 2004 09:19:00 -0000 On Tue, Jan 20, 2004 at 11:48:44AM +0300, Andrew Riabtsev wrote: A> >> Connecting ng_iface:inet and ng_ether:upper/lower do nothing, well, it A> >> do something but not what you are waiting for, i think. A> A> DN> i know, hence was asking if there was something i could do, even if it A> DN> meant writing an extension to ng_ether to create a new netgraph type. A> A> You could try to write netgraph module that makes same thing with A> packets and frame as functions ether_(input/output) in A> net/if_ethersubr.c. Thats all that come in my mind. Isn't ng_etf(4) the one you need? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 03:32:28 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 0AA4F16A4CE for ; Tue, 20 Jan 2004 03:32:28 -0800 (PST) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D33F43D2D for ; Tue, 20 Jan 2004 03:32:26 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])i0KBWLug015640; Tue, 20 Jan 2004 22:32:21 +1100 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i0KBWHp2023265; Tue, 20 Jan 2004 22:32:19 +1100 Date: Tue, 20 Jan 2004 22:32:18 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: itojun@iijlab.net In-Reply-To: <20040120063133.EC399B2@coconut.itojun.org> Message-ID: <20040120210418.V3916@gamplex.bde.org> References: <20040120063133.EC399B2@coconut.itojun.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org cc: rrs@cisco.com Subject: Re: timersub/timeradd/timercmp 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: Tue, 20 Jan 2004 11:32:28 -0000 On Tue, 20 Jan 2004 itojun@iijlab.net wrote: > could anyone let me know why timersub/add/cmp are disabled in the > kernel? They are spelled timevalsub/add/cmp in the kernel. This is a better spelling, since there are several data structures that can represent the time. timersub/add/cmp are disabled in the kernel to prevent regressions to worse names. > they were introduced in 4.4BSD, Actually, they were mostly introduced in NetBSD. 4.4BSD only has timercmp (and some other timer* functions) as a macro, and timevalsub/add as (unprototyped, not even declared) non-inline functions. FreeBSD picked up timersub/add from NetBSD for use in userland, and soon after renamed timercmp to timevalcmp in the kernel, and added timeval* for userland and timespec* for the kernel, and a few years later added bintime* for both the userland and the kernel. So FreeBSD now has kitchensinktime*^Wtimekitchensink*, and is only missing timercmp in the kernel relative to 4.4BSD. > and (non-)availability of > these macro makes it difficult for kame/rrs to deal with multiple > *BSDs. (guessing: are you trying to enforce the use of timespec > in the kernel?) That may have been a minor reason (before FreeBSD renamed timercmp to get the consistently better timeval* names). I tried to prevent timersub/add from being exported to userland. timevals are stupid interfaces that were needed when CPUs were slow and couldn't do floating point or wide integer operations very well. Why introduce macros to operate on them several years after they became obsolete? Portable code can't use these macros anyway. I agree the timeval access macros are better suited to things like adjusting select() timeouts than converting everything to floating point and back. It was in Dec. 1996 that timevals had been obsolete for several years and FreeBSD picked up the timer macros from NetBSD. timevals weren't obsolete in practice then of course. timespecs had only been standard in POSIX for 8 years, and lots of interfaces still used only timevals. 7 years later, time handling is messier than ever. POSIX has standardized all the old interfaces, so timevals are unlikely to go away for more than another 8+7 years (I guess twice that). OTOH, timespecs stopped being precise enough for some applications at about the same time as POSIX regressed from supporting only timespecs. phk is now trying to convert things to bintimes, and C99 couldn't agree on any useful extensions of time_t. Bruce From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 03:44:28 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 367FE16A4CE for ; Tue, 20 Jan 2004 03:44:28 -0800 (PST) Received: from mail.butovo-online.ru (mail.b-o.ru [212.5.78.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D82643D2D for ; Tue, 20 Jan 2004 03:44:27 -0800 (PST) (envelope-from resident@b-o.ru) Received: from [192.168.92.185] (helo=192.168.92.185) by mail.butovo-online.ru with esmtp (Exim 4.24) id 1AiuPY-000DMo-L3; Tue, 20 Jan 2004 14:51:12 +0300 Date: Tue, 20 Jan 2004 14:45:34 +0300 From: Andrew Riabtsev X-Mailer: The Bat! (v1.62i) Business X-Priority: 3 (Normal) Message-ID: <4312991350.20040120144534@b-o.ru> To: Gleb Smirnoff In-Reply-To: <20040120091732.GB10731@cell.sick.ru> References: <20040120012819.I312-100000@prophet.alphaque.com> <1602380953.20040120114844@b-o.ru> <20040120091732.GB10731@cell.sick.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re[2]: netgraph questions on ng_tee, ng_iface, ng_socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Andrew Riabtsev List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 11:44:28 -0000 GS> On Tue, Jan 20, 2004 at 11:48:44AM +0300, Andrew Riabtsev wrote: A>> >> Connecting ng_iface:inet and ng_ether:upper/lower do nothing, well, it A>> >> do something but not what you are waiting for, i think. A>> A>> DN> i know, hence was asking if there was something i could do, even if it A>> DN> meant writing an extension to ng_ether to create a new netgraph type. A>> A>> You could try to write netgraph module that makes same thing with A>> packets and frame as functions ether_(input/output) in A>> net/if_ethersubr.c. Thats all that come in my mind. GS> Isn't ng_etf(4) the one you need? As i undestand this module just filters packets, using values in ethernet header, but Dinesh need something that add ethernet header to ip packet in one direction and stript ip-packet from ethernet frame in other direction. -- Andrew mailto:resident@b-o.ru From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 04:19:24 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 8492C16A4CE for ; Tue, 20 Jan 2004 04:19:24 -0800 (PST) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id B038943D54 for ; Tue, 20 Jan 2004 04:19:15 -0800 (PST) (envelope-from bpwatkins@internode.on.net) Received: from bradtop (ppp191-189.lns1.bne1.internode.on.net [150.101.191.189])i0KCJAxC029332; Tue, 20 Jan 2004 22:49:11 +1030 (CST) Message-ID: <005901c3df4f$9cd48650$33a119ac@ptds.qld.prism.int> From: "Brad Watkins" To: Date: Tue, 20 Jan 2004 22:19:09 +1000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: Tom Storey Subject: mpd 3.15 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: Tue, 20 Jan 2004 12:19:24 -0000 I'm having trouble configuring mpd 3.15, Im trying to create a vpn tunnel to a friends network throguh the = internet who is using windows 2003 at the moment but will be using = freebsd and mpd as well. the vpn will allow incomming connections but not outgoing. i will attach the configuration files below mpd.links ~~~~~~~~~ vpn: set link type pptp set pptp self 172.25.161.45/27 set pptp peer 172.25.161.51/27 set pptp enable originate incoming outcall mpd.conf ~~~~~~~~~ default: load vpn vpn: new -i ng1 vpn vpn set iface disable on-demand set iface addrs 172.25.144.1 172.25.145.1 set iface idle 0 set bundle session 28800 set iface route 172.25.145.0/24 set bundle disable multilink set bundle authname "BRADTOP\\tom_brad" set bundle password "rotaredom" set bundle enable compression set link yes acfcomp protocomp set link no pap set link yes chap set link mtu 1500 set link enable no-orig-auth set link keep-alive 60 100 set ipcp yes vjcomp set ipcp ranges 172.25.144.0/24 172.25.145.0/24 set bundle enable compression set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set bundle enable crypt-reqd set ccp yes mpp-s open The log output to the screen when i try to establish and outgoing = connection is: Multi-link PPP for FreeBSD, by Archie L. Cobbs. Based on iij-ppp, by Toshiharu OHNO. mpd: pid 607, version 3.15 (root@freebsd.org 04:02 5-Dec-2003) [vpn] ppp node is "mpd607-vpn" mpd: local IP address for PPTP is 172.25.161.45 [vpn] using interface ng1 set bundle session: unknown command. Try "help". [vpn] IFACE: Open event [vpn] IPCP: Open event [vpn] IPCP: state change Initial --> Starting [vpn] IPCP: LayerStart [vpn:vpn] [vpn] bundle: OPEN event in state CLOSED [vpn] opening link "vpn"... [vpn] link: OPEN event [vpn] LCP: Open event [vpn] LCP: state change Initial --> Starting [vpn] LCP: LayerStart [vpn] device: OPEN event in state DOWN pptp0: connecting to 172.25.161.51:1723 [vpn] device is now in state OPENING pptp0: connected to 172.25.161.51:1723 pptp0: attached to connection with 172.25.161.51:1723 pptp0-0: outgoing call connected at -2131151101 bps [vpn] PPTP call successful [vpn] device: UP event in state OPENING [vpn] device is now in state UP [vpn] link: UP event [vpn] link: origination is local [vpn] LCP: Up event [vpn] LCP: state change Starting --> Req-Sent [vpn] LCP: phase shift DEAD --> ESTABLISH [vpn] LCP: SendConfigReq #1 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM aa4072b4 AUTHPROTO CHAP MSOFTv2 [vpn] LCP: rec'd Configure Request #0 link 0 (Req-Sent) MRU 1400 AUTHPROTO CHAP MSOFTv2 MAGICNUM 6ed15b39 PROTOCOMP ACFCOMP CALLBACK Not supported MP MRRU 1614 ENDPOINTDISC [LOCAL] 43 b0 65 0f 83 4e 42 24 b8 53 b2 3b a9 1a d8 f7 00 = 00 00 00 BACP Not supported [vpn] LCP: SendConfigRej #0 CALLBACK MP MRRU 1614 BACP [vpn] LCP: rec'd Configure Ack #1 link 0 (Req-Sent) ACFCOMP PROTOCOMP MRU 1500 MAGICNUM aa4072b4 AUTHPROTO CHAP MSOFTv2 [vpn] LCP: state change Req-Sent --> Ack-Rcvd [vpn] LCP: rec'd Configure Request #1 link 0 (Ack-Rcvd) MRU 1400 AUTHPROTO CHAP MSOFTv2 MAGICNUM 6ed15b39 PROTOCOMP ACFCOMP ENDPOINTDISC [LOCAL] 43 b0 65 0f 83 4e 42 24 b8 53 b2 3b a9 1a d8 f7 00 = 00 00 00 [vpn] LCP: SendConfigAck #1 MRU 1400 AUTHPROTO CHAP MSOFTv2 MAGICNUM 6ed15b39 PROTOCOMP ACFCOMP ENDPOINTDISC [LOCAL] 43 b0 65 0f 83 4e 42 24 b8 53 b2 3b a9 1a d8 f7 00 = 00 00 00 [vpn] LCP: state change Ack-Rcvd --> Opened [vpn] LCP: phase shift ESTABLISH --> AUTHENTICATE [vpn] LCP: auth: peer wants CHAP, I want CHAP [vpn] CHAP: sending CHALLENGE [vpn] LCP: LayerUp [vpn] CHAP: rec'd CHALLENGE #0 Name: "BRADTOP" Using authname "BRADTOP\tom_brad" [vpn] CHAP: sending RESPONSE [vpn] CHAP: rec'd SUCCESS #0 MESG: S=3D14B3226FA5A3C3ACD9074A862DEF0130008868E9 [vpn] LCP: rec'd Configure Request #3 link 0 (Opened) MRU 1400 AUTHPROTO CHAP MSOFTv2 MAGICNUM 6f953262 PROTOCOMP ACFCOMP CALLBACK Not supported MP MRRU 1614 ENDPOINTDISC [LOCAL] 43 b0 65 0f 83 4e 42 24 b8 53 b2 3b a9 1a d8 f7 00 = 00 00 00 BACP Not supported [vpn] LCP: LayerDown [vpn] LCP: SendConfigReq #2 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM aa4072b4 AUTHPROTO CHAP MSOFTv2 [vpn] LCP: SendConfigRej #3 CALLBACK MP MRRU 1614 BACP [vpn] LCP: state change Opened --> Req-Sent [vpn] LCP: phase shift AUTHENTICATE --> ESTABLISH [vpn] LCP: rec'd Configure Reject #2 link 0 (Req-Sent) AUTHPROTO CHAP MSOFTv2 [vpn] LCP: SendConfigReq #3 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM aa4072b4 AUTHPROTO CHAP MSOFTv2 pptp0: CID 0x57d3 in SetLinkInfo not found [vpn] LCP: rec'd Configure Request #4 link 0 (Req-Sent) MRU 1400 AUTHPROTO CHAP MSOFTv2 MAGICNUM 6f953262 PROTOCOMP ACFCOMP ENDPOINTDISC [LOCAL] 43 b0 65 0f 83 4e 42 24 b8 53 b2 3b a9 1a d8 f7 00 = 00 00 00 [vpn] LCP: SendConfigAck #4 MRU 1400 AUTHPROTO CHAP MSOFTv2 MAGICNUM 6f953262 PROTOCOMP ACFCOMP ENDPOINTDISC [LOCAL] 43 b0 65 0f 83 4e 42 24 b8 53 b2 3b a9 1a d8 f7 00 = 00 00 00 [vpn] LCP: state change Req-Sent --> Ack-Sent [vpn] LCP: rec'd Configure Reject #3 link 0 (Ack-Sent) AUTHPROTO CHAP MSOFTv2 [vpn] LCP: SendConfigReq #4 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM aa4072b4 AUTHPROTO CHAP MSOFTv2 pptp0: CID 0x57d3 in SetLinkInfo not found [vpn] LCP: rec'd Configure Reject #4 link 0 (Ack-Sent) AUTHPROTO CHAP MSOFTv2 [vpn] LCP: SendConfigReq #5 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM aa4072b4 AUTHPROTO CHAP MSOFTv2 [vpn] LCP: rec'd Configure Reject #5 link 0 (Ack-Sent) AUTHPROTO CHAP MSOFTv2 [vpn] LCP: SendConfigReq #6 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM aa4072b4 AUTHPROTO CHAP MSOFTv2 [vpn] LCP: rec'd Configure Reject #6 link 0 (Ack-Sent) AUTHPROTO CHAP MSOFTv2 [vpn] LCP: SendConfigReq #7 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM aa4072b4 AUTHPROTO CHAP MSOFTv2 [vpn] LCP: rec'd Terminate Request #5 link 0 (Ack-Sent) [vpn] LCP: state change Ack-Sent --> Req-Sent [vpn] LCP: SendTerminateAck #8 [vpn] LCP: rec'd Terminate Request #6 link 0 (Req-Sent) [vpn] LCP: SendTerminateAck #9 [vpn] LCP: SendConfigReq #10 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM aa4072b4 AUTHPROTO CHAP MSOFTv2 From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 04:21:18 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 0680816A4CE for ; Tue, 20 Jan 2004 04:21:18 -0800 (PST) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BC9743D2D for ; Tue, 20 Jan 2004 04:21:16 -0800 (PST) (envelope-from bootsector@internode.on.net) Received: from laptom (ppp191-189.lns1.bne1.internode.on.net [150.101.191.189])i0KCLExC032630 for ; Tue, 20 Jan 2004 22:51:15 +1030 (CST) Message-ID: <001001c3df4f$e69a05d0$34a119ac@ptds.qld.prism.int> From: "Thomas Storey" To: Date: Tue, 20 Jan 2004 22:21:10 +1000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: VPN from me to a friend 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: Tue, 20 Jan 2004 12:21:18 -0000 Me and a friend want to setup a VPN between our "core" routers using = FreeBSD to join our networks together (to a certain extent) Which software will do the job and how do we set it up? Cheers From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 04:23:34 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 3A0EE16A4CE for ; Tue, 20 Jan 2004 04:23:34 -0800 (PST) Received: from redqueen.elvandar.org (cust.94.120.adsl.cistron.nl [195.64.94.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id D76FF43D39 for ; Tue, 20 Jan 2004 04:23:30 -0800 (PST) (envelope-from remko@elvandar.org) From: "Remko Lodder" To: Date: Tue, 20 Jan 2004 13:23:35 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) Importance: Normal In-Reply-To: <20040120122143.1B9BA5E@mail.elvandar.org> X-Virus-Scanned: by amavisd-new at elvandar.org Message-Id: <20040120122329.CE0782B4D89@redqueen.elvandar.org> Subject: RE: [Freebsd-net] VPN from me to a friend 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: Tue, 20 Jan 2004 12:23:34 -0000 You can use pptp, isakmpd, racoon, They are all used to do VPN stuff, racoon is a common VPN software package that is in use by FreeBSD. Hope this helped. -- Kind regards, Remko Lodder Elvandar.org/DSINet.org www.mostly-harmless.nl Dutch community for helping newcomers on the hackerscene -----Oorspronkelijk bericht----- Van: freebsd-net-bounces@lists.elvandar.org [mailto:freebsd-net-bounces@lists.elvandar.org]Namens Thomas Storey Verzonden: dinsdag 20 januari 2004 13:21 Aan: freebsd-net@freebsd.org Onderwerp: [Freebsd-net] VPN from me to a friend Me and a friend want to setup a VPN between our "core" routers using FreeBSD to join our networks together (to a certain extent) Which software will do the job and how do we set it up? Cheers _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" _______________________________________________ Freebsd-net mailing list Freebsd-net@lists.elvandar.org http://lists.elvandar.org/mailman/listinfo/freebsd-net From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 06:02:53 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 B365F16A4CE for ; Tue, 20 Jan 2004 06:02:53 -0800 (PST) Received: from mail.a-quadrat.at (mail.a-quadrat.at [81.223.141.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1453843D39 for ; Tue, 20 Jan 2004 06:02:52 -0800 (PST) (envelope-from mbretter@a-quadrat.at) Received: from BRUTUS.a-quadrat.at (brutus.a-quadrat.at [192.168.90.60]) by files.a-quadrat.at (Postfix) with ESMTP id D6D835C041; Tue, 20 Jan 2004 14:59:02 +0100 (CET) Date: Tue, 20 Jan 2004 15:02:44 +0100 (=?ISO-8859-15?Q?Westeurop=E4ische_Normalzeit?=) From: Michael Bretterklieber To: Brad Watkins In-Reply-To: <005901c3df4f$9cd48650$33a119ac@ptds.qld.prism.int> Message-ID: References: <005901c3df4f$9cd48650$33a119ac@ptds.qld.prism.int> X-X-Sender: mbretter@files.a-quadrat.at MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org cc: Tom Storey Subject: Re: mpd 3.15 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: Tue, 20 Jan 2004 14:02:53 -0000 Hi, On Tue, 20 Jan 2004, Brad Watkins wrote: > I'm having trouble configuring mpd 3.15, > Im trying to create a vpn tunnel to a friends network throguh the internet who is using windows 2003 at the moment but will be using freebsd and mpd as well. > the vpn will allow incomming connections but not outgoing. > i will attach the configuration files below > > mpd.links > ~~~~~~~~~ > vpn: > set link type pptp > set pptp self 172.25.161.45/27 > set pptp peer 172.25.161.51/27 > set pptp enable originate incoming outcall for outgoing connections remove "incoming" and "set pptp self", and a single IP-Address is here expected and not an address-range. > > mpd.conf > ~~~~~~~~~ > default: > > load vpn > > vpn: > new -i ng1 vpn vpn > set iface disable on-demand > set iface addrs 172.25.144.1 172.25.145.1 > set iface idle 0 > set bundle session 28800 > set iface route 172.25.145.0/24 > set bundle disable multilink > set bundle authname "BRADTOP\\tom_brad" > set bundle password "rotaredom" > set bundle enable compression > set link yes acfcomp protocomp > set link no pap > set link yes chap for outgoing connections it's better just doing: set link no pap chap set link accept chap ... because "yes" stands for "enable" and "accept", whereas "enable" means, "I'm actively requesting this feature", wich can make problems in client mode. bye, -- ------------------------------- ---------------------------------- Michael Bretterklieber - http://www.bretterklieber.com A-Quadrat Automation GmbH - http://www.a-quadrat.at Tel: ++43-(0)3172-41679 - GSM: ++43-(0)699 12861847 ------------------------------- ---------------------------------- "...the number of UNIX installations has grown to 10, with more expected..." - Dennis Ritchie and Ken Thompson, June 1972 From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 11:21:52 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 2995E16A4CE for ; Tue, 20 Jan 2004 11:21:52 -0800 (PST) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id 685BF43D64 for ; Tue, 20 Jan 2004 11:21:47 -0800 (PST) (envelope-from dinesh@alphaque.com) Received: (qmail 30488 invoked by uid 0); 20 Jan 2004 19:21:46 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 20 Jan 2004 19:21:46 -0000 Received: from localhost (localhost.alphaque.com [127.0.0.1]) by prophet.alphaque.com (8.12.10/8.12.9) with ESMTP id i0KINix3004442; Wed, 21 Jan 2004 02:23:44 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Wed, 21 Jan 2004 02:23:44 +0800 (MYT) From: Dinesh Nair To: Craig Rodrigues In-Reply-To: <20040119191352.GA52975@crodrigues.org> Message-ID: <20040121022329.S312-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@FreeBSD.org Subject: Re: Two ISP lines 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: Tue, 20 Jan 2004 19:21:52 -0000 On Mon, 19 Jan 2004, Craig Rodrigues wrote: > On Tue, Jan 20, 2004 at 01:50:57AM +0800, Dinesh Nair wrote: > > there was a multipath patch for 4-STABLE some months back, though for the > > life of me, i don't know where it's archived anymore. > > Are you referring to these patches? > > http://lists.freebsd.org/pipermail/freebsd-hackers/2003-July/001843.html the very same ! thanx a bunch, craig. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 11:21:52 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 D86E516A4CE for ; Tue, 20 Jan 2004 11:21:52 -0800 (PST) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id 9E50B43D58 for ; Tue, 20 Jan 2004 11:21:46 -0800 (PST) (envelope-from dinesh@alphaque.com) Received: (qmail 30480 invoked by uid 0); 20 Jan 2004 19:21:44 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 20 Jan 2004 19:21:44 -0000 Received: from localhost (localhost.alphaque.com [127.0.0.1]) by prophet.alphaque.com (8.12.10/8.12.9) with ESMTP id i0KIpqx3004536; Wed, 21 Jan 2004 02:51:52 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Wed, 21 Jan 2004 02:51:52 +0800 (MYT) From: Dinesh Nair To: Gleb Smirnoff In-Reply-To: <20040120091732.GB10731@cell.sick.ru> Message-ID: <20040121024916.K312-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Andrew Riabtsev cc: freebsd-net@FreeBSD.org Subject: Re: netgraph questions on ng_tee, ng_iface, ng_socket 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: Tue, 20 Jan 2004 19:21:53 -0000 On Tue, 20 Jan 2004, Gleb Smirnoff wrote: > Isn't ng_etf(4) the one you need? ng_etf does filtering, i'm planning on doing round robin IP tranmission, with source IP address set accordingly. see ng_one2many which gives an example for ethernet frames. i want to do the same thing in ng_one2many's EXAMPLE section, but with the added functionality of changing the ip address to match the ip address bound to the interface the packet is going out from. with this ip address, the next hop router(s) wont be able to route the reply back thru the same interface, especially if they're seeing non legit src addressed packets. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 11:22:05 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 B75D816A4DC for ; Tue, 20 Jan 2004 11:22:05 -0800 (PST) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id DFBD543D4C for ; Tue, 20 Jan 2004 11:21:46 -0800 (PST) (envelope-from dinesh@alphaque.com) Received: (qmail 30484 invoked by uid 0); 20 Jan 2004 19:21:45 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 20 Jan 2004 19:21:45 -0000 Received: from localhost (localhost.alphaque.com [127.0.0.1]) by prophet.alphaque.com (8.12.10/8.12.9) with ESMTP id i0KIWkx3004485; Wed, 21 Jan 2004 02:32:46 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Wed, 21 Jan 2004 02:32:46 +0800 (MYT) From: Dinesh Nair To: Max Laier In-Reply-To: <200401192034.22796.max@love2party.net> Message-ID: <20040121023111.X312-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@FreeBSD.org Subject: Re: Two ISP lines 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: Tue, 20 Jan 2004 19:22:05 -0000 On Mon, 19 Jan 2004, Max Laier wrote: > On Monday 19 January 2004 18:50, Dinesh Nair wrote: > > however, there was a multipath patch for 4-STABLE some months back, > > though for the life of me, i don't know where it's archived anymore. > > > > check -questions archives for this thread. > > take a look at secuirty/pf (from ports) it can make use of more than one > uplink. It provides round-robin and source-hash load balancing and you > can define even finer policy routing with it. > > It works currently for 5.x only, for a 4.x version check KAME. will do. i'm on 4.9-STABLE. will try the following in this order: 1. the multipath patches 2. security/pf port 3. rewriting ng_ether to plonk in the new ip address directly into the mbuf. along with ng_one2many, this should provide the same functionality. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 12:14:53 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 679D616A4CE for ; Tue, 20 Jan 2004 12:14:53 -0800 (PST) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF07743D48 for ; Tue, 20 Jan 2004 12:14:51 -0800 (PST) (envelope-from gnagelhout@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Tue, 20 Jan 2004 14:59:44 -0500 Message-ID: From: Gerrit Nagelhout To: freebsd-net@freebsd.org Date: Tue, 20 Jan 2004 14:59:36 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Subject: Intel em transmit hangs with DMA packet prefetching enabled 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: Tue, 20 Jan 2004 20:14:53 -0000 Hi, Recently I turned on the packet prefetching feature (register TXDMAC 0x3000, set DPP to 0). This increases the maximum transmit performance per port by about 50KPPS. Everything worked fine, until one of our applications that sends lots of data with multiple (2 - 3) mbufs per descriptor started using this feature, and the transmitter started hanging. The watchdog feature in the driver catches it, and resets the chip, after which everything is good again for a while. Has anyone else seen this behaviour before? Thanks, Gerrit Nagelhout From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 12:30:33 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 EE79916A4CE for ; Tue, 20 Jan 2004 12:30:33 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E43743D54 for ; Tue, 20 Jan 2004 12:29:40 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i0KKTd5P013066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 20 Jan 2004 15:29:39 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i0KKTYkA097987; Tue, 20 Jan 2004 15:29:34 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16397.36782.415899.626311@grasshopper.cs.duke.edu> Date: Tue, 20 Jan 2004 15:29:34 -0500 (EST) To: freebsd-net@freebsd.org X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Subject: tcp mss MCLBYTES restriction 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: Tue, 20 Jan 2004 20:30:34 -0000 For the case where the mtu is larger than MCLBYTES (2048), FreeBSD's TCP implementation restricts the mss to a multiple of MCLBYTES. This appears to have been inherited from 4.4BSD-lite. On adapters with 9000 byte jumbo frames, this limits the mss to 8192 bytes, and wastes nearly 1KB out of each frame. This is especially annoying because many drivers for adapters which support 9000 byte mtus allocate their own 9000 byte receive buffers and don't even use mbufs which are MCLBYTES in length. In this case, the mss restriction guarantees a nearly 1000 byte wastage per frame. Would it be OK if I made this code optional via a sysctl? Drew From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 12:42:05 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 7E45016A4CE for ; Tue, 20 Jan 2004 12:42:05 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5953743D79 for ; Tue, 20 Jan 2004 12:41:23 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 96184 invoked from network); 20 Jan 2004 20:41:22 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 20 Jan 2004 20:41:22 -0000 Message-ID: <400D9271.1259CBC8@freebsd.org> Date: Tue, 20 Jan 2004 21:41:21 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin References: <16397.36782.415899.626311@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: tcp mss MCLBYTES restriction 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: Tue, 20 Jan 2004 20:42:05 -0000 Andrew Gallatin wrote: > > For the case where the mtu is larger than MCLBYTES (2048), FreeBSD's > TCP implementation restricts the mss to a multiple of MCLBYTES. This > appears to have been inherited from 4.4BSD-lite. > > On adapters with 9000 byte jumbo frames, this limits the mss to 8192 > bytes, and wastes nearly 1KB out of each frame. This is especially > annoying because many drivers for adapters which support 9000 byte mtus > allocate their own 9000 byte receive buffers and don't even use mbufs > which are MCLBYTES in length. In this case, the mss restriction guarantees > a nearly 1000 byte wastage per frame. When I was implementing the tcp_hostcache I reorganized/redid the tcp_mss() function and wondered about that too. I don't know if this rounding to MCLBYTES is still the right thing to do. > Would it be OK if I made this code optional via a sysctl? Could you run some bechmarks with the current MCLBYTES rounding and without it on 100Mbit 1.5kMTU and GigE with 9k MTU? -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 12:53: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 4FD0C16A4CE; Tue, 20 Jan 2004 12:53:02 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D6AB43D6B; Tue, 20 Jan 2004 12:52:33 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i0KKqW5P016692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jan 2004 15:52:32 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i0KKqRq5098009; Tue, 20 Jan 2004 15:52:27 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16397.38155.418523.634400@grasshopper.cs.duke.edu> Date: Tue, 20 Jan 2004 15:52:27 -0500 (EST) To: Andre Oppermann In-Reply-To: <400D9271.1259CBC8@freebsd.org> References: <16397.36782.415899.626311@grasshopper.cs.duke.edu> <400D9271.1259CBC8@freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-net@freebsd.org Subject: Re: tcp mss MCLBYTES restriction 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: Tue, 20 Jan 2004 20:53:02 -0000 Andre Oppermann writes: > When I was implementing the tcp_hostcache I reorganized/redid the > tcp_mss() function and wondered about that too. I don't know if > this rounding to MCLBYTES is still the right thing to do. I have the feeling its something from ancient days on vaxes. ;) > > Would it be OK if I made this code optional via a sysctl? > > Could you run some bechmarks with the current MCLBYTES rounding > and without it on 100Mbit 1.5kMTU and GigE with 9k MTU? 1.5k MTU won't matter -- it doesn't hit the rounding case anyway. But I can certainly run some tests with 9k. Drew From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 13:09:15 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 0E91616A4CE; Tue, 20 Jan 2004 13:09:15 -0800 (PST) Received: from mail1.cray.com (mail1.cray.com [136.162.0.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id B49AB43D5E; Tue, 20 Jan 2004 13:08:58 -0800 (PST) (envelope-from dab@cray.com) Received: from relayb.mw.cray.com (relayb.us.cray.com [192.168.252.110]) i0KL8l7W002114; Tue, 20 Jan 2004 15:08:48 -0600 (CST) Received: from saffron.us.cray.com (saffron.mw.cray.com [172.31.27.14]) i0KL8ksB004506; Tue, 20 Jan 2004 15:08:46 -0600 (CST) Received: from [127.0.0.1] (troll [192.168.250.5])i0KL8juP4188597; Tue, 20 Jan 2004 15:08:45 -0600 (CST) In-Reply-To: <16397.38155.418523.634400@grasshopper.cs.duke.edu> References: <16397.36782.415899.626311@grasshopper.cs.duke.edu> <400D9271.1259CBC8@freebsd.org> <16397.38155.418523.634400@grasshopper.cs.duke.edu> Mime-Version: 1.0 (Apple Message framework v609) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: David Borman Date: Tue, 20 Jan 2004 15:08:32 -0600 To: Andrew Gallatin X-Mailer: Apple Mail (2.609) X-Cray-VirusStatus: clean cc: freebsd-net@freebsd.org cc: Andre Oppermann Subject: Re: tcp mss MCLBYTES restriction 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: Tue, 20 Jan 2004 21:09:15 -0000 On the sending side, you'll tend to get your best performance when the socket buffer is a multiple of the amount of TCP data per packet, and the users writes are a multiple of the socket buffer. This keeps everything neatly aligned, minimizing the number of data copies that need to be done, and improving the chance of doing page flips. Rounding down a 1500 byte ethernet packet to a 1K boundary looses too much data, but for larger MTUs, the win of keeping everything neatly aligned can exceed the cost of not packing each packet with the maximum amount of data. Since applications that are writing large amounts of data to a socket will tend to be using buffers aligned on a K boundary, using a K aligned amount of TCP data increases the chances that everything stays aligned. -David Borman, dab@cray.com On Jan 20, 2004, at 2:52 PM, Andrew Gallatin wrote: > > Andre Oppermann writes: >> When I was implementing the tcp_hostcache I reorganized/redid the >> tcp_mss() function and wondered about that too. I don't know if >> this rounding to MCLBYTES is still the right thing to do. > > I have the feeling its something from ancient days on vaxes. ;) > >>> Would it be OK if I made this code optional via a sysctl? >> >> Could you run some bechmarks with the current MCLBYTES rounding >> and without it on 100Mbit 1.5kMTU and GigE with 9k MTU? > > 1.5k MTU won't matter -- it doesn't hit the rounding case anyway. > But I can certainly run some tests with 9k. > > Drew > > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 13:26:07 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 BD9AE16A4CE; Tue, 20 Jan 2004 13:26:07 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5CE743D48; Tue, 20 Jan 2004 13:26:03 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i0KLQ15P022276 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jan 2004 16:26:01 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i0KLPuKa098055; Tue, 20 Jan 2004 16:25:56 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16397.40164.341384.651639@grasshopper.cs.duke.edu> Date: Tue, 20 Jan 2004 16:25:56 -0500 (EST) To: David Borman In-Reply-To: References: <16397.36782.415899.626311@grasshopper.cs.duke.edu> <400D9271.1259CBC8@freebsd.org> <16397.38155.418523.634400@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-net@freebsd.org cc: Andre Oppermann Subject: Re: tcp mss MCLBYTES restriction 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: Tue, 20 Jan 2004 21:26:07 -0000 David Borman writes: > On the sending side, you'll tend to get your best performance when the > socket buffer is a multiple of the amount of TCP data per packet, and > the users writes are a multiple of the socket buffer. This keeps > everything neatly aligned, minimizing the number of data copies that > need to be done, and improving the chance of doing page flips. Yes, this was very handy when doing the zero-copy receives. > Rounding down a 1500 byte ethernet packet to a 1K boundary looses too > much data, but for larger MTUs, the win of keeping everything neatly > aligned can exceed the cost of not packing each packet with the maximum > amount of data. Since applications that are writing large amounts of > data to a socket will tend to be using buffers aligned on a K boundary, > using a K aligned amount of TCP data increases the chances that > everything stays aligned. Good point. But how would you feel about making it optional with it defaulting as it is now? There are special cases. For example, I think its killing me on an experimental network interface which stripes data across 2 links. Drew From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 20:47:22 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 A8BC616A4CE for ; Tue, 20 Jan 2004 20:47:22 -0800 (PST) Received: from aradia.cybernetik.net (c-66-41-32-30.mn.client2.attbi.com [66.41.32.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4F4243D41 for ; Tue, 20 Jan 2004 20:47:10 -0800 (PST) (envelope-from kristofer@aradia.cybernetik.net) Received: by aradia.cybernetik.net (Postfix, from userid 1002) id B09041147D; Tue, 20 Jan 2004 22:37:07 -0600 (CST) Date: Tue, 20 Jan 2004 22:37:07 -0600 From: Kristofer Pettijohn To: freebsd-net@freebsd.org Message-ID: <20040121043707.GA24470@cybernetik.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.5.1i Subject: if_gif issues 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, 21 Jan 2004 04:47:22 -0000 I'm seeing some weird issues with the gif interface, if someone could enlighten me. This was working fine on 5.1-RELEASE when I was running it, and then I did a clean install of 5.2-RELEASE from CVS, and I'm having some weird things. I have an ipip tunnel setup using gif0 as follows: gif1: flags=8051 mtu 1460 tunnel inet a.b.c.d --> w.x.y.z inet a.b.c.d --> w.x.y.z netmask 0xffffffff inet6 fe80::2e0:18ff:fe25:21%gif1 prefixlen 64 scopeid 0x4 The first issue I saw was when someone was trying to load a webpage that traffic came in through the tunnel, it would stall; thought it was an issue with Apache, but I loaded it locally.. then I started to see weird things with mail and errors in my mailq showing up such as (conversation with servername[m.n.o.p] timed out while sending end of data -- message may be sent more than once)). The thing I noticed about all of these stalls was that the data packets are large, and I see them sitting in my netstat as ESTABLISHED sessions waiting to transmit the data.. For example, the SMTP stuff.. Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 2941 aradia.55492 smtp.otherhost.co.smtp ESTABLISHED and it will stay like that until it times out.. The mtu on my end and the other end of the tunnel match. This is setup exactly the same as it was in 5.1-RELEASE, as I copied the configuration [and also re-did it to ensure I'm sane]. So I'm seeing that gif is breaking large packets, for whatever reason. Can someone point me in the right direction, or see a bug in any new code? I looked at the cvs repository to see what has changed in it, and I don't see anything there.. I could be blind. -- Kristofer Pettijohn kristofer@cybernetik.net From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 22:11:53 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 57D3716A4CE for ; Tue, 20 Jan 2004 22:11:53 -0800 (PST) Received: from web60510.mail.yahoo.com (web60510.mail.yahoo.com [216.109.116.131]) by mx1.FreeBSD.org (Postfix) with SMTP id 2CBCA43D4C for ; Tue, 20 Jan 2004 22:11:49 -0800 (PST) (envelope-from ath101a@yahoo.com) Message-ID: <20040121061148.87496.qmail@web60510.mail.yahoo.com> Received: from [67.100.76.206] by web60510.mail.yahoo.com via HTTP; Tue, 20 Jan 2004 22:11:48 PST Date: Tue, 20 Jan 2004 22:11:48 -0800 (PST) From: Andrew Thomas To: freebsd-net@freebsd.org In-Reply-To: <20040118114517.GA1360@cell.sick.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: MPD server not routing 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, 21 Jan 2004 06:11:53 -0000 Gleb, > A> I'm trying to get mpd working as a simple vpn server. I'm doing > A> this on a 4.9-STABLE machine of a week or so ago. No matter what > A> I do, packets will not route to the client. The login is fine, > A> the server machine has gateway enabled=YES (and in fact works OK > > <==skip==> > > For me mpd works well on STABLE system. I suppose, you should > examine your firewall configuration, and NAT, if there is one. Could you please tell me - are you using IPFILTER by any chance? And, if you are, are you using IPFILTER_DEFAULT_BLOCK? For me it's yes and yes. In looking at things it seems like the latter setting might be the problem since the 4.6 machine I tried uses IPFILTER but not default blocking. No NAT on either setup. Thanks for the feedback! Andy __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 23:40:28 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 9D76016A4CE for ; Tue, 20 Jan 2004 23:40:28 -0800 (PST) Received: from ns.mmk.ru (ns1.mmk.ru [195.54.3.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67FB343D4C for ; Tue, 20 Jan 2004 23:40:22 -0800 (PST) (envelope-from freebsd@mmk.ru) Received: from antivirus.mmk.ru (antivirus [161.8.100.3]) by ns.mmk.ru (8.12.9p1/8.12.9) with ESMTP id i0L7fLlV026846; Wed, 21 Jan 2004 12:41:21 +0500 (YEKT) (envelope-from freebsd@mmk.ru) Received: from wall.mmk.ru (localhost [127.0.0.1]) by antivirus.mmk.ru (8.12.9/8.12.9) with ESMTP id i0L7cPBQ019278; Wed, 21 Jan 2004 12:38:25 +0500 (YEKT) Received: from wall (localhost [127.0.0.1]) by wall.mmk.ru (8.12.9p2/8.12.9) with SMTP id i0L7Z0X5022974; Wed, 21 Jan 2004 12:35:02 +0500 (YEKT) (envelope-from freebsd@mmk.ru) Message-ID: <044401c3e002$917bc530$02010101@wall> From: "Dmitry A. Bondareff" To: , "CHOI Junho" References: <20040114.143113.74684785.cjh@kr.FreeBSD.org><20040115.224407.41715339.cjh@kr.FreeBSD.org><20040118220617.P5672@odysseus.silby.com> <20040119.152732.55788233.cjh@kr.FreeBSD.org> Date: Wed, 21 Jan 2004 12:40:04 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 cc: freebsd-net@freebsd.org Subject: Re: FreeBSD -> Windows HTTP TCP performance 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, 21 Jan 2004 07:40:28 -0000 ----- Original Message ----- From: "CHOI Junho" To: Cc: Sent: Monday, January 19, 2004 9:27 AM Subject: Re: FreeBSD -> Windows HTTP TCP performance > > After more investigation, I realized the problem is on the router > side. I think the problem is solved... Thanks. > > From: Mike Silbersack > Subject: Re: FreeBSD -> Windows HTTP TCP performance > Date: Sun, 18 Jan 2004 22:12:34 -0600 (CST) > > > > > On Thu, 15 Jan 2004, CHOI Junho wrote: > > > > > For those who interested, I made packet dump file: > > > > > > http://www.kr.freebsd.org/~cjh/misc/freebsd-net/ > > > > > > Best thing is do tcpdump at client machine but I have no admin > > > permission, so failed. > > > > > > -- > > > CHOI Junho KFUG > > > > I can read these fine, Andre must be going through some web proxy that > > corrupts them. :) > > > > All of the computers in the dumps are on a LAN, right? There seems to be > > quite a bit of packet loss going on, from what I can see. This is most > > certainly the cause of low throughput; we'd need tcpdumps from both ends > > to really determine if there's some suboptimal tcp interaction between w2k > > and freebsd. (From a single side of the connection, we can't even be sure > > if retransmissions are getting through, etc.) > > > > Mike "Silby" Silbersack > > -- > CHOI Junho KFUG > FreeBSD Project Web Data Bank > Key fingerprint = 1369 7374 A45F F41A F3C0 07E3 4A01 C020 E602 60F5 > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 23:53:00 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 9B0A716A4CE for ; Tue, 20 Jan 2004 23:53:00 -0800 (PST) Received: from mail.park7.number.ru (host212-5-99-220.izmaylovo.ru [212.5.99.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id D639943D1D for ; Tue, 20 Jan 2004 23:52:58 -0800 (PST) (envelope-from blacksir@number.ru) Received: from blacksir.local ([192.168.2.166] helo=blacksir) by mail.park7.number.ru with smtp (Exim 4.30 #0 (Slackware)) id 1AjDAR-0000BS-9k for ; Wed, 21 Jan 2004 10:52:51 +0300 From: "Vasenin Alexander aka BlackSir" To: Date: Wed, 21 Jan 2004 10:51:18 +0300 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Subject: What does it mean: arp_rtrequest: bad gateway value 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, 21 Jan 2004 07:53:00 -0000 Those messages sometimes appears in log. Maybe someone know where to find what it actually mean? Jan 21 02:58:54 inet /kernel: arp_rtrequest: bad gateway value Jan 21 03:03:54 inet /kernel: arp_rtrequest: bad gateway value Jan 21 03:08:53 inet /kernel: arp_rtrequest: bad gateway value Jan 21 03:13:52 inet /kernel: arp_rtrequest: bad gateway value Jan 21 03:23:51 inet last message repeated 2 times Jan 21 03:33:48 inet last message repeated 2 times Vasenin Alexander aka BlackSir From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 00:20:52 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 DD96016A4CF for ; Wed, 21 Jan 2004 00:20:52 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D78F43D46 for ; Wed, 21 Jan 2004 00:20:50 -0800 (PST) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i0L8KlAB015977 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jan 2004 11:20:48 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i0L8KkE9015976; Wed, 21 Jan 2004 11:20:46 +0300 (MSK) Date: Wed, 21 Jan 2004 11:20:46 +0300 From: Gleb Smirnoff To: Andrew Thomas Message-ID: <20040121082046.GA15855@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Andrew Thomas , freebsd-net@freebsd.org References: <20040118114517.GA1360@cell.sick.ru> <20040121061148.87496.qmail@web60510.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040121061148.87496.qmail@web60510.mail.yahoo.com> User-Agent: Mutt/1.5.4i cc: freebsd-net@freebsd.org Subject: Re: MPD server not routing 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, 21 Jan 2004 08:20:53 -0000 On Tue, Jan 20, 2004 at 10:11:48PM -0800, Andrew Thomas wrote: A> > A> I'm trying to get mpd working as a simple vpn server. I'm doing A> > A> this on a 4.9-STABLE machine of a week or so ago. No matter what A> > A> I do, packets will not route to the client. The login is fine, A> > A> the server machine has gateway enabled=YES (and in fact works OK A> > A> > <==skip==> A> > A> > For me mpd works well on STABLE system. I suppose, you should A> > examine your firewall configuration, and NAT, if there is one. A> A> Could you please tell me - are you using IPFILTER by any chance? A> And, if you are, are you using IPFILTER_DEFAULT_BLOCK? No, I don't. A> For me it's yes and yes. In looking at things it seems like the A> latter setting might be the problem since the 4.6 machine I tried A> uses IPFILTER but not default blocking. No NAT on either setup. You'd better disable packet filtering at all. Establish working mpd. And then configure your ip filtering. It is easier to build a complicated router configuration step by step. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 00:50:16 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 DE22716A4CE for ; Wed, 21 Jan 2004 00:50:16 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9B2DB43D4C for ; Wed, 21 Jan 2004 00:50:15 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 89347 invoked from network); 21 Jan 2004 08:50:14 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 21 Jan 2004 08:50:14 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 21 Jan 2004 02:50:12 -0600 (CST) From: Mike Silbersack To: richard@wendland.org.uk In-Reply-To: <200401200027.AAA09260@starburst.demon.co.uk> Message-ID: <20040121024817.I56100@odysseus.silby.com> References: <200401200027.AAA09260@starburst.demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Ken Faiczak cc: freebsd-net@freebsd.org Subject: Re: forged tsecr giving -ve numbers in rtt calculation causing retran 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, 21 Jan 2004 08:50:17 -0000 On Tue, 20 Jan 2004, Richard Wendland wrote: > This does suggest Ken is seeing TSecr messed up in some other way than > simple zeroing. Or working from an old codebase... we'll have to wait for him to respond to find out. KEN! KEN! WHERE ARE YOOOOOO? > I'd expect this to be a pretty rare event, and perhaps my suggestion > that the 64 sec TCPTV_REXMTMAX limit be implemented correctly is a > good enough solution on its own for a rare event. It should certainly > avoid the insane -450000000 tp->t_rxtcur Ken has seen. It's simple to > implement, does what was probably originally intended, and also protects > from bizarre problems with non-timestamp option SRTT calculation. > > Full validation of TSecr would be nice, but perhaps excessive for > something that should not happen. A 64 second RTO may discourage such > strangeness :) > > Richard I think that just ensuring proper capping of the timeout is good enough, the other timestamp issue I was referring to is how it (incorrectly) scales with hz. I think I'll take a look at both of these problems once I catch up on other patches I have in the pipeline. Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 01:11:28 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 50BC816A4CE for ; Wed, 21 Jan 2004 01:11:28 -0800 (PST) Received: from mailgw.servicefactory.se (mailgw.servicefactory.se [192.71.33.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C6D543D1D for ; Wed, 21 Jan 2004 01:11:26 -0800 (PST) (envelope-from xfree@bulow.mine.nu) Received: from ark.servicefactory.se (ark.servicefactory.se [192.71.33.5]) i0L9BNw21225 for ; Wed, 21 Jan 2004 10:11:24 +0100 (CET) Received: from bulow.mine.nu (ark.servicefactory.se [192.71.33.5]) by ark.servicefactory.se (8.12.9/8.12.6) with ESMTP id i0L99xmP063490 for ; Wed, 21 Jan 2004 10:10:00 +0100 (CET) (envelope-from xfree@bulow.mine.nu) Message-ID: <400E4239.7080708@bulow.mine.nu> Date: Wed, 21 Jan 2004 10:11:21 +0100 From: Jonas Bulow User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20031218 X-Accept-Language: en-us, en, sv MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: netgraph: ng_eiface and bpf gives duplicate packets 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, 21 Jan 2004 09:11:28 -0000 Hi, Using bpf with ng_eiface results in duplication of all incoming packets. The duplicated packet is only "visible" on the bpf tap and the ngeth interface works as expected besides this behaviour with bpf. The following examplifies the problem: (pasted from my memory) ngctl -f- < tcpdump: WARNING: ngeth0: no IPv4 address assigned tcpdump: listening on ngeth0 09:53:38.200941 192.168.2.6 > 192.36.125.18: icmp: echo request 09:53:38.200949 192.168.2.6 > 192.36.125.18: icmp: echo request ^C 2 packets received by filter 0 packets dropped by kernel "netstat -i -I ngeth0" shows only one incoming packet. If I attach a ng_tee between the fxp's lower and upper hook (ng_ether) and then attache the eif0 ether hook to correct tap on the tee, I see the smae behaviour but can also se that a tcpdump on fxp0 show only one packet. Any hints on what's wrong? This problem occurs on a late FreeBSD 4.9-STABLE. /jonas From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 01:45:06 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 5F2B316A4CF for ; Wed, 21 Jan 2004 01:45:06 -0800 (PST) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id C3E8D43D53 for ; Wed, 21 Jan 2004 01:44:57 -0800 (PST) (envelope-from dinesh@alphaque.com) Received: (qmail 52960 invoked by uid 0); 21 Jan 2004 09:44:51 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 21 Jan 2004 09:44:51 -0000 Received: from localhost (localhost.alphaque.com [127.0.0.1]) by prophet.alphaque.com (8.12.10/8.12.9) with ESMTP id i0L9i4DQ000711 for ; Wed, 21 Jan 2004 17:44:04 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Wed, 21 Jan 2004 17:44:04 +0800 (MYT) From: Dinesh Nair To: freebsd-net@freebsd.org In-Reply-To: <20040121023111.X312-100000@prophet.alphaque.com> Message-ID: <20040121170911.Y532-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Two ISP lines 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, 21 Jan 2004 09:45:06 -0000 On Wed, 21 Jan 2004, Dinesh Nair wrote: > will do. i'm on 4.9-STABLE. will try the following in this order: > > 1. the multipath patches > 2. security/pf port > 3. rewriting ng_ether to plonk in the new ip address directly into the > mbuf. along with ng_one2many, this should provide the same > functionality. i downloaded the multipath patches, and applied them to 4.9-STABLE. by itself, the kernel didn't compile, and broke in if_ether.c due to the added argument list into rtrequest(). this was easily remedied with an #ifdef, and after a new kernel and new userland route and netstat binaries followed by a reboot, i attempted to test out multipath routing over two interfaces, fxp0 and aue0 (see below). i added a default route using both gateways like so: route add default -gateway 10.1.1.1 -gateway 192.168.0.1 and the routing table (netstat -rn) was as follows: Destination Gateway Flags/ Refs/ Use Netif Expire metric left default UGSc 0 0 aue0 192.168.0.1 10 0 fxp0 *10.1.1.1 10 0 0 aue0 10.1/16 link#8 UC 1 0 aue0 10.1.1.1 00:00:1c:d5:03:63 UHLW 2 2 aue0 1115 127.0.0.1 127.0.0.1 UH 0 362 lo0 192.168.0 link#2 UC 1 0 fxp0 192.168.0.1 00:30:ab:10:6c:0d UHLW 1 0 fxp0 981 i then attempted a tcp connection to an external machine as well as snooping on both interfaces and came to this observation. while this multipath patch does round robin the packets (according to pathmetric) across the two gateways, it does not change the source ip address of the packet to correspond with the interface it went out on. as such, the round robin works this way. the first 10 packets are sent with a src ip of 192.168.0.5 (fxp0's address) out via fxp0. the next 10 are sent still with a src ip of 192.168.0.5 out via aue0. then the cycle repeats with 10 more being sent out via fxp0. this magic number 10 is equivalent to the -pathmetric argument given when creating the route. the default, obviously, is 10. but i digress. this obviously doesn't work for me, since higher upstream from aue0 (ip address 10.1.105.26), the src address of 192.168.0.5 is address translated to a public IP address. the router/natd which does that will obviously not have any address translation maps for 192.168.0.5, and thus silently drop the packet. packets going out fxp0 work the way they should. after all, why shouldn't they ? :) it would however work if both the interfaces were assigned a public ip address, though all this still would do is to round robin outgoing packets, but incoming packets will still come down the same interface (due to the src address not changing). i'm guessing the the picked source ip address depends on the current active gateway for that route, as i've seen the same happen in reverse with a source ip address of 10.1.105.26, the address on aue0. which leads me to deduce that the src address is picked on a per connection basis, depending on the current active gateway, and held for the duration of the connection. thus this does not ensure proper load balancing over both links, even if public ip addresses were used. this does not do what i want to do, i.e. multipath routing in a round robin fashion over x number of interfaces with src ip address changed to the address of the interface the packet goes out on. this would ensure that the reply packets from the destination are routed back in correctly. i'm probably going to experiment with creating a new netgraph node type to do this. looking thru /usr/src/sys/netgraph, and reading the ng_one2many(4) man page, i think it would be possible to base a new node type on one2many which takes input from one interface (hooked to the upper hook of the ether node) and writes to the lower nodes of the interfaces we want to round robin multipath over. in between reading from one and writing to the lower interfaces, i'd need to figure out how to do the following: for outgoing packets: 1. modify the passed in mbuf to change the src ip address of the packet from what it is to what is currently tagged on the chosen outgoing interface. 2. modify the ethernet dest address of the mbuf to point to the next hop router for the chosen outgoing interface for incoming packets: 3. modify the destination ip address on incoming packets to what is currently tagged on the interface hooked to the one hook. conceptually, you'd have just one default route pointing to one interface, and the netgraph nodes would take care of the round robin and packet delivery. i'm new to netgraph, though i think i understand how it works and have read the source in /usr/src/sys/netgraph. i'm absolutely new to mbuf manipulation however. any pointers in this endeavour will be much appreciated, as well as any gotchas i'd need to watch out for. also, would the method i'm proposing above be the way to do it ? Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 02:15:37 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 E222516A4CE for ; Wed, 21 Jan 2004 02:15:37 -0800 (PST) Received: from phantom.cris.net (phantom.cris.net [212.110.130.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7730043D31 for ; Wed, 21 Jan 2004 02:15:34 -0800 (PST) (envelope-from ru@FreeBSD.org.ua) Received: from phantom.cris.net (ru@localhost [127.0.0.1]) by phantom.cris.net (8.12.10/8.12.10) with ESMTP id i0LAG2em010708; Wed, 21 Jan 2004 12:16:02 +0200 (EET) (envelope-from ru@FreeBSD.org.ua) Received: (from ru@localhost) by phantom.cris.net (8.12.10/8.12.10/Submit) id i0LAG24e010703; Wed, 21 Jan 2004 12:16:02 +0200 (EET) (envelope-from ru) Date: Wed, 21 Jan 2004 12:16:02 +0200 From: Ruslan Ermilov To: Jonas Bulow Message-ID: <20040121101602.GI9372@FreeBSD.org.ua> References: <400E4239.7080708@bulow.mine.nu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jt0yj30bxbg11sci" Content-Disposition: inline In-Reply-To: <400E4239.7080708@bulow.mine.nu> User-Agent: Mutt/1.5.5.1i cc: freebsd-net@freebsd.org Subject: Re: netgraph: ng_eiface and bpf gives duplicate packets 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, 21 Jan 2004 10:15:38 -0000 --jt0yj30bxbg11sci Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 21, 2004 at 10:11:21AM +0100, Jonas Bulow wrote: > Using bpf with ng_eiface results in duplication of all incoming packets.= =20 > The duplicated packet is only "visible" on the bpf tap and the ngeth=20 > interface works as expected besides this behaviour with bpf. [...] >=20 > This problem occurs on a late FreeBSD 4.9-STABLE. >=20 Already fixed this problem a month ago in ng_eiface.c,v 1.4.2.6. Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --jt0yj30bxbg11sci Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFADlFiUkv4P6juNwoRAoOYAJ9eiMihc/WASydw1C1DwvkuZFUb9ACeMZeC flaxo7r9rmN02RKv6X9ayTk= =Pfu1 -----END PGP SIGNATURE----- --jt0yj30bxbg11sci-- From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 02:38:28 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 DAAD416A4CE for ; Wed, 21 Jan 2004 02:38:28 -0800 (PST) Received: from phantom.cris.net (phantom.cris.net [212.110.130.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id D047243D2D for ; Wed, 21 Jan 2004 02:38:22 -0800 (PST) (envelope-from ru@FreeBSD.org.ua) Received: from phantom.cris.net (ru@localhost [127.0.0.1]) by phantom.cris.net (8.12.10/8.12.10) with ESMTP id i0LAd5em010971; Wed, 21 Jan 2004 12:39:06 +0200 (EET) (envelope-from ru@FreeBSD.org.ua) Received: (from ru@localhost) by phantom.cris.net (8.12.10/8.12.10/Submit) id i0LAd0AU010966; Wed, 21 Jan 2004 12:39:00 +0200 (EET) (envelope-from ru) Date: Wed, 21 Jan 2004 12:38:55 +0200 From: Ruslan Ermilov To: Vasenin Alexander aka BlackSir Message-ID: <20040121103855.GK9372@FreeBSD.org.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QDIl5R72YNOeCxaP" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.5.1i cc: freebsd-net@freebsd.org Subject: Re: What does it mean: arp_rtrequest: bad gateway value 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, 21 Jan 2004 10:38:29 -0000 --QDIl5R72YNOeCxaP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 21, 2004 at 10:51:18AM +0300, Vasenin Alexander aka BlackSir wr= ote: > Those messages sometimes appears in log. Maybe someone know where to find > what it actually mean? >=20 > Jan 21 02:58:54 inet /kernel: arp_rtrequest: bad gateway value > Jan 21 03:03:54 inet /kernel: arp_rtrequest: bad gateway value > Jan 21 03:08:53 inet /kernel: arp_rtrequest: bad gateway value > Jan 21 03:13:52 inet /kernel: arp_rtrequest: bad gateway value > Jan 21 03:23:51 inet last message repeated 2 times > Jan 21 03:33:48 inet last message repeated 2 times >=20 The ARP entries are stored in the routing table. A valid ARP entry has a link-type gateway address. If your routing table is misconfigured, it's possible that gateway will be something else -- then the kernel whines. An example. Here's a valid ARP entry, that can also be viewed in less verbose form by arp(8): : # route -vn get -host 192.168.0.66 : u: inet 192.168.0.66; u: link ; RTM_GET: Report Metrics: len 164, pid: 0,= seq 1, errno 0, flags: : locks: inits: : sockaddrs: : 192.168.0.66 : route to: 192.168.0.66 : destination: 192.168.0.66 : interface: dc0 : flags: : recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu = expire : 0 0 0 0 0 0 1500 = 1067 :=20 : locks: inits: : sockaddrs: : 192.168.0.66 0.2.2d.1a.6d.df dc0:0.10.a4.c0.c0.45 192.168.0.90 The gateway is 0.2.2d.1a.6d.df, of type AF_LINK. Now I attempt to change it to something else: : # route change -host 192.168.0.66 1.2.3.4 : change host 192.168.0.66: gateway 1.2.3.4 Results in the following from the kernel: : arp_rtrequest: bad gateway 192.168.0.66 (!AF_LINK) This is on 5.2-CURRENT, the message is slightly more informative here. Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --QDIl5R72YNOeCxaP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFADla/Ukv4P6juNwoRAu0yAJ9P3uA+HqccPhGUAGgWuMJ4U4j05ACfZd/r j0p0YURPNkRJG2xTrlyAGhk= =/Dns -----END PGP SIGNATURE----- --QDIl5R72YNOeCxaP-- From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 03:17:01 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 5319116A4CE for ; Wed, 21 Jan 2004 03:17:01 -0800 (PST) Received: from mx2.ibbsonline.com (mx2.ibbsonline.com [67.32.118.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6D9343D46 for ; Wed, 21 Jan 2004 03:16:59 -0800 (PST) (envelope-from sammy.davis@patmedia.net) Received: from localhost (localhost [127.0.0.1]) by mx2.ibbsonline.com (Postfix) with ESMTP id CCEE1FC044 for ; Wed, 21 Jan 2004 06:23:30 -0500 (EST) Received: from mx2.ibbsonline.com ([127.0.0.1]) by localhost (mx2.ibbsonline.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02030-07 for ; Wed, 21 Jan 2004 06:23:30 -0500 (EST) Received: from mail.patmedia.net (mail.patmedia.net [67.32.118.35]) by mx2.ibbsonline.com (Postfix) with ESMTP id 73FAEFC0F1 for ; Wed, 21 Jan 2004 06:23:30 -0500 (EST) Received: from systemsqbja5x7 (host-24-225-161-191.patmedia.net [24.225.161.191]) by mail.patmedia.net (Postfix) with SMTP id 70A124CC49 for ; Wed, 21 Jan 2004 06:13:11 -0500 (EST) Message-ID: <000801c3e010$1773a7e0$bfa1e118@systemsqbja5x7> From: "sammy davis" To: Date: Wed, 21 Jan 2004 06:17:00 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at ibbsonline.com Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: setsockopt IP_ADD_MEMBERSHIP not honored 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, 21 Jan 2004 11:17:01 -0000 Does the behavior described in = http://lists.freebsd.org/pipermail/freebsd-net/2003-October/001726.html = apply to Solaris 8 systems? Also, can you tell me what the difference is = between binding IPADDR_ANY, a local network ip address or multicast ip = address to the socket and should you use the same address for the local = network ip address you join on? thanks. From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 03:21:53 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 AA17B16A4CE for ; Wed, 21 Jan 2004 03:21:53 -0800 (PST) Received: from softservecom.com (mail.softservecom.com [194.44.102.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 282CE43D2F for ; Wed, 21 Jan 2004 03:21:46 -0800 (PST) (envelope-from pam@polynet.lviv.ua) Received: from mail.softservecom.com (root@localhost) by softservecom.com (8.11.6/8.11.6) with SMTP id i0LBLdG25288 for ; Wed, 21 Jan 2004 13:21:39 +0200 Received: from polynet.lviv.ua (digger.softservecom.com [192.168.17.2]) by softservecom.com (8.11.6/8.11.6) with ESMTP id i0LBLZI25258; Wed, 21 Jan 2004 13:21:38 +0200 Message-ID: <400E614F.4060804@polynet.lviv.ua> Date: Wed, 21 Jan 2004 13:23:59 +0200 From: Adrian Pavlykevych User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: uk, en-us, en, pl, ru, de, de-at, de-de, de-li, de-lu, de-ch MIME-Version: 1.0 To: Dinesh Nair References: <20040121170911.Y532-100000@prophet.alphaque.com> In-Reply-To: <20040121170911.Y532-100000@prophet.alphaque.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Two ISP lines 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, 21 Jan 2004 11:21:53 -0000 Dinesh Nair wrote: > while this multipath patch does round robin the packets (according to > pathmetric) across the two gateways, it does not change the source ip > address of the packet to correspond with the interface it went out on. > > as such, the round robin works this way. the first 10 packets are sent > with a src ip of 192.168.0.5 (fxp0's address) out via fxp0. the next 10 > are sent still with a src ip of 192.168.0.5 out via aue0. then the cycle > repeats with 10 more being sent out via fxp0. this magic number 10 is > equivalent to the -pathmetric argument given when creating the route. the > default, obviously, is 10. but i digress. > > this obviously doesn't work for me, since higher upstream from aue0 (ip > address 10.1.105.26), the src address of 192.168.0.5 is address translated > to a public IP address. the router/natd which does that will obviously not > have any address translation maps for 192.168.0.5, and thus silently drop > the packet. packets going out fxp0 work the way they should. after all, > why shouldn't they ? :) > > it would however work if both the interfaces were assigned a public ip > address, though all this still would do is to round robin outgoing > packets, but incoming packets will still come down the same interface (due > to the src address not changing). i'm guessing the the picked source ip > address depends on the current active gateway for that route, as i've seen > the same happen in reverse with a source ip address of 10.1.105.26, the > address on aue0. which leads me to deduce that the src address is picked > on a per connection basis, depending on the current active gateway, and > held for the duration of the connection. thus this does not ensure proper > load balancing over both links, even if public ip addresses were used. > > this does not do what i want to do, i.e. multipath routing in a round > robin fashion over x number of interfaces with src ip address changed to > the address of the interface the packet goes out on. this would ensure > that the reply packets from the destination are routed back in correctly. Hmm, have you accounted for the fact, that if packets of same connection will be distributed in round-robin fashion between several outgoing interfaces and get their src IP "fixed", destination host won't see that as single connection and drop them? If you want to round-robin with two different src IPs on the gateway (host), you have to implement this as functionality of NAT service, which will keep track of connections and send each connection's traffic via _exactly_ one(same) interface. On routing level, IMHO, patch operation, you've described, is exactly following multipath functionality. Issue with return traffic could be resolved with both ISPs announcing route to your IP to the Internet. In this way, return packets will be routed from the destination according to routing decisions take by routers on the path. Regards, -- Adrian Pavlykevych From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 03:57:11 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 18CB116A4CE for ; Wed, 21 Jan 2004 03:57:11 -0800 (PST) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id EF21A43D2D for ; Wed, 21 Jan 2004 03:57:02 -0800 (PST) (envelope-from dinesh@alphaque.com) Received: (qmail 55866 invoked by uid 0); 21 Jan 2004 11:56:59 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 21 Jan 2004 11:56:59 -0000 Received: from localhost (localhost.alphaque.com [127.0.0.1]) by prophet.alphaque.com (8.12.10/8.12.9) with ESMTP id i0LBtZDQ001164; Wed, 21 Jan 2004 19:55:35 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Wed, 21 Jan 2004 19:55:35 +0800 (MYT) From: Dinesh Nair To: Adrian Pavlykevych In-Reply-To: <400E614F.4060804@polynet.lviv.ua> Message-ID: <20040121195028.M532-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: Two ISP lines 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, 21 Jan 2004 11:57:11 -0000 On Wed, 21 Jan 2004, Adrian Pavlykevych wrote: > Hmm, have you accounted for the fact, that if packets of same connection > will be distributed in round-robin fashion between several outgoing > interfaces and get their src IP "fixed", destination host won't see that > as single connection and drop them? you're absolutely right, of course. i realised the same a couple of hours ago, but am still mulling over the idea of a netgraph node instead of the multipath patch. one does get tired eyes from reading too many screenfuls of tcpdump and ng_tee outputs. :) > On routing level, IMHO, patch operation, you've described, is exactly > following multipath functionality. Issue with return traffic could be > resolved with both ISPs announcing route to your IP to the Internet. In > this way, return packets will be routed from the destination according > to routing decisions take by routers on the path. true, but still, if you're behind nat boxes on both interfaces, multipath still wont help. multipath as it stands now only works if both interfaces have public ip addresses. oh well, back to the drawing board. thanx for being a sounding board, adrian. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 05:10:14 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 3633516A4CE for ; Wed, 21 Jan 2004 05:10:14 -0800 (PST) Received: from mail.butovo-online.ru (mail.b-o.ru [212.5.78.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9BF543D2D for ; Wed, 21 Jan 2004 05:10:11 -0800 (PST) (envelope-from resident@b-o.ru) Received: from [192.168.92.185] (helo=192.168.92.185) by mail.butovo-online.ru with esmtp (Exim 4.24) id 1AjIEE-000ETf-VP; Wed, 21 Jan 2004 16:17:06 +0300 Date: Wed, 21 Jan 2004 16:11:30 +0300 From: Andrew Riabtsev X-Mailer: The Bat! (v1.62i) Business X-Priority: 3 (Normal) Message-ID: <185104547741.20040121161130@b-o.ru> To: Dinesh Nair In-Reply-To: <20040121024916.K312-100000@prophet.alphaque.com> References: <20040121024916.K312-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re[2]: netgraph questions on ng_tee, ng_iface, ng_socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Andrew Riabtsev List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2004 13:10:14 -0000 Tuesday, January 20, 2004, 9:51:52 PM, you wrote: DN> On Tue, 20 Jan 2004, Gleb Smirnoff wrote: >> Isn't ng_etf(4) the one you need? DN> ng_etf does filtering, i'm planning on doing round robin IP tranmission, DN> with source IP address set accordingly. see ng_one2many which gives an DN> example for ethernet frames. i want to do the same thing in ng_one2many's DN> EXAMPLE section, but with the added functionality of changing the ip DN> address to match the ip address bound to the interface the packet is going DN> out from. with this ip address, the next hop router(s) wont be able to DN> route the reply back thru the same interface, especially if they're seeing DN> non legit src addressed packets. DN>i presently have two NICs on the box, fxp0 (192.168.0.5) and aue0 DN>(10.1.1.25). both fxp0 and aue0 go out to different ISPs. currently, DN>default route is thru ISP1 on fxp0, i.e. defroute to 192.168.0.1. what i DN>want to do is to round robin outgoing packets across both ISP links, i.e. DN>one packet out on fxp0 then the next out on aue0 and then the next out on DN>fxp0 ad nauseaum. of course, packets going out on fxp0 will have a src DN>address of 192.168.0.5 and packets going out on aue0 will have a src DN>address of 10.1.1.25. Ok, now i undestand :). I think no need to do new virtual interface ng0 and set default route to it as anyway even if u find the way connect together ng_ether and ng_iface src ip wont be overwritten. Here is the one example of solving this problem: 1 let default route be to fxp0 2 conncet fxp0's upper hook to "one" hook of ng_one2many 3 connect lower hooks of fxp0 and aue0 to "many" hooks of ng_one2many 4 u have what u r accept for the overwriting src ip 5 time for uber hack ng_one2many: config parm for ng_one2many: struct ng_one2many_config { u_int32_t xmitAlg; /* how to distribute packets */ u_int32_t failAlg; /* how to detect link failure */ u_char enabledLinks[NG_ONE2MANY_MAX_LINKS]; }; modify array enabledLinks, let it be array of structs per_link_conf { u_char enabled; struct in_addr src; } so finaly: config parm for ng_one2many: struct ng_one2many_config { u_int32_t xmitAlg; /* how to distribute packets */ u_int32_t failAlg; /* how to detect link failure */ struct per_link_conf { u_char enabled; struct in_addr src; } enabledLinks[NG_ONE2MANY_MAX_LINKS]; }; And now befor send out packet throw one of "many" hook just overwrite ip-src address with address given in node->private->enabledLinks[hook->private->numb] or whatever it is called in ng_one2many.c Not many to hack, but it should work i think. 6 and the last: when u get packets from ur default routers they travel throw hooks to the upper hook of fxp0 so kernel thinks that packets arrived directly from fxp0, we know it is not, and as all fair kernels, our kernel check for ethernet dst addr of arrived packets and see that not all packets came from fxp0 (some of them came from aue0, as he has different MAC) and drop it. All u need is just comment or modify this terrible check in ether_demux() in net/if_ethersubr.c. After read man ng_one2many i think this step is not necessary as looks like ng_one2many take care about set right MAC in packet header. Ok, two sleepless nights and u have ur router with 2 defaukt gateways and with unpredictable work. But, anyway this packets will be rejected by remote host as they will be with different addresses (10.* and 192.*). -- Andrew mailto:resident@b-o.ru From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 05:56:51 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 3075E16A4CE for ; Wed, 21 Jan 2004 05:56:51 -0800 (PST) Received: from mailer.cat.co.za (ftp.cat.co.za [196.33.33.51]) by mx1.FreeBSD.org (Postfix) with SMTP id D6E2C43D2D for ; Wed, 21 Jan 2004 05:56:34 -0800 (PST) (envelope-from bradd@cat.co.za) Received: (qmail 30807 invoked from network); 21 Jan 2004 13:55:50 -0000 Received: from unknown (HELO 161?DEMO?400) (196.33.33.52) by mail.cat.co.za with SMTP; 21 Jan 2004 13:55:50 -0000 Content-Type: text/plain; charset="us-ascii" From: Brad du Plessis To: net@freebsd.org Date: Wed, 21 Jan 2004 15:40:57 +0200 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200401211540.57528.bradd@cat.co.za> Subject: RTM_LOSING: Kernel Suspects Partitioning 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, 21 Jan 2004 13:56:51 -0000 Hi, I've tried a NetBSD mailing list to no avail and was hoping that someone = here=20 could help me. I have the following setup: A ----- B =3D=3D=3D=3D=3D=3D C Box A and Box B are on a LAN both on the same subnet. Now from box B I ma= ke a=20 pppd modem dialup to box C. Manual routes are setup on A and C to allow a= =20 connection between A and C. It appears that if while a connection is acti= ve=20 and access to C is momentarily lost, but the ppp interface remains up,=20 packets that were being sent to B from A are redirected to B's default=20 gateway. =20 If that dialup is closed and then reopened a connection to C from A will = fail=20 because all packets to C through B are being routed to B's default gatewa= y.=20 In fact, the only way I'm able to get the connection to work again is eit= her=20 to delete the default gateway on B, do a ping from C to A, or to reboot b= ox=20 B. Now I've looked through the kernel and it appears that in netinet/in_pcb.= c the=20 function "in_losing(inp)" is called when this happens. I've put printouts= in=20 the kernel and found that the route to redirect the packets (which I pres= ume=20 was setup by the kernel) from A to the default gateway has been setup as = a=20 static route. (rt->rt_flags & RTF_DYNAMIC =3D=3D 0) I would've thought that this route should be dynamic, my reasoning being = that=20 the route would then be deleted in in_losing(inp) and packets could then = be=20 redirected through a valid route if one were available. Has anyone come across this before, is this a bug in the kernel? (I assum= e it=20 does the same thing in FreeBSD) Any help would be most appreciated! Thanks, Brad From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 06:21:42 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 AB7D116A555 for ; Wed, 21 Jan 2004 06:21:41 -0800 (PST) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A7B143D55 for ; Wed, 21 Jan 2004 06:21:36 -0800 (PST) (envelope-from kfaiczak@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Wed, 21 Jan 2004 09:21:30 -0500 Message-ID: From: Ken Faiczak To: 'Mike Silbersack' , richard@wendland.org.uk Date: Wed, 21 Jan 2004 09:21:29 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: freebsd-net@freebsd.org Subject: RE: forged tsecr giving -ve numbers in rtt calculation causing re tran 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, 21 Jan 2004 14:21:42 -0000 it is on 4.7 since that is what our product is using but the same code still exists in 5.2 (we're actively migrating our product there) We definitely are seeing incorrect Tsecr returned (ie not 0, but tsecr > ticks, thus the -ve result) The question was more that it could be a problem in general since the checks are in place to make sure its between the min and max but the results end up outside that range and the question of whether this could be used as some sort of DoS attack since it causes significant bandwidth utilization that would not otherwise occur. And then even if later in the connection it sends proper tsecr the smoothing causes it to go nowhere fast (from -450M). In our case hz = 2500 so the retransmit is -ve so it happens at the next tick which is 400us if the other side does not ack that fast.. Disabling 1323 is not what we want as these do happen, but are not that common and we want it on all other connections. > -----Original Message----- > From: Mike Silbersack [mailto:silby@silby.com] > Sent: Wednesday, January 21, 2004 3:50 AM > To: richard@wendland.org.uk > Cc: Ken Faiczak; freebsd-net@freebsd.org > Subject: Re: forged tsecr giving -ve numbers in rtt > calculation causing > retran > > > > On Tue, 20 Jan 2004, Richard Wendland wrote: > > > This does suggest Ken is seeing TSecr messed up in some > other way than > > simple zeroing. > > Or working from an old codebase... we'll have to wait for him > to respond > to find out. KEN! KEN! WHERE ARE YOOOOOO? > > > I'd expect this to be a pretty rare event, and perhaps my suggestion > > that the 64 sec TCPTV_REXMTMAX limit be implemented correctly is a > > good enough solution on its own for a rare event. It > should certainly > > avoid the insane -450000000 tp->t_rxtcur Ken has seen. > It's simple to > > implement, does what was probably originally intended, and > also protects > > from bizarre problems with non-timestamp option SRTT calculation. > > > > Full validation of TSecr would be nice, but perhaps excessive for > > something that should not happen. A 64 second RTO may > discourage such > > strangeness :) > > > > Richard > > I think that just ensuring proper capping of the timeout is > good enough, > the other timestamp issue I was referring to is how it (incorrectly) > scales with hz. I think I'll take a look at both of these > problems once I > catch up on other patches I have in the pipeline. > > Mike "Silby" Silbersack > From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 06:25:58 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 E100716A4CE for ; Wed, 21 Jan 2004 06:25:58 -0800 (PST) Received: from mail.butovo-online.ru (mail.b-o.ru [212.5.78.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7233043D2D for ; Wed, 21 Jan 2004 06:25:57 -0800 (PST) (envelope-from resident@b-o.ru) Received: from [192.168.92.185] (helo=192.168.92.185) by mail.butovo-online.ru with esmtp (Exim 4.24) id 1AjJPZ-000EX1-EM for freebsd-net@freebsd.org; Wed, 21 Jan 2004 17:32:53 +0300 Date: Wed, 21 Jan 2004 17:27:22 +0300 From: Andrew Riabtsev X-Mailer: The Bat! (v1.62i) Business X-Priority: 3 (Normal) Message-ID: <172109099707.20040121172722@b-o.ru> To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: netgraph: bridge with fwd and divert X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Andrew Riabtsev List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2004 14:25:59 -0000 Hi, All I'm trying to let my FreeBSD 4.9 box, working as bridge, divert and fwd bridged packets. As i undestand it is not realized in FreeBSD 4.9. I was thinking about to do it (realize), but im too lazy and when i see this huge amount of work i start thinking :) Befor i continue my work i just want u to look at what come on my mind and tell me what you think about it. Maybe i missed something and it wont work and so on... Thats came on my mind. If we cant realize fwd and divert on bridged packets lets just send packets we need to layer 3 and let system fwd and divert them as other layer 3 packets. And here is the plan: for example, we have box with 2 ethernet devices: fxp0 and fxp1, have one ip 64.64.64.64/24 on fxp0 and default gw to 64.64.64.1 Lets make the following netgraph: +------+ lower +---------+ left +---------------+ right +------+ | fxp1 |<----->|ng_bridge|<----->|ng_ether_divert|<------->| fxp0 | +------+ link0 +---------+ link1 +---------------+ lower +------+ /\ /\ || upper || +---------------------+ divert point is that ng_ether_divert (the one im working on) analyze packets coming from left and right hooks and checks set of rules if it should be send to divert hook, if no packet sends to left hook if come for right and to the right if come from left. And so with packets came from divert hook if there is a rule to send packet to the right hook packet sends if no rule - to the left. And rule format is src_ip, dst_ip, masks, proto, src_port, dst_port, some flags for NOT extentions in address, ports and poroto, from_hook (came from), to_hook (should be send to). So how it should work: if no rules everything works just like bridge should work with ng_bridge, but when adding the following rules: ip from 192.168.0.0/16 to 0.0.0.0/0 via left --> divert (packets from private network sends to layer 3 for divert and/or fwd in kernel using ipfw) ip from 0.0.0.0/0 to 64.64.64.64/32 from left -->divert ip from 0.0.0.0/0 to 64.64.64.64/32 from right -->divert (let box get packets directed to it) ip from 0.0.0.0/0 to ip_u_want_to_be_send from divert --->hook_on_what_that_ip_should_be (ether route to other hosts in local ethernet and gateways on other known local routes (layer3)) ip from 0.0.0.0/0 to 0.0.0.0/0 from divert --->right (default ether gateway :) just send other packets to the interfase where default (layer3) gateway placed) -- With best regards, Andrew mailto:resident@b-o.ru From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 07:10:12 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 CAB4416A4CE for ; Wed, 21 Jan 2004 07:10:12 -0800 (PST) Received: from mx.sat.corp.rackspace.com (mx.sat.corp.rackspace.com [64.39.1.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C64643D45 for ; Wed, 21 Jan 2004 07:10:02 -0800 (PST) (envelope-from amason@rackspace.com) Received: from mail.rackspace.com (mail.rackspace.com [64.39.2.181]) i0LF7s4w023873 for ; Wed, 21 Jan 2004 09:07:54 -0600 Received: from [10.1.101.24] (office101-24.sat.rackspace.com [10.1.101.24]) by mail.rackspace.com (8.12.10/8.12.10) with ESMTP id i0LF9q32011118 for ; Wed, 21 Jan 2004 09:09:52 -0600 From: Art Mason To: freebsd-net@freebsd.org Content-Type: text/plain Organization: Rackspace Managed Hosting Message-Id: <1074697963.32768.4.camel@mizar.rackspace.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 21 Jan 2004 09:12:43 -0600 Content-Transfer-Encoding: 7bit X-MailScanner: Dd6rvCg9: Found to be clean Subject: PF installation on 5.2-RELEASE 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, 21 Jan 2004 15:10:12 -0000 Hello, My sincerest apologies if this isn't the correct list to post this question to, but I was wondering if anyone has any guidelines/procedures to follow regarding the correct installation method for PF on FreeBSD 5.2-RELEASE. I know of its existence in ports/security, but was wondering if there are any additional kernel compilation options or sysctl variables required to get it, along w/ ALTQ, up and running properly on a fresh install. Many thanks in advance, -- Art Mason Rackspace Managed Hosting amason@rackspace.com From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 07:20:33 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 E642A16A4CE for ; Wed, 21 Jan 2004 07:20:33 -0800 (PST) Received: from redqueen.elvandar.org (cust.94.120.adsl.cistron.nl [195.64.94.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 122E143D1F for ; Wed, 21 Jan 2004 07:20:30 -0800 (PST) (envelope-from remko@elvandar.org) From: "Remko Lodder" To: "Freebsd-Net@Freebsd. Org" Date: Wed, 21 Jan 2004 16:20:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) Importance: Normal In-Reply-To: <20040121151040.E924916@mail.elvandar.org> X-Virus-Scanned: by amavisd-new at elvandar.org Message-Id: <20040121152028.275D52B4D82@redqueen.elvandar.org> Subject: RE: [Freebsd-net] PF installation on 5.2-RELEASE 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, 21 Jan 2004 15:20:34 -0000 from pkg-message which lives in /usr/ports/security/pf/ To use pf, please follow these steps: 1. Add kernel options into your kernel config file and recompile kernel: device bpf options PFIL_HOOKS options RANDOM_IP_ID 2. Please set the following variables in /etc/rc.conf according to your needs: pf_enable="Yes" pf_logd="Yes" pf_conf="%%PREFIX%%/etc/pf.conf" 3. Check %%PREFIX%%/etc/rc.d/pf.sh, it is the startup script for pf! --> Makefile snippet .if !defined(WITH_ALTQ) || (${WITH_ALTQ} != "yes") pre-fetch: @${ECHO_MSG} "=======================================================" @${ECHO_MSG} "* If you have ALTQ support from: *" @${ECHO_MSG} "* http://www.nipsi.de/altq/index.html or *" @${ECHO_MSG} "* http://www.rofug.ro/projects/freebsd-altq/ *" @${ECHO_MSG} "* You can define WITH_ALTQ=yes to make use of it *" @${ECHO_MSG} "* Please define SYS_ALTQ to point to the patched src *" @${ECHO_MSG} "* *" @${ECHO_MSG} "* e.g.: make WITH_ALTQ=yes SYS_ALTQ=/usr/src/sys.altq *" @${ECHO_MSG} "* *" @${ECHO_MSG} "=======================================================" @sleep 2 .endif /snip Does that fill in the blanks? Cheers -- Kind regards, Remko Lodder Elvandar.org/DSINet.org www.mostly-harmless.nl Dutch community for helping newcomers on the hackerscene -----Oorspronkelijk bericht----- Van: freebsd-net-bounces@lists.elvandar.org [mailto:freebsd-net-bounces@lists.elvandar.org]Namens Art Mason Verzonden: woensdag 21 januari 2004 16:13 Aan: freebsd-net@freebsd.org Onderwerp: [Freebsd-net] PF installation on 5.2-RELEASE Hello, My sincerest apologies if this isn't the correct list to post this question to, but I was wondering if anyone has any guidelines/procedures to follow regarding the correct installation method for PF on FreeBSD 5.2-RELEASE. I know of its existence in ports/security, but was wondering if there are any additional kernel compilation options or sysctl variables required to get it, along w/ ALTQ, up and running properly on a fresh install. Many thanks in advance, -- Art Mason Rackspace Managed Hosting amason@rackspace.com _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" _______________________________________________ Freebsd-net mailing list Freebsd-net@lists.elvandar.org http://lists.elvandar.org/mailman/listinfo/freebsd-net From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 07:51:50 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 645CD16A4CE for ; Wed, 21 Jan 2004 07:51:50 -0800 (PST) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id 97BD343D1F for ; Wed, 21 Jan 2004 07:51:45 -0800 (PST) (envelope-from dinesh@alphaque.com) Received: (qmail 62014 invoked by uid 0); 21 Jan 2004 15:51:39 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 21 Jan 2004 15:51:39 -0000 Received: from localhost (localhost.alphaque.com [127.0.0.1]) by prophet.alphaque.com (8.12.10/8.12.9) with ESMTP id i0LFpQDQ001384; Wed, 21 Jan 2004 23:51:26 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Wed, 21 Jan 2004 23:51:26 +0800 (MYT) From: Dinesh Nair To: Andrew Riabtsev In-Reply-To: <185104547741.20040121161130@b-o.ru> Message-ID: <20040121234818.U532-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re[2]: netgraph questions on ng_tee, ng_iface, ng_socket 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, 21 Jan 2004 15:51:50 -0000 On Wed, 21 Jan 2004, Andrew Riabtsev wrote: > 1 let default route be to fxp0 > 2 conncet fxp0's upper hook to "one" hook of ng_one2many > 3 connect lower hooks of fxp0 and aue0 to "many" hooks of ng_one2many > 4 u have what u r accept for the overwriting src ip > 5 time for uber hack ng_one2many: i had initially tried this, without modifying ng_one2many, but like adrian pointed out in an earlier email, i wasnt checking if the destination host was receiving the packets ok. it was exploratory alright. :) > kernels, our kernel check for ethernet dst addr of arrived packets and > see that not all packets came from fxp0 (some of them came from aue0, > as he has different MAC) and drop it. All u need is just comment or > modify this terrible check in ether_demux() in net/if_ethersubr.c. not really necessary. you can set the aue0 and other interfaces connected to the many hooks to be promiscous and to not overwrite the ethernet address. this, of course, only works on bonding the links for same segment traffic. the bottleneck will still be the ISP thru which it goes out. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 07:55:43 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 EF0D716A4CE for ; Wed, 21 Jan 2004 07:55:42 -0800 (PST) Received: from mx.sat.corp.rackspace.com (mx.sat.corp.rackspace.com [64.39.1.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 458F943D31 for ; Wed, 21 Jan 2004 07:55:39 -0800 (PST) (envelope-from amason@rackspace.com) Received: from mail.rackspace.com (mail.rackspace.com [64.39.2.181]) i0LFrW4w030131 for ; Wed, 21 Jan 2004 09:53:32 -0600 Received: from [10.1.101.24] (office101-24.sat.rackspace.com [10.1.101.24]) by mail.rackspace.com (8.12.10/8.12.10) with ESMTP id i0LFtW32024221 for ; Wed, 21 Jan 2004 09:55:32 -0600 From: Art Mason To: "Freebsd-Net@Freebsd. Org" In-Reply-To: <20040121152028.275D52B4D82@redqueen.elvandar.org> References: <20040121152028.275D52B4D82@redqueen.elvandar.org> Content-Type: text/plain Organization: Rackspace Managed Hosting Message-Id: <1074700702.32768.14.camel@mizar.rackspace.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 21 Jan 2004 09:58:23 -0600 Content-Transfer-Encoding: 7bit X-MailScanner: Dd6rvCg9: Found to be clean Subject: RE: [Freebsd-net] PF installation on 5.2-RELEASE 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, 21 Jan 2004 15:55:43 -0000 Yes, indeed, many thanks for the quick response. I had read through the makefile, but wasn't sure if there were any additional settings that I should take into consideration. On that note, does anyone have any experience running PF under 5.2-RELEASE in a production environment, especially in conjunction w/ ALTQ? I'm just curious, because I've really taken a liking to PF under OpenBSD and really like the ALTQ integration, especially in regards to upstream traffic shaping. Does anyone have any experience with such implementations under 5.2-RELEASE. Thanks again in advance, On Wed, 2004-01-21 at 09:20, Remko Lodder wrote: > from pkg-message which lives in /usr/ports/security/pf/ > > To use pf, please follow these steps: > > 1. Add kernel options into your kernel config file and recompile kernel: > > device bpf > options PFIL_HOOKS > options RANDOM_IP_ID > > 2. Please set the following variables in /etc/rc.conf according to your > needs: > > pf_enable="Yes" > pf_logd="Yes" > pf_conf="%%PREFIX%%/etc/pf.conf" > > 3. Check %%PREFIX%%/etc/rc.d/pf.sh, it is the startup script for pf! > > --> Makefile snippet > > .if !defined(WITH_ALTQ) || (${WITH_ALTQ} != "yes") > pre-fetch: > @${ECHO_MSG} "=======================================================" > @${ECHO_MSG} "* If you have ALTQ support from: *" > @${ECHO_MSG} "* http://www.nipsi.de/altq/index.html or *" > @${ECHO_MSG} "* http://www.rofug.ro/projects/freebsd-altq/ *" > @${ECHO_MSG} "* You can define WITH_ALTQ=yes to make use of it *" > @${ECHO_MSG} "* Please define SYS_ALTQ to point to the patched src *" > @${ECHO_MSG} "* *" > @${ECHO_MSG} "* e.g.: make WITH_ALTQ=yes SYS_ALTQ=/usr/src/sys.altq *" > @${ECHO_MSG} "* *" > @${ECHO_MSG} "=======================================================" > @sleep 2 > .endif > > /snip > > Does that fill in the blanks? Cheers > > > > -- > > Kind regards, > > Remko Lodder > Elvandar.org/DSINet.org > www.mostly-harmless.nl Dutch community for helping newcomers on the > hackerscene > > -----Oorspronkelijk bericht----- > Van: freebsd-net-bounces@lists.elvandar.org > [mailto:freebsd-net-bounces@lists.elvandar.org]Namens Art Mason > Verzonden: woensdag 21 januari 2004 16:13 > Aan: freebsd-net@freebsd.org > Onderwerp: [Freebsd-net] PF installation on 5.2-RELEASE > > > Hello, > > My sincerest apologies if this isn't the correct list to post this > question to, but I was wondering if anyone has any guidelines/procedures > to follow regarding the correct installation method for PF on FreeBSD > 5.2-RELEASE. I know of its existence in ports/security, but was > wondering if there are any additional kernel compilation options or > sysctl variables required to get it, along w/ ALTQ, up and running > properly on a fresh install. > > Many thanks in advance, > > -- > Art Mason > Rackspace Managed Hosting > amason@rackspace.com > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ > Freebsd-net mailing list > Freebsd-net@lists.elvandar.org > http://lists.elvandar.org/mailman/listinfo/freebsd-net > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" -- Art Mason Technical Support - Team F Rackspace Managed Hosting (800) 961-4454 ext. 1223 amason@rackspace.com From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 08:11:33 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 2F44B16A4D0; Wed, 21 Jan 2004 08:11:33 -0800 (PST) Received: from TheWorld.com (pcls4-e.std.com [192.74.137.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 256D143D2F; Wed, 21 Jan 2004 08:11:32 -0800 (PST) (envelope-from kwc@shell.TheWorld.com) Received: from shell.TheWorld.com (pip1-5.std.com [192.74.137.185]) by TheWorld.com (8.12.8p1/8.12.8) with ESMTP id i0LGBUiW000912; Wed, 21 Jan 2004 11:11:30 -0500 Received: (from kwc@localhost) by shell.TheWorld.com (8.9.3/8.9.3) id LAA16954677; Wed, 21 Jan 2004 11:11:25 -0500 (EST) Date: Wed, 21 Jan 2004 11:11:25 -0500 (EST) From: Kenneth W Cochran Message-Id: <200401211611.LAA16954677@shell.TheWorld.com> To: freebsd-hardware@freebsd.org, freebsd-net@freebsd.org Subject: Troubleshooting network card/link 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, 21 Jan 2004 16:11:33 -0000 Hello: Is there anything for FreeBSD that's analogous to Linux's "mii-diag" program? I'm (still) trying to troubleshoot a card's (mis)communication with a router. For background, see http://docs.freebsd.org/cgi/mid.cgi?200401120237.VAA15119655 Thanks, -kc From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 08:39:04 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 D226C16A4CE for ; Wed, 21 Jan 2004 08:39:04 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5953243D4C for ; Wed, 21 Jan 2004 08:38:43 -0800 (PST) (envelope-from max@love2party.net) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AjLNK-0002uL-00 for freebsd-net@freebsd.org; Wed, 21 Jan 2004 17:38:42 +0100 Received: from [80.131.148.180] (helo=vampire.homelinux.org) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1AjLNK-0001ub-00 for freebsd-net@freebsd.org; Wed, 21 Jan 2004 17:38:42 +0100 Received: (qmail 65009 invoked from network); 21 Jan 2004 16:43:00 -0000 Received: from unknown (HELO fbsd52.laiers.local) (192.168.4.88) by 192.168.4.1 with SMTP; 21 Jan 2004 16:43:00 -0000 From: Max Laier To: Art Mason , "Freebsd-Net@Freebsd. Org" Date: Wed, 21 Jan 2004 17:38:36 +0100 User-Agent: KMail/1.5.4 References: <20040121152028.275D52B4D82@redqueen.elvandar.org> <1074700702.32768.14.camel@mizar.rackspace.com> In-Reply-To: <1074700702.32768.14.camel@mizar.rackspace.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401211738.36532.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:e28873fbe4dbe612ce62ab869898ff08 Subject: Re: [Freebsd-net] PF installation on 5.2-RELEASE 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, 21 Jan 2004 16:39:05 -0000 On Wednesday 21 January 2004 16:58, Art Mason wrote: > Yes, indeed, many thanks for the quick response. I had read through > the makefile, but wasn't sure if there were any additional settings > that I should take into consideration. On that note, does anyone have > any experience running PF under 5.2-RELEASE in a production > environment, especially in conjunction w/ ALTQ? I'm just curious, > because I've really taken a liking to PF under OpenBSD and really like > the ALTQ integration, especially in regards to upstream traffic > shaping. Does anyone have any experience with such implementations > under 5.2-RELEASE. > If you will use pf on a dail-up line, which gets a dynamic IP via dhcp or similar means, or if you are _very_ concerned about secuirty, you might want to take a look at the "patches" directory (cd /usr/ports/security/pf; make patch; cd work/pf_freebsd_2.02/patches/; less README) to learn about additonal tweaks ("(if_name)" syntax, and bpf security). pf alone has proven stable on a large number of FreeBSD installations (SMP, UP, 64bit ...) among them very busy sites. ALTQ lacks real-life tests for some of the "supported" NICs (as none of the ALTQ patchset developers has access to a big testlab). fxp, rl, tun and dc are well tested (by either Adrian, Pyun or myself) ... if you have another card reports are _very_ welcome! Just write a mail and we will spam you with patchsets until it works ;) -- Best regards, | max@love2party.net Max Laier | ICQ #67774661 http://pf4freebsd.love2party.net/ | mlaier@EFnet From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 09:16:59 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 62A9C16A4CE; Wed, 21 Jan 2004 09:16:59 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D79843D1D; Wed, 21 Jan 2004 09:16:58 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i0LHGq5P018692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jan 2004 12:16:52 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i0LHGlbu099388; Wed, 21 Jan 2004 12:16:47 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16398.46079.127565.221708@grasshopper.cs.duke.edu> Date: Wed, 21 Jan 2004 12:16:47 -0500 (EST) To: Andre Oppermann In-Reply-To: <400D9271.1259CBC8@freebsd.org> References: <16397.36782.415899.626311@grasshopper.cs.duke.edu> <400D9271.1259CBC8@freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-net@freebsd.org cc: dab@cray.com Subject: Re: tcp mss MCLBYTES restriction 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, 21 Jan 2004 17:16:59 -0000 Andre Oppermann writes: > > Could you run some bechmarks with the current MCLBYTES rounding > and without it on 100Mbit 1.5kMTU and GigE with 9k MTU? David Borman is totally right. Clipping the mss is really worth it, especially with zero-copy sockets. Forget I said anything. Here is some data I just took.. Send and receiver are 3GHz P4s. Test is netperf -- -S131072 -s131072. Sender is running current as of Saturday. Receiver is running 4.9-Release. "em" is Intel(R) PRO/1000 Network Connection, Version - 1.7.19 "myri" is a M3F2-PCIXE-2. (4Gb/s). NIC mtu BW %cpu mss_truncate zero_copy (bytes) (Mb/s) ---- ------ ----- ---- ----- ------ em 16114 727 12.8 0 0 em 16114 730 15.2 1 0 em 16114 728 12.4 0 1 em 16114 743 7.3 1 1 em 9000 870 19.2 0 0 em 9000 900 21.6 1 0 em 9000 867 18.2 0 1 em 9000 845 8.9 1 1 myri 9000 1972 69.0 0 0 myri 9000 2312 68.6 1 0 myri 9000 2609 56.3 0 1 myri 9000 3009 52.3 1 1 Drew From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 12:06:23 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 9CF4716A4CE for ; Wed, 21 Jan 2004 12:06:23 -0800 (PST) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id 3B0BA43D49 for ; Wed, 21 Jan 2004 12:06:19 -0800 (PST) (envelope-from dinesh@alphaque.com) Received: (qmail 68169 invoked by uid 0); 21 Jan 2004 20:06:17 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 21 Jan 2004 20:06:17 -0000 Received: from localhost (localhost.alphaque.com [127.0.0.1]) by prophet.alphaque.com (8.12.10/8.12.9) with ESMTP id i0LJ9IDQ001899; Thu, 22 Jan 2004 03:09:18 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Thu, 22 Jan 2004 03:09:18 +0800 (MYT) From: Dinesh Nair To: Andrew Riabtsev In-Reply-To: <185104547741.20040121161130@b-o.ru> Message-ID: <20040122030427.S532-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re[2]: netgraph questions on ng_tee, ng_iface, ng_socket 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, 21 Jan 2004 20:06:23 -0000 On Wed, 21 Jan 2004, Andrew Riabtsev wrote: > And now befor send out packet throw one of "many" hook just overwrite > ip-src address with address given in > node->private->enabledLinks[hook->private->numb] or whatever it is > called in ng_one2many.c you'd also need to overwrite the destination ethernet address with the ethernet address of the next hop router for that interface. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 13:02: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 2317A16A4CE; Wed, 21 Jan 2004 13:02:02 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id D36E243D68; Wed, 21 Jan 2004 13:02:00 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.3) with ESMTP id i0LL1qaT024167; Wed, 21 Jan 2004 13:01:52 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i0LL1qPZ024164; Wed, 21 Jan 2004 13:01:52 -0800 Date: Wed, 21 Jan 2004 13:01:52 -0800 From: Brooks Davis To: net@freebsd.org Message-ID: <20040121210152.GA21939@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: brian@freebsd.org Subject: minor bug in user ppp? 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, 21 Jan 2004 21:02:02 -0000 --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm reviewing uses of sdl->sdl_data so see if I can make a minor change to the way that data is stored and I noticed what I think is a bug in the userland ppp implementation. It looks like it's trying to print the interface name from the sdl, but the precision specifier is wrong. A simpiler printf a little ways above this one appears to be correct. I'm I correct that this is a bug? See the patch below. -- Brooks Index: usr.sbin/ppp/arp.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/cvs/src/usr.sbin/ppp/arp.c,v retrieving revision 1.44 diff -u -p -r1.44 arp.c --- usr.sbin/ppp/arp.c 16 Jan 2002 14:03:51 -0000 1.44 +++ usr.sbin/ppp/arp.c 21 Jan 2004 20:49:42 -0000 @@ -302,7 +302,7 @@ arp_EtherAddr(int s, struct in_addr ipad if ((ifa->sin_addr.s_addr & netmask->sin_addr.s_addr) =3D=3D (ipaddr.s_addr & netmask->sin_addr.s_addr)) { log_Printf(verbose ? LogPHASE : LogDEBUG, - "Found interface %.*s for %s\n", dl->sdl_alen, + "Found interface %.*s for %s\n", dl->sdl_nlen, dl->sdl_data, inet_ntoa(ipaddr)); memcpy(hwaddr, dl, dl->sdl_len); free(buf); --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFADuimXY6L6fI4GtQRAn9lAKCzClKupAeFZlWJsTtVAkCUualMMwCfSBsp Y+g+LYYAIz6uM7dc8bb9xAo= =izvY -----END PGP SIGNATURE----- --5vNYLRcllDrimb99-- From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 13:49:19 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 04BA716A4CE; Wed, 21 Jan 2004 13:49:19 -0800 (PST) Received: from Awfulhak.org (awfulhak.demon.co.uk [80.177.173.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13C7243D1F; Wed, 21 Jan 2004 13:49:17 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from mail.lan.Awfulhak.org (brian@dev.lan.Awfulhak.org [172.16.0.5]) by Awfulhak.org (8.12.10/8.12.10) with SMTP id i0LLnAoC073204; Wed, 21 Jan 2004 21:49:10 GMT (envelope-from brian@Awfulhak.org) Date: Wed, 21 Jan 2004 21:49:10 +0000 From: Brian Somers To: Brooks Davis Message-Id: <20040121214910.23764671@dev.lan.Awfulhak.org> In-Reply-To: <20040121210152.GA21939@Odin.AC.HMC.Edu> References: <20040121210152.GA21939@Odin.AC.HMC.Edu> X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.61 X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on gw.lan.Awfulhak.org cc: brian@freebsd.org cc: net@freebsd.org Subject: Re: minor bug in user ppp? 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, 21 Jan 2004 21:49:19 -0000 Yep, that's a bug... feel free to apply the patch. Cheers. On Wed, 21 Jan 2004 13:01:52 -0800, Brooks Davis wrote: > I'm reviewing uses of sdl->sdl_data so see if I can make a minor change > to the way that data is stored and I noticed what I think is a bug in > the userland ppp implementation. It looks like it's trying to print the > interface name from the sdl, but the precision specifier is wrong. A > simpiler printf a little ways above this one appears to be correct. I'm > I correct that this is a bug? See the patch below. > > -- Brooks > > Index: usr.sbin/ppp/arp.c > =================================================================== > RCS file: /usr/cvs/src/usr.sbin/ppp/arp.c,v > retrieving revision 1.44 > diff -u -p -r1.44 arp.c > --- usr.sbin/ppp/arp.c 16 Jan 2002 14:03:51 -0000 1.44 > +++ usr.sbin/ppp/arp.c 21 Jan 2004 20:49:42 -0000 > @@ -302,7 +302,7 @@ arp_EtherAddr(int s, struct in_addr ipad > if ((ifa->sin_addr.s_addr & netmask->sin_addr.s_addr) == > (ipaddr.s_addr & netmask->sin_addr.s_addr)) { > log_Printf(verbose ? LogPHASE : LogDEBUG, > - "Found interface %.*s for %s\n", dl->sdl_alen, > + "Found interface %.*s for %s\n", dl->sdl_nlen, > dl->sdl_data, inet_ntoa(ipaddr)); > memcpy(hwaddr, dl, dl->sdl_len); > free(buf); > > -- > Any statement of the form "X is the one, true Y" is FALSE. > PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 > -- Brian Don't _EVER_ lose your sense of humour ! From owner-freebsd-net@FreeBSD.ORG Wed Jan 21 23:27:45 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 377D516A4CE for ; Wed, 21 Jan 2004 23:27:45 -0800 (PST) Received: from mailout.informatik.tu-muenchen.de (mailout.informatik.tu-muenchen.de [131.159.0.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AAA043D49 for ; Wed, 21 Jan 2004 23:27:43 -0800 (PST) (envelope-from langd@informatik.tu-muenchen.de) Date: Thu, 22 Jan 2004 08:27:42 +0100 From: Daniel Lang To: freebsd-net@freebsd.org Message-ID: <20040122072741.GB62252@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y+ User-Agent: Mutt/1.5.1i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de Subject: dhcp setup advice 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: Thu, 22 Jan 2004 07:27:45 -0000 Hi, I'm currently chewing on a problem how to setup DHCP properly the way I want it. My notebook computer (running 5.2-CURRENT) has a fxp0 and a wi0 (wavelan) interface. WaveLan ist available most of the times. Now, what I would like it to do is: 1. If fxp0 link is up, configure fxp0 interface, get DNS and default router from dhcp via fxp0. 2. If fxp0 link falls down, configure wi0 now, get DNS and default router from dhcp via wi0 3. If fxp0 is up again, do 1. This can be simplified a little bit, since each interface can stay configured and DNS servers are the same, so what it really needs to do, is: - fetch default route from fxp0 is fxp0 is available - else fetch default route from wi0 I know, that dhclient can bind to more than one interface and dhclient has the capability to detect link up/link down. Further it appears, that its possible call a script on certain events (so maybe I can call a script on link/up/down events on any interface). What I don't know is, how to tell dhclient to fetch a new default route from a certain interface. I do not like to kill dhclient and start it again (well, possibly that's the only solution, but if not, I would prefer another way). Even the documentation of the omshell interface did not help me much in that matter. Any help appreciated. Thanks, Daniel -- IRCnet: Mr-Spock - Work is for people, who don't surf - Daniel Lang * dl@leo.org * +49 89 289 18532 * http://www.leo.org/~dl/ From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 03:13:50 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 67C1416A4CE for ; Thu, 22 Jan 2004 03:13:50 -0800 (PST) Received: from web21510.mail.yahoo.com (web21510.mail.yahoo.com [66.163.169.59]) by mx1.FreeBSD.org (Postfix) with SMTP id 912B843D2D for ; Thu, 22 Jan 2004 03:13:49 -0800 (PST) (envelope-from actionarnie@yahoo.com) Message-ID: <20040122111349.46405.qmail@web21510.mail.yahoo.com> Received: from [196.33.33.52] by web21510.mail.yahoo.com via HTTP; Thu, 22 Jan 2004 03:13:49 PST Date: Thu, 22 Jan 2004 03:13:49 -0800 (PST) From: Arnie Schwartz To: Brad du Plessis In-Reply-To: <200401221247.50332.bradd@cat.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: net@freebsd.org Subject: Re: RTM_LOSING: Kernel Suspects Partitioning 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: Thu, 22 Jan 2004 11:13:50 -0000 > Has anyone come across this before, is this a bug in > the kernel? (I assume it > does the same thing in FreeBSD) Not sure if this is a bug, but doing the following shows a similar problem. With boxes A and B as you mentioned; Create a ppp interface manually on B using IP's like 10.1.1.1 -> 10.1.1.2. Then setup a route on A to get to 10.1.1.2 via B's ethernet IP address. If you now do a traceroute to 10.1.1.2 on A, it succeeds using B's IP as a gateway. Now delete the ppp interface on B, and try the traceroute again, you'll notice that it now uses B's default gateway. Create the ppp interface on B the same as before, and do the traceroute on A again, you'll find that it will still use the default gateway, even though the route to 10.1.1.2 via 10.1.1.1 was setup by adding the ppp interface. This looks similar to your problem, could be a bug? Arnie __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 05:23:34 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 A2E1516A4CE for ; Thu, 22 Jan 2004 05:23:34 -0800 (PST) Received: from server.rucus.ru.ac.za (server.rucus.ru.ac.za [146.231.115.1]) by mx1.FreeBSD.org (Postfix) with SMTP id 5F47343D80 for ; Thu, 22 Jan 2004 05:23:20 -0800 (PST) (envelope-from guy@rucus.ru.ac.za) Received: (qmail 22438 invoked from network); 22 Jan 2004 13:23:18 -0000 Received: from shell-em0.rucus.ru.ac.za (guy@10.0.0.1) by server-em0.rucus.ru.ac.za with QMQP; 22 Jan 2004 13:23:18 -0000 Date: Thu, 22 Jan 2004 15:23:18 +0200 From: Guy Antony Halse To: freebsd-net@freebsd.org Message-ID: <20040122132318.GA40533@rucus.ru.ac.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Fwd: DHCP and multiple vlans 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: Thu, 22 Jan 2004 13:23:34 -0000 I'm trying to configure a FreeBSD 5.1-RELEASE system to act as the default gateway for several virtual lans. I've got two NICs in the box, one which supplies the uplink, and one which has about 40 vlan(4) vlans on it. I was trying to run isc-dhcp3's dhcrelay to relay DHCP messages to our DHCP server when I ran into a problem. Only the first ten vlans (vlan0 through vlan9) are serviced by dhcrelay. I originally thought that this was a dhcrelay limitation, so I tried using the wide-dhcp relay as well. The same problem occurs, but with a useful error message if I try and configure more than ten vlans: root@worm:~# relay -d vlan1 vlan2 vlan3 vlan4 vlan5 vlan6 vlan7 vlan8 vlan9 ^C root@worm:~# relay -d vlan1 vlan2 vlan3 vlan4 vlan5 vlan6 vlan7 vlan8 vlan9 vlan10 relay[15320]: can't open bpf in open_if() root@worm:~# It appears to me that there is a limit of ten bpf devices somewhere. This is backed up by what I see in dhcrelay. I suspect it has something to do with the way its cloned, but can't see anything like a limit. So the question is how do I overcome this limitation? In FreeBSD 4.x you used to specify the number of BPF devices in the kernel configuration pseudo-device line. That doesn't appear to be the case now. Out of desperation I tried creating more BPF devices in /dev with mknod - I now have 80 /dev/bpf* entries, but as expected that didn't help. Any assistance would be appreciated. - Guy -- Systems Manager, IT Division, Rhodes University, Grahamstown, South Africa Email: G.Halse@ru.ac.za Web: http://mombe.org/ IRC: rm-rf@irc.zanet.net *** ANSI Standard Disclaimer *** J.A.P.H From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 08:57:06 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 EA3F316A4CE for ; Thu, 22 Jan 2004 08:57:06 -0800 (PST) Received: from stewart.chicago.il.us (stewart.chicago.il.us [66.93.186.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B4A243D1D for ; Thu, 22 Jan 2004 08:57:04 -0800 (PST) (envelope-from randall@stewart.chicago.il.us) Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1]) i0JCDQO6087874; Mon, 19 Jan 2004 06:13:27 -0600 (CST) (envelope-from randall@stewart.chicago.il.us) Message-ID: <400BC9E5.8010609@stewart.chicago.il.us> Date: Mon, 19 Jan 2004 06:13:25 -0600 From: "Randall R. Stewart (home)" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <92245.1074513480@critter.freebsd.dk> In-Reply-To: <92245.1074513480@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: net@freebsd.org Subject: Re: Multihomed UDP server 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: Thu, 22 Jan 2004 16:57:07 -0000 Poul-Henning Kamp wrote: >In message <20040119143315.N81347@news1.macomnet.ru>, Maxim Konovalov writes: > > >>On Mon, 19 Jan 2004, 12:07+0100, Poul-Henning Kamp wrote: >> >> >> >>>Simple question: >>> >>>Very simple UDP server daemon. >>> >>>Many clients (connect(2)'ing a socket for each is not an option) >>> >>>Multihomed machine. >>> >>>What's the simple trick to replying with the same source-IP as the >>>client used as destination-IP ? >>> >>> >>Probably bin/58012 worth to look (Multihomed tftpd enhancement). Yes, >>it relies on protocol but still. >> >> > >But that's not a general solution, and it certainly doesn't solve >the problem for my application. > >I'm considering ways to make sendmsg(2)/recvmsg(2) DTRT, and my >current candidate is give them a flag bit which says "msg_name has >both addresses". > > > Poul: One of the problems I think that is fundamental to BSD and multi-homing is the lack of supports for multiple-default routes. And even in O/S's that do support multiple default routes (aka Linux and winXP) they really don't deal with them correctly... If you have multiple default gateways (which you probably do if your multi-homed) what you really would like to do is use both of them. One way to do that, that would aid TCP (which probably does not help you) is to have built into the routing system a way to allocate a alternate route... That way when TCP starts hitting RTX-Timeouts it could do something like: newroute = rtalloc_alt(dst, tcb->old_rt); if ( newroute != tcb->old_rt && newroute) { RT_FREE(tcb->old_rt); tcb->old_rt = newroute } Now for TCP this would mean a more robust use of a multi-homed host.. For your situation you COULD use something like that but UDP would have to do a heck of a lot more than it currently does with routing .. which I think is zilch right now :--0 sigh... someday BSD's will decide to better support M-Homing.. for now hacks are appropriate :-/ R -- Randall R. Stewart 815-477-2127 (office) 815-342-5222 (cell phone) From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 10:28:50 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 584B616A4CE for ; Thu, 22 Jan 2004 10:28:50 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 305AB43D39 for ; Thu, 22 Jan 2004 10:28:48 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 62698 invoked from network); 22 Jan 2004 18:28:47 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.47]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 22 Jan 2004 18:28:47 -0000 Message-ID: <4010165F.2080507@freebsd.org> Date: Thu, 22 Jan 2004 19:28:47 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Rate limiting icmp host unreachable replies? 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: Thu, 22 Jan 2004 18:28:50 -0000 I'm having a FreeBSD router here that has many networks connected to it which are only sparsely populated. These days I get network scans (deliberate and worms scanning for new targets) every second or so going through every IP in my netblocks. The router is faithfully generating ICMP host unreachable replies to all these scans for each and every unreachable destination IP. I wonder whether it is justifyable to rate limit the icmp host unreachable replies just like the other icmp stuff to 200 (default) per second? Should help alot if the next SQL slammer is coming around and you get thousands of packets per second for unreachable destinations. Comments and opinions welcome! PS: I've already coded it and it works nicely. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 10:36:17 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 5E8CC16A4CE for ; Thu, 22 Jan 2004 10:36:17 -0800 (PST) Received: from clever.eusc.inter.net (clever.eusc.inter.net [213.73.101.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCB6443D31 for ; Thu, 22 Jan 2004 10:36:15 -0800 (PST) (envelope-from msch@snafu.de) Received: from tc01-n70-243.de.inter.net ([213.73.70.243]) by clever.eusc.inter.net with esmtp (Exim 3.36 #4) id 1Ajjgc-0005HJ-00 for freebsd-net@freebsd.org; Thu, 22 Jan 2004 19:36:14 +0100 From: Matthias Schuendehuette Organization: Micro$oft-free Zone To: freebsd-net@freebsd.org Date: Thu, 22 Jan 2004 19:36:13 +0100 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401221936.13739.msch@snafu.de> Subject: Bridging X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: msch@snafu.de List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2004 18:36:17 -0000 Hi, I'm heavily working on a filtering bridge with FreeBSD 5.2-RELEASE... First I tried to configure the host (a HP DL380) with three interfaces: fxp0 and fxp1 for bridging (without ip-addresses) and bge0 for ssh-access with an ip-address - this does not work so far because ipfw obviously cannot get the tree interfaces managed right (but that's not my last word on this... :-) After I gave up on this, I tried with only two interfaces (bge0 and bge1) where bge0 also has an IP-address. After much try and error I got it working, but the configuration is more complicated than I expected. The central point is, that I first have to configure the various interfaces (bge0 up, bge1 up, vlan0/IP and vlan1) and afterwards may configure the bridge, i.e. set 'net.link.ether.bridge.config=....'. This means that on a filtering bridge you can't use /etc/sysctl.conf for bridge configuration because /etc/rc.d/sysctl is executed before /etc/ rc.d/netif and in this order it doesn't work. Short question: Is this intended behaviour and public knowledge? Should a /etc/rc.d/bridge be added? -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 11:03:04 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 8D28216A4CE for ; Thu, 22 Jan 2004 11:03:04 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 8C13943D2F for ; Thu, 22 Jan 2004 11:03:02 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 39267 invoked from network); 22 Jan 2004 19:03:01 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 22 Jan 2004 19:03:01 -0000 X-pair-Authenticated: 209.68.2.70 Date: Thu, 22 Jan 2004 13:02:59 -0600 (CST) From: Mike Silbersack To: Andre Oppermann In-Reply-To: <4010165F.2080507@freebsd.org> Message-ID: <20040122130156.N7234@odysseus.silby.com> References: <4010165F.2080507@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: Rate limiting icmp host unreachable replies? 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: Thu, 22 Jan 2004 19:03:04 -0000 On Thu, 22 Jan 2004, Andre Oppermann wrote: > I'm having a FreeBSD router here that has many networks connected to it which > are only sparsely populated. These days I get network scans (deliberate and > worms scanning for new targets) every second or so going through every IP in > my netblocks. The router is faithfully generating ICMP host unreachable replies > to all these scans for each and every unreachable destination IP. > > I wonder whether it is justifyable to rate limit the icmp host unreachable replies > just like the other icmp stuff to 200 (default) per second? Should help alot if > the next SQL slammer is coming around and you get thousands of packets per second > for unreachable destinations. > > Comments and opinions welcome! I like this a lot, and I would be willing to write up an implementation! > PS: I've already coded it and it works nicely. > > -- > Andre Doh! Well, I guess we'll just have to go with your implementation then. :) Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 11:26:33 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 0540216A4CF for ; Thu, 22 Jan 2004 11:26:33 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 313A843D2D for ; Thu, 22 Jan 2004 11:26:26 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 67695 invoked from network); 22 Jan 2004 19:26:25 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 22 Jan 2004 19:26:25 -0000 Message-ID: <401023E0.9D6A5952@freebsd.org> Date: Thu, 22 Jan 2004 20:26:24 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Silbersack References: <4010165F.2080507@freebsd.org> <20040122130156.N7234@odysseus.silby.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Rate limiting icmp host unreachable replies? 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: Thu, 22 Jan 2004 19:26:33 -0000 Mike Silbersack wrote: > > On Thu, 22 Jan 2004, Andre Oppermann wrote: > > > I'm having a FreeBSD router here that has many networks connected to it which > > are only sparsely populated. These days I get network scans (deliberate and > > worms scanning for new targets) every second or so going through every IP in > > my netblocks. The router is faithfully generating ICMP host unreachable replies > > to all these scans for each and every unreachable destination IP. > > > > I wonder whether it is justifyable to rate limit the icmp host unreachable replies > > just like the other icmp stuff to 200 (default) per second? Should help alot if > > the next SQL slammer is coming around and you get thousands of packets per second > > for unreachable destinations. > > > > Comments and opinions welcome! > > I like this a lot, and I would be willing to write up an implementation! > > > PS: I've already coded it and it works nicely. > > > > -- > > Andre > > Doh! Well, I guess we'll just have to go with your implementation then. > :) Here it is (pretty trivial actually): Index: icmp_var.h =================================================================== RCS file: /home/ncvs/src/sys/netinet/icmp_var.h,v retrieving revision 1.21 diff -u -p -r1.21 icmp_var.h --- icmp_var.h 19 Mar 2002 21:25:46 -0000 1.21 +++ icmp_var.h 22 Jan 2004 19:23:23 -0000 @@ -81,11 +81,12 @@ SYSCTL_DECL(_net_inet_icmp); extern int badport_bandlim(int); #define BANDLIM_UNLIMITED -1 #define BANDLIM_ICMP_UNREACH 0 -#define BANDLIM_ICMP_ECHO 1 -#define BANDLIM_ICMP_TSTAMP 2 -#define BANDLIM_RST_CLOSEDPORT 3 /* No connection, and no listeners */ -#define BANDLIM_RST_OPENPORT 4 /* No connection, listener */ -#define BANDLIM_MAX 4 +#define BANDLIM_ICMP_UNREACH_HOST 1 +#define BANDLIM_ICMP_ECHO 2 +#define BANDLIM_ICMP_TSTAMP 3 +#define BANDLIM_RST_CLOSEDPORT 4 /* No connection, and no listeners */ +#define BANDLIM_RST_OPENPORT 5 /* No connection, listener */ +#define BANDLIM_MAX 5 #endif #endif Index: ip_icmp.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/ip_icmp.c,v retrieving revision 1.87 diff -u -p -r1.87 ip_icmp.c --- ip_icmp.c 8 Jan 2004 17:40:06 -0000 1.87 +++ ip_icmp.c 22 Jan 2004 19:23:23 -0000 /* * ICMP broadcast echo sysctl */ @@ -169,6 +173,18 @@ icmp_error(n, type, code, dest, destifp) if (n->m_flags & (M_BCAST|M_MCAST)) goto freeit; /* + * Limit sending of ICMP host unreachable messages. + * If we are acting as a router and someone is doing a sweep + * scan (eg. nmap and/or numerous windows worms) for destinations + * we are the gateway for but are not reachable (ie. a /24 on a + * interface and only a couple of hosts on the ethernet) we would + * generate a storm of ICMP host unreachable messages. + */ + if (type == ICMP_UNREACH && code == ICMP_UNREACH_HOST) { + if (badport_bandlim(BANDLIM_ICMP_UNREACH_HOST) < 0) + goto freeit; + } + /* * First, formulate icmp message */ m = m_gethdr(M_DONTWAIT, MT_HEADER); @@ -859,7 +901,8 @@ badport_bandlim(int which) struct timeval lasttime; int curpps;; } rates[BANDLIM_MAX+1] = { - { "icmp unreach response" }, + { "icmp unreach port response" }, + { "icmp unreach host response" }, { "icmp ping response" }, { "icmp tstamp response" }, { "closed port RST response" }, From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 13:53:31 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 3364216A4CE; Thu, 22 Jan 2004 13:53:31 -0800 (PST) Received: from sep.oldach.net (sep.oldach.net [194.180.25.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6423943D2F; Thu, 22 Jan 2004 13:53:28 -0800 (PST) (envelope-from hmo@sep.oldach.net) Received: from sep.oldach.net (localhost [127.0.0.1])i0MLrHKi070645 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Thu, 22 Jan 2004 22:53:18 +0100 (CET) (envelope-from hmo@sep.oldach.net) Received: (from hmo@localhost) by sep.oldach.net (8.12.10/8.12.10/Submit) id i0MLrGt8070644; Thu, 22 Jan 2004 22:53:16 +0100 (CET) (envelope-from hmo) Message-Id: <200401222153.i0MLrGt8070644@sep.oldach.net> In-Reply-To: from Alex Hayward at "Nov 30, 2003 11:20:19 am" To: xelah-freebsd@xelah.com (Alex Hayward) Date: Thu, 22 Jan 2004 22:53:16 +0100 (CET) From: Helge Oldach <1822661512@oldach.net> X-Message-Flag: No HTML mail please MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Racoon(8) Deleting SPD Entries 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: Thu, 22 Jan 2004 21:53:31 -0000 [Yes, this is an old issue, but I have been biten by it today, googled a bit, and here's a dirty fix] Alex Hayward wrote on Sun Nov 30 03:20:24 2003: > On Sat, 29 Nov 2003, Crist J. Clark wrote: > > I am having some problems with racoon(8). Everything works fine for > > the lifetime of the initial SA, but then things die. When the initial > > SA is removed, racoon(8) seems to be clearing out the corresponding > > entry in the SPD. However, when we had reached the soft timeout > > earlier, racoon(8) had established new SAs. Since we have good SAs, > > racoon(8) doesn't try to do new negotiations. Both ends have a good > > SAD, but the responder no longer has SPD entries for the pair. > > I've come across this, too. It appears to be a bug in Racoon; I've > submitted a bug report to KAME - bug fbsd4/530. When Racoon creates the > security policy it gives it a timeout equal to the timeout on the SA. > It doesn't renew this timeout when a new SA is negotiated and will only > create a new SP if the existing SP has already timed out. Yep. Racoon appears to check if an SP entry is already there, and since it is (because it hasn't been expired already), it doesn't install a fresh SP upon SA renewal. I have simply fixed this by avoiding the "it SP already there?" check. See the very simple-minded patch below. Yes, this will install an additional (in fact, identical) SP, so you will see two of them during the period when the old SA is dying and the new SA is already there, but it appears that it works fine and doesn't harm. Helge --- racoon/isakmp_quick.c.ORIG Tue Oct 21 09:18:03 2003 +++ racoon/isakmp_quick.c Thu Jan 22 22:26:13 2004 @@ -2012,7 +2012,7 @@ /* get inbound policy */ sp_in = getsp_r(&spidx); - if (sp_in == NULL) { + /* if (sp_in == NULL) */ { if (iph2->ph1->rmconf->gen_policy) { plog(LLV_INFO, LOCATION, NULL, "no policy found, " From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 13:55:05 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 B205A16A4CE for ; Thu, 22 Jan 2004 13:55:05 -0800 (PST) Received: from dexter.starfire.mn.org (starfire.skypoint.net [199.199.159.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id A959643D3F for ; Thu, 22 Jan 2004 13:55:03 -0800 (PST) (envelope-from john@dexter.starfire.mn.org) Received: (from john@localhost) by dexter.starfire.mn.org (8.11.3/8.11.3) id i0MLt2S01672 for freebsd-net@freebsd.org; Thu, 22 Jan 2004 15:55:02 -0600 (CST) (envelope-from john) Date: Thu, 22 Jan 2004 15:55:02 -0600 From: John To: freebsd-net@freebsd.org Message-ID: <20040122155502.A1658@starfire.mn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Subject: Relative merits of different approaches (ipf, ipfw, ipnat, natd, etc) 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: Thu, 22 Jan 2004 21:55:05 -0000 I have looked at the FAQ, the handbook, The Complete FreeBSD, and haven't found anything like what I'm looking for. There seems to be 2-3 implementations of access control lists and 2-3 implementations of network address translation that apply to FreeBSD. Is there anywhere that discusses the relative strengths and weaknesses of these different implementations, and why you might want to use one rather than another? -- John Lind john@starfire.MN.ORG From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 16:38:57 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 3F24416A4CE for ; Thu, 22 Jan 2004 16:38:57 -0800 (PST) Received: from stewart.chicago.il.us (stewart.chicago.il.us [66.93.186.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1822E43D41 for ; Thu, 22 Jan 2004 16:38:56 -0800 (PST) (envelope-from randall@stewart.chicago.il.us) Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1]) i0N0cpO6015484; Thu, 22 Jan 2004 18:38:52 -0600 (CST) (envelope-from randall@stewart.chicago.il.us) Message-ID: <40106D1A.3000902@stewart.chicago.il.us> Date: Thu, 22 Jan 2004 18:38:50 -0600 From: "Randall R. Stewart (home)" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrea Venturoli References: <200401191533.i0JFXUDE050449@soth.ventu> In-Reply-To: <200401191533.i0JFXUDE050449@soth.ventu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Two ISP lines 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: Fri, 23 Jan 2004 00:38:57 -0000 Andrea/all: An interesting question... the following link has some thoughts along these lines... and something for the BSD community to think upon... http://www.sctp.org/what_is_alt_route TCP could definetly use something like the above (with Itojun's Multi-path updates as well).. it would give more reliability to even a singly homed protocol such as TCP :-> R Andrea Venturoli wrote: >Ok, I asked already asked something similar to this in the past, but it's not the same thing... maybe it's a trivial >question... >If I had two lines to the Internet: how would I use both? >Could I just provide two default routes? How? >What algorithm would be used to choose among the two? >What if one failed? > > bye & Thanks > av. > > > >_______________________________________________ >freebsd-net@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-net >To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > > > -- Randall R. Stewart 815-477-2127 (office) 815-342-5222 (cell phone) From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 17:12:07 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 E438516A4CF for ; Thu, 22 Jan 2004 17:12:07 -0800 (PST) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A99943D46 for ; Thu, 22 Jan 2004 17:12:07 -0800 (PST) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id i0N1C6B02288; Thu, 22 Jan 2004 17:12:06 -0800 (PST) Date: Thu, 22 Jan 2004 17:12:06 -0800 From: Mike Hunter To: freebsd-net@freebsd.org Message-ID: <20040123011206.GA1701@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i cc: dell-d800@eicat.ca Subject: Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 01:12:08 -0000 Hi everybody, I'm going to be trying to get gigabit throughput between my laptop (Dell Latitude D800 running 5.2-release) and a shuttle box running FreeBSD 5.1 (not in front of me at the moment.) As part of the process, I attempted to increase the frame size on my laptop, only to be greeted with disappointment: celeste# ifconfig bge0 bge0: flags=8802 mtu 1500 options=1b ether 00:0b:db:99:d6:06 media: Ethernet 1000baseTX (none) status: no carrier celeste# ifconfig bge0 mtu 9000 ifconfig: ioctl (set mtu): Invalid argument celeste# ifconfig bge0 mtu 1501 ifconfig: ioctl (set mtu): Invalid argument celeste# ifconfig bge0 mtu 1500 celeste# The C file talks about being able to do jumbo frames when the mtu is big enough...anybody know what I'm missing? My card is a "Broadcom BCM5705M" and I'm running FreeBSD 5.2-release. When I asked google, it mostly pointed me at comments in if_bge.c talking about jumbo frames :| Thanks, Mike From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 17:18:47 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 AB35616A4CE for ; Thu, 22 Jan 2004 17:18:47 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFB4B43D41 for ; Thu, 22 Jan 2004 17:18:45 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 93105 invoked from network); 23 Jan 2004 01:18:45 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.54]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 23 Jan 2004 01:18:45 -0000 Message-ID: <40107674.A5C22203@freebsd.org> Date: Fri, 23 Jan 2004 02:18:44 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Hunter References: <20040123011206.GA1701@ack.Berkeley.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: dell-d800@eicat.ca cc: freebsd-net@freebsd.org Subject: Re: Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 01:18:47 -0000 Mike Hunter wrote: > > Hi everybody, > > I'm going to be trying to get gigabit throughput between my laptop (Dell > Latitude D800 running 5.2-release) and a shuttle box running FreeBSD 5.1 > (not in front of me at the moment.) As part of the process, I attempted > to increase the frame size on my laptop, only to be greeted with > disappointment: > > celeste# ifconfig bge0 > bge0: flags=8802 mtu 1500 > options=1b > ether 00:0b:db:99:d6:06 > media: Ethernet 1000baseTX (none) > status: no carrier > celeste# ifconfig bge0 mtu 9000 > ifconfig: ioctl (set mtu): Invalid argument > celeste# ifconfig bge0 mtu 1501 > ifconfig: ioctl (set mtu): Invalid argument > celeste# ifconfig bge0 mtu 1500 > celeste# > > The C file talks about being able to do jumbo frames when the mtu is big > enough...anybody know what I'm missing? My card is a "Broadcom BCM5705M" > and I'm running FreeBSD 5.2-release. When I asked google, it mostly > pointed me at comments in if_bge.c talking about jumbo frames :| Hmm... works for me (on my shiny new dual-Opteron): # ifconfig bge1 mtu 2000 # ifconfig bge1 bge1: flags=8842 mtu 2000 options=1b ether 00:e0:81:27:e0:aa media: Ethernet autoselect (100baseTX ) status: active Mine is a 5704C dual GigE chip. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 17:28:24 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 69F8D16A4CE for ; Thu, 22 Jan 2004 17:28:24 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF20C43D2F for ; Thu, 22 Jan 2004 17:28:22 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.3) with ESMTP id i0N1S7aT001473; Thu, 22 Jan 2004 17:28:07 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i0N1S7Q9001471; Thu, 22 Jan 2004 17:28:07 -0800 Date: Thu, 22 Jan 2004 17:28:06 -0800 From: Brooks Davis To: Mike Hunter Message-ID: <20040123012806.GA608@Odin.AC.HMC.Edu> References: <20040123011206.GA1701@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: <20040123011206.GA1701@ack.Berkeley.EDU> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: dell-d800@eicat.ca cc: freebsd-net@freebsd.org Subject: Re: Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 01:28:24 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 22, 2004 at 05:12:06PM -0800, Mike Hunter wrote: > Hi everybody, >=20 > I'm going to be trying to get gigabit throughput between my laptop (Dell > Latitude D800 running 5.2-release) and a shuttle box running FreeBSD 5.1= =20 > (not in front of me at the moment.) As part of the process, I attempted > to increase the frame size on my laptop, only to be greeted with > disappointment: >=20 > celeste# ifconfig bge0 > bge0: flags=3D8802 mtu 1500 > options=3D1b > ether 00:0b:db:99:d6:06 > media: Ethernet 1000baseTX (none) > status: no carrier > celeste# ifconfig bge0 mtu 9000 > ifconfig: ioctl (set mtu): Invalid argument > celeste# ifconfig bge0 mtu 1501 > ifconfig: ioctl (set mtu): Invalid argument > celeste# ifconfig bge0 mtu 1500 > celeste# >=20 > The C file talks about being able to do jumbo frames when the mtu is big > enough...anybody know what I'm missing? My card is a "Broadcom BCM5705M" > and I'm running FreeBSD 5.2-release. When I asked google, it mostly > pointed me at comments in if_bge.c talking about jumbo frames :| =46rom looking at the code, BCM5705's don't support Jumbo Frames. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAEHilXY6L6fI4GtQRAqmTAJ0bLYLuER274/UkCDPGI8C/tbTSbQCgyp1v dPlUNbBOUfWYXHBwupc7cPY= =e5Ib -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE-- From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 18:00:18 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 815AF16A4CE for ; Thu, 22 Jan 2004 18:00:18 -0800 (PST) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03E9A43D31 for ; Thu, 22 Jan 2004 18:00:17 -0800 (PST) (envelope-from anderson@centtech.com) Received: from centtech.com ([192.168.42.24]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id i0N2046T089276; Thu, 22 Jan 2004 20:00:04 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4010800A.2050109@centtech.com> Date: Thu, 22 Jan 2004 19:59:38 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20040121 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Hunter References: <20040123011206.GA1701@ack.Berkeley.EDU> In-Reply-To: <20040123011206.GA1701@ack.Berkeley.EDU> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: dell-d800@eicat.ca cc: freebsd-net@freebsd.org Subject: Re: [D800] Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 02:00:18 -0000 Mike Hunter wrote: >Hi everybody, > >I'm going to be trying to get gigabit throughput between my laptop (Dell >Latitude D800 running 5.2-release) and a shuttle box running FreeBSD 5.1 >(not in front of me at the moment.) As part of the process, I attempted >to increase the frame size on my laptop, only to be greeted with >disappointment: > >celeste# ifconfig bge0 >bge0: flags=8802 mtu 1500 > options=1b > ether 00:0b:db:99:d6:06 > media: Ethernet 1000baseTX (none) > status: no carrier >celeste# ifconfig bge0 mtu 9000 >ifconfig: ioctl (set mtu): Invalid argument >celeste# ifconfig bge0 mtu 1501 >ifconfig: ioctl (set mtu): Invalid argument >celeste# ifconfig bge0 mtu 1500 >celeste# > >The C file talks about being able to do jumbo frames when the mtu is big >enough...anybody know what I'm missing? My card is a "Broadcom BCM5705M" >and I'm running FreeBSD 5.2-release. When I asked google, it mostly >pointed me at comments in if_bge.c talking about jumbo frames :| > > As a data point, my BCM5702 (Dell D600) works fine: # ifconfig -a bge0: flags=8843 mtu 9000 options=1b inet6 fe80::20b:dbff:fea3:f9a1%bge0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 ether 00:0b:db:a3:f9:a1 media: Ethernet autoselect (none) status: no carrier Eric -- ------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Today is the tomorrow you worried about yesterday. ------------------------------------------------------------------ From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 18:06:39 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 9E8F316A4CE for ; Thu, 22 Jan 2004 18:06:39 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0A7243D3F for ; Thu, 22 Jan 2004 18:06:33 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id 2AC6C307DC; Thu, 22 Jan 2004 21:06:33 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 3299F1D1E3F; Thu, 22 Jan 2004 21:06:30 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16400.33190.25580.251371@canoe.dclg.ca> Date: Thu, 22 Jan 2004 21:06:30 -0500 To: Mike Hunter In-Reply-To: <20040123011206.GA1701@ack.Berkeley.EDU> References: <20040123011206.GA1701@ack.Berkeley.EDU> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid cc: dell-d800@eicat.ca cc: freebsd-net@freebsd.org Subject: [D800] Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 02:06:39 -0000 >>>>> "Mike" == Mike Hunter writes: Mike> Hi everybody, I'm going to be trying to get gigabit throughput Mike> between my laptop (Dell Latitude D800 running 5.2-release) and a Mike> shuttle box running FreeBSD 5.1 (not in front of me at the Mike> moment.) As part of the process, I attempted to increase the Mike> frame size on my laptop, only to be greeted with disappointment: A few things to think about. I don't know what disk you got, but the 60G disk in mine doesn't appear to be all that fast. You might be able to get memory to memory transfers to be GigE speeds, but your hard drive(s) are likely a limit from getting too much speed. Mike> The C file talks about being able to do jumbo frames when the Mike> mtu is big enough...anybody know what I'm missing? My card is a Mike> "Broadcom BCM5705M" and I'm running FreeBSD 5.2-release. When I Mike> asked google, it mostly pointed me at comments in if_bge.c Mike> talking about jumbo frames :| Unfortunately, the chip in the D800 is a scaled down version. It doesn't support jumbo frames. I assume that broadcom sells the cripled part at a lower price than the full part. There are notes in the driver about what's diabled in this specific version. :(. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 18:09: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 1EBC516A4CE for ; Thu, 22 Jan 2004 18:09:02 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04EAE43D39 for ; Thu, 22 Jan 2004 18:09:01 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id 961E1307DC; Thu, 22 Jan 2004 21:09:00 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 30D551D1E3F; Thu, 22 Jan 2004 21:08:58 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16400.33337.986657.212849@canoe.dclg.ca> Date: Thu, 22 Jan 2004 21:08:57 -0500 To: Eric Anderson In-Reply-To: <4010800A.2050109@centtech.com> References: <20040123011206.GA1701@ack.Berkeley.EDU> <4010800A.2050109@centtech.com> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid cc: dell-d800@eicat.ca cc: freebsd-net@freebsd.org cc: Mike Hunter Subject: Re: [D800] Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 02:09:02 -0000 >>>>> "Eric" == Eric Anderson writes: Eric> As a data point, my BCM5702 (Dell D600) works fine: # ifconfig Eric> -a bge0: flags=8843 mtu Eric> 9000 options=1b inet6 Eric> fe80::20b:dbff:fea3:f9a1%bge0 prefixlen 64 scopeid 0x1 inet Eric> 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 ether Eric> 00:0b:db:a3:f9:a1 media: Ethernet autoselect (none) status: no Eric> carrier What is the probe line for your bge? Mine is: bge0: mem 0xfaff0000-0xfaffffff irq 11 at device 0.0 on pci2 bge0: Ethernet address: 00:0b:db:94:3d:01 miibus0: on bge0 Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 18:14:46 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 DF85016A4CE; Thu, 22 Jan 2004 18:14:46 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id F24FB43D41; Thu, 22 Jan 2004 18:14:45 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id 8F7A630838; Thu, 22 Jan 2004 21:14:45 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 28BF81D1F6B; Thu, 22 Jan 2004 21:14:43 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16400.33683.38650.755105@canoe.dclg.ca> Date: Thu, 22 Jan 2004 21:14:43 -0500 To: Andre Oppermann In-Reply-To: <40107674.A5C22203@freebsd.org> References: <20040123011206.GA1701@ack.Berkeley.EDU> <40107674.A5C22203@freebsd.org> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid cc: dell-d800@eicat.ca cc: freebsd-net@freebsd.org cc: Mike Hunter Subject: [D800] Re: Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 02:14:47 -0000 >>>>> "Andre" == Andre Oppermann writes: Andre> Hmm... works for me (on my shiny new dual-Opteron): Andre> Mine is a 5704C dual GigE chip. Yeah... the D800 has a 5705M chip ... which doesn't support jumbo frames... which is some deliberate bit of marketing goo, I suspect. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 18:22:20 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 8518C16A4CE for ; Thu, 22 Jan 2004 18:22:20 -0800 (PST) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31BB143D39 for ; Thu, 22 Jan 2004 18:22:19 -0800 (PST) (envelope-from anderson@centtech.com) Received: from centtech.com ([192.168.42.24]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id i0N2MG6T091456; Thu, 22 Jan 2004 20:22:16 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4010853E.20105@centtech.com> Date: Thu, 22 Jan 2004 20:21:50 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20040121 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Gilbert References: <20040123011206.GA1701@ack.Berkeley.EDU> <4010800A.2050109@centtech.com> <16400.33337.986657.212849@canoe.dclg.ca> In-Reply-To: <16400.33337.986657.212849@canoe.dclg.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: dell-d800@eicat.ca cc: freebsd-net@freebsd.org cc: Mike Hunter Subject: Re: [D800] Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 02:22:20 -0000 David Gilbert wrote: >>>>>>"Eric" == Eric Anderson writes: >>>>>> >>>>>> > >Eric> As a data point, my BCM5702 (Dell D600) works fine: # ifconfig >Eric> -a bge0: flags=8843 mtu >Eric> 9000 options=1b inet6 >Eric> fe80::20b:dbff:fea3:f9a1%bge0 prefixlen 64 scopeid 0x1 inet >Eric> 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 ether >Eric> 00:0b:db:a3:f9:a1 media: Ethernet autoselect (none) status: no >Eric> carrier > >What is the probe line for your bge? > >Mine is: > >bge0: mem 0xfaff0000-0xfaffffff irq 11 at device 0.0 on pci2 >bge0: Ethernet address: 00:0b:db:94:3d:01 >miibus0: on bge0 > > bge0: mem 0xfaff0000-0xfaffffff irq 11 at device 0.0 on pci2 bge0: Ethernet address: 00:0b:db:a3:f9:a1 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto Strange - it shows BCM5702, then BCM5703 Eric -- ------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Today is the tomorrow you worried about yesterday. ------------------------------------------------------------------ From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 18:28:26 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 E0F8F16A4CE for ; Thu, 22 Jan 2004 18:28:26 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6FAB43D39 for ; Thu, 22 Jan 2004 18:28:25 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.3) with ESMTP id i0N2S5aT011273; Thu, 22 Jan 2004 18:28:05 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i0N2S5CH011269; Thu, 22 Jan 2004 18:28:05 -0800 Date: Thu, 22 Jan 2004 18:28:05 -0800 From: Brooks Davis To: Eric Anderson Message-ID: <20040123022805.GA10764@Odin.AC.HMC.Edu> References: <20040123011206.GA1701@ack.Berkeley.EDU> <4010800A.2050109@centtech.com> <16400.33337.986657.212849@canoe.dclg.ca> <4010853E.20105@centtech.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline In-Reply-To: <4010853E.20105@centtech.com> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: dell-d800@eicat.ca cc: freebsd-net@freebsd.org cc: Mike Hunter cc: David Gilbert Subject: Re: [D800] Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 02:28:27 -0000 --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 22, 2004 at 08:21:50PM -0600, Eric Anderson wrote: > bge0: mem=20 > 0xfaff0000-0xfaffffff irq 11 at device 0.0 on pci2 > bge0: Ethernet address: 00:0b:db:a3:f9:a1 > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,=20 > 1000baseTX-FDX, auto >=20 > Strange - it shows BCM5702, then BCM5703 Not really. the whole point of MII is that you can mix and match phy's. It's not done much outside of a single product line, but it's technically an option. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAEIa0XY6L6fI4GtQRAnw7AKDJd9yGt/DPNm47lbUXV+kmHZAdAACgt1Fq xJ3fzmKW9DVtDxoCsAjY6vg= =l3qI -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM-- From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 19:17:48 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 0572316A4CE for ; Thu, 22 Jan 2004 19:17:48 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DCEC43D46 for ; Thu, 22 Jan 2004 19:17:45 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id 2CCAC3083B; Thu, 22 Jan 2004 22:17:44 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 6903D1D1F21; Thu, 22 Jan 2004 22:17:41 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16400.37461.290134.492889@canoe.dclg.ca> Date: Thu, 22 Jan 2004 22:17:41 -0500 To: Eric Anderson In-Reply-To: <4010853E.20105@centtech.com> References: <20040123011206.GA1701@ack.Berkeley.EDU> <4010800A.2050109@centtech.com> <16400.33337.986657.212849@canoe.dclg.ca> <4010853E.20105@centtech.com> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid cc: dell-d800@eicat.ca cc: freebsd-net@freebsd.org cc: Mike Hunter cc: David Gilbert Subject: Re: [D800] Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 03:17:48 -0000 >>>>> "Eric" == Eric Anderson writes: Eric> bge0: mem Eric> 0xfaff0000-0xfaffffff irq 11 at device 0.0 on pci2 bge0: Eric> Ethernet address: 00:0b:db:a3:f9:a1 miibus0: on bge0 Eric> brgphy0: on miibus0 brgphy0: Eric> 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, Eric> 1000baseTX-FDX, auto So the D600 (or possibly newer Dell laptops) have the better part... maybe. The 'M' designation might also be about low power ... but how much does batterylife matter when you're plugged into ethernet :). Eric> Strange - it shows BCM5702, then BCM5703 If you look in the code, you'll probably find that one of the lines is being more specific about the chip. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 19:23:28 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 E3D1816A4CE for ; Thu, 22 Jan 2004 19:23:28 -0800 (PST) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2C6943D70 for ; Thu, 22 Jan 2004 19:22:54 -0800 (PST) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id i0N3Mrc19741; Thu, 22 Jan 2004 19:22:53 -0800 (PST) Date: Thu, 22 Jan 2004 19:22:53 -0800 From: Mike Hunter To: Brooks Davis Message-ID: <20040123032253.GB19208@ack.Berkeley.EDU> References: <20040123011206.GA1701@ack.Berkeley.EDU> <20040123012806.GA608@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040123012806.GA608@Odin.AC.HMC.Edu> User-Agent: Mutt/1.4i cc: dell-d800@eicat.ca cc: freebsd-net@freebsd.org Subject: Re: Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 03:23:29 -0000 On Jan 22, "Brooks Davis" wrote: > On Thu, Jan 22, 2004 at 05:12:06PM -0800, Mike Hunter wrote: > > > > I'm going to be trying to get gigabit throughput between my laptop (Dell > > Latitude D800 running 5.2-release) and a shuttle box running FreeBSD 5.1 > > (not in front of me at the moment.) As part of the process, I attempted > > to increase the frame size on my laptop, only to be greeted with > > disappointment: > > > > celeste# ifconfig bge0 > > bge0: flags=8802 mtu 1500 > > options=1b > > ether 00:0b:db:99:d6:06 > > media: Ethernet 1000baseTX (none) > > status: no carrier > > celeste# ifconfig bge0 mtu 9000 > > ifconfig: ioctl (set mtu): Invalid argument > > celeste# ifconfig bge0 mtu 1501 > > ifconfig: ioctl (set mtu): Invalid argument > > celeste# ifconfig bge0 mtu 1500 > > celeste# > > > > The C file talks about being able to do jumbo frames when the mtu is big > > enough...anybody know what I'm missing? My card is a "Broadcom BCM5705M" > > and I'm running FreeBSD 5.2-release. When I asked google, it mostly > > pointed me at comments in if_bge.c talking about jumbo frames :| > > From looking at the code, BCM5705's don't support Jumbo Frames. Thanks for the help everybody. "I will not 'read' C files with `grep`. I will not 'read' C files with `grep`. I will not 'read' C files with `grep`...." Mike From owner-freebsd-net@FreeBSD.ORG Thu Jan 22 23:02:21 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 B4D1716A4F0 for ; Thu, 22 Jan 2004 23:02:21 -0800 (PST) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id 168A443D4C for ; Thu, 22 Jan 2004 23:00:56 -0800 (PST) (envelope-from dinesh@alphaque.com) Received: (qmail 9766 invoked by uid 0); 23 Jan 2004 06:59:22 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 23 Jan 2004 06:59:22 -0000 Received: from localhost (localhost.alphaque.com [127.0.0.1]) by prophet.alphaque.com (8.12.10/8.12.9) with ESMTP id i0N6VxDQ003982; Fri, 23 Jan 2004 14:31:59 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Fri, 23 Jan 2004 14:31:59 +0800 (MYT) From: Dinesh Nair To: "Randall R. Stewart (home)" In-Reply-To: <400BC9E5.8010609@stewart.chicago.il.us> Message-ID: <20040123142736.B532-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Poul-Henning Kamp cc: net@freebsd.org Subject: Re: Multihomed UDP server 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: Fri, 23 Jan 2004 07:02:21 -0000 On Mon, 19 Jan 2004, Randall R. Stewart (home) wrote: > One of the problems I think that is fundamental to BSD and multi-homing > is the lack of supports for multiple-default routes. And even in O/S's there's a patch to FreeBSD 4.8 which adds multipath support at http://www.dsm.fordham.edu/~tanzer/multipath/ i've tested it on FreeBSD 4.9 and it works, with the addition of an additional modification. see another thread in -net for details. > sigh... someday BSD's will decide to better support M-Homing.. for now > hacks are appropriate :-/ yes they are. i'm exploring to see if i can implement multipath functionality as a new netgraph node. this, for starters, would at least to an extent provide modularity to the existing mpath patches referenced above and back porting to earlier 4.x systems without modifying the core tcp/ip stack of freebsd. one possible addition to functionality in this yet-to-be-written node could perhaps be a heartbeat to the next hop router and to down that route/interface if the next hop was down for any reason. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-net@FreeBSD.ORG Fri Jan 23 03:09:58 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 BB97416A4CE for ; Fri, 23 Jan 2004 03:09:58 -0800 (PST) Received: from guard.polynet.lviv.ua (guard.polynet.lviv.ua [217.9.2.1]) by mx1.FreeBSD.org (Postfix) with SMTP id 128D043D31 for ; Fri, 23 Jan 2004 03:09:53 -0800 (PST) (envelope-from akorud@polynet.lviv.ua) Received: (qmail 90708 invoked from network); 23 Jan 2004 11:09:43 -0000 Received: from eaux.polynet.lviv.ua (HELO localhost) (217.9.2.4) by 217.9.2.1 with SMTP; 23 Jan 2004 11:09:43 -0000 Received: from ip-81-210-9-42.netia.com.pl (ip-81-210-9-42.netia.com.pl [81.210.9.42]) by isp.polynet.lviv.ua (IMP) with HTTP for <.akorud.netadmin.lp@guard>; Fri, 23 Jan 2004 13:09:43 +0200 Message-ID: <1074856183.401100f764173@isp.polynet.lviv.ua> Date: Fri, 23 Jan 2004 13:09:43 +0200 From: Andriy Korud To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 Subject: Which one ip_nat.h? 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: Fri, 23 Jan 2004 11:09:58 -0000 Hi, I need to define LARGE_NAT in ip_nat.h, however there are 3 such files in my system: locate ip_nat.h /usr/include/netinet/ip_nat.h /usr/src/contrib/ipfilter/ip_nat.h /usr/src/sys/contrib/ipfilter/netinet/ip_nat.h The question is simple - which one should I change? regards, Andriy Korud From owner-freebsd-net@FreeBSD.ORG Fri Jan 23 03:41:15 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 8B93216A4CE for ; Fri, 23 Jan 2004 03:41:15 -0800 (PST) Received: from c7.campus.utcluj.ro (c7.campus.utcluj.ro [193.226.6.226]) by mx1.FreeBSD.org (Postfix) with SMTP id E99EC43D53 for ; Fri, 23 Jan 2004 03:41:13 -0800 (PST) (envelope-from veedee@c7.campus.utcluj.ro) Received: (qmail 37320 invoked by uid 1008); 23 Jan 2004 11:41:12 -0000 From: veedee@c7.campus.utcluj.ro Date: Fri, 23 Jan 2004 13:41:12 +0200 To: Andriy Korud Message-ID: <20040123114112.GA37273@c7.campus.utcluj.ro> References: <1074856183.401100f764173@isp.polynet.lviv.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1074856183.401100f764173@isp.polynet.lviv.ua> cc: freebsd-net@freebsd.org Subject: Re: Which one ip_nat.h? 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: Fri, 23 Jan 2004 11:41:15 -0000 On Fri, Jan 23, 2004 at 01:09:43PM +0200, Andriy Korud wrote: > > Hi, > I need to define LARGE_NAT in ip_nat.h, however there are 3 such files in my > system: > locate ip_nat.h > /usr/include/netinet/ip_nat.h > /usr/src/contrib/ipfilter/ip_nat.h > /usr/src/sys/contrib/ipfilter/netinet/ip_nat.h > > The question is simple - which one should I change? the last two. you need to recompile afterwards... > regards, > Andriy Korud -- | Radu Bogdan 'veedee' Rusu | NetSysAdm at campus dot utcluj dot ro | Personal gallery at http://rbrusu.com | ...mirroring FreeBSD and coffee From owner-freebsd-net@FreeBSD.ORG Fri Jan 23 04:09:07 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 4197816A4CE for ; Fri, 23 Jan 2004 04:09:07 -0800 (PST) Received: from phantom.cris.net (phantom.cris.net [212.110.130.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D5F543D2F for ; Fri, 23 Jan 2004 04:09:03 -0800 (PST) (envelope-from ru@FreeBSD.org.ua) Received: from phantom.cris.net (ru@localhost [127.0.0.1]) by phantom.cris.net (8.12.10/8.12.10) with ESMTP id i0NC9Wem036547; Fri, 23 Jan 2004 14:09:32 +0200 (EET) (envelope-from ru@FreeBSD.org.ua) Received: (from ru@localhost) by phantom.cris.net (8.12.10/8.12.10/Submit) id i0NC9WR1036542; Fri, 23 Jan 2004 14:09:32 +0200 (EET) (envelope-from ru) Date: Fri, 23 Jan 2004 14:09:32 +0200 From: Ruslan Ermilov To: veedee@c7.campus.utcluj.ro Message-ID: <20040123120932.GD36171@FreeBSD.org.ua> References: <1074856183.401100f764173@isp.polynet.lviv.ua> <20040123114112.GA37273@c7.campus.utcluj.ro> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uxuisgdDHaNETlh8" Content-Disposition: inline In-Reply-To: <20040123114112.GA37273@c7.campus.utcluj.ro> User-Agent: Mutt/1.5.5.1i cc: freebsd-net@freebsd.org cc: Andriy Korud Subject: Re: Which one ip_nat.h? 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: Fri, 23 Jan 2004 12:09:07 -0000 --uxuisgdDHaNETlh8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 23, 2004 at 01:41:12PM +0200, veedee@c7.campus.utcluj.ro wrote: > On Fri, Jan 23, 2004 at 01:09:43PM +0200, Andriy Korud wrote: > >=20 > > Hi, > > I need to define LARGE_NAT in ip_nat.h, however there are 3 such files = in my > > system: > > locate ip_nat.h > > /usr/include/netinet/ip_nat.h > > /usr/src/contrib/ipfilter/ip_nat.h > > /usr/src/sys/contrib/ipfilter/netinet/ip_nat.h > > > > The question is simple - which one should I change? >=20 > the last two. you need to recompile afterwards... >=20 For this same reason, I've removed a couple of duplicate IPFilter headers =66rom HEAD 2,5 years ago, including src/contrib/ipfilter/ip_nat.h: : revision 1.2 : date: 2001/06/18 15:54:04; author: ru; state: dead; lines: +0 -0 : Removed duplicate copies of files already present in sys/contrib/ipfilter. :=20 : Not objected to by: -arch No, I'm not volunteering to do the MFC. ;) Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --uxuisgdDHaNETlh8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAEQ78Ukv4P6juNwoRAlvQAJ9XrFvdaW7sPXNDvq8M/6JuXIV28QCfdb8w cbW0TLOSwuYNjt/GwJ//+VE= =3tEE -----END PGP SIGNATURE----- --uxuisgdDHaNETlh8-- From owner-freebsd-net@FreeBSD.ORG Fri Jan 23 08:34:04 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 734D016A55E for ; Fri, 23 Jan 2004 08:34:04 -0800 (PST) Received: from moo.sysabend.org (moo.sysabend.org [66.111.41.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0003A43D45 for ; Fri, 23 Jan 2004 08:33:40 -0800 (PST) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id 3C5C7F75; Fri, 23 Jan 2004 08:33:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id 3B219F24; Fri, 23 Jan 2004 08:33:40 -0800 (PST) Date: Fri, 23 Jan 2004 08:33:40 -0800 (PST) From: Jamie Bowden To: David Gilbert In-Reply-To: <16400.33190.25580.251371@canoe.dclg.ca> Message-ID: <20040123083134.B78161-100000@moo.sysabend.org> X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: dell-d800@eicat.ca cc: freebsd-net@freebsd.org cc: Mike Hunter Subject: Re: [D800] Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 16:34:04 -0000 On Thu, 22 Jan 2004, David Gilbert wrote: > >>>>> "Mike" == Mike Hunter writes: > > Mike> Hi everybody, I'm going to be trying to get gigabit throughput > Mike> between my laptop (Dell Latitude D800 running 5.2-release) and a > Mike> shuttle box running FreeBSD 5.1 (not in front of me at the > Mike> moment.) As part of the process, I attempted to increase the > Mike> frame size on my laptop, only to be greeted with disappointment: > > A few things to think about. I don't know what disk you got, but the > 60G disk in mine doesn't appear to be all that fast. You might be > able to get memory to memory transfers to be GigE speeds, but your > hard drive(s) are likely a limit from getting too much speed. The 40GB disk is 7200 RPM, but the others offered on that model are all 5400RPM. I was going to order mine with the 60G disk until my Dell rep. told me that little tidbit. > Mike> The C file talks about being able to do jumbo frames when the > Mike> mtu is big enough...anybody know what I'm missing? My card is a > Mike> "Broadcom BCM5705M" and I'm running FreeBSD 5.2-release. When I > Mike> asked google, it mostly pointed me at comments in if_bge.c > Mike> talking about jumbo frames :| > > Unfortunately, the chip in the D800 is a scaled down version. It > doesn't support jumbo frames. I assume that broadcom sells the > cripled part at a lower price than the full part. There are notes in > the driver about what's diabled in this specific version. I'm curious why the 800 would have the lower end chip, it's a higher end laptop all around when compared to the 600. Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen From owner-freebsd-net@FreeBSD.ORG Fri Jan 23 08:38:32 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 4F7B716A4CE for ; Fri, 23 Jan 2004 08:38:32 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id C112A43D3F for ; Fri, 23 Jan 2004 08:38:27 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id 0915930862; Fri, 23 Jan 2004 11:38:27 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 98BF51D1FB8; Fri, 23 Jan 2004 11:38:26 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16401.19970.471799.464038@canoe.dclg.ca> Date: Fri, 23 Jan 2004 11:38:26 -0500 To: Jamie Bowden In-Reply-To: <20040123083134.B78161-100000@moo.sysabend.org> References: <16400.33190.25580.251371@canoe.dclg.ca> <20040123083134.B78161-100000@moo.sysabend.org> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid cc: dell-d800@eicat.ca cc: freebsd-net@freebsd.org cc: Mike Hunter cc: David Gilbert Subject: Re: [D800] Dell D800 (FBSD 5.2-release) Broadcom BCM5705M MTU/Jumbo Problem 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: Fri, 23 Jan 2004 16:38:32 -0000 >>>>> "Jamie" == Jamie Bowden writes: Jamie> The 40GB disk is 7200 RPM, but the others offered on that model Jamie> are all 5400RPM. I was going to order mine with the 60G disk Jamie> until my Dell rep. told me that little tidbit. I chose the storage over speed. Besides 60G at 5400 RPM (in terms of raw data rate) is almost as fast as 40G at 7200 RPM. Either way, this is pretty slow compared to the 120G and larger drives in desktops. Jamie> I'm curious why the 800 would have the lower end chip, it's a Jamie> higher end laptop all around when compared to the 600. I've been wondering if it's a revision thing. Maybe newer D800's have the better chip. Maybe the power profile of the 'M' chip is "better" ... Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-net@FreeBSD.ORG Fri Jan 23 08:59:11 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 5AD1116A4CE for ; Fri, 23 Jan 2004 08:59:11 -0800 (PST) Received: from bragi.housing.ufl.edu (bragi.housing.ufl.edu [128.227.47.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4297843D80 for ; Fri, 23 Jan 2004 08:59:10 -0800 (PST) (envelope-from WillS@housing.ufl.edu) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Fri, 23 Jan 2004 11:46:00 -0500 Message-ID: <0E972CEE334BFE4291CD07E056C76ED8DB36FC@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: vlan interfaces and channel bonding/etherchannel Thread-Index: AcPh0GFpxpx8Lf44QSiOW7wLOW0ZFg== From: "Will Saxon" To: Subject: vlan interfaces and channel bonding/etherchannel 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: Fri, 23 Jan 2004 16:59:11 -0000 Are there any plans to support vlan pseudo intefaces with a ng_fec or = ng_one2many parent? I would like to create some sort of failover or = aggregation with one of my servers, but unfortunately it is using an = 802.1Q trunk. -Will From owner-freebsd-net@FreeBSD.ORG Fri Jan 23 09:05:34 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 19FA316A4CE for ; Fri, 23 Jan 2004 09:05:34 -0800 (PST) Received: from phantom.cris.net (phantom.cris.net [212.110.130.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93D3043DA8 for ; Fri, 23 Jan 2004 09:04:23 -0800 (PST) (envelope-from ru@FreeBSD.org.ua) Received: from phantom.cris.net (ru@localhost [127.0.0.1]) by phantom.cris.net (8.12.10/8.12.10) with ESMTP id i0NH4aem039481; Fri, 23 Jan 2004 19:04:36 +0200 (EET) (envelope-from ru@FreeBSD.org.ua) Received: (from ru@localhost) by phantom.cris.net (8.12.10/8.12.10/Submit) id i0NH4aJR039476; Fri, 23 Jan 2004 19:04:36 +0200 (EET) (envelope-from ru) Date: Fri, 23 Jan 2004 19:04:36 +0200 From: Ruslan Ermilov To: Will Saxon Message-ID: <20040123170436.GH38510@FreeBSD.org.ua> References: <0E972CEE334BFE4291CD07E056C76ED8DB36FC@bragi.housing.ufl.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="y0Ed1hDcWxc3B7cn" Content-Disposition: inline In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED8DB36FC@bragi.housing.ufl.edu> User-Agent: Mutt/1.5.5.1i cc: freebsd-net@freebsd.org Subject: Re: vlan interfaces and channel bonding/etherchannel 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: Fri, 23 Jan 2004 17:05:34 -0000 --y0Ed1hDcWxc3B7cn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 23, 2004 at 11:46:00AM -0500, Will Saxon wrote: > Are there any plans to support vlan pseudo intefaces with > a ng_fec or ng_one2many parent? I would like to create some > sort of failover or aggregation with one of my servers, but > unfortunately it is using an 802.1Q trunk. >=20 I have the ng_vlan(4) module ready, trying to persuade my employer to give it back to open source. Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --y0Ed1hDcWxc3B7cn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAEVQkUkv4P6juNwoRAtDVAJ9zS/iDNhF5B7JvFhzcGW8ZSLIVzQCgg5Ee MLqu9fbTcvDOxH6bI729ezA= =FHXY -----END PGP SIGNATURE----- --y0Ed1hDcWxc3B7cn-- From owner-freebsd-net@FreeBSD.ORG Fri Jan 23 09:43:20 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 0542916A4CE for ; Fri, 23 Jan 2004 09:43:20 -0800 (PST) Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.136.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14F8143D41 for ; Fri, 23 Jan 2004 09:43:17 -0800 (PST) (envelope-from jrh@it.uc3m.es) Received: from smtp02.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id D60F65B69; Fri, 23 Jan 2004 18:43:15 +0100 (CET) Received: from cimborrio (cimborrio.it.uc3m.es [163.117.139.95]) by smtp02.uc3m.es (Postfix) with ESMTP id B4D5F5B68; Fri, 23 Jan 2004 18:43:15 +0100 (CET) From: Juan Rodriguez Hervella Organization: UC3M To: "Randall R. Stewart (home)" , Andrea Venturoli Date: Fri, 23 Jan 2004 18:43:14 +0100 User-Agent: KMail/1.5.4 References: <200401191533.i0JFXUDE050449@soth.ventu> <40106D1A.3000902@stewart.chicago.il.us> In-Reply-To: <40106D1A.3000902@stewart.chicago.il.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401231843.14422.jrh@it.uc3m.es> cc: freebsd-net@freebsd.org Subject: Re: Two ISP lines 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: Fri, 23 Jan 2004 17:43:20 -0000 Just some questions about this paper: "(...) Note that this route has to be at the same level of the tree, i.e. the code cannot return a less specific match or a more specific match (...)" Question: I don't understand why if you are looking for an alternate route you aren't allowed to retrieve a more specific route. This doesn't make sense to me. If you are routing packets using a route when there is a more specific match, you aren't doing "longest prefix match". Another question: if ISP-1 goes down, and you use this feature of alternatives routes, this still doesn't fix the communication problem. Unless you make something with the source addr. of the multihomed site's packets, the reply packets will be lost in the faulty ISP, imho. Regards. On Friday 23 January 2004 01:38, Randall R. Stewart (home) wrote: > Andrea/all: > > An interesting question... the following link has > some thoughts along these lines... and something > for the BSD community to think upon... > > http://www.sctp.org/what_is_alt_route > > TCP could definetly use something like the above (with Itojun's Multi-path > updates as well).. it would give more reliability to even a singly > homed protocol such as TCP :-> > > R > > Andrea Venturoli wrote: > >Ok, I asked already asked something similar to this in the past, but it's > > not the same thing... maybe it's a trivial question... > >If I had two lines to the Internet: how would I use both? > >Could I just provide two default routes? How? > >What algorithm would be used to choose among the two? > >What if one failed? > > > > bye & Thanks > > av. > > > > > > > >_______________________________________________ > >freebsd-net@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-net > >To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" -- ****** JFRH ****** "If a camel flies, no one laughs if it doesn't get very far." -- Paul White From owner-freebsd-net@FreeBSD.ORG Fri Jan 23 12:02:47 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 B65C916A4CE for ; Fri, 23 Jan 2004 12:02:47 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E62043D39 for ; Fri, 23 Jan 2004 12:02:43 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.3) with ESMTP id i0NK2daT005875 for ; Fri, 23 Jan 2004 12:02:39 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i0NK2dDC005872 for net@freebsd.org; Fri, 23 Jan 2004 12:02:39 -0800 Date: Fri, 23 Jan 2004 12:02:38 -0800 From: Brooks Davis To: net@freebsd.org Message-ID: <20040123200238.GA3133@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu Subject: review request: interface renaming patch 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: Fri, 23 Jan 2004 20:02:47 -0000 The following patch implements network interface renaming via: ifconfig name The mechanism is to change if_xname in the ifp and then to adjust the link level address sockaddr_dl appropriatly. One question I do have is if locking the ifa is sufficent or if we need to force the user to down the interface before renaming it. I'm not sure where all the places that use the sockaddr_dl are. The patch is split into cleanups that apply to the tree regardless of this functional change and the actual functional changes. You will need to use "patch -p2" to apply the patch due to they way I generated it =66rom my perforce trees. Please let me know about both problem with the patch it self and any edge cases where chaning the interface name will cause problems (for instance, I just noticed a minor problem in if_clone_create where you could end up with duplicate interfaces names.) Thanks, Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 *** Cleanup diffs *** --- ../freebsd/sbin/ifconfig/ifconfig.c Wed Oct 29 10:24:27 2003 +++ ../cleanup/sbin/ifconfig/ifconfig.c Fri Jan 23 10:44:54 2004 @@ -113,7 +113,7 @@ struct sockaddr_in netmask; struct netrange at_nr; /* AppleTalk net range */ =20 -char name[32]; +char name[IFNAMSIZ]; int flags; int setaddr; int setipdst; @@ -596,8 +596,9 @@ addrcount++; next +=3D nextifm->ifm_msglen; } - strncpy(name, sdl->sdl_data, sdl->sdl_nlen); - name[sdl->sdl_nlen] =3D '\0'; + strlcpy(name, sdl->sdl_data, + sizeof(name) <=3D sdl->sdl_nlen ? + sizeof(name) : sdl->sdl_nlen + 1); =20 if (all || namesonly) { if (uponly) --- ../freebsd/sbin/ifconfig/ifconfig.h Thu Oct 9 18:23:30 2003 +++ ../cleanup/sbin/ifconfig/ifconfig.h Fri Jan 23 10:44:54 2004 @@ -36,7 +36,7 @@ =20 extern struct ifreq ifr; =20 -extern char name[32]; /* name of interface */ +extern char name[IFNAMSIZ]; /* name of interface */ extern int allmedia; extern int supmedia; struct afswtch; --- ../freebsd/sys/net/if.c Fri Jan 23 09:26:48 2004 +++ ../cleanup/sys/net/if.c Fri Jan 23 10:21:15 2004 @@ -410,36 +410,34 @@ * create a Link Level name for this device */ namelen =3D strlen(ifp->if_xname); -#define _offsetof(t, m) ((int)((caddr_t)&((t *)0)->m)) - masklen =3D _offsetof(struct sockaddr_dl, sdl_data[0]) + namelen; + masklen =3D offsetof(struct sockaddr_dl, sdl_data[0]) + namelen; socksize =3D masklen + ifp->if_addrlen; #define ROUNDUP(a) (1 + (((a) - 1) | (sizeof(long) - 1))) if (socksize < sizeof(*sdl)) socksize =3D sizeof(*sdl); socksize =3D ROUNDUP(socksize); +#undef ROUNDUP ifasize =3D sizeof(*ifa) + 2 * socksize; - ifa =3D (struct ifaddr *)malloc(ifasize, M_IFADDR, M_WAITOK | M_ZERO); - if (ifa) { - IFA_LOCK_INIT(ifa); - sdl =3D (struct sockaddr_dl *)(ifa + 1); - sdl->sdl_len =3D socksize; - sdl->sdl_family =3D AF_LINK; - bcopy(ifp->if_xname, sdl->sdl_data, namelen); - sdl->sdl_nlen =3D namelen; - sdl->sdl_index =3D ifp->if_index; - sdl->sdl_type =3D ifp->if_type; - ifaddr_byindex(ifp->if_index) =3D ifa; - ifa->ifa_ifp =3D ifp; - ifa->ifa_rtrequest =3D link_rtrequest; - ifa->ifa_addr =3D (struct sockaddr *)sdl; - sdl =3D (struct sockaddr_dl *)(socksize + (caddr_t)sdl); - ifa->ifa_netmask =3D (struct sockaddr *)sdl; - sdl->sdl_len =3D masklen; - while (namelen !=3D 0) - sdl->sdl_data[--namelen] =3D 0xff; - ifa->ifa_refcnt =3D 1; - TAILQ_INSERT_HEAD(&ifp->if_addrhead, ifa, ifa_link); - } + ifa =3D malloc(ifasize, M_IFADDR, M_WAITOK | M_ZERO); + IFA_LOCK_INIT(ifa); + sdl =3D (struct sockaddr_dl *)(ifa + 1); + sdl->sdl_len =3D socksize; + sdl->sdl_family =3D AF_LINK; + bcopy(ifp->if_xname, sdl->sdl_data, namelen); + sdl->sdl_nlen =3D namelen; + sdl->sdl_index =3D ifp->if_index; + sdl->sdl_type =3D ifp->if_type; + ifaddr_byindex(ifp->if_index) =3D ifa; + ifa->ifa_ifp =3D ifp; + ifa->ifa_rtrequest =3D link_rtrequest; + ifa->ifa_addr =3D (struct sockaddr *)sdl; + sdl =3D (struct sockaddr_dl *)(socksize + (caddr_t)sdl); + ifa->ifa_netmask =3D (struct sockaddr *)sdl; + sdl->sdl_len =3D masklen; + while (namelen !=3D 0) + sdl->sdl_data[--namelen] =3D 0xff; + ifa->ifa_refcnt =3D 1; + TAILQ_INSERT_HEAD(&ifp->if_addrhead, ifa, ifa_link); ifp->if_broadcastaddr =3D 0; /* reliably crash if used uninitialized */ =20 if (domains) *** Functional diffs *** --- ../cleanup/sbin/ifconfig/ifconfig.8 Fri Jan 23 09:36:11 2004 +++ sbin/ifconfig/ifconfig.8 Fri Jan 23 10:58:58 2004 @@ -322,6 +322,9 @@ and 802.11g .Pq Dq 11g operating modes. +.It Cm name Ar name +Set the interface name to +.Ar name . .It Cm rxcsum , txcsum If the driver supports user-configurable checksum offloading, enable receive (or transmit) checksum offloading on the interface. @@ -353,7 +356,10 @@ If the interface is given without a unit number, try to create a new device with an arbitrary unit number. If creation of an arbitrary device is successful, the new device name is -printed to standard output. +printed to standard output unless the interface is renamed or destroyed +in the same +.Nm +invocation. .It Cm destroy Destroy the specified network pseudo-device. .It Cm plumb --- ../cleanup/sbin/ifconfig/ifconfig.c Fri Jan 23 10:44:54 2004 +++ sbin/ifconfig/ifconfig.c Fri Jan 23 10:58:58 2004 @@ -129,6 +129,7 @@ =20 int supmedia =3D 0; int listcloners =3D 0; +int printname =3D 0; /* Print the name of the created interface. */ =20 #ifdef INET6 char addr_buf[MAXHOSTNAMELEN *2 + 1]; /*for getnameinfo()*/ @@ -172,6 +173,7 @@ c_func setifipdst; c_func setifflags, setifmetric, setifmtu, setifcap; c_func clone_destroy; +c_func setifname; =20 =20 void clone_create(void); @@ -286,6 +288,7 @@ { "compress", IFF_LINK0, setifflags }, { "noicmp", IFF_LINK1, setifflags }, { "mtu", NEXTARG, setifmtu }, + { "name", NEXTARG, setifname }, { 0, 0, setifaddr }, { 0, 0, setifdstaddr }, }; @@ -525,7 +528,7 @@ clone_create(); argc--, argv++; if (argc =3D=3D 0) - exit(0); + goto end; } ifindex =3D if_nametoindex(name); if (ifindex =3D=3D 0) @@ -629,6 +632,9 @@ =20 if (namesonly && need_nl > 0) putchar('\n'); +end: + if (printname) + printf("%s\n", name); =20 exit (0); } @@ -1037,6 +1043,30 @@ warn("ioctl (set mtu)"); } =20 +void +setifname(const char *val, int dummy __unused, int s,=20 + const struct afswtch *afp) +{ + char *newname; + + newname =3D strdup(val); + + ifr.ifr_data =3D newname; + if (ioctl(s, SIOCSIFNAME, (caddr_t)&ifr) < 0) { + warn("ioctl (set name)"); + free(newname); + return; + } + strlcpy(name, newname, sizeof(name)); + free(newname); + + /* + * Even if we just created the interface, we don't need to print + * its name because we just nailed it down separately. + */ + printname =3D 0; +} + #define IFFBITS \ "\020\1UP\2BROADCAST\3DEBUG\4LOOPBACK\5POINTOPOINT\6SMART\7RUNNING" \ "\10NOARP\11PROMISC\12ALLMULTI\13OACTIVE\14SIMPLEX\15LINK0\16LINK1\17LINK2= " \ @@ -1883,8 +1913,13 @@ if (ioctl(s, SIOCIFCREATE, &ifr) < 0) err(1, "SIOCIFCREATE"); =20 + /* + * If we get a different name back then we put in, we probably + * want to print it out, but we might change our mind later so + * we just signal our intrest and leave the printout for later. + */ if (strcmp(name, ifr.ifr_name) !=3D 0) { - printf("%s\n", ifr.ifr_name); + printname =3D 1; strlcpy(name, ifr.ifr_name, sizeof(name)); } =20 @@ -1898,4 +1933,9 @@ (void) strncpy(ifr.ifr_name, name, sizeof(ifr.ifr_name)); if (ioctl(s, SIOCIFDESTROY, &ifr) < 0) err(1, "SIOCIFDESTROY"); + /* + * If we create and destroy an interface in the same command, + * there isn't any reason to print it's name. + */ + printname =3D 0; } --- ../cleanup/sys/net/if.c Fri Jan 23 10:21:15 2004 +++ sys/net/if.c Fri Jan 23 10:24:19 2004 @@ -410,7 +410,11 @@ * create a Link Level name for this device */ namelen =3D strlen(ifp->if_xname); - masklen =3D offsetof(struct sockaddr_dl, sdl_data[0]) + namelen; + /* + * Always save enough space for any possiable name so we can do + * a rename in place later. + */ + masklen =3D offsetof(struct sockaddr_dl, sdl_data[0]) + IFNAMSIZ; socksize =3D masklen + ifp->if_addrlen; #define ROUNDUP(a) (1 + (((a) - 1) | (sizeof(long) - 1))) if (socksize < sizeof(*sdl)) @@ -733,17 +737,16 @@ int bytoff, bitoff; int unit; =20 - ifc =3D if_clone_lookup(name, &unit); - if (ifc =3D=3D NULL) - return (EINVAL); - - if (unit < ifc->ifc_minifs) - return (EINVAL); - ifp =3D ifunit(name); if (ifp =3D=3D NULL) return (ENXIO); =20 + unit =3D ifp->if_dunit; + + ifc =3D if_clone_lookup(ifp->if_dname, NULL); + if (ifc =3D=3D NULL) + return (EINVAL); + if (ifc->ifc_destroy =3D=3D NULL) return (EOPNOTSUPP); =20 @@ -1228,25 +1231,11 @@ struct ifnet * ifunit(const char *name) { - char namebuf[IFNAMSIZ + sizeof("net")]; /* XXX net_cdevsw.d_name */ struct ifnet *ifp; - dev_t dev; - - /* - * Now search all the interfaces for this name/number - */ =20 - /* - * XXX - * Devices should really be known as /dev/fooN, not /dev/net/fooN. - */ - snprintf(namebuf, sizeof(namebuf), "%s/%s", net_cdevsw.d_name, name); IFNET_RLOCK(); TAILQ_FOREACH(ifp, &ifnet, if_link) { - dev =3D ifdev_byindex(ifp->if_index); - if (strcmp(devtoname(dev), namebuf) =3D=3D 0) - break; - if (dev_named(dev, name)) + if (strncmp(name, ifp->if_xname, IFNAMSIZ) =3D=3D 0) break; } IFNET_RUNLOCK(); @@ -1289,6 +1278,10 @@ struct ifstat *ifs; int error =3D 0; int new_flags; + size_t namelen, onamelen; + char new_name[IFNAMSIZ]; + struct ifaddr *ifa; + struct sockaddr_dl *sdl; =20 ifr =3D (struct ifreq *)data; switch (cmd) { @@ -1370,6 +1363,39 @@ error =3D mac_ioctl_ifnet_set(td->td_ucred, ifr, ifp); break; #endif + + case SIOCSIFNAME: + error =3D suser(td); + if (error) + return (error); + error =3D copyinstr(ifr->ifr_data, new_name, IFNAMSIZ, NULL); + if (error) + return (error); + if (ifunit(new_name) !=3D NULL) + return (EEXIST); + strlcpy(ifp->if_xname, new_name, sizeof(ifp->if_xname)); + ifa =3D TAILQ_FIRST(&ifp->if_addrhead); + IFA_LOCK(ifa); + sdl =3D (struct sockaddr_dl *)ifa->ifa_addr; + namelen =3D strlen(new_name); + onamelen =3D sdl->sdl_nlen; + /* + * Move the address if needed. This is safe because we + * allocate space for a name of length IFNAMSIZ when we + * create this in if_attach(). + */ + if (namelen !=3D onamelen) { + bcopy(sdl->sdl_data + onamelen, + sdl->sdl_data + namelen, sdl->sdl_alen); + } + bcopy(new_name, sdl->sdl_data, namelen); + sdl->sdl_nlen =3D namelen; + sdl =3D (struct sockaddr_dl *)ifa->ifa_netmask; + bzero(sdl->sdl_data, onamelen); + while (namelen !=3D 0) + sdl->sdl_data[--namelen] =3D 0xff; + IFA_UNLOCK(ifa); + break; =20 case SIOCSIFMETRIC: error =3D suser(td); --- ../cleanup/sys/sys/sockio.h Fri Jan 23 09:38:05 2004 +++ sys/sys/sockio.h Mon Dec 8 12:03:32 2003 @@ -82,6 +82,7 @@ #define SIOCGIFINDEX _IOWR('i', 32, struct ifreq) /* get IF index */ #define SIOCGIFMAC _IOWR('i', 38, struct ifreq) /* get IF MAC label */ #define SIOCSIFMAC _IOW('i', 39, struct ifreq) /* set IF MAC label */ +#define SIOCSIFNAME _IOW('i', 40, struct ifreq) /* set IF name */ =20 #define SIOCADDMULTI _IOW('i', 49, struct ifreq) /* add m'cast addr */ #define SIOCDELMULTI _IOW('i', 50, struct ifreq) /* del m'cast addr */ From owner-freebsd-net@FreeBSD.ORG Fri Jan 23 17:57:33 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 E0A3B16A4CE for ; Fri, 23 Jan 2004 17:57:33 -0800 (PST) Received: from exchange.wan.no (exchange.wan.no [80.86.128.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16CE143D41 for ; Fri, 23 Jan 2004 17:57:31 -0800 (PST) (envelope-from sten.daniel.sorsdal@wan.no) Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Sat, 24 Jan 2004 02:57:29 +0100 Message-ID: <0AF1BBDF1218F14E9B4CCE414744E70F5D999B@exchange.wanglobal.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: DHCP and multiple vlans thread-index: AcPg7Wc32Uh/X2QyTvCmEFEla0bmpQBKauQg From: =?iso-8859-1?Q?Sten_Daniel_S=F8rsdal?= To: "Guy Antony Halse" , Subject: RE: DHCP and multiple vlans 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: Sat, 24 Jan 2004 01:57:34 -0000 > I'm trying to configure a FreeBSD 5.1-RELEASE system to act=20 > as the default gateway for several virtual lans. I've got=20 > two NICs in the box, one which supplies the uplink, and one=20 > which has about 40 vlan(4) vlans on it. >=20 > I was trying to run isc-dhcp3's dhcrelay to relay DHCP=20 > messages to our DHCP server when I ran into a problem. Only=20 > the first ten vlans (vlan0 through > vlan9) are serviced by dhcrelay. >=20 It's a limitation in the isc-dhcp software, AFAIK. If my memory serves me correctly you can try something along these = lines; # cd /usr/ports/net/isc-dhcp3-server # make patch now edit work/dhcp-3.0.1rc12/common/discover.c at line 138 or so there should be "char buf[2048]" change 2048 into for example 16384. # make build install assuming you are building on your gateway. _// Sten Daniel S=F8rsdal From owner-freebsd-net@FreeBSD.ORG Sat Jan 24 03:33:58 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 4984216A4CE for ; Sat, 24 Jan 2004 03:33:58 -0800 (PST) Received: from king.suceava.rdsnet.ro (king.suceava.rdsnet.ro [62.231.118.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7C3343D1F for ; Sat, 24 Jan 2004 03:33:55 -0800 (PST) (envelope-from ady@freebsd.ady.ro) Received: from datacenter.office.suceava.rdsnet.ro (datacenter.office.suceava.rdsnet.ro [217.156.25.194])i0OBXs3U013971 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 24 Jan 2004 13:33:54 +0200 Received: from sunny.home.ady.ro ([82.208.147.127])id i0OBWXa8025156 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 24 Jan 2004 13:33:52 +0200 (EET) (envelope-from ady@freebsd.ady.ro) Date: Sat, 24 Jan 2004 13:32:28 +0200 (EET) From: Adrian Penisoara X-X-Sender: ady@sunny.home.ady.ro To: freebsd-net@freebsd.org Message-ID: <20040124132053.S1830@sunny.home.ady.ro> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-RAVMilter-Version: 8.4.2(snapshot 20021212) (datacenter.office.suceava.rdsnet.ro) Subject: vlan(4)/bridge(4) interaction ? 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: Sat, 24 Jan 2004 11:33:58 -0000 Hi, I recently made a test bridging a few VLAN interfaces under FreeBSD 5.2-REL and ran into some unexpected issue: some packets coming from one vlan inteface with destination MAC on another vlan would pass in the parent VLAN interface, but didn't make it into the child vlan interface, as seen by tcpdump'ing on both of them. Like the packet was eaten before it made it into the child vlan interface. Activating the debug code shows that neither the bridge fordwarding routine wasn't catching the packets. All vlans were child of the same parent interface (a RealTek) and they were all configuren in the same bridge cluster. Either with configured IPs or without (just up'ed the intefaces). I might have botched the interfaces by mutiple reconfigurations, but I just would like to know if other people had success with bridged VLAN interfaces (yes, it sounds a bit weird if you think of it :) ). -- Adrian Penisoara Ady (@freebsd,ady.ro) From owner-freebsd-net@FreeBSD.ORG Sat Jan 24 03:42:56 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 3CE7F16A4CE for ; Sat, 24 Jan 2004 03:42:56 -0800 (PST) Received: from relay.macomnet.ru (relay.macomnet.ru [195.128.64.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 743F343D1D for ; Sat, 24 Jan 2004 03:42:54 -0800 (PST) (envelope-from maxim@macomnet.ru) Received: from news1.macomnet.ru (kr2mbdxi@news1.macomnet.ru [195.128.64.14]) by relay.macomnet.ru (8.12.10/8.12.10) with ESMTP id i0OBgpo24528575; Sat, 24 Jan 2004 14:42:51 +0300 (MSK) Date: Sat, 24 Jan 2004 14:42:51 +0300 (MSK) From: Maxim Konovalov To: Adrian Penisoara In-Reply-To: <20040124132053.S1830@sunny.home.ady.ro> Message-ID: <20040124144230.S29370@news1.macomnet.ru> References: <20040124132053.S1830@sunny.home.ady.ro> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: vlan(4)/bridge(4) interaction ? 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: Sat, 24 Jan 2004 11:42:56 -0000 On Sat, 24 Jan 2004, 13:32+0200, Adrian Penisoara wrote: > Hi, > > I recently made a test bridging a few VLAN interfaces under FreeBSD > 5.2-REL and ran into some unexpected issue: some packets coming from one > vlan inteface with destination MAC on another vlan would pass in the > parent VLAN interface, but didn't make it into the child vlan interface, > as seen by tcpdump'ing on both of them. Like the packet was eaten before > it made it into the child vlan interface. Activating the debug code > shows that neither the bridge fordwarding routine wasn't catching the > packets. > > All vlans were child of the same parent interface (a RealTek) and they > were all configuren in the same bridge cluster. Either with configured > IPs or without (just up'ed the intefaces). > > I might have botched the interfaces by mutiple reconfigurations, but I > just would like to know if other people had success with bridged VLAN > interfaces (yes, it sounds a bit weird if you think of it :) ). Try this: Index: if_ethersubr.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_ethersubr.c,v retrieving revision 1.155 diff -u -r1.155 if_ethersubr.c --- if_ethersubr.c 14 Nov 2003 21:02:22 -0000 1.155 +++ if_ethersubr.c 17 Jan 2004 10:12:54 -0000 @@ -627,6 +627,7 @@ if (rule) /* packet was already bridged */ goto post_stats; +#if 0 if (!(BDG_ACTIVE(ifp))) { /* * Discard packet if upper layers shouldn't see it because it @@ -643,6 +644,7 @@ return; } } +#endif /* Discard packet if interface is not up */ if ((ifp->if_flags & IFF_UP) == 0) { %%% -- Maxim Konovalov, maxim@macomnet.ru, maxim@FreeBSD.org From owner-freebsd-net@FreeBSD.ORG Sat Jan 24 10:46:05 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 3000716A4CF for ; Sat, 24 Jan 2004 10:46:05 -0800 (PST) Received: from clever.eusc.inter.net (clever.eusc.inter.net [213.73.101.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id DED6143D48 for ; Sat, 24 Jan 2004 10:46:03 -0800 (PST) (envelope-from msch@snafu.de) Received: from tc01-n71-160.de.inter.net ([213.73.71.160]) by clever.eusc.inter.net with esmtp (Exim 3.36 #4) id 1AkSnC-00020a-00 for freebsd-net@freebsd.org; Sat, 24 Jan 2004 19:46:02 +0100 From: Matthias Schuendehuette Organization: Micro$oft-free Zone To: freebsd-net@freebsd.org Date: Sat, 24 Jan 2004 19:46:00 +0100 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401241946.01311.msch@snafu.de> Subject: Bridging a 802.1Q VLAN-Trunk X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: msch@snafu.de List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2004 18:46:05 -0000 Hello, I have some difficulties to understand the bridge(4) man-page. I want to build a filtering bridge between two 802.1Q VLAN-Trunk interfaces and in the meantime I assume that I make some mistakes configuring the bridge... Actually I configured the bridge (for one VLAN only as an example) "bge0:1,bge1:1,vlan0:2,vlan1:2", where 'vlan0' has the parent interface 'bge0' and the same for index 1. But I'm uncertain, if this is correct. First, the man-page says, "By putting both physical and logical (vlan(4)) interfaces in the same cluster, a FreeBSD box can also implement what in commercial terms is called a ``trunk'' interface." I understand this as "bge0:1,bge1:1,vlan0:1,vlan1:1,...." Does this keep the several VLANs isolated from each other? Have the parent interfaces to be in there? Why? Or is my original configuration correct to put each VLANs vlan(4) interfaces in their own cluster? Again, have the parent interfaces to have their own cluster? Have they to appear anyway? In an example in bridge(4) I read they must not appear to avoid loops... I must admit, I'm a bit confused :-} Can anybody explain this more clearly to me? Thanks a lot - Matthias -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F