From owner-freebsd-net@FreeBSD.ORG Sun Sep 11 10:00:21 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 B9E2916A41F for ; Sun, 11 Sep 2005 10:00:21 +0000 (GMT) (envelope-from peter@dataloss.nl) Received: from useful.dataloss.nl (useful.dataloss.nl [80.84.249.161]) by mx1.FreeBSD.org (Postfix) with SMTP id 3EEFF43D45 for ; Sun, 11 Sep 2005 10:00:20 +0000 (GMT) (envelope-from peter@dataloss.nl) Received: (qmail 68025 invoked by uid 1001); 11 Sep 2005 10:00:18 -0000 Date: Sun, 11 Sep 2005 12:00:18 +0200 From: Peter van Dijk To: freebsd-net@freebsd.org Message-ID: <20050911100018.GR17888@dataloss.nl> References: <20050822223952.GA62234@dataloss.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050822223952.GA62234@dataloss.nl> User-Agent: Mutt/1.4i Subject: Re: freebsd 6-beta2, pf, route-to, checksum errors X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2005 10:00:21 -0000 On Tue, Aug 23, 2005 at 12:39:53AM +0200, Peter van Dijk wrote: > Hi, > > I recently upgraded my FreeBSD/sparc64 5.4 router at home to 6-BETA2, > without changing pf.conf. Since this upgrade, UDP packets redirected > with pf's route-to feature get the wrong checksum. This is still defective in FreeBSD 6-BETA4 on sparc64. Cheers, Peter -- peter@dataloss.nl | ~ tonight tonight, what is this potion http://blog.dataloss.nl/ | ~ that makes a fool of me UnderNet/#clue | Wayfinder, fr-025 soundtrack From owner-freebsd-net@FreeBSD.ORG Sun Sep 11 13:51:37 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 B05C316A41F; Sun, 11 Sep 2005 13:51:37 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F49543D49; Sun, 11 Sep 2005 13:51:37 +0000 (GMT) (envelope-from max@love2party.net) Received: from p54A3DDDF.dip.t-dialin.net [84.163.221.223] (helo=donor.laier.local) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0ML2ov-1EESF53tey-0003mt; Sun, 11 Sep 2005 15:51:35 +0200 From: Max Laier To: freebsd-net@freebsd.org Date: Sun, 11 Sep 2005 15:51:19 +0200 User-Agent: KMail/1.8.2 References: <20050822223952.GA62234@dataloss.nl> <20050911100018.GR17888@dataloss.nl> In-Reply-To: <20050911100018.GR17888@dataloss.nl> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1820515.j4jHtxOxhI"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200509111551.33738.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Peter van Dijk , yongari@freebsd.org Subject: Re: freebsd 6-beta2, pf, route-to, checksum errors X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2005 13:51:37 -0000 --nextPart1820515.j4jHtxOxhI Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 11 September 2005 12:00, Peter van Dijk wrote: > On Tue, Aug 23, 2005 at 12:39:53AM +0200, Peter van Dijk wrote: > > Hi, > > > > I recently upgraded my FreeBSD/sparc64 5.4 router at home to 6-BETA2, > > without changing pf.conf. Since this upgrade, UDP packets redirected > > with pf's route-to feature get the wrong checksum. > > This is still defective in FreeBSD 6-BETA4 on sparc64. Does your network card support checksum offloading? Does disabling it chan= ge=20 the situation? =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1820515.j4jHtxOxhI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDJDZlXyyEoT62BG0RArmXAJ42kQvU7J7RquMoT4AaH++7Ezot/QCeOHuN cLz+LFLZjsLF5lQfKsL5wJ4= =LcvE -----END PGP SIGNATURE----- --nextPart1820515.j4jHtxOxhI-- From owner-freebsd-net@FreeBSD.ORG Sun Sep 11 15:15:14 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 9EDCA16A41F for ; Sun, 11 Sep 2005 15:15:14 +0000 (GMT) (envelope-from peter@dataloss.nl) Received: from useful.dataloss.nl (useful.dataloss.nl [80.84.249.161]) by mx1.FreeBSD.org (Postfix) with SMTP id 0DBD043D45 for ; Sun, 11 Sep 2005 15:15:11 +0000 (GMT) (envelope-from peter@dataloss.nl) Received: (qmail 9347 invoked by uid 1001); 11 Sep 2005 15:15:10 -0000 Date: Sun, 11 Sep 2005 17:15:10 +0200 From: Peter van Dijk To: freebsd-net@freebsd.org Message-ID: <20050911151510.GT17888@dataloss.nl> References: <20050822223952.GA62234@dataloss.nl> <20050911100018.GR17888@dataloss.nl> <200509111551.33738.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200509111551.33738.max@love2party.net> User-Agent: Mutt/1.4i Subject: Re: freebsd 6-beta2, pf, route-to, checksum errors X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2005 15:15:14 -0000 On Sun, Sep 11, 2005 at 03:51:19PM +0200, Max Laier wrote: > Does your network card support checksum offloading? Does disabling it change > the situation? Interfaces are vlanX on an fxp. As far as I know fxp doesn't do checksum offloading. Setting LINK0 (load microcode for reducing interrupt load, according to the manpage) makes no difference either. Cheers, Peter -- peter@dataloss.nl | ~ tonight tonight, what is this potion http://blog.dataloss.nl/ | ~ that makes a fool of me UnderNet/#clue | Wayfinder, fr-025 soundtrack From owner-freebsd-net@FreeBSD.ORG Sun Sep 11 22:48:28 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 9E3A016A41F for ; Sun, 11 Sep 2005 22:48:28 +0000 (GMT) (envelope-from spork@bway.net) Received: from mail.bway.net (xena.bway.net [216.220.96.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B4C943D46 for ; Sun, 11 Sep 2005 22:48:27 +0000 (GMT) (envelope-from spork@bway.net) Received: (qmail 46630 invoked by uid 0); 11 Sep 2005 22:48:26 -0000 Received: from unknown (HELO white.nat.fasttrackmonkey.com) (spork@bway.net@216.220.116.154) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 11 Sep 2005 22:48:26 -0000 Date: Sun, 11 Sep 2005 18:48:25 -0400 (EDT) From: Charles Sprickman X-X-Sender: spork@white.nat.fasttrackmonkey.com To: "Julian H. Stacey" In-Reply-To: <200509100930.j8A9UoHN062107@fire.jhs.private> Message-ID: References: <200509100930.j8A9UoHN062107@fire.jhs.private> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: PPPoE and UDP fragmentation X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2005 22:48:28 -0000 On Sat, 10 Sep 2005, Julian H. Stacey wrote: >> -Are there any tunables at either end (both hosts are FreeBSD 4.11 p11) to >> alter how fragmented packets are re-assembled? > > /usr/ports/net/tcpmssd > An MTU adapter. Apparently not needed on FreeBSD-5 but I mean to > install it on my FreeBSD-4 DSL gateways when I find time to think if it might > have any implications re ipfw & security. I don't think that does anything to UDP, it just digs into tcp and "fixes up" the MSS by altering it on outgoing packets. I'm looking to further understand UDP fragmentation and why a host might ignore fragments, and who along the way is actually doing the fragmentation. My current "fix" is just to set the interface MTU on the sending box to 1492, and that works well, but I'd really like to understand why it fails without that. Thanks! Charles > -- > Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com > Mail Ascii not HTML. Ihr Rauch = meine allergischen Kopfschmerzen. > From owner-freebsd-net@FreeBSD.ORG Sun Sep 11 23:38:23 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 AF79516A41F for ; Sun, 11 Sep 2005 23:38:23 +0000 (GMT) (envelope-from gcorcoran@rcn.com) Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D4BE43D46 for ; Sun, 11 Sep 2005 23:38:23 +0000 (GMT) (envelope-from gcorcoran@rcn.com) Received: from 207-172-224-47.c3-0.tlg-ubr1.atw-tlg.pa.cable.rcn.com (HELO [10.56.78.168]) ([207.172.224.47]) by smtp02.mrf.mail.rcn.net with ESMTP; 11 Sep 2005 19:38:22 -0400 X-IronPort-AV: i="3.97,97,1125892800"; d="scan'208"; a="84083582:sNHT23110514" Message-ID: <4324C389.5010001@rcn.com> Date: Sun, 11 Sep 2005 19:53:45 -0400 From: Gary Corcoran User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Charles Sprickman References: <200509100930.j8A9UoHN062107@fire.jhs.private> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, "Julian H. Stacey" Subject: Re: PPPoE and UDP fragmentation X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2005 23:38:23 -0000 Charles Sprickman wrote: > On Sat, 10 Sep 2005, Julian H. Stacey wrote: > >>> -Are there any tunables at either end (both hosts are FreeBSD 4.11 >>> p11) to >>> alter how fragmented packets are re-assembled? >> >> >> /usr/ports/net/tcpmssd >> An MTU adapter. Apparently not needed on FreeBSD-5 but I mean to >> install it on my FreeBSD-4 DSL gateways when I find time to think if >> it might >> have any implications re ipfw & security. > > > I don't think that does anything to UDP, it just digs into tcp and > "fixes up" the MSS by altering it on outgoing packets. I'm looking to > further understand UDP fragmentation and why a host might ignore > fragments, and who along the way is actually doing the fragmentation. > > My current "fix" is just to set the interface MTU on the sending box to > 1492, and that works well, but I'd really like to understand why it > fails without that. Do you know about the horribly-large overhead that PPPoE adds? It's about 36 bytes, if I recall. So to keep the *total* ethernet frame size under the max limit of 1500-something (don't recall exact number), you *always* have to limit *any* frame size, before PPPoE overhead, to 1492 bytes. Does this help? Gary From owner-freebsd-net@FreeBSD.ORG Mon Sep 12 10:49:36 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 3B57D16A41F for ; Mon, 12 Sep 2005 10:49:36 +0000 (GMT) (envelope-from bsd-daemon@spray.se) Received: from lmfilto01.st1.spray.net (lmfilto01.st1.spray.net [212.78.202.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 554AF43D45 for ; Mon, 12 Sep 2005 10:49:34 +0000 (GMT) (envelope-from bsd-daemon@spray.se) Received: from localhost (localhost [127.0.0.1]) by lmfilto01.st1.spray.net (Postfix) with ESMTP id 59E2D1E3282 for ; Mon, 12 Sep 2005 10:49:33 +0000 (GMT) Received: from lmcodec02.st1.spray.net ([212.78.202.56]) by localhost (lmfilto01.st1.spray.net [212.78.202.32]) (amavisd-new, port 10024) with ESMTP id 14920-03 for ; Mon, 12 Sep 2005 10:49:33 +0000 (GMT) Received: from lmcodec02.st1.spray.net (localhost [127.0.0.1]) by lmcodec02.st1.spray.net (Postfix) with SMTP id 2EDC3AB206 for ; Mon, 12 Sep 2005 10:49:33 +0000 (GMT) Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=spray.se; h=From:Subject; b=RAS//C4bvt8tt3nou4oI+a7BSX3qPPWtA8RTYOd50J1k+IwUsMbBD9uRmGnM2g+n/fEqZILqNDJx91Wu8EudIrfUErCYkXf+xKrgIhy5yQSFr5gjCONMKqCLqyrld60kagS57HPeXo1TJ5MFEhbUnhpCW9RSm+jElUdlTvmA8N8=; From: "G B" To: freebsd-net@freebsd.org Message-ID: <17691085124991@lycos-europe.com> X-Mailer: LycosMail X-Priority: 3 X-Originating-IP: 213.199.67.100 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=_NextPart_Lycos_49911769108513_ID" Date: Mon, 12 Sep 2005 10:49:33 +0000 (GMT) X-Virus-Scanned: by amavisd-new at spray.net Subject: pptpclient vpn connection with FreeBSD 6.0-BETA4 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2005 10:49:36 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --=_NextPart_Lycos_49911769108513_ID Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Hello all, I'm trying to connect a FreeBSD client computer to a Watchguard company firewall that only has PPTP VPN connectivity. # uname -sr FreeBSD 6.0-BETA4 pptpclient 1.7.0 + patch-aa and patch-ac from ports (also tried the older 1.5.0 from ports) /etc/ppp/ppp.conf company: set authname username set authkey password set timeout 0 set ifaddr 0 0 add 192.168.100.0/24 HISADDR disable ipv6cp /var/log/messages Sep 12 11:35:30 thinkpad pptp[819]: anon log[main:pptp.c:267]: The synchronous pptp option is NOT activated Sep 12 11:35:30 thinkpad pptp[822]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Sep 12 11:35:30 thinkpad pptp[822]: anon log[ctrlp_disp:pptp_ctrl.c:738]: Received Start Control Connection Reply Sep 12 11:35:30 thinkpad pptp[822]: anon log[ctrlp_disp:pptp_ctrl.c:772]: Client connection established. Sep 12 11:35:31 thinkpad pptp[822]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request' Sep 12 11:35:31 thinkpad pptp[822]: anon log[ctrlp_disp:pptp_ctrl.c:857]: Received Outgoing Call Reply. Sep 12 11:35:31 thinkpad pptp[822]: anon log[ctrlp_disp:pptp_ctrl.c:896]: Outgoing call established (call ID 0, peer's call ID 1). Sep 12 11:35:34 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 1 Sep 12 11:35:34 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 2 Sep 12 11:35:34 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 3 Sep 12 11:35:34 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 4 Sep 12 11:35:34 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 5 Sep 12 11:35:34 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 6 Sep 12 11:35:35 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 7 Sep 12 11:35:35 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 8 Sep 12 11:35:35 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 9 Sep 12 11:35:35 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 10 Sep 12 11:35:35 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 11 Sep 12 11:35:35 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 12 Sep 12 11:35:35 thinkpad pptp[823]: anon log[decaps_gre:pptp_gre.c:388]: accepting packet 13 Sep 12 11:36:31 thinkpad pptp[822]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received. Sep 12 11:37:31 thinkpad pptp[822]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received. Sep 12 11:39:31 thinkpad last message repeated 2 times /var/log/ppp.log Sep 12 11:35:32 thinkpad ppp[819]: Phase: Using interface: tun0 Sep 12 11:35:32 thinkpad ppp[819]: Phase: deflink: Created in closed state Sep 12 11:35:32 thinkpad ppp[819]: Phase: PPP Started (direct mode). Sep 12 11:35:32 thinkpad ppp[819]: Phase: bundle: Establish Sep 12 11:35:32 thinkpad ppp[819]: Phase: deflink: closed -> opening Sep 12 11:35:32 thinkpad ppp[819]: Phase: deflink: Connected! Sep 12 11:35:32 thinkpad ppp[819]: Phase: deflink: opening -> carrier Sep 12 11:35:33 thinkpad ppp[819]: Phase: deflink: carrier -> lcp Sep 12 11:35:34 thinkpad ppp[819]: Phase: bundle: Authenticate Sep 12 11:35:34 thinkpad ppp[819]: Phase: deflink: his = CHAP 0x81, mine = none Sep 12 11:35:34 thinkpad ppp[819]: Phase: Chap Input: CHALLENGE (16 bytes from watchguard) Sep 12 11:35:34 thinkpad ppp[819]: Phase: Chap Output: RESPONSE (username) Sep 12 11:35:34 thinkpad ppp[819]: Phase: Chap Input: SUCCESS (S=XXXXXXXXXXXXXXXXXXXXXXXXX) Sep 12 11:35:34 thinkpad ppp[819]: Phase: deflink: lcp -> open Sep 12 11:35:34 thinkpad ppp[819]: Phase: bundle: Network # ifconfig tun0 tun0: flags=8051 mtu 336 inet 192.168.100.242 --> 192.168.100.1 netmask 0xffffffff Opened by PID 819 # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 213.199.xx.xx UGS 0 81 fxp0 127.0.0.1 127.0.0.1 UH 0 10 lo0 192.168.100 192.168.100.1 UGS 0 12 tun0 192.168.100.1 192.168.100.242 UH 1 18 tun0 213.199.xx link#2 UC 0 0 fxp0 213.199.xx.xx 00:00:0c:xx:xx:xx UHLW 2 0 fxp0 577 So the tunnel seems to be up, but there seems to be no traffic reaching the other side: # ping 192.168.100.1 PING 192.168.100.1 (192.168.100.1): 56 data bytes ^C --- 192.168.100.1 ping statistics --- 6 packets transmitted, 0 packets received, 100% packet loss Is pptp broken on FreeBSD 6.x or is there another problem? FWIW the connection works from another computer running Mac OS X 10.3 --=_NextPart_Lycos_49911769108513_ID-- From owner-freebsd-net@FreeBSD.ORG Mon Sep 12 11:02:07 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 F156C16A41F for ; Mon, 12 Sep 2005 11:02:07 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB34143D46 for ; Mon, 12 Sep 2005 11:02:07 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j8CB27ls025510 for ; Mon, 12 Sep 2005 11:02:07 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j8CB266N025504 for freebsd-net@freebsd.org; Mon, 12 Sep 2005 11:02:06 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 12 Sep 2005 11:02:06 GMT Message-Id: <200509121102.j8CB266N025504@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 Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2005 11:02:08 -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] [patch] NFS root configurations wit 1 problem total. From owner-freebsd-net@FreeBSD.ORG Mon Sep 12 13:19:53 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 B345716A41F for ; Mon, 12 Sep 2005 13:19:53 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 609ED43D68 for ; Mon, 12 Sep 2005 13:19:50 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from 217-13-2-82.dd.nextgentel.com ([217.13.2.82] helo=lapdance.yazzy.net) by mail.yazzy.org with esmtps (TLSv1:AES256-SHA:256) (YazzY.org) id 1EEoDM-0000dV-Fp for freebsd-net@freebsd.org; Mon, 12 Sep 2005 15:19:17 +0200 Date: Mon, 12 Sep 2005 13:19:21 +0000 From: Marcin Jessa To: FreeBSD-net Message-Id: <20050912131921.52d61a79.lists@yazzy.org> Organization: YazzY.org X-Mailer: Sylpheed version 2.0.1 (GTK+ 2.6.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.5 (--) Subject: Bridging and divert X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2005 13:19:53 -0000 Hi guys. Is there a trick to make bridge work with divert ? I know man bridge says "...some ipfw(8) actions such as divert do not apply to bridged packets." What I want to do is to send traffic to the port of my process to be processesed there and then bridge the traffic. Is something like thay maybe possible with pf or ipf ? Cheers, Marcin. From owner-freebsd-net@FreeBSD.ORG Tue Sep 13 03:52:11 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 35EAF16A41F for ; Tue, 13 Sep 2005 03:52:11 +0000 (GMT) (envelope-from on@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC0D543D45 for ; Tue, 13 Sep 2005 03:52:06 +0000 (GMT) (envelope-from on@cs.ait.ac.th) Received: from banyan.cs.ait.ac.th (banyan.cs.ait.ac.th [192.41.170.5]) by mail.cs.ait.ac.th (8.12.11/8.12.11) with ESMTP id j8D3pVlr000300 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Sep 2005 10:51:31 +0700 (ICT) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.13.1/8.12.11) id j8D2LRW7083379; Tue, 13 Sep 2005 09:21:27 +0700 (ICT) Date: Tue, 13 Sep 2005 09:21:27 +0700 (ICT) Message-Id: <200509130221.j8D2LRW7083379@banyan.cs.ait.ac.th> From: Olivier Nicole To: lists@yazzy.org In-reply-to: <20050912131921.52d61a79.lists@yazzy.org> (message from Marcin Jessa on Mon, 12 Sep 2005 13:19:21 +0000) References: <20050912131921.52d61a79.lists@yazzy.org> X-Virus-Scanned: on CSIM by amavisd-milter (http://www.amavis.org/) Cc: freebsd-net@freebsd.org Subject: Re: Bridging and divert X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2005 03:52:11 -0000 > Is there a trick to make bridge work with divert ? I use ipf not ipfw. Divert I think is same as redirection. What I found out is: 1) firewall applies only to incoming packets (while I think it should apply to incoming and outgoing) so only half the rules applies, and the revert rule of an a redirection will never apply. 2) the IP packet is modified OK, but the Ethernet frame that encl;ose the packet is not modified, so whatever the IP says, the packet will be delivered to the same old MAC address. > Is something like thay maybe possible with pf or ipf ? Modify /sys/net/bridge.c (good luck!) Olivier From owner-freebsd-net@FreeBSD.ORG Tue Sep 13 12:07:32 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 D7E9016A41F for ; Tue, 13 Sep 2005 12:07:32 +0000 (GMT) (envelope-from admin@zedis.lv) Received: from mail.zedis.lv (mail.zedis.lv [80.249.195.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id A40D643D60 for ; Tue, 13 Sep 2005 12:07:24 +0000 (GMT) (envelope-from admin@zedis.lv) Received: from geko (localhost.zedis.lv [127.0.0.1]) (authenticated bits=0) by mail.zedis.lv (8.13.1/8.13.1) with ESMTP id j8DCM0kJ073559 for ; Tue, 13 Sep 2005 15:22:00 +0300 (EEST) From: "Administrator" To: Date: Tue, 13 Sep 2005 15:07:55 +0300 Message-ID: <000a01c5b85b$c75183b0$4400a8c0@geko> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Virus-Scanned: ClamAV 0.80/1034/Thu Aug 18 23:07:58 2005 clamav-milter version 0.80j on mail.zedis.lv X-Virus-Status: Clean Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: altq for vlans? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2005 12:07:33 -0000 Sorry I read you replay on sum inet forum and I find that information = that you know how can work with VLAN'S on ALTQ you have some patch. Can You help me please this is very important for me......... From owner-freebsd-net@FreeBSD.ORG Wed Sep 14 13:42:54 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 A1CA516A41F for ; Wed, 14 Sep 2005 13:42:54 +0000 (GMT) (envelope-from modelt20@canada.com) Received: from canada.com (smtp-4.vancouver.ipapp.com [216.152.192.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D87B43D45 for ; Wed, 14 Sep 2005 13:42:54 +0000 (GMT) (envelope-from modelt20@canada.com) Received: from canada.com ([216.152.192.56]) by smtp-3.vancouver.ipapp.com ; Wed, 14 Sep 2005 06:42:53 -0700 Sender: modelt20@canada.com From: "Boris Karloff" To: freebsd-net@freebsd.org X-Mailer: Quality Web Email v3.1m, http://netwinsite.com/refw.htm X-Originating-IP: 71.29.66.64 Date: Wed, 14 Sep 2005 08:42:53 -0500 Message-id: <432828dd.261.7370.32443@canada.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Rcpt-To: X-Country: CA Subject: stopping response to nmap X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2005 13:42:54 -0000 Hello: How do I cause freeBSD 5.4 to not respond to an nmap inquiry? I have already tried creating a line in rc.firewall that says: ${fwcmd} deny all from any to any ${fwcmd} drop all from any to any I know these are active, since 1) I see them on the screen at startup, and 2) pinging from any computer to any computer results in a timeout. (both of these should drop all TCP packets; but apparently, they cause a RESET message to be sent.) I've also tried adding the following to sysctl.conf: net.inet.tcp.blackhole=2 net.inet.udp.blackhole=1 Again, these don't seem to prevent my freeBSD from sending a packet (probably a RESET or UNREACHABLE-HOST ack). Once the person sending the nmap to this machine has the IP, its a simple step for them to ip-flood this machine; or worse. How do I make freeBSD not acknowledge the fingerprint from nmap? Thanks in advance. Harold. ---------------------------------------- Upgrade your account today for increased storage; mail forwarding or POP enabled e-mail with automatic virus scanning. Visit http://www.canada.com/email/premiumservices.html for more information. From owner-freebsd-net@FreeBSD.ORG Wed Sep 14 14:23:32 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 7B76D16A41F for ; Wed, 14 Sep 2005 14:23:32 +0000 (GMT) (envelope-from comte0@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id A601243D45 for ; Wed, 14 Sep 2005 14:23:31 +0000 (GMT) (envelope-from comte0@gmail.com) Received: by nproxy.gmail.com with SMTP id a4so73007nfc for ; Wed, 14 Sep 2005 07:23:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=plBeYEYY+Vp6FunWMHcvrdzkeyZz6x7PXV+SNpbyYyHQ8wKEjh8+GGZ7Ns3i2tO3IOAMbgeR+JIkrGHw9HeYAULbT8k9xf/pOCMRbxG5KPW/E4RXsKc2CLGS39NXPDBRu5XrrLOh5EDPn6BulfIYKwkrrxQ3M9sCAThXOJjK7vs= Received: by 10.48.239.18 with SMTP id m18mr38757nfh; Wed, 14 Sep 2005 07:23:30 -0700 (PDT) Received: by 10.48.157.6 with HTTP; Wed, 14 Sep 2005 07:23:30 -0700 (PDT) Message-ID: <1d881b2f050914072350d79a65@mail.gmail.com> Date: Wed, 14 Sep 2005 16:23:30 +0200 From: ComteZero _ To: freebsd-net@freebsd.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1277_15589553.1126707810597" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: PPPoE (STABLE 5) : two PADI packets emitted and then nothing... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: comte0@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2005 14:23:32 -0000 ------=_Part_1277_15589553.1126707810597 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, I already posted this thread in freebsd-stable but seems that this list is= =20 more appropriate. it's been two weeks I try to find out what's wrong. Clean install from cvsu= p=20 STABLE (5). my ADSL account works fine with REL. 4.4+rp_pppoe but not with my new STABL= E=20 (5) (without using rp_pppoe). could someone help me on this issue (logs provided here, ppp.log in attache= d=20 file)...=20 two PADI are emitted but nothing happens after. (i saw that someone had a similar problem, but with previous netgraph=20 revisions). thank you. Since my ADSL modem is 3Com HomeConnect, I've set the=20 net.graph.nonstandard_pppoe=3D1 ng_pppoe.c rev. is 1.67.2.1 ng_socket.c rev. is 1.53.2.3 my ppp.conf is : default: set log all set ifaddr X.X.X.X/0 10.0.0.2/0 my_isp : set device PPPoE:xl0 set authname MY_USER set authkey MY_PWD set dial #set login add default HISADDR here is a tcpdump -vv -i xl0 : 18:48:40.808687 PPPoE PADI [Host-Uniq 0x00E654C1] 18:48:42.807533 PPPoE PADI [Host-Uniq 0x00E654C1] 18:51:44.010839 PPPoE PADI [Host-Uniq 0x40F195C1] 18:51:46.009639 PPPoE PADI [Host-Uniq 0x40F195C1] =20 thx for your comments. ------=_Part_1277_15589553.1126707810597-- From owner-freebsd-net@FreeBSD.ORG Wed Sep 14 14:28:53 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 2DA1C16A420 for ; Wed, 14 Sep 2005 14:28:53 +0000 (GMT) (envelope-from comte0@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 934E943D46 for ; Wed, 14 Sep 2005 14:28:50 +0000 (GMT) (envelope-from comte0@gmail.com) Received: by nproxy.gmail.com with SMTP id a4so73588nfc for ; Wed, 14 Sep 2005 07:28:50 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=h90j0vEdeukm3tRwoRNoY7P0GUkzT8oMLuwd9lyNSE85XSbAW8ecHddBOJUej71iUWwd4FGe5kvGNSPa2bSG1qK9hFQRaXtly3NGevfIXCttL1zTUC3WBV4Vad1A0dHOnWYyiJFxGGrNavKgCq6R114CFpop5be9t+g2v+5Xnsg= Received: by 10.49.5.13 with SMTP id h13mr38570nfi; Wed, 14 Sep 2005 07:28:50 -0700 (PDT) Received: by 10.48.157.6 with HTTP; Wed, 14 Sep 2005 07:28:49 -0700 (PDT) Message-ID: <1d881b2f05091407283fcaa73f@mail.gmail.com> Date: Wed, 14 Sep 2005 16:28:50 +0200 From: ComteZero _ To: freebsd-net@freebsd.org In-Reply-To: <1d881b2f050914072350d79a65@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1337_6303685.1126708130023" References: <1d881b2f050914072350d79a65@mail.gmail.com> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: PPPoE (STABLE 5) : two PADI packets emitted and then nothing... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: comte0@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2005 14:28:53 -0000 ------=_Part_1337_6303685.1126708130023 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline here is ppp.log in plain text : here is ppp.log : Sep 11 19:42:17 fidelio ppp[24723]: Phase: Using interface: tun0 Sep 11 19:42:17 fidelio ppp[24723]: Phase: deflink: Created in closed state Sep 11 19:42:17 fidelio ppp[24723]: tun0: Command: default: set ifaddr=20 X.X.X.X/0 10.0.0.2/0 Sep 11 19:42:17 fidelio ppp[24723]: tun0: Phase: PPP Started (interactive= =20 mode). Sep 11 19:42:17 fidelio ppp[24723]: tun0: Timer: prompt /dev/ttyv0: fdset(r= )=20 0 Sep 11 19:42:23 fidelio ppp[24723]: tun0: Timer: Select returns 1 Sep 11 19:42:23 fidelio ppp[24723]: tun0: Command: /dev/ttyv0: load MY_ISP Sep 11 19:42:23 fidelio ppp[24723]: tun0: ID0: 0x282e97c0 =3D=20 fopen("/etc/ppp/ppp.conf", "r") Sep 11 19:42:23 fidelio ppp[24723]: tun0: Debug: ReadSystem: Checking=20 default (/etc/ppp/ppp.conf). Sep 11 19:42:23 fidelio ppp[24723]: tun0: ID0: 0x282e97c0 =3D=20 fopen("/etc/ppp/ppp.conf", "r") Sep 11 19:42:23 fidelio ppp[24723]: tun0: Debug: ReadSystem: Checking MY_IS= P=20 (/etc/ppp/ppp.conf). Sep 11 19:42:23 fidelio ppp[24723]: tun0: ID0: 0x282e97c0 =3D=20 fopen("/etc/ppp/ppp.conf", "r") Sep 11 19:42:23 fidelio ppp[24723]: tun0: Debug: ReadSystem: Checking MY_IS= P=20 (/etc/ppp/ppp.conf). Sep 11 19:42:23 fidelio ppp[24723]: tun0: Command: easyconnect: set device= =20 PPPoE:xl0 Sep 11 19:42:23 fidelio ppp[24723]: tun0: Command: easyconnect: set authnam= e=20 MY_USER Sep 11 19:42:23 fidelio ppp[24723]: tun0: Command: easyconnect: set authkey= =20 ******** Sep 11 19:42:23 fidelio ppp[24723]: tun0: Command: easyconnect: set dial Sep 11 19:42:23 fidelio ppp[24723]: tun0: Command: easyconnect: add default= =20 HISADDR Sep 11 19:42:23 fidelio ppp[24723]: tun0: ID0: 3 =3D socket(17, 3, 0) Sep 11 19:42:23 fidelio ppp[24723]: tun0: ID0: -1 =3D write(3, data, 140) Sep 11 19:42:23 fidelio ppp[24723]: tun0: TCP/IP: rt_Set failure: Sep 11 19:42:23 fidelio ppp[24723]: tun0: TCP/IP: rt_Set: Cmd =3D Add Sep 11 19:42:23 fidelio ppp[24723]: tun0: TCP/IP: rt_Set: Dst =3D 0.0.0.0/0 Sep 11 19:42:23 fidelio ppp[24723]: tun0: TCP/IP: rt_Set: Gateway =3D 10.0.0.2 Sep 11 19:42:23 fidelio ppp[24723]: tun0: Debug: wrote -1: cmd =3D Add, dst= =3D=20 0.0.0.0/0 , gateway =3D 10.0.0.2 Sep 11 19:42:23 fidelio ppp[24723]: tun0: Timer: prompt /dev/ttyv0: fdset(r= )=20 0 Sep 11 19:42:26 fidelio ppp[24723]: tun0: Timer: Select returns 1 Sep 11 19:42:26 fidelio ppp[24723]: tun0: Command: /dev/ttyv0: dial Sep 11 19:42:26 fidelio ppp[24723]: tun0: Phase: bundle: Establish Sep 11 19:42:26 fidelio ppp[24723]: tun0: Phase: deflink: closed -> opening Sep 11 19:42:26 fidelio ppp[24723]: tun0: ID0: 0 =3D NgMkSockNode("", &cs,= =20 &ds) Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: List of netgraph node=20 ``xl0:'' (id 2) hooks: Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Found orphans -> ethernet Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Connecting netgraph socket= =20 .:tun0 -> [4]::tun0 Sep 11 19:42:26 fidelio ppp[24723]: tun0: ID0: 4 =3D socket(2, 2, 0) Sep 11 19:42:26 fidelio ppp[24723]: tun0: ID0: 0 =3D ioctl(4, 3223349521,= =20 0xbfbfdd90) Sep 11 19:42:26 fidelio ppp[24723]: tun0: ID0: 0 =3D ioctl(4, 2149607696,= =20 0xbfbfdd90) Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Sending PPPOE_CONNECT to= =20 .:tun0 Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Found the following=20 interfaces: Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Index 1, name "fxp0" Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Index 2, name "xl0" Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Index 3, name "plip0" Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Index 4, name "lo0" Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Index 5, name "tun0" Sep 11 19:42:26 fidelio ppp[24723]: tun0: Timer: timer_Start: Inserting=20 physical throughput timer[0x80be068] Sep 11 19:42:26 fidelio ppp[24723]: tun0: Phase: deflink: Connected! Sep 11 19:42:26 fidelio ppp[24723]: tun0: Phase: deflink: opening -> dial Sep 11 19:42:26 fidelio ppp[24723]: tun0: Chat: deflink: Dial attempt 1 of = 1 Sep 11 19:42:26 fidelio ppp[24723]: tun0: Phase: deflink: dial -> carrier Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Waiting for carrier Sep 11 19:42:26 fidelio ppp[24723]: tun0: Timer: prompt /dev/ttyv0: fdset(r= )=20 0 Sep 11 19:42:27 fidelio ppp[24723]: tun0: Timer: Select returns -1 Sep 11 19:42:27 fidelio ppp[24723]: tun0: Timer: ---- Begin of Timer Servic= e=20 List--- Sep 11 19:42:27 fidelio ppp[24723]: tun0: Timer: physical throughput=20 timer[0x80be068]: freq =3D 1.00s, next =3D 0.00s, state =3D running Sep 11 19:42:27 fidelio ppp[24723]: tun0: Timer: ---- End of Timer Service= =20 List --- Sep 11 19:42:27 fidelio ppp[24723]: tun0: Timer: timer_Start: Inserting=20 physical throughput timer[0x80be068] Sep 11 19:42:27 fidelio ppp[24723]: tun0: Debug: Waiting for carrier Sep 11 19:42:27 fidelio ppp[24723]: tun0: Timer: prompt /dev/ttyv0: fdset(r= )=20 0 Sep 11 19:42:28 fidelio ppp[24723]: tun0: Timer: Select returns -1 Sep 11 19:42:28 fidelio ppp[24723]: tun0: Timer: ---- Begin of Timer Servic= e=20 List--- Sep 11 19:42:28 fidelio ppp[24723]: tun0: Timer: physical throughput=20 timer[0x80be068]: freq =3D 1.00s, next =3D 0.00s, state =3D running Sep 11 19:42:28 fidelio ppp[24723]: tun0: Timer: ---- End of Timer Service= =20 List --- Sep 11 19:42:28 fidelio ppp[24723]: tun0: Timer: timer_Start: Inserting=20 physical throughput timer[0x80be068] Sep 11 19:42:28 fidelio ppp[24723]: tun0: Debug: Waiting for carrier Sep 11 19:42:28 fidelio ppp[24723]: tun0: Timer: prompt /dev/ttyv0: fdset(r= )=20 0 Sep 11 19:42:29 fidelio ppp[24723]: tun0: Timer: Select returns -1 Sep 11 19:42:29 fidelio ppp[24723]: tun0: Timer: ---- Begin of Timer Servic= e=20 List--- Sep 11 19:42:29 fidelio ppp[24723]: tun0: Timer: physical throughput=20 timer[0x80be068]: freq =3D 1.00s, next =3D 0.00s, state =3D running Sep 11 19:42:29 fidelio ppp[24723]: tun0: Timer: ---- End of Timer Service= =20 List --- Sep 11 19:42:29 fidelio ppp[24723]: tun0: Timer: timer_Start: Inserting=20 physical throughput timer[0x80be068] Sep 11 19:42:29 fidelio ppp[24723]: tun0: Debug: Waiting for carrier Sep 11 19:42:29 fidelio ppp[24723]: tun0: Timer: prompt /dev/ttyv0: fdset(r= )=20 0 Sep 11 19:42:30 fidelio ppp[24723]: tun0: Timer: Select returns -1 Sep 11 19:42:30 fidelio ppp[24723]: tun0: Timer: ---- Begin of Timer Servic= e=20 List--- Sep 11 19:42:30 fidelio ppp[24723]: tun0: Timer: physical throughput=20 timer[0x80be068]: freq =3D 1.00s, next =3D 0.00s, state =3D running Sep 11 19:42:30 fidelio ppp[24723]: tun0: Timer: ---- End of Timer Service= =20 List --- Sep 11 19:42:30 fidelio ppp[24723]: tun0: Timer: timer_Start: Inserting=20 physical throughput timer[0x80be068] Sep 11 19:42:30 fidelio ppp[24723]: tun0: Debug: Waiting for carrier Sep 11 19:42:30 fidelio ppp[24723]: tun0: Timer: prompt /dev/ttyv0: fdset(r= )=20 0 Sep 11 19:42:31 fidelio ppp[24723]: tun0: Timer: Select returns -1 Sep 11 19:42:31 fidelio ppp[24723]: tun0: Timer: ---- Begin of Timer Servic= e=20 List--- Sep 11 19:42:31 fidelio ppp[24723]: tun0: Timer: physical throughput=20 timer[0x80be068]: freq =3D 1.00s, next =3D 0.00s, state =3D running Sep 11 19:42:31 fidelio ppp[24723]: tun0: Timer: ---- End of Timer Service= =20 List --- Sep 11 19:42:31 fidelio ppp[24723]: tun0: Timer: timer_Start: Inserting=20 physical throughput timer[0x80be068] Sep 11 19:42:31 fidelio ppp[24723]: tun0: Phase: deflink: Disconnected! Sep 11 19:42:31 fidelio ppp[24723]: tun0: Phase: deflink: carrier -> hangup Sep 11 19:42:31 fidelio ppp[24723]: tun0: Debug: deflink: Close Sep 11 19:42:31 fidelio ppp[24723]: tun0: Phase: deflink: Connect time: 5= =20 secs: 0 octets in, 0 octets out Sep 11 19:42:31 fidelio ppp[24723]: tun0: Phase: deflink: 0 packets in, 0= =20 packets out Sep 11 19:42:31 fidelio ppp[24723]: tun0: Phase: total 0 bytes/sec, peak 0= =20 bytes/sec on Sun Sep 11 19:42:26 2005 Sep 11 19:42:31 fidelio ppp[24723]: tun0: Phase: deflink: hangup -> closed Sep 11 19:42:31 fidelio ppp[24723]: tun0: Debug: route_IfDelete (5) Sep 11 19:42:31 fidelio ppp[24723]: tun0: Debug: Found ff02:5::/32=20 fe80:5::208:c7ff:fe7f:7535 Sep 11 19:42:31 fidelio ppp[24723]: tun0: Debug: route_IfDelete: Skip it=20 (pass 0) Sep 11 19:42:31 fidelio ppp[24723]: tun0: Debug: Found ff02:5::/32=20 fe80:5::208:c7ff:fe7f:7535 Sep 11 19:42:31 fidelio ppp[24723]: tun0: ID0: 2 =3D socket(17, 3, 0) Sep 11 19:42:31 fidelio ppp[24723]: tun0: ID0: 148 =3D write(2, data, 148) Sep 11 19:42:31 fidelio ppp[24723]: tun0: Debug: wrote 148: cmd =3D Delete,= =20 dst =3D ff02:5::/32, gateway =3D Sep 11 19:42:31 fidelio ppp[24723]: tun0: ID0: 2 =3D socket(2, 2, 0) Sep 11 19:42:31 fidelio ppp[24723]: tun0: ID0: 0 =3D ioctl(2, 3223349521,= =20 0xbfbfe970) Sep 11 19:42:31 fidelio ppp[24723]: tun0: ID0: 0 =3D ioctl(2, 2149607696,= =20 0xbfbfe970) Sep 11 19:42:31 fidelio ppp[24723]: tun0: Phase: bundle: Dead Sep 11 19:42:31 fidelio ppp[24723]: tun0: Timer: timer_Start: Inserting dia= l=20 timer[0x80bcd44] Sep 11 19:42:31 fidelio ppp[24723]: tun0: Timer: prompt /dev/ttyv0: fdset(r= )=20 0 On 9/14/05, ComteZero _ wrote: >=20 > Hello, >=20 > I already posted this thread in freebsd-stable but seems that this list i= s=20 > more appropriate. >=20 > it's been two weeks I try to find out what's wrong. Clean install from=20 > cvsup STABLE (5). > my ADSL account works fine with REL. 4.4+rp_pppoe but not with my new=20 > STABLE (5) (without using rp_pppoe). > could someone help me on this issue (logs provided here, ppp.log in=20 > attached file)...=20 > two PADI are emitted but nothing happens after. > (i saw that someone had a similar problem, but with previous netgraph=20 > revisions). >=20 > thank you. >=20 > Since my ADSL modem is 3Com HomeConnect, I've set the=20 > net.graph.nonstandard_pppoe=3D1 >=20 > ng_pppoe.c rev. is 1.67.2.1 > ng_socket.c rev. is 1.53.2.3 >=20 > my ppp.conf is : > default: > set log all > set ifaddr X.X.X.X/0 10.0.0.2/0 >=20 > my_isp : > set device PPPoE:xl0 > set authname MY_USER > set authkey MY_PWD > set dial > #set login > add default HISADDR >=20 >=20 > here is a tcpdump -vv -i xl0 : >=20 > 18:48:40.808687 PPPoE PADI [Host-Uniq 0x00E654C1] > 18:48:42.807533 PPPoE PADI [Host-Uniq 0x00E654C1] > 18:51:44.010839 PPPoE PADI [Host-Uniq 0x40F195C1] > 18:51:46.009639 PPPoE PADI [Host-Uniq 0x40F195C1] > =20 > thx for your comments. > =20 > ------=_Part_1337_6303685.1126708130023-- From owner-freebsd-net@FreeBSD.ORG Wed Sep 14 23:47:16 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 3BD6116A41F for ; Wed, 14 Sep 2005 23:47:16 +0000 (GMT) (envelope-from dave-sender-1932b5@seddon.ca) Received: from seddon.ca (seddon.ca [203.209.212.18]) by mx1.FreeBSD.org (Postfix) with SMTP id 7E66B43D46 for ; Wed, 14 Sep 2005 23:47:15 +0000 (GMT) (envelope-from dave-sender-1932b5@seddon.ca) Received: (qmail 69016 invoked by uid 89); 14 Sep 2005 23:47:13 -0000 Received: by seddon.ca (tmda-sendmail, from uid 89); Thu, 15 Sep 2005 09:47:11 +1000 (EST) References: <432828dd.261.7370.32443@canada.com> In-Reply-To: <432828dd.261.7370.32443@canada.com> To: "Boris Karloff" Date: Thu, 15 Sep 2005 09:47:10 +1000 Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <1126741631.68995.TMDA@seddon.ca> X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Dave+Seddon Cc: freebsd-net@freebsd.org Subject: Re: stopping response to nmap X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: das-keyword-net.6770cb@seddon.ca List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2005 23:47:16 -0000 Just configure /etc/rc.conf with one of these options and the firewall should work. These are the options, from /etc/rc.firewall: ############ # Define the firewall type in /etc/rc.conf. Valid values are: # open - will allow anyone in # client - will try to protect just this machine # simple - will try to protect a whole network # closed - totally disables IP services except via lo0 interface # UNKNOWN - disables the loading of firewall rules. # filename - will load the rules in the given filename (full path required) So set this: firewall_enable="YES" firewall_type="closed" Regards, Dave Boris Karloff writes: > Hello: > > How do I cause freeBSD 5.4 to not respond to an nmap > inquiry? I have already tried creating a line in rc.firewall > that says: > > ${fwcmd} deny all from any to any > ${fwcmd} drop all from any to any > > I know these are active, since 1) I see them on the screen > at startup, and 2) pinging from any computer to any computer > results in a timeout. > > (both of these should drop all TCP packets; but apparently, > they cause a RESET message to be sent.) > > I've also tried adding the following to sysctl.conf: > > net.inet.tcp.blackhole=2 > net.inet.udp.blackhole=1 > > Again, these don't seem to prevent my freeBSD from sending a > packet (probably a RESET or UNREACHABLE-HOST ack). > > Once the person sending the nmap to this machine has the IP, > its a simple step for them to ip-flood this machine; or > worse. > > How do I make freeBSD not acknowledge the fingerprint from > nmap? > > Thanks in advance. > > Harold. > > > ---------------------------------------- > Upgrade your account today for increased storage; mail > forwarding or POP enabled e-mail with automatic virus > scanning. Visit > http://www.canada.com/email/premiumservices.html for more > information. > _______________________________________________ > 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 Thu Sep 15 16:19:07 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 DEE3D16A421; Thu, 15 Sep 2005 16:19:07 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C31C43D5A; Thu, 15 Sep 2005 16:19:06 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 732B146B98; Thu, 15 Sep 2005 12:19:05 -0400 (EDT) Date: Thu, 15 Sep 2005 17:19:05 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Andre Oppermann In-Reply-To: <4321BD3D.66417FA6@freebsd.org> Message-ID: <20050915171617.D75005@fledge.watson.org> References: <20050908221115.038c3abd.lists@yazzy.org> <004701c5b4df$9207d260$1200a8c0@gsicomp.on.ca> <4320EDDF.6090303@errno.com> <20050909054110.08pqjx9bi884c0sg@mail.bafirst.com> <4321BA08.9060500@errno.com> <4321BD3D.66417FA6@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: net.inet.ip.forwarding and net.inet.ip.fastforwarding X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2005 16:19:08 -0000 On Fri, 9 Sep 2005, Andre Oppermann wrote: >> 6.0 and 7.x share the same code so the settings are identical. As to >> downside you pay a penalty if the fastforwarding code has to hand the >> packet back to the "slow path". There may also be side effects from >> the run-to-completion model it uses. You should test to decide if the >> feature is worth enabling for your environment. I'm not sure it's had >> much testing (Andre?). > > When activated on a router it gives a very nice speed boost. Process > completion pays off very well here. It has got a lot of testing at > various ISP's on their production routers. For hosts it doesn't really > hurt but is totally pointless. In measurements a couple of years ago, I demonstrated to myself that on several interesting pieces of hardware, running with net.isr.enable=1 resulted in lower latency packet forwarding and processing on 5.x (at the time) than 4.x (at the time). I've not re-measured with recent 7.x/6.x or 4.x on recent hardware. Over the last couple of years, we've shaken out a number of important bugs in local network stack code that tripped up with net.isr.enable, so we're reaching the point where I might start encouraging people to work with it more actively for local (as well as routed) paths. There are still open questions about what models make the most sense, though -- run to completion has some nice latency properties, and also increases the opportunities for parallelism in the network stack. On the other hand, it increases the load born by ithreads, so if your ithread was already maxing out available CPU, you would decrease the amount of work it could do, and on UP it can result in more context switches if you have several active interfaces running out of different ithreads. Many of these questions are the same as the ones we'll be talking about for next generation polling support at the developer summit this fall, so it would make sense to talk about them at the same time. Robert N M Watson From owner-freebsd-net@FreeBSD.ORG Fri Sep 16 15:33:09 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 10A4216A41F for ; Fri, 16 Sep 2005 15:33:09 +0000 (GMT) (envelope-from dom@helenmarks.co.uk) Received: from mail.helenmarks.co.uk (mail.helenmarks.co.uk [82.68.196.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 802D143D48 for ; Fri, 16 Sep 2005 15:33:08 +0000 (GMT) (envelope-from dom@helenmarks.co.uk) Received: from localhost (localhost [127.0.0.1]) by mail.helenmarks.co.uk (Postfix) with ESMTP id 1CA212710C02; Fri, 16 Sep 2005 16:33:07 +0100 (BST) Received: from mail.helenmarks.co.uk ([127.0.0.1]) by localhost (mail.helenmarks.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10427-02; Fri, 16 Sep 2005 16:33:04 +0100 (BST) Received: by mail.helenmarks.co.uk (Postfix, from userid 80) id EE2E12710C01; Fri, 16 Sep 2005 16:33:03 +0100 (BST) Received: from graphicaldatacapture-ll-194.altohiway.com ([195.12.22.194]) (SquirrelMail authenticated user dom) by www.helenmarks.co.uk with HTTP; Fri, 16 Sep 2005 16:33:03 +0100 (BST) Message-ID: <4452.195.12.22.194.1126884783.squirrel@www.helenmarks.co.uk> Date: Fri, 16 Sep 2005 16:33:03 +0100 (BST) From: "Dominic Marks" To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: By ClamAV 0.85.1 Subject: Packet loss with ng_one2many X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2005 15:33:09 -0000 Hello, I'm trying to use two gigabit links together using ng_one2many. I haven't done this before, so here is the environment: FreeBSD 6 system with four gigabit interfaces, two of the four are going to be used a single interface. I've attached em0 and em1 to a gigabit switch and read manual pages / googled for information on how to configure this. I have the following script to set things up: ngctl mkpeer em0: one2many upper one ngctl connect em0: em0:upper lower many0 ngctl connect em1: em0:upper lower many1 ngctl msg em1: setpromisc 1 ngctl msg em1: setautosrc 0 ngctl msg em0:upper \ setconfig "{ xmitAlg=1 failAlg=1 enabledLinks=[ 1 1 ] }" I get 50% packet loss when using this. It seems to me like only the em0 interface is operating properly, although both NICs are connected and work alright without ng_one2many. Any clues as to what I am doing wrong / guides to implementation ng_one2many? Is this email related to my problem? http://lists.freebsd.org/pipermail/freebsd-net/2005-February/006500.html Thanks, -- Dominic Marks From owner-freebsd-net@FreeBSD.ORG Sat Sep 17 14:38:32 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 23F5216A41F for ; Sat, 17 Sep 2005 14:38:32 +0000 (GMT) (envelope-from fergus@cobbled.net) Received: from ni-mail2.dna.utvinternet.net (mail2.u.tv [194.46.8.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D9DB43D45 for ; Sat, 17 Sep 2005 14:38:30 +0000 (GMT) (envelope-from fergus@cobbled.net) Received: from mail.cobbled.net (unverified [195.218.107.162]) by ni-mail2.dna.utvinternet.net (Vircom SMTPRS 4.1.361.18) with ESMTP id for ; Sat, 17 Sep 2005 15:38:24 +0100 Received: from eyore.cobbled.net (localhost [127.0.0.1]) by mail.cobbled.net (8.12.10/8.12.10) with ESMTP id j8HEcBm7006687 for ; Sat, 17 Sep 2005 15:38:11 +0100 (BST) (envelope-from fergus@eyore.public.cobbled.net) Received: (from fergus@localhost) by eyore.cobbled.net (8.12.10/8.12.10/Submit) id j8HEcBxi006686 for freebsd-net@freebsd.org; Sat, 17 Sep 2005 15:38:11 +0100 (BST) (envelope-from fergus) Date: Sat, 17 Sep 2005 15:38:11 +0100 From: n0g0013 To: freebsd-net@freebsd.org Message-ID: <20050917143811.GC6440@eyore.cobbled.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: netgraph ISDN driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Sep 2005 14:38:32 -0000 does a PCI device driver need to have either a network device or a character device or can i simply allow it to be a netgraph only device? don't want to register the layer1 device driver as a network interface but no real reason for the character interface either. currently it's hard rebooting the system when loading the module so i have background problems to iron out (getting a CVS repo to work from is taking time). if anyone knows the answer "in principle" i'd appreciate it. cheers, -- t t w From owner-freebsd-net@FreeBSD.ORG Sat Sep 17 14:56:56 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 8CDCD16A41F for ; Sat, 17 Sep 2005 14:56:56 +0000 (GMT) (envelope-from fergus@cobbled.net) Received: from ni-mail2.dna.utvinternet.net (mail2.u.tv [194.46.8.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CAB243D48 for ; Sat, 17 Sep 2005 14:56:55 +0000 (GMT) (envelope-from fergus@cobbled.net) Received: from mail.cobbled.net (unverified [195.218.107.162]) by ni-mail2.dna.utvinternet.net (Vircom SMTPRS 4.1.361.18) with ESMTP id for ; Sat, 17 Sep 2005 15:56:49 +0100 Received: from eyore.cobbled.net (localhost [127.0.0.1]) by mail.cobbled.net (8.12.10/8.12.10) with ESMTP id j8HEuYm7006762 for ; Sat, 17 Sep 2005 15:56:36 +0100 (BST) (envelope-from fergus@eyore.public.cobbled.net) Received: (from fergus@localhost) by eyore.cobbled.net (8.12.10/8.12.10/Submit) id j8HEuWZ1006761 for freebsd-net@freebsd.org; Sat, 17 Sep 2005 15:56:32 +0100 (BST) (envelope-from fergus) Resent-Message-Id: <200509171456.j8HEuWZ1006761@eyore.cobbled.net> Date: Sat, 17 Sep 2005 15:31:53 +0100 From: n0g0013 To: freebsd-net@freebsd.org Message-ID: <20050917143153.GB6440@eyore.cobbled.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Resent-From: ttw@cobbled.net Resent-Date: Sat, 17 Sep 2005 15:56:32 +0100 Resent-To: freebsd-net@freebsd.org Subject: netgraph PCI driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Sep 2005 14:56:56 -0000 i'm assuming that during a PCI device probe/attach i'll have to somehow register that we have a new netgraph node available so that it can be created not to mention the corresponding destruction when the module is unloaded. can't find anything apparent from looking at the "sr" driver. is this auto-magical? -- t t w From owner-freebsd-net@FreeBSD.ORG Sat Sep 17 17:28:44 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 2F75416A41F for ; Sat, 17 Sep 2005 17:28:44 +0000 (GMT) (envelope-from fergus@cobbled.net) Received: from ni-mail2.dna.utvinternet.net (mail2.u.tv [194.46.8.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 942AF43D48 for ; Sat, 17 Sep 2005 17:28:43 +0000 (GMT) (envelope-from fergus@cobbled.net) Received: from mail.cobbled.net (unverified [195.218.107.162]) by ni-mail2.dna.utvinternet.net (Vircom SMTPRS 4.1.361.18) with ESMTP id for ; Sat, 17 Sep 2005 18:28:37 +0100 Received: from eyore.cobbled.net (localhost [127.0.0.1]) by mail.cobbled.net (8.12.10/8.12.10) with ESMTP id j8HHSOm7007050 for ; Sat, 17 Sep 2005 18:28:24 +0100 (BST) (envelope-from fergus@eyore.public.cobbled.net) Received: (from fergus@localhost) by eyore.cobbled.net (8.12.10/8.12.10/Submit) id j8HHSOrr007049 for freebsd-net@freebsd.org; Sat, 17 Sep 2005 18:28:24 +0100 (BST) (envelope-from fergus) Date: Sat, 17 Sep 2005 18:28:23 +0100 From: n0g0013 To: freebsd-net@freebsd.org Message-ID: <20050917172823.GH6440@eyore.cobbled.net> References: <20050917143153.GB6440@eyore.cobbled.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050917143153.GB6440@eyore.cobbled.net> Subject: Re: netgraph PCI driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Sep 2005 17:28:44 -0000 On 17.09-15:31, n0g0013 wrote: [ ... ] > can't find anything apparent from looking at the "sr" driver. now i've seen it -- i'm not sure how i missed it. -- t t w From owner-freebsd-net@FreeBSD.ORG Sat Sep 17 17:32:34 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 6145616A41F for ; Sat, 17 Sep 2005 17:32:34 +0000 (GMT) (envelope-from fergus@cobbled.net) Received: from ni-mail3.dna.utvinternet.net (mail3.u.tv [194.46.8.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id C468643D46 for ; Sat, 17 Sep 2005 17:32:33 +0000 (GMT) (envelope-from fergus@cobbled.net) Received: from mail.cobbled.net (unverified [195.218.107.162]) by ni-mail3.dna.utvinternet.net (Vircom SMTPRS 4.1.361.20) with ESMTP id for ; Sat, 17 Sep 2005 18:32:27 +0100 Received: from eyore.cobbled.net (localhost [127.0.0.1]) by mail.cobbled.net (8.12.10/8.12.10) with ESMTP id j8HHWAm7007070 for ; Sat, 17 Sep 2005 18:32:10 +0100 (BST) (envelope-from fergus@eyore.public.cobbled.net) Received: (from fergus@localhost) by eyore.cobbled.net (8.12.10/8.12.10/Submit) id j8HHWADS007069 for freebsd-net@freebsd.org; Sat, 17 Sep 2005 18:32:10 +0100 (BST) (envelope-from fergus) Date: Sat, 17 Sep 2005 18:32:10 +0100 From: n0g0013 To: freebsd-net@freebsd.org Message-ID: <20050917173210.GI6440@eyore.cobbled.net> References: <20050917143811.GC6440@eyore.cobbled.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050917143811.GC6440@eyore.cobbled.net> Subject: Re: netgraph ISDN driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Sep 2005 17:32:34 -0000 On 17.09-15:38, n0g0013 wrote: > does a PCI device driver need to have either a network device or a > character device or can i simply allow it to be a netgraph only > device? OK. think i got the answer from the "sr" driver. looks like most of the NETGRAPH ifndef's are there to remove the "ifp" stuff from the driver and there isn't any additional character stuff that i can see. so netgraph only looks fine. now i just need to know what's causing the kernel damage. -- t t w