From owner-freebsd-net Wed Jan 2 8:10:44 2002 Delivered-To: freebsd-net@freebsd.org Received: from smtp.www-service.de (smtp.www-service.de [212.77.161.16]) by hub.freebsd.org (Postfix) with ESMTP id A327A37B42F for ; Wed, 2 Jan 2002 08:10:25 -0800 (PST) Received: from fw.tue.le (pD95033EC.dip.t-dialin.net [217.80.51.236]) by smtp.www-service.de (8.11.6/8.11.6) with ESMTP id g02HWOI28459; Wed, 2 Jan 2002 18:32:25 +0100 Received: from mezcal.tue.le (mezcal.tue.le [192.168.201.20]) by fw.tue.le (8.8.8/8.8.8) with ESMTP id RAA08017; Wed, 2 Jan 2002 17:09:17 +0100 (CET) (envelope-from thz@mezcal.tue.le) Received: (from thz@localhost) by mezcal.tue.le (8.11.6/8.11.6) id g02G9Hj08358; Wed, 2 Jan 2002 17:09:17 +0100 (CET) (envelope-from thz) Date: Wed, 2 Jan 2002 17:09:17 +0100 From: Thomas Zenker To: Mike Silbersack Cc: net@freebsd.org, Josef Karthauser , Matthew Dillon Subject: Re: USB ethernet problem Message-ID: <20020102170917.A8308@mezcal.tue.le> References: <20011221115851.A10172@mezcal.tue.le> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from silby@silby.com on Fri, Dec 21, 2001 at 01:35:36PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Dec 21, 2001 at 01:35:36PM -0500, Mike Silbersack wrote: > On Fri, 21 Dec 2001, Thomas Zenker wrote: > > Might there be a run condition, interrupt problem or priority problem > > with the ata driver, which become visible now on the slower machine? > > > > May be I have to go back to fbsd 4.3 > > Hmm. I agree, it doesn't like like much of anything usb-related changed > between 4.3 and now. If we examine the ata driver, one big thing changed > between 4.3 and 4.4: Write caching was re-enabled. This caused a big > change in disk throughput for some people, perhaps it's affecting you. > Try turning it off (see the ata manpage for details) and see if that > changes your results. > > Also, is your USB adapter sharing interrupts with anything else? Are > interrupts being allocated the same way on 4.3 and 4.4? > > Mike "Silby" Silbersack On Tue, Jan 01, 2002 at 08:32:09PM -0500, Mike Silbersack wrote: > Wow, talk about Terry getting off-topic again... > > Anyway, out of curiosity, did anyone figure out anything about what is > wrong with USB ethernet? I have this feeling that it's just a driver bug, > but since so few developers use usb ethernet cards, it hasn't been > noticed. > > Thomas, you noted that your USB ethernet performance is worse with 4.4 > than it was with 4.3. Could you setup a test where you use a 4.3/usb > client and then 4.3 & 4.4 pci servers? (With the server being the one > primarily sending.) This would be useful in telling us if the changes > which affect you are tcp stack changes, or if something in the usb > subsystem changed. Equalize the slowstart flightsizes and receive / send > buffers in all test cases, of course. > > Thanks, > > Mike "Silby" Silbersack Hi Mike, back from holidays... because this is now discussed in different threads, on -stable and on -net, I will try to recapitulate what has happened and keep this on -net "USB ethernet problem". The performance problems apeared after updating my test system from 4.3 to 4.4 with Netgear EA101 USB/ethernet adaptor (kue driver). Performance dropped by a factor of 10 or more. The server in all cases was 4.4. After testing different slowstart flightsizes and send/recv buffer sizes with ttcp the findings were, that mostly the recvspace reduced to 16K (as in 4.3) recovered the performance. See also my message to -stable from 2001/12/14. The usb host controller on this system is a VIA 83C572 (UHCI). Now going to the final embedded hardware, the suprise was a hanging usb driver. The strange thing is, this does not happen while testing with ttcp, but only if the data is written to disk. The following kernel messages are printed: usb0: host controller process error usb0: host controller halted kue0: watchdog timeout kue0: usb error on tx: TIMEOUT this comes from uhci_intr() in dev/usb/uhci.c. Aparently the usb0-messages reflect a hw status register!? This happens very quickly with 4.4 (it is impossible to install over usb/ethernet), but I have seen it today for the first time with 4.3 also. The usb host controller is UHCI Intel 82371AB/EB (PIIX4). On none of the systems is the interrupt shared. Interrupts are allocated the same way on 4.3 and 4.4. hw.ata.wc has no influence. It looks like a longstanding, but not discovered issue. as for the performance tests: the test from 2001/12/14 (-stable) were done with 4.4&4.3 as client, server was 4.4 - primarily sending. Do you mean to repeat the tests with a 4.3 server? -- Thomas Zenker c/o Lennartz electronic GmbH Bismarckstrasse 136, D-72072 Tuebingen, Germany Phone: +49-(0)7071-93550 Email: thz@lennartz-electronic.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 2 18: 9:48 2002 Delivered-To: freebsd-net@freebsd.org Received: from opensrs.saignon.net (216-120-17-31.dsl.cust.tfb.com [216.120.17.31]) by hub.freebsd.org (Postfix) with ESMTP id BEEEB37B419 for ; Wed, 2 Jan 2002 18:09:46 -0800 (PST) Received: from tsaignmobl (216-120-17-24.dsl.cust.tfb.com [216.120.17.24]) by opensrs.saignon.net (8.11.4/8.11.3) with ESMTP id g032BVZ06103 for ; Wed, 2 Jan 2002 18:11:32 -0800 (PST) (envelope-from tony@saign.com) From: Tony Saign Reply-To: To: Subject: DHCPD handing out IP's backwards! Date: Wed, 2 Jan 2002 18:09:28 -0800 Message-ID: <000001c193fb$ace2bea0$0201a8c0@saignon.net> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have a FreeBSD4.4 box running as a firewall/natd system for a small workgoup. Everything is working fine, but IP's are being handed out backwards! (i.e. 1st box gets 192.168.1.253, 2nd Box gets 192.168.1.252, etc.) I've never seen this before on any other system, any ideas?? Thanks in advance, -Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 2 21:52: 3 2002 Delivered-To: freebsd-net@freebsd.org Received: from quartz.bos.dyndns.org (quartz.bos.dyndns.org [66.37.218.198]) by hub.freebsd.org (Postfix) with ESMTP id E4E7E37B41B for ; Wed, 2 Jan 2002 21:52:00 -0800 (PST) Received: from localhost (twilde@localhost) by quartz.bos.dyndns.org (8.11.5/8.11.5) with ESMTP id g035puA04510; Thu, 3 Jan 2002 00:51:56 -0500 (EST) Date: Thu, 3 Jan 2002 00:51:56 -0500 (EST) From: Tim Wilde X-X-Sender: twilde@quartz.bos.dyndns.org To: Tony Saign Cc: freebsd-net@FreeBSD.ORG Subject: Re: DHCPD handing out IP's backwards! In-Reply-To: <000001c193fb$ace2bea0$0201a8c0@saignon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 2 Jan 2002, Tony Saign wrote: > I have a FreeBSD4.4 box running as a firewall/natd system for a small > workgoup. > Everything is working fine, but IP's are being handed out backwards! > (i.e. 1st box gets 192.168.1.253, 2nd Box gets 192.168.1.252, etc.) > > I've never seen this before on any other system, any ideas?? That's how ISC dhcpd works. See dhcpd(8) and dhcpd.conf(5) Tim Wilde -- Tim Wilde twilde@dyndns.org Systems Administrator Dynamic DNS Network Services http://www.dyndns.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 3 0:54:51 2002 Delivered-To: freebsd-net@freebsd.org Received: from sln01.megadat.com (exchange.megadat.com [195.22.224.154]) by hub.freebsd.org (Postfix) with ESMTP id BD52237B405 for ; Thu, 3 Jan 2002 00:54:43 -0800 (PST) Received: by sln01.megadat.com with Internet Mail Service (5.5.2653.19) id ; Thu, 3 Jan 2002 10:54:38 +0200 Message-ID: <8E9035BABCA0514EB0E574B6A7082FC30530FA@sln01.megadat.com> From: Girnet Vladimir To: "'net@freebsd.org'" Subject: zebra OSPF + redistributing static Date: Thu, 3 Jan 2002 10:54:37 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="koi8-r" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi I use zebra OSPFD to connect to my OSPF network. The router have 4 ethernet adapters, with diferrent subnets on them. Only one interface is connected to ospf network. So, I use "redistribute connected" option in ospf. I have such strange situation: Routes, that are distributed with "redistribute connected" are recalculated on other OSPF routers in the same area every minute. Why this is happened? Zebra - 0.92a, FreeBSD - 4.4-RELEASE. Thanks, Vladimir Girnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 3 4:13:18 2002 Delivered-To: freebsd-net@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 103FA37B41A for ; Thu, 3 Jan 2002 04:13:15 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id CDFBD319; Thu, 3 Jan 2002 12:13:05 +0000 (GMT) Date: Thu, 3 Jan 2002 12:13:05 +0000 From: Josef Karthauser To: Girnet Vladimir Cc: "'net@freebsd.org'" Subject: Re: zebra OSPF + redistributing static Message-ID: <20020103121305.A34240@tao.org.uk> References: <8E9035BABCA0514EB0E574B6A7082FC30530FA@sln01.megadat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8E9035BABCA0514EB0E574B6A7082FC30530FA@sln01.megadat.com>; from VGirnet@megadat.com on Thu, Jan 03, 2002 at 10:54:37AM +0200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 03, 2002 at 10:54:37AM +0200, Girnet Vladimir wrote: > Hi >=20 > I use zebra OSPFD to connect to my OSPF network. The router have 4 ethern= et > adapters, with diferrent subnets on them. > Only one interface is connected to ospf network. So, I use "redistribute > connected" option in ospf. >=20 > I have such strange situation: Routes, that are distributed with > "redistribute connected" are recalculated on other OSPF routers in the sa= me > area every minute. Hiya Vladimir, You should ask this question on the zebra mailing list. Take a stroll over to their web site (http://www.zebra.org) for its address. Joe --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjw0StEACgkQXVIcjOaxUBYLRQCg3YmyAS8TZzxc9kpyNncDpS6G EtoAoMi2sbgtzrhgcUmNhHTVTNH/7F5T =bNug -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 3 12:43:45 2002 Delivered-To: freebsd-net@freebsd.org Received: from niwun.pair.com (niwun.pair.com [209.68.2.70]) by hub.freebsd.org (Postfix) with SMTP id D4A1C37B41D for ; Thu, 3 Jan 2002 12:43:29 -0800 (PST) Received: (qmail 63344 invoked by uid 3193); 3 Jan 2002 20:43:29 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 Jan 2002 20:43:29 -0000 Date: Thu, 3 Jan 2002 15:43:29 -0500 (EST) From: Mike Silbersack X-Sender: To: Thomas Zenker Cc: , Josef Karthauser , Matthew Dillon Subject: Re: USB ethernet problem In-Reply-To: <20020102170917.A8308@mezcal.tue.le> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 2 Jan 2002, Thomas Zenker wrote: > Hi Mike, > > back from holidays... > > because this is now discussed in different threads, on -stable and > on -net, I will try to recapitulate what has happened and keep this > on -net "USB ethernet problem". > > The performance problems apeared after updating my test system from > 4.3 to 4.4 with Netgear EA101 USB/ethernet adaptor (kue driver). > Performance dropped by a factor of 10 or more. The server in all > cases was 4.4. After testing different slowstart flightsizes and > send/recv buffer sizes with ttcp the findings were, that mostly the > recvspace reduced to 16K (as in 4.3) recovered the performance. See > also my message to -stable from 2001/12/14. The usb host controller > on this system is a VIA 83C572 (UHCI). > > Now going to the final embedded hardware, the suprise was a hanging > usb driver. The strange thing is, this does not happen while testing > with ttcp, but only if the data is written to disk. The following > kernel messages are printed: > > usb0: host controller process error > usb0: host controller halted > kue0: watchdog timeout > kue0: usb error on tx: TIMEOUT > > this comes from uhci_intr() in dev/usb/uhci.c. Aparently the > usb0-messages reflect a hw status register!? This happens very > quickly with 4.4 (it is impossible to install over usb/ethernet), > but I have seen it today for the first time with 4.3 also. The usb > host controller is UHCI Intel 82371AB/EB (PIIX4). Well, since you've been able to isolate this as the cause, there's no need to run any more tcp tests with varying servers. Try changing hz, as I mentioned in the e-mail I just sent to you guys. Also, try running ttcp while seperately creating disk load (through a disk benchmark or something.) Meanwhile, watch systat -vm and see if the interrupt counts show you anything interesting. Thanks, Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 3 20:33:45 2002 Delivered-To: freebsd-net@freebsd.org Received: from cairo.zsat.net (cairo.zsat.net [64.6.64.200]) by hub.freebsd.org (Postfix) with ESMTP id D9CDD37B416 for ; Thu, 3 Jan 2002 20:33:40 -0800 (PST) Received: by cairo.zsat.net (Postfix, from userid 1002) id 3E055A6A04; Thu, 3 Jan 2002 22:33:35 -0600 (CST) Date: Thu, 3 Jan 2002 22:33:35 -0600 From: Scott Lamb To: freebsd-net@freebsd.org Subject: netgraph kernel panic Message-ID: <20020104043335.GA87710@cairo.zsat.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.24i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, FreeBSD 4.5-PRERELEASE (as of a few days ago) is crashing consistently when I try to initiate a PPTP connection to with mpd-netgraph 3.3 (from ports). mpd ups the interface happily: mpd: [vpn] IPCP: rec'd Configure Ack #3 link 0 (Ack- Sent) mpd: IPADDR a.b.c.d mpd: [vpn] IPCP: state change Ack-Sent --> Opened mpd: [vpn] IPCP: LayerUp mpd: a.b.c.d -> a.b.c.e mpd: [vpn] IFACE: Up event mpd: [vpn] exec: /sbin/ifconfig ng0 a.b.c.d a.b.c.e netmask 0xffffffff -link0 mpd: [vpn] exec: /sbin/route add a.b.0.0 a.b.c.e -netmask 0xffff0000 mpd: [vpn] IFACE: Up event ...then crashes immediately afterward with "fatal trap 12: page fault while in kernel mode". I saved the kernel core file. The panic looks like this: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x70 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01ca6b8 stack pointer = 0x10:0xc03f1d58 frame pointer = 0x10:0xc03f1d7c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0303f72 stack pointer = 0x10:0xc03f1b2c frame pointer = 0x10:0xc03f1b40 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam trap number = 12 panic: page fault Uptime: 24s The stack trace looks like this: #0 0xc01c78c2 in dumpsys () #1 0xc01c76e3 in boot () #2 0xc01c7ab8 in poweroff_wait () #3 0xc036c4c6 in trap_fatal () #4 0xc036c199 in trap_pfault () #5 0xc036bd83 in trap () #6 0xc0303f72 in mfs_strategy () #7 0xc01ecc6a in bwrite () #8 0xc01f2286 in vop_stdbwrite () #9 0xc01f20e1 in vop_defaultop () #10 0xc01ecfba in bawrite () #11 0xc01ffcd0 in spec_fsync () #12 0xc0303e2a in mfs_fsync () #13 0xc03022ff in ffs_sync () #14 0xc01f703b in sync () #15 0xc01c7496 in boot () #16 0xc01c7ab8 in poweroff_wait () #17 0xc036c4c6 in trap_fatal () #18 0xc036c199 in trap_pfault () #19 0xc036bd83 in trap () #20 0xc01ca6b8 in tsleep () #21 0xc01e7c75 in sb_lock () #22 0xc01e5698 in sosend () #23 0xc0225201 in ng_ksocket_rcvdata () #24 0xc021ef71 in ng_send_data () #25 0xc022c4e3 in ng_pptpgre_xmit () #26 0xc022c04c in ng_pptpgre_rcvdata () #27 0xc021ef71 in ng_send_data () #28 0xc0228638 in ng_ppp_output () #29 0xc0228186 in ng_ppp_rcvdata () #30 0xc021ef71 in ng_send_data () #31 0xc0221f26 in ng_bpf_rcvdata () #32 0xc021ef71 in ng_send_data () #33 0xc0224085 in ng_iface_output () #34 0xc02376df in ip_output () #35 0xc02390d6 in rip_output () #36 0xc023952b in rip_send () #37 0xc01e5bb3 in sosend () #38 0xc0225201 in ng_ksocket_rcvdata () #39 0xc021ef71 in ng_send_data () #40 0xc022c4e3 in ng_pptpgre_xmit () #41 0xc022cb24 in ng_pptpgre_send_ack_timeout () #42 0xc01cd515 in softclock () The kernel I'm running has all the NETGRAPH options from LINT compiled in (minus NETGRAPH_MPPC_COMPRESSION, which was commented out). I'd appreciate any help. (And have other data...my mpd configuration, etc. I don't have a full symbol table, though...my system didn't quite match up with what the Developer's Handbook said to expect. /sys/compile and /usr/sys/compile have only an empty ".keepit" after doing the "make buildkernel" / "make installkernel" thing. I did compile with the DEBUG=-g line uncommented in my kernel config file. Thanks a lot, Scott Lamb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 3 22:45:12 2002 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 1AFD037B405 for ; Thu, 3 Jan 2002 22:45:06 -0800 (PST) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id WAA58097; Thu, 3 Jan 2002 22:34:04 -0800 (PST) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.6/8.11.6) id g046Y5N23209; Thu, 3 Jan 2002 22:34:05 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200201040634.g046Y5N23209@arch20m.dellroad.org> Subject: Re: netgraph kernel panic In-Reply-To: <20020104043335.GA87710@cairo.zsat.net> "from Scott Lamb at Jan 3, 2002 10:33:35 pm" To: Scott Lamb Date: Thu, 3 Jan 2002 22:34:05 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Scott Lamb writes: > FreeBSD 4.5-PRERELEASE (as of a few days ago) is crashing consistently > when I try to initiate a PPTP connection to with mpd-netgraph 3.3 (from > ports). This is due to a problem caused by the peer's "outside" PPTP IP address (the one from mpd.links) being equal to its "inside" IP address (the one from "set ipcp ranges ..."). Make those different and it should stop crashing. Also, apply the patch below to prevent it from happening again. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com Index: ipcp.c =================================================================== RCS file: /home/cvs/archie/mpd/src/ipcp.c,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- ipcp.c 2001/04/12 17:03:31 1.2 +++ ipcp.c 2001/12/16 03:47:25 1.3 @@ -19,6 +19,7 @@ #include "custom.h" #include "msg.h" #include "ngfunc.h" +#include "pptp.h" #include #include @@ -607,7 +608,7 @@ switch (mode) { case MODE_REQ: if (!IpAddrInRange(&ipcp->conf.peer_allow, *ip) || !ip->s_addr) { - if (ipcp->peer_addr.s_addr == 0) +nak_ip: if (ipcp->peer_addr.s_addr == 0) Log(LG_IPCP, (" %s", "no IP address available for peer!")); if (Enabled(&ipcp->conf.options, IPCP_CONF_PRETENDIP)) { Log(LG_IPCP, (" pretending that %s is OK, will ignore", @@ -620,6 +621,17 @@ Log(LG_IPCP, (" NAKing with %s", inet_ntoa(*ip))); FsmNak(fp, opt); break; + } + if (bund->links[0]->phys->type == &gPptpPhysType) { + struct in_addr pip; + + lnk = bund->links[0]; + pip = PptpGetPeerIp(); + if (ip->s_addr == pip.s_addr) { + Log(LG_IPCP, + (" Same as PPTP IP; would cause routing loop")); + goto nak_ip; + } } Log(LG_IPCP, (" %s is OK", inet_ntoa(*ip))); ipcp->peer_addr = *ip; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 3 23:28:42 2002 Delivered-To: freebsd-net@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 6AC4537B416 for ; Thu, 3 Jan 2002 23:28:38 -0800 (PST) Received: (from tim@localhost) by shell.futuresouth.com (8.11.6/8.11.1) id g047SbG67123 for freebsd-net@FreeBSD.ORG; Fri, 4 Jan 2002 01:28:37 -0600 (CST) Date: Fri, 4 Jan 2002 01:28:37 -0600 From: Tim To: freebsd-net@FreeBSD.ORG Subject: PPPoE and "carrier" lost? Message-ID: <20020104012836.A65890@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org We just got a DSL connection and I am having a slight problem with ppp/PPPoE not recognizing a lost connection and renegotiate a new IP address. For example, if I reboot the DSL modem or unplug/plug the line back in where the remote ppp connection is lost, ppp doesn't recognize this and still associates the old IP address with tun0. Isn't PPPoE supposed to recognize a "carrier" lost? It seems to never notice when I reboot the DSL modem (or just turn it off). This is obviously not ideal if the remote ppp session ever went down. Any suggestions? This is what we have: 1) FreeBSD -stable (4.5-PRE) 2) Alcatel 1000 Ethernet DSL modem, connected to xl0 3) internal network connected to fxp0 4) my ppp.conf looks like this: DSL: set device PPPoE:xl0 # set MRU 1490 # set MTU 1490 set authname ... set authkey ... set dial set ifaddr 10.0.0.1/0 10.0.0.2/0 add default HISADDR nat enable yes # set cd off # set crtscts off 5) ifconfig -a looks like this: tim@gw [1:23am] ~ > ifconfig -a xl0: flags=8843 mtu 1500 ether 00:c0:4f:bf:13:4c media: Ethernet autoselect (10baseT/UTP) status: active fxp0: flags=8843 mtu 1500 inet 192.168.0.1 netmask 0xffff0000 broadcast 192.168.255.255 ether 00:d0:b7:18:f8:82 media: Ethernet autoselect (10baseT/UTP) status: active lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 ppp0: flags=8010 mtu 1500 tun0: flags=8051 mtu 1492 inet 66.165.196.231 --> 66.165.196.1 netmask 0xff000000 Opened by PID 659 Thanks! Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 4 0:57:22 2002 Delivered-To: freebsd-net@freebsd.org Received: from cairo.zsat.net (cairo.zsat.net [64.6.64.200]) by hub.freebsd.org (Postfix) with ESMTP id 8084A37B419 for ; Fri, 4 Jan 2002 00:57:18 -0800 (PST) Received: by cairo.zsat.net (Postfix, from userid 1002) id C1970A6A04; Fri, 4 Jan 2002 02:57:12 -0600 (CST) Date: Fri, 4 Jan 2002 02:57:12 -0600 From: Scott Lamb To: Archie Cobbs Cc: freebsd-net@freebsd.org Subject: Re: netgraph kernel panic Message-ID: <20020104085712.GA88991@cairo.zsat.net> References: <20020104043335.GA87710@cairo.zsat.net> <200201040634.g046Y5N23209@arch20m.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200201040634.g046Y5N23209@arch20m.dellroad.org> User-Agent: Mutt/1.3.24i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Looks like I have a slightly different situation than you're describing. I'm not specifying a "set ipcp ranges" anywhere. The peer chooses an inside address that's different from but within the same /24 as its outside address. I'm trying to run everything within two /16s over the VPN (which include those addresses). So I guess I'm getting the same routing loop but in a slightly more complicated way. Taking out my "set iface route" lines in mpd.conf made it no longer crash and I can talk to just the VPN host. So I tried next a "route add vpnhost mygw" before starting the VPN. It worked. So that's definitely the problem. It would be nice if there were a slicker way of doing this (mpd automatically adding that route if this situation occurs?), especially since I'm on DHCP. And it does make me nervous that mpd can make the kernel crash at all. But I can at least work around this now. Thanks a lot for your quick, helpful response. Scott Lamb On Thu, Jan 03, 2002 at 10:34:05PM -0800, Archie Cobbs wrote: > Scott Lamb writes: > > FreeBSD 4.5-PRERELEASE (as of a few days ago) is crashing consistently > > when I try to initiate a PPTP connection to with mpd-netgraph 3.3 (from > > ports). > > This is due to a problem caused by the peer's "outside" PPTP IP address > (the one from mpd.links) being equal to its "inside" IP address (the > one from "set ipcp ranges ..."). > > Make those different and it should stop crashing. Also, apply > the patch below to prevent it from happening again. > > -Archie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 4 1:16: 2 2002 Delivered-To: freebsd-net@freebsd.org Received: from roadrunner.rominet.net (ATuileries-109-1-1-175.abo.wanadoo.fr [217.128.134.175]) by hub.freebsd.org (Postfix) with ESMTP id F3E6337B417 for ; Fri, 4 Jan 2002 01:15:58 -0800 (PST) Received: by roadrunner.rominet.net (Postfix, from userid 1000) id D98F73EBF; Fri, 4 Jan 2002 10:15:46 +0100 (CET) Date: Fri, 4 Jan 2002 10:15:46 +0100 From: Alain Thivillon To: Tim Cc: freebsd-net@FreeBSD.ORG Subject: Re: PPPoE and "carrier" lost? Message-ID: <20020104091546.GD67729@roadrunner.rominet.net> References: <20020104012836.A65890@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020104012836.A65890@futuresouth.com> User-Agent: Mutt/1.3.24i X-Organization: Rominet Networks Inc. X-Operating-System: FreeBSD 4.5-PRERELEASE Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > back in where the remote ppp connection is lost, ppp doesn't recognize > this and still associates the old IP address with tun0. Isn't PPPoE > supposed to recognize a "carrier" lost? It seems to never notice when I No. > DSL: > set device PPPoE:xl0 > # set MRU 1490 > # set MTU 1490 > set authname ... > set authkey ... > set dial > set ifaddr 10.0.0.1/0 10.0.0.2/0 > add default HISADDR > nat enable yes Add: set lqrperiod 5 set reconnect 5 10000 set redial 5 10000 To enable lqr (lcp echo) on link and reconnect automagically. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 4 1:26:40 2002 Delivered-To: freebsd-net@freebsd.org Received: from jane.inty.net (jane.inty.net [195.224.93.242]) by hub.freebsd.org (Postfix) with ESMTP id 356E037B41D for ; Fri, 4 Jan 2002 01:26:28 -0800 (PST) Received: from inty.hq.inty.net (inty.hq.inty.net [213.38.150.150]) by jane.inty.net (8.11.3/8.11.3) with ESMTP id g049QNH50099 for ; Fri, 4 Jan 2002 09:26:23 GMT Received: from tariq ([10.0.1.156]) by inty.hq.inty.net (8.12.1/8.12.1) with SMTP id g049QMiv094029 for ; Fri, 4 Jan 2002 09:26:22 GMT From: "Tariq Rashid" To: Subject: KAME ipsec and mtu (via gif) - no icmp frag needed Date: Fri, 4 Jan 2002 09:27:33 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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) In-Reply-To: <20020104085712.GA88991@cairo.zsat.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Sender-IP: 10.0.1.156 X-suppress-rcpt-virus-notify: yes X-Skip-Virus-Check: yes X-Virus-Checked: 36455 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org this is a question about the correct way to handle MTUs and fragmentation when using IPSEC on FreeBSD4.4R I'm routing via a local gif0 tunnel which has aliases added to it for multiple destinations... and the KAME ipsec code grabs the packets just after they enter the gif0 device. In fact the ipsec SAs are handled by a port of the openbsd isakmpd. There is no problem here. Now, a standard ping packet is small enough to go through the ipsec encapsulation and not require fragmentation. However, a larger ping packet, or say, an ftp transfer, does cause fragmentation to occur such that one normal packet is broken into two packets and then the ipsec headers are added. The resulting ipsec esp packets are below the mtu limit (of 1500). This is also fine. But i was wondering why the kame ipsec code does not send an icmp error message to the sender informing it of the need to defragment. The sender would then send smaller chunks resulting in no fragmentation. I think this is normal for plain IP communication? any ideas gratefully received... or am i configuring it wrong? i have experimented with the mtu of the external interfaces and the gif devices too. tariq ----------------------------------------------- Information in this electronic mail message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient any use, disclosure, copying or distribution of this message is prohibited and may be unlawful. When addressed to our customers, any information contained in this message is subject to Intelligent Network Technology Ltd Terms & Conditions. ----------------------------------------------- Take part in the intY 2001 Email Usage survey online at http://www.inty.net/email/survey.html ----------------------------------------------- intY has automatically scanned this email with Sophos Anti-Virus (www.inty.net) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 4 8:35:39 2002 Delivered-To: freebsd-net@freebsd.org Received: from zrtps0kn.nortelnetworks.com (h55s192a140n47.user.nortelnetworks.com [47.140.192.55]) by hub.freebsd.org (Postfix) with ESMTP id 1194E37B405 for ; Fri, 4 Jan 2002 08:35:35 -0800 (PST) Received: from zrtpd004.us.nortel.com (zrtpd004.us.nortel.com [47.28.160.173]) by zrtps0kn.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g04GZRZ06992 for ; Fri, 4 Jan 2002 11:35:28 -0500 (EST) Received: by zrtpd004.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 4 Jan 2002 11:33:49 -0500 Message-ID: <3324A9F618DDD511B8210002A52CDE38130137@zcaly0jd.ca.nortel.com> From: "Samuel Chow" To: "'freebsd-net@freebsd.org'" Subject: Please commit kern/31954 patch Date: Fri, 4 Jan 2002 11:33:58 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1953D.9BBEA1F0" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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_001_01C1953D.9BBEA1F0 Content-Type: text/plain; charset="iso-8859-1" Hi there, Can someone please commit kern/31954? I've just been bitten by it on a recently cvsup'ed -stable. For reference, the problem is the xl card not seeing its own broadcast packet. Thanks in advance. --- Samuel Chow This message is displayed using recycled electrons. Segmentation Fault (core dumped) ------_=_NextPart_001_01C1953D.9BBEA1F0 Content-Type: text/html; charset="iso-8859-1" Please commit kern/31954 patch

Hi there,

        Can someone please commit kern/31954?  I've
        just been bitten by it on a recently cvsup'ed
        -stable.

        For reference, the problem is the xl card not
        seeing its own broadcast packet.

        Thanks in advance.

---
Samuel Chow

This message is displayed using recycled electrons.
Segmentation Fault (core dumped)

------_=_NextPart_001_01C1953D.9BBEA1F0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 4 10:20:18 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 5783237B417 for ; Fri, 4 Jan 2002 10:20:12 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020104182011.MEPC20119.rwcrmhc51.attbi.com@InterJet.elischer.org>; Fri, 4 Jan 2002 18:20:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA28903; Fri, 4 Jan 2002 10:15:34 -0800 (PST) Date: Fri, 4 Jan 2002 10:15:32 -0800 (PST) From: Julian Elischer To: Tim Cc: freebsd-net@FreeBSD.ORG Subject: Re: PPPoE and "carrier" lost? In-Reply-To: <20020104012836.A65890@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The pppoe protocol has no 'keepalives' so there is no way for the client side to know that there is a broken connection. However PPP DOES have keepalives so it should discover that it has lost connection after a while and tear down the link and restart it. In other wirds, it's not PPPOE's job but PP's job to identify teh problem. On Fri, 4 Jan 2002, Tim wrote: > We just got a DSL connection and I am having a slight problem with > ppp/PPPoE not recognizing a lost connection and renegotiate a new IP > address. For example, if I reboot the DSL modem or unplug/plug the line > back in where the remote ppp connection is lost, ppp doesn't recognize > this and still associates the old IP address with tun0. Isn't PPPoE > supposed to recognize a "carrier" lost? It seems to never notice when I > reboot the DSL modem (or just turn it off). This is obviously not ideal > if the remote ppp session ever went down. Any suggestions? This is what > we have: > > 1) FreeBSD -stable (4.5-PRE) > 2) Alcatel 1000 Ethernet DSL modem, connected to xl0 > 3) internal network connected to fxp0 > 4) my ppp.conf looks like this: > > DSL: > set device PPPoE:xl0 > # set MRU 1490 > # set MTU 1490 > set authname ... > set authkey ... > set dial > set ifaddr 10.0.0.1/0 10.0.0.2/0 > add default HISADDR > nat enable yes > # set cd off > # set crtscts off > > 5) ifconfig -a looks like this: > > tim@gw [1:23am] ~ > ifconfig -a > xl0: flags=8843 mtu 1500 > ether 00:c0:4f:bf:13:4c > media: Ethernet autoselect (10baseT/UTP) > status: active > fxp0: flags=8843 mtu 1500 > inet 192.168.0.1 netmask 0xffff0000 broadcast 192.168.255.255 > ether 00:d0:b7:18:f8:82 > media: Ethernet autoselect (10baseT/UTP) > status: active > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > ppp0: flags=8010 mtu 1500 > tun0: flags=8051 mtu 1492 > inet 66.165.196.231 --> 66.165.196.1 netmask 0xff000000 > Opened by PID 659 > > Thanks! > > Tim > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 4 11:17:33 2002 Delivered-To: freebsd-net@freebsd.org Received: from mail2.home.nl (mail2.home.nl [213.51.129.226]) by hub.freebsd.org (Postfix) with ESMTP id 64C5337B416 for ; Fri, 4 Jan 2002 11:17:30 -0800 (PST) Received: from testuser ([213.51.195.75]) by mail2.home.nl (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20020104191815.EVEL9819.mail2.home.nl@testuser> for ; Fri, 4 Jan 2002 20:18:15 +0100 Message-ID: <023f01c19554$770e6c70$0200a8c0@testuser> From: "Marcel Dijk" To: Subject: ProFTPd RESUME Date: Fri, 4 Jan 2002 20:17:32 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_023C_01C1955C.D709D440" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Disposition-Notification-To: "Marcel Dijk" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_023C_01C1955C.D709D440 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, How do I configure ProFTPd to support resuming broken downloads. Thanks! Marcel ------=_NextPart_000_023C_01C1955C.D709D440 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
 
How do I configure ProFTPd to support = resuming=20 broken downloads.
 
Thanks!
 
Marcel
------=_NextPart_000_023C_01C1955C.D709D440-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 4 13: 9:44 2002 Delivered-To: freebsd-net@freebsd.org Received: from rerun.lucentctc.com (rerun.lucentctc.com [199.93.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 631BB37B42A for ; Fri, 4 Jan 2002 13:09:28 -0800 (PST) Received: by rerun.lucentctc.com with Internet Mail Service (5.5.2653.19) id ; Fri, 4 Jan 2002 16:09:19 -0500 Message-ID: <3A6D367EA1EFD4118C9B00A0C9DD99D7065399@rerun.lucentctc.com> From: "Cambria, Mike" To: "'freebsd-net@freebsd.org'" Cc: "Cambria, Mike" Subject: TCP connection via IPsec machine also running natd Date: Fri, 4 Jan 2002 16:09:15 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm having problems connecting (e.g. telnet, ssh, ftp etc.) to a machine which is at the other end of an IPsec tunnel. Passing data with machines, via this tunnel, on subnets for which the tunnel endpoint is acting as a router work just fine. I'm using FreeBSD 4.4-Stable (cvsup'ed shortly after 4.4-Release) and have an IPsec tunnel from one subnet at home to a machine at a friends house. The subnet at home is behind ipfw/natd and uses a cable modem (i.e. one IP address) to access the Internet. I'm using ipfw "simple" with one addition to allow incoming TCP traffic from the friends machine (also FreeBSD 4.4). This _works_ fine for traffic to/from the subnet. Encrypted packets hit divert, get counted on the ipfw allow esp rule, are decrypted and are then routed to the destination machine and vice versa. Problems exist only with traffic from the remote (friends) machine that terminates at the ipfw/natd machine itself. The IKE (racoon) ISAKMP-SA is established just fine, an IPsec-SA is established for both directions and the remote machine sends the (e.g.) telnet traffic encrypted. The counters for ipfw show the packet hitting the divert rule and esp packet has been received. However, the connection never seems to make it to telnetd. Before setting up IPsec, this worked just fine. I tried again using the sock program (see Unix Network Programming, Vol. 1 2ed ) to have more control, rule out inted etc. with the same results. sock -s never returns form the listen call. As I said earlier, packets which route through ipfw/natd get unencrypted and make it to the remote subnet just fine. Looking at 'ipfw -a l' it seems that the ESP packets are being received _after_ being diverted to natd, but just not sent to the socket: [deleted] 01600 20 4384 divert 8668 ip from any to any via vx0 01700 0 0 deny ip from 10.0.0.0/8 to any via vx0 01800 0 0 deny ip from 172.16.0.0/12 to any via vx0 01900 0 0 deny ip from 192.168.0.0/16 to any via vx0 02000 0 0 deny ip from 0.0.0.0/8 to any via vx0 02100 0 0 deny ip from 169.254.0.0/16 to any via vx0 02200 0 0 deny ip from 192.0.2.0/24 to any via vx0 02300 0 0 deny ip from 224.0.0.0/4 to any via vx0 02400 0 0 deny ip from 240.0.0.0/4 to any via vx0 02500 19 4272 allow tcp from any to any established (an ssh session I have up to gather info on one PC) 02600 0 0 allow ip from any to any frag 02700 0 0 allow udp from any to any 500 02800 0 0 allow udp from any 500 to any 02900 1 112 allow esp from any to any (the encrypted packet) [deleted] 03500 0 0 allow tcp from to 66.31.106.72 setup [rest deleted] Any thoughts on where to look next? I don't see any counters for "deny" rules going up, so I'm guessing that the unencrypted packet isn't getting dropped due to one of my ipfw rules. I also notice that the counter on my firewall rule which explicitly allows session setup from my friends machine is not incrementing. Any help appreciated. Thanks, MikeC Michael C. Cambria Avaya Inc. Consulting Engineer Former Enterprise Networks Group voice: (978) 287 - 2807 of Lucent Technologies fax: (978) 381 - 6415 300 Baker Avenue email: mcambria@avaya.com Concord, Massachusetts 01742 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 4 15:51: 9 2002 Delivered-To: freebsd-net@freebsd.org Received: from artemis.drwilco.net (artemis.drwilco.net [209.167.6.62]) by hub.freebsd.org (Postfix) with ESMTP id 12C9937B419 for ; Fri, 4 Jan 2002 15:51:07 -0800 (PST) Received: from ceres.drwilco.net (docwilco.xs4all.nl [213.84.68.230]) by artemis.drwilco.net (8.11.6/8.11.6) with ESMTP id g04Np4R76009 (using TLSv1/SSLv3 with cipher DES-CBC3-SHA (168 bits) verified NO); Fri, 4 Jan 2002 18:51:06 -0500 (EST) (envelope-from drwilco@drwilco.net) Message-Id: <5.1.0.14.0.20020105005712.01cdcc50@mail.drwilco.net> X-Sender: lists@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 05 Jan 2002 00:59:58 +0100 To: "Cambria, Mike" From: "Rogier R. Mulhuijzen" Subject: Re: TCP connection via IPsec machine also running natd Cc: freebsd-net@freebsd.org In-Reply-To: <3A6D367EA1EFD4118C9B00A0C9DD99D7065399@rerun.lucentctc.com > Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >As I said earlier, packets which route through ipfw/natd get unencrypted and >make it to the remote subnet just fine. > >Looking at 'ipfw -a l' it seems that the ESP packets are being received >_after_ being diverted to natd, but just >not sent to the socket: I'm no IPsec expert (still something I need to look into) but something that springs to mind is to allow the packet before the natd divert. I couldn't say why this would work (since natd shouldn't touch the packet, and you say other packets go through fine), but it's just a hunch =) DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 4 16:41:23 2002 Delivered-To: freebsd-net@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id BAD5E37B41D for ; Fri, 4 Jan 2002 16:41:16 -0800 (PST) Received: from user-11202ba.dsl.mindspring.com ([66.32.9.106] helo=compaq) by blount.mail.mindspring.net with smtp (Exim 3.33 #1) id 16Metc-00014R-00 for freebsd-net@freebsd.org; Fri, 04 Jan 2002 19:41:12 -0500 Message-ID: <006f01c19453$aad27440$6a092042@compaq> From: "Naga R Narayanaswamy" To: Subject: Bridging and 'pseudo-device tap' and PPPoE Date: Thu, 3 Jan 2002 07:39:20 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_006C_01C19429.C1B1A7A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_006C_01C19429.C1B1A7A0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello: I want to create pseudo ethernet devices to simulate many NICs on=20 a PC. In Solaris, we can do "ifconfig hme0:1 10.1.1.1 up" hme0:2 etc to create logival interfaces. I am trying to do a similar = thing on FreeBSD. But after searching the archives, I find that I have to use=20 tap device. Is there any other way than the approach I am using below. I reconfigured the kernel and I have configured the tap device. =20 ifconfig tap0 shows a MAC address and UP status. I assigned a IP address also. I want to make fxp0 and tap0 in one bridge group.=20 I tried both approaches, using "option BRIDGE" and ng_bridge example in /usr/share/examples. Is bridging supposed to work with tap devices? I do not see the bridging happen between tap0 and fxp0.=20 I can see the packet written on tap device when I do a =20 "hexdump /dev/tap0", but not on fxp0 (using ethereal).=20 (I am doing a ping out of tap interface). And when I have bridging turned on using ng_bridge, if I initiate a PPPoE session, I get socket already connected warning, but I do not see the PADI packet on the fxp0 interface at all. The goal is that I want to use tap0 device in ppp.conf and initiate a ppp -ddial =20 The goal is to have 100 tap devices and initiate pppoe sessions over each of the tap sessions=20 to simulate a 100 NIC cards with different mac addresses. Thanks Naga ------=_NextPart_000_006C_01C19429.C1B1A7A0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hello:
 
I want to create pseudo ethernet devices to simulate many NICs on =
a PC. In Solaris, we can do "ifconfig hme0:1 10.1.1.1 up"
hme0:2 etc to create logival interfaces. I am trying to do a = similar=20 thing
on FreeBSD. But after searching the archives, I find that I have to = use=20
tap device. Is there any other way than the approach I am using=20 below.
 
I reconfigured the kernel and I have configured the tap = device. =20
ifconfig tap0 shows a MAC address and UP status.
I assigned a IP address also.
I want to make fxp0 and tap0 in one bridge group.
I tried both approaches, using "option BRIDGE"
and ng_bridge example in /usr/share/examples.
Is bridging supposed to work with tap devices?
 
I do not see the bridging  happen between tap0 and fxp0. =
I can see the packet written on tap device when I do a 
"hexdump /dev/tap0", but not on fxp0 (using ethereal).
(I am doing a ping out of tap interface).
And when I have bridging turned on using ng_bridge,
if I initiate a PPPoE session, I get socket already connected
warning, but I do not see the PADI packet on the fxp0 = interface
at all.
 
The goal is that I want to use tap0 device in ppp.conf
and initiate a ppp -ddial <service>
The goal is to have 100 tap devices and initiate
pppoe sessions over each of the tap sessions
to simulate a 100 NIC cards with different mac = addresses.
 
Thanks
Naga
------=_NextPart_000_006C_01C19429.C1B1A7A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 4 17:31:57 2002 Delivered-To: freebsd-net@freebsd.org Received: from artemis.drwilco.net (artemis.drwilco.net [209.167.6.62]) by hub.freebsd.org (Postfix) with ESMTP id 7237D37B9F0 for ; Fri, 4 Jan 2002 17:17:44 -0800 (PST) Received: from ceres.drwilco.net (docwilco.xs4all.nl [213.84.68.230]) by artemis.drwilco.net (8.11.6/8.11.6) with ESMTP id g051HgR78110 (using TLSv1/SSLv3 with cipher DES-CBC3-SHA (168 bits) verified NO); Fri, 4 Jan 2002 20:17:44 -0500 (EST) (envelope-from drwilco@drwilco.net) Message-Id: <5.1.0.14.0.20020105021521.01cdcc50@mail.drwilco.net> X-Sender: lists@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 05 Jan 2002 02:26:35 +0100 To: "Naga R Narayanaswamy" From: "Rogier R. Mulhuijzen" Subject: Re: Bridging and 'pseudo-device tap' and PPPoE Cc: freebsd-net@freebsd.org In-Reply-To: <006f01c19453$aad27440$6a092042@compaq> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_119636758==_.ALT" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --=====================_119636758==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed At 07:39 3-1-2002 -0500, you wrote: >Hello: > >I want to create pseudo ethernet devices to simulate many NICs on >a PC. In Solaris, we can do "ifconfig hme0:1 10.1.1.1 up" >hme0:2 etc to create logival interfaces. I am trying to do a similar thing >on FreeBSD. But after searching the archives, I find that I have to use >tap device. Is there any other way than the approach I am using below. Doing that on Solaris gives you additional MAC addresses? >I reconfigured the kernel and I have configured the tap device. $ kldload tap >:-) >ifconfig tap0 shows a MAC address and UP status. >I assigned a IP address also. >I want to make fxp0 and tap0 in one bridge group. >I tried both approaches, using "option BRIDGE" >and ng_bridge example in /usr/share/examples. >Is bridging supposed to work with tap devices? I've used bridging with tap devices plenty. Works fine for me. >I do not see the bridging happen between tap0 and fxp0. >I can see the packet written on tap device when I do a >"hexdump /dev/tap0", but not on fxp0 (using ethereal). >(I am doing a ping out of tap interface). >And when I have bridging turned on using ng_bridge, >if I initiate a PPPoE session, I get socket already connected >warning, but I do not see the PADI packet on the fxp0 interface >at all. TAP devices don't actually work unless there's a process that has the /dev/ entry opened and reads from it (well, they'll buffer a little). >The goal is that I want to use tap0 device in ppp.conf >and initiate a ppp -ddial >The goal is to have 100 tap devices and initiate >pppoe sessions over each of the tap sessions >to simulate a 100 NIC cards with different mac addresses. You might want to use the netgraph ng_eiface node which simulates an ethernet interface (if I recall correctly) and you should be able to connect that to the ng_bridge node fine. Though what exactly is happening with ng_bridge & pppoe you'd need to find out. Maybe someone who knows more about userland ppp & PPPoE can clarify that. One downside.... I just looked and ng_eiface is not in 4.X yet. Looking at the CVS logs I'm not even sure it will be built when you build -CURRENT. Maybe Julian can shed some light on this =) DocWilco --=====================_119636758==_.ALT Content-Type: text/html; charset="us-ascii" At 07:39 3-1-2002 -0500, you wrote:
Hello:
 
I want to create pseudo ethernet devices to simulate many NICs on
a PC. In Solaris, we can do "ifconfig hme0:1 10.1.1.1 up"
hme0:2 etc to create logival interfaces. I am trying to do a similar thing
on FreeBSD. But after searching the archives, I find that I have to use
tap device. Is there any other way than the approach I am using below.

Doing that on Solaris gives you additional MAC addresses?

I reconfigured the kernel and I have configured the tap device. 

$ kldload tap          >:-)

ifconfig tap0 shows a MAC address and UP status.
I assigned a IP address also.
I want to make fxp0 and tap0 in one bridge group.
I tried both approaches, using "option BRIDGE"
and ng_bridge example in /usr/share/examples.
Is bridging supposed to work with tap devices?

I've used bridging with tap devices plenty. Works fine for me.

I do not see the bridging  happen between tap0 and fxp0.
I can see the packet written on tap device when I do a 
"hexdump /dev/tap0", but not on fxp0 (using ethereal).
(I am doing a ping out of tap interface).
And when I have bridging turned on using ng_bridge,
if I initiate a PPPoE session, I get socket already connected
warning, but I do not see the PADI packet on the fxp0 interface
at all.

TAP devices don't actually work unless there's a process that has the /dev/ entry opened and reads from it (well, they'll buffer a little).

The goal is that I want to use tap0 device in ppp.conf
and initiate a ppp -ddial <service>
The goal is to have 100 tap devices and initiate
pppoe sessions over each of the tap sessions
to simulate a 100 NIC cards with different mac addresses.

You might want to use the netgraph ng_eiface node which simulates an ethernet interface (if I recall correctly) and you should be able to connect that to the ng_bridge node fine. Though what exactly is happening with ng_bridge & pppoe you'd need to find out. Maybe someone who knows more about userland ppp & PPPoE can clarify that.

One downside.... I just looked and ng_eiface is not in 4.X yet. Looking at the CVS logs I'm not even sure it will be built when you build -CURRENT. Maybe Julian can shed some light on this =)

        DocWilco

--=====================_119636758==_.ALT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 4 19:45:12 2002 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 8A86E37B41D for ; Fri, 4 Jan 2002 19:45:08 -0800 (PST) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id TAA64335; Fri, 4 Jan 2002 19:35:15 -0800 (PST) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.6/8.11.6) id g053ZFo26297; Fri, 4 Jan 2002 19:35:15 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200201050335.g053ZFo26297@arch20m.dellroad.org> Subject: Re: netgraph kernel panic In-Reply-To: <20020104085712.GA88991@cairo.zsat.net> "from Scott Lamb at Jan 4, 2002 02:57:12 am" To: Scott Lamb Date: Fri, 4 Jan 2002 19:35:15 -0800 (PST) Cc: Archie Cobbs , freebsd-net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Scott Lamb writes: > Looks like I have a slightly different situation than you're describing. > I'm not specifying a "set ipcp ranges" anywhere. The peer chooses an > inside address that's different from but within the same /24 as its > outside address. I'm trying to run everything within two /16s over the > VPN (which include those addresses). So I guess I'm getting the same > routing loop but in a slightly more complicated way. Yes.. the problem happens when the route to the outside IP address goes over the PPTP tunnel.. you get an "infinite encapsulation loop". > Taking out my "set iface route" lines in mpd.conf made it no longer > crash and I can talk to just the VPN host. So I tried next a "route add > vpnhost mygw" before starting the VPN. It worked. So that's definitely > the problem. It would be nice if there were a slicker way of doing this > (mpd automatically adding that route if this situation occurs?), > especially since I'm on DHCP. And it does make me nervous that mpd can > make the kernel crash at all. But I can at least work around this now. You are right, kernel crashing is always bogus no matter how it happens. Mpd adding a host route for the remote IP is a good idea, I didn't think of that. I'll try to add something to that effect when time permits. Really there are two things to fix: mpd as you describe, and ng_ksocket, which is where the crash originates. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 4 20:30: 7 2002 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 45BF937B419 for ; Fri, 4 Jan 2002 20:30:04 -0800 (PST) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id UAA64571; Fri, 4 Jan 2002 20:20:23 -0800 (PST) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.6/8.11.6) id g054KNx26451; Fri, 4 Jan 2002 20:20:23 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200201050420.g054KNx26451@arch20m.dellroad.org> Subject: Re: netgraph kernel panic In-Reply-To: <200201050335.g053ZFo26297@arch20m.dellroad.org> "from Archie Cobbs at Jan 4, 2002 07:35:15 pm" To: Archie Cobbs Date: Fri, 4 Jan 2002 20:20:23 -0800 (PST) Cc: Scott Lamb , freebsd-net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Archie Cobbs writes: > > Taking out my "set iface route" lines in mpd.conf made it no longer > > crash and I can talk to just the VPN host. So I tried next a "route add > > vpnhost mygw" before starting the VPN. It worked. So that's definitely > > the problem. It would be nice if there were a slicker way of doing this > > (mpd automatically adding that route if this situation occurs?), > > especially since I'm on DHCP. And it does make me nervous that mpd can > > make the kernel crash at all. But I can at least work around this now. > > You are right, kernel crashing is always bogus no matter how it > happens. Mpd adding a host route for the remote IP is a good idea, > I didn't think of that. I'll try to add something to that effect > when time permits. > > Really there are two things to fix: mpd as you describe, and > ng_ksocket, which is where the crash originates. If you have time, please try applying the patch below to your kernel. Leave the mpd configuration as it was, and let's see if we get a normal error instead of a kernel panic (I don't have a test setup for this myself just now). This is for FreeBSD-4.4, let me know if you have a different version. Thanks, -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com --- netgraph/ng_ksocket.c.orig Fri Feb 16 09:37:48 2001 +++ netgraph/ng_ksocket.c Fri Jan 4 20:18:49 2002 @@ -72,8 +72,9 @@ /* Node private data */ struct ng_ksocket_private { - hook_p hook; - struct socket *so; + hook_p hook; /* our hook, if any */ + struct socket *so; /* our associated socket */ + u_int sending; /* writing to socket */ }; typedef struct ng_ksocket_private *priv_p; @@ -792,7 +793,13 @@ int error; NG_FREE_META(meta); + if (priv->sending) { + NG_FREE_DATA(m); + return (EDEADLK); + } + priv->sending++; error = (*so->so_proto->pr_usrreqs->pru_sosend)(so, 0, 0, m, 0, 0, p); + priv->sending--; return (error); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 5 11:21: 4 2002 Delivered-To: freebsd-net@freebsd.org Received: from cairo.zsat.net (cairo.zsat.net [64.6.64.200]) by hub.freebsd.org (Postfix) with ESMTP id 0794B37B419 for ; Sat, 5 Jan 2002 11:20:59 -0800 (PST) Received: by cairo.zsat.net (Postfix, from userid 1002) id 0B17AA6A04; Sat, 5 Jan 2002 13:20:53 -0600 (CST) Date: Sat, 5 Jan 2002 13:20:52 -0600 From: Scott Lamb To: Archie Cobbs Cc: freebsd-net@freebsd.org Subject: Re: netgraph kernel panic Message-ID: <20020105192052.GA1739@cairo.zsat.net> References: <200201050335.g053ZFo26297@arch20m.dellroad.org> <200201050420.g054KNx26451@arch20m.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200201050420.g054KNx26451@arch20m.dellroad.org> User-Agent: Mutt/1.3.24i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Jan 04, 2002 at 08:20:23PM -0800, Archie Cobbs wrote: > If you have time, please try applying the patch below to your kernel. > Leave the mpd configuration as it was, and let's see if we get a > normal error instead of a kernel panic (I don't have a test setup > for this myself just now). Yep. I get this message when I don't add that route: [work] error writing len 12 frame to bypass: Resource deadlock avoided and it still works when I do add the route. > This is for FreeBSD-4.4, let me know if you have a different version. I'm following RELENG-4 (which calls itself 4.5-PRERELEASE now), so your patch didn't apply quite cleanly. Below is what I used (which likely isn't quite right). Thanks, Scott Lamb Index: netgraph/ng_ksocket.c =================================================================== RCS file: /home/ncvs/src/sys/netgraph/ng_ksocket.c,v retrieving revision 1.5.2.8 diff -u -r1.5.2.8 ng_ksocket.c --- netgraph/ng_ksocket.c 2001/12/07 02:59:20 1.5.2.8 +++ netgraph/ng_ksocket.c 2002/01/05 19:18:24 @@ -72,8 +72,9 @@ /* Node private data */ struct ng_ksocket_private { - hook_p hook; - struct socket *so; + hook_p hook; /* our hook, if any */ + struct socket *so; /* our associated socket */ + u_int sending; /* writing to socket */ }; typedef struct ng_ksocket_private *priv_p; @@ -810,7 +811,13 @@ } /* Send packet */ + if (priv->sending) { + NG_FREE_DATA(m, meta); + return (EDEADLK); + } + priv->sending++; error = (*so->so_proto->pr_usrreqs->pru_sosend)(so, sa, 0, m, 0, 0, p); + priv->sending--; /* Clean up and exit */ NG_FREE_META(meta); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 5 16: 4:12 2002 Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 2690F37B405 for ; Sat, 5 Jan 2002 16:04:09 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 6 Jan 2002 00:04:08 +0000 (GMT) To: freebsd-net@freebsd.org Subject: Bge driver problems. X-Request-Do: Date: Sun, 06 Jan 2002 00:04:08 +0000 From: David Malone Message-ID: <200201060004.aa73043@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org We've been playing with some Dell 2550 machines and ran into a problem with the bge driver. We have a machine which was recieving a continious stream of NFS requests. The machine is completey stable when we use the fxp driver and don't add the bge driver to the kernel. If we add the bge driver then we see the following erratically: 1) NMI just after the driver probes the card. 2) Freezes between the first and second probe message for the phy. 3) Freezes during fscking. 4) Freezes immediately after ifconfiging up. The lockups seem really solid - we can't break to the debugger using a serial console when they occur. If the machine manages to boot up past ifconfig (it manages this about 1 time in 10) then the machine seems to run quite happly for several days until it eventually locks up again. We suspect that reproducing this requires a constant stream of packets while the card is being initialised. We did also try breaking out of the lockups by programing the APIC to produce a NMI on keyboard interrupts. Unfortunately the lockups seem so solid that the NMI doesn't get through. I know Matt Dillon has seen some lockups at ifconfig time and was wondering if anyone else has seen similar problems? I dunno who has access to programming information for this chip, but I suspect something about how the hardware is being reset can't be quite right. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 5 17:15:10 2002 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id E2F2A37B416 for ; Sat, 5 Jan 2002 17:15:07 -0800 (PST) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id RAA70962; Sat, 5 Jan 2002 17:10:50 -0800 (PST) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.6/8.11.6) id g061Al132376; Sat, 5 Jan 2002 17:10:47 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200201060110.g061Al132376@arch20m.dellroad.org> Subject: Re: netgraph kernel panic In-Reply-To: <20020105192052.GA1739@cairo.zsat.net> "from Scott Lamb at Jan 5, 2002 01:20:52 pm" To: Scott Lamb Date: Sat, 5 Jan 2002 17:10:47 -0800 (PST) Cc: freebsd-net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Scott Lamb writes: > > If you have time, please try applying the patch below to your kernel. > > Leave the mpd configuration as it was, and let's see if we get a > > normal error instead of a kernel panic (I don't have a test setup > > for this myself just now). > > Yep. I get this message when I don't add that route: > > [work] error writing len 12 frame to bypass: Resource deadlock > avoided > > and it still works when I do add the route. Great, thanks for testing it. > > This is for FreeBSD-4.4, let me know if you have a different version. > > I'm following RELENG-4 (which calls itself 4.5-PRERELEASE now), so your > patch didn't apply quite cleanly. Below is what I used (which likely > isn't quite right). Your patch should be equivalent.. Thanks, -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 5 18:29:53 2002 Delivered-To: freebsd-net@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id C0C6337B439 for ; Sat, 5 Jan 2002 18:28:56 -0800 (PST) Received: from user-38lc2j1.dialup.mindspring.com ([209.86.10.97] helo=gohan.cjclark.org) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16N33N-0006KK-00; Sat, 05 Jan 2002 18:28:54 -0800 Received: (from cjc@localhost) by gohan.cjclark.org (8.11.6/8.11.1) id g05L0op03589; Sat, 5 Jan 2002 13:00:50 -0800 (PST) (envelope-from cjc) Date: Sat, 5 Jan 2002 12:58:31 -0800 From: "Crist J. Clark" To: Naga R Narayanaswamy Cc: freebsd-net@FreeBSD.ORG Subject: Re: Bridging and 'pseudo-device tap' and PPPoE Message-ID: <20020105125831.C204@gohan.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <006f01c19453$aad27440$6a092042@compaq> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <006f01c19453$aad27440$6a092042@compaq>; from nraju@mindspring.com on Thu, Jan 03, 2002 at 07:39:20AM -0500 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Jan 03, 2002 at 07:39:20AM -0500, Naga R Narayanaswamy wrote: > Hello: > > I want to create pseudo ethernet devices to simulate many NICs on > a PC. In Solaris, we can do "ifconfig hme0:1 10.1.1.1 up" > hme0:2 etc to create logival interfaces. I am trying to do a similar thing > on FreeBSD. # ifconfig fxp0 inet 10.1.1.1 alias -- "It's always funny until someone gets hurt. Then it's hilarious." Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 5 19:58:30 2002 Delivered-To: freebsd-net@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id CE6B637B402 for ; Sat, 5 Jan 2002 19:58:26 -0800 (PST) Received: from user-uiveql9.dsl.mindspring.com ([165.247.106.169] helo=mindspring.com) by granger.mail.mindspring.net with esmtp (Exim 3.33 #1) id 16N4S1-00088x-00; Sat, 05 Jan 2002 22:58:25 -0500 Message-ID: <3C372238.F529FB40@mindspring.com> Date: Sat, 05 Jan 2002 10:56:40 -0500 From: Naga R Narayanaswamy X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org, drwilco@drwilco.net Subject: Re: Bridging and 'pseudo-device tap' and PPPoE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > From: Rogier R. Mulhuijzen > To: Naga R Narayanaswamy > Cc: freebsd-net@freebsd.org > Sent: Friday, January 04, 2002 8:26 PM > Subject: Re: Bridging and 'pseudo-device tap' and PPPoE > > At 07:39 3-1-2002 -0500, you wrote: > >> Hello: >> >> I want to create pseudo ethernet devices to simulate many NICs on >> a PC. In Solaris, we can do "ifconfig hme0:1 10.1.1.1 up" >> hme0:2 etc to create logival interfaces. I am trying to do a similar thing >> on FreeBSD. But after searching the archives, I find that I have to use >> tap device. Is there any other way than the approach I am using below. > Doing that on Solaris gives you additional MAC addresses? No, but I can configure my own MAC address as in freebsd by changing the mac address using ifconfig lladdr option. > I've used bridging with tap devices plenty. Works fine for me. What bridging method do you use with tap device ? option BRIDGE in kernel method OR netgraph bridging method? > TAP devices don't actually work unless there's a process that has the /dev/ entry > opened and reads from it (well, they'll buffer a little). So, just let a process like "cat /dev/tap0" read the tap device, I assume. Thanks Naga To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 5 20: 1: 1 2002 Delivered-To: freebsd-net@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id 61EE737B404 for ; Sat, 5 Jan 2002 20:00:58 -0800 (PST) Received: from user-uiveql9.dsl.mindspring.com ([165.247.106.169] helo=mindspring.com) by granger.mail.mindspring.net with esmtp (Exim 3.33 #1) id 16N4UT-00028F-00; Sat, 05 Jan 2002 23:00:57 -0500 Message-ID: <3C3722D0.7DF8B00C@mindspring.com> Date: Sat, 05 Jan 2002 10:59:12 -0500 From: Naga R Narayanaswamy X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: cjclark@alum.mit.edu Cc: freebsd-net@FreeBSD.ORG Subject: Re: Bridging and 'pseudo-device tap' and PPPoE References: <006f01c19453$aad27440$6a092042@compaq> <20020105125831.C204@gohan.cjclark.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Crist J. Clark" wrote: > > On Thu, Jan 03, 2002 at 07:39:20AM -0500, Naga R Narayanaswamy wrote: > > Hello: > > > > I want to create pseudo ethernet devices to simulate many NICs on > > a PC. In Solaris, we can do "ifconfig hme0:1 10.1.1.1 up" > > hme0:2 etc to create logival interfaces. I am trying to do a similar thing > > on FreeBSD. > > # ifconfig fxp0 inet 10.1.1.1 alias This will only add another IP address to the same fxp0 interface. I want different interfaces like fxp0:1, fxp0:2 (like tap0, tap1 ...) with their own MAC addresses and IP addresses (but no physical card to represent them) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 5 20:20:25 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id EA37C37B449 for ; Sat, 5 Jan 2002 20:20:16 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020106042011.UAUN20395.rwcrmhc52.attbi.com@InterJet.elischer.org>; Sun, 6 Jan 2002 04:20:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id UAA35808; Sat, 5 Jan 2002 20:19:13 -0800 (PST) Date: Sat, 5 Jan 2002 20:19:11 -0800 (PST) From: Julian Elischer To: Naga R Narayanaswamy Cc: cjclark@alum.mit.edu, freebsd-net@FreeBSD.ORG Subject: Re: Bridging and 'pseudo-device tap' and PPPoE In-Reply-To: <3C3722D0.7DF8B00C@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org you should be able to use N ng_eiface interfaces and then connect them together with teh bridging code somehow, so that all teh packets come and go on a single physical interface. the ng_eiface node is not in -stable but it's a pretty simple edit to make it work there, as it was originally written there. (I have not actually looked at trying this but just get the feeling that it should work.) julian On Sat, 5 Jan 2002, Naga R Narayanaswamy wrote: > "Crist J. Clark" wrote: > > > > On Thu, Jan 03, 2002 at 07:39:20AM -0500, Naga R Narayanaswamy wrote: > > > Hello: > > > > > > I want to create pseudo ethernet devices to simulate many NICs on > > > a PC. In Solaris, we can do "ifconfig hme0:1 10.1.1.1 up" > > > hme0:2 etc to create logival interfaces. I am trying to do a similar thing > > > on FreeBSD. > > > > # ifconfig fxp0 inet 10.1.1.1 alias > > This will only add another IP address to the same fxp0 interface. > I want different interfaces like fxp0:1, fxp0:2 (like tap0, tap1 ...) > with their own MAC addresses and IP addresses (but no physical card > to represent them) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message