From owner-freebsd-net Sun Aug 20 0:25:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 1A0F237B43C; Sun, 20 Aug 2000 00:25:22 -0700 (PDT) Received: from 149.211.6.64.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Sun, 20 Aug 2000 00:24:15 -0700 Received: (from cjc@localhost) by 149.211.6.64.reflexcom.com (8.9.3/8.9.3) id AAA15013; Sun, 20 Aug 2000 00:25:16 -0700 (PDT) (envelope-from cjc) Date: Sun, 20 Aug 2000 00:25:16 -0700 From: "Crist J . Clark" To: "Jason L. Schwab" Cc: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, "Roger T. Harvey" , "Rick M. Aseltine" , "Jonathan M. Slivko" , Steve Krujelskis Subject: Re: Networking Error Question Message-ID: <20000820002516.V28027@149.211.6.64.reflexcom.com> Reply-To: cjclark@alum.mit.edu References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jlschwab@simphost.com on Sat, Aug 19, 2000 at 05:37:57PM -0600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Aug 19, 2000 at 05:37:57PM -0600, Jason L. Schwab wrote: > Heya People, > > I have three machines, up on a colocated network, > One machine handles almost everything, it has > > 216.84.199.164 thro 216.84.199.154, and > 216.253.163.2 thro 216.253.163.254 binded to it > using (ifconfig device inet IP netmask NETMASK alias) > > I get this error alot in my messages: > > Aug 19 17:33:20 alpha /kernel: arplookup 216.253.163.1 failed: host is not > on local network > Aug 19 17:33:20 alpha last message repeated 4 times > > > Any ideas or suggestions would be greatful! One of the addresses on the 216.253.163.0/24 should not be an alias and have a 255.255.255.0. -- Crist J. Clark cjclark@alum.mit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Aug 20 12:28:35 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by hub.freebsd.org (Postfix) with ESMTP id C929737B440; Sun, 20 Aug 2000 12:28:30 -0700 (PDT) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.9.3/8.9.3) with ESMTP id MAA29732; Sun, 20 Aug 2000 12:28:25 -0700 (PDT) Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Sun, 20 Aug 2000 12:28:24 -0700 Received: from glitch ([17.219.158.69]) by scv2.apple.com (8.9.3/8.9.3) with SMTP id MAA03453; Sun, 20 Aug 2000 12:28:24 -0700 (PDT) Message-Id: <200008201928.MAA03453@scv2.apple.com> Date: Sun, 20 Aug 2000 00:51:30 -0700 From: "Justin C. Walker" Reply-To: justin@apple.com Content-Type: text/plain; charset=us-ascii Subject: Re: Networking Error Question Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org, "Roger T. Harvey" , "Rick M. Aseltine" , "Jonathan M. Slivko" , Steve Krujelskis To: "Jason L. Schwab" X-Mailer: Apple Mail (2.328.2) Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v328.2) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Saturday, August 19, 2000, at 04:37 PM, Jason L. Schwab wrote: > Heya People,=20 > =20 > I have three machines, up on a colocated network,=20 > One machine handles almost everything, it has=20 > =20 > 216.84.199.164 thro 216.84.199.154, and=20 > 216.253.163.2 thro 216.253.163.254 binded to it=20 > using (ifconfig device inet IP netmask NETMASK alias)=20 > =20 > I get this error alot in my messages:=20 > =20 > Aug 19 17:33:20 alpha /kernel: arplookup 216.253.163.1 failed: host is = not=20 > on local network=20 > Aug 19 17:33:20 alpha last message repeated 4 times=20 > =20 > =20 > Any ideas or suggestions would be greatful!=20 Since you don't have enough info here to be sure, I can't help much; you = may already know this, but one thing to keep in mind: when assigning to = an interface an alias which is on the same subnet as an existing = address, you should use the netmask 255.255.255.255; and at least one of = the addresses from that subnet should be assigned with a "real" netmask. The fact that the use of only the .1 address gives complaints leads me = to believe that the latter could be your problem. Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking | Men are from Earth. Apple Computer, Inc. | Women are from Earth. 2 Infinite Loop | Deal with it. Cupertino, CA 95014 | *-------------------------------------*-----------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Aug 20 12:59:24 2000 Delivered-To: freebsd-net@freebsd.org Received: from amazhan.bitstream.net (amazhan.bitstream.net [216.243.128.132]) by hub.freebsd.org (Postfix) with SMTP id C844137B43C for ; Sun, 20 Aug 2000 12:59:21 -0700 (PDT) Received: (qmail 89821 invoked from network); 20 Aug 2000 19:59:20 -0000 Received: from unknown (HELO copper) (216.243.168.19) by amazhan with SMTP; 20 Aug 2000 19:59:20 -0000 Date: Sun, 20 Aug 2000 12:57:59 -0700 From: Dan Debertin X-Sender: airboss@copper.air-boss.net To: Todd Backman Cc: freebsd-net@freebsd.org Subject: Re: Routing firewall w/ipfw questions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 19 Aug 2000, Todd Backman wrote: > established connection) but no access from the outside could be > established even after adding as the last rulesets: > > allow ip from any to any If you are inserting this rule onto the end of your ruleset, you're still going through all of your other rules before getting to this one. Given that we're just trying to get the routing working, you're better off turning off firewalling completely with: sysctl -w net.inet.ip.fw.enable=0 Once we get routing working from inside out, and from outside in, we can throw ipfw back into the mix. If that doesn't work, perhaps an ASCII drawing of your network, with the relevant addresses (converted into made-up ones, of course), etc., would be helpful. ~Dan D. -- ++ Dan Debertin ++ Senior Systems Administrator ++ Bitstream Underground, LLC ++ airboss@bitstream.net ++ (612)321-9290 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Aug 20 14: 1:23 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.surrealideas.net (im1.scinternet.net [208.46.64.146]) by hub.freebsd.org (Postfix) with ESMTP id 0CB6937B42C for ; Sun, 20 Aug 2000 14:01:15 -0700 (PDT) Received: from phiber [24.165.247.146] by mail.surrealideas.net (SMTPD32-6.04) id A427F74A01A2; Sun, 20 Aug 2000 14:48:39 -0600 From: "Phiber" To: Subject: What NIC card to get? Date: Sun, 20 Aug 2000 17:07:26 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I recently put freeBSD on an old p166 with 16 megs of ram. I am on a cable modem, and have a home network with two win 98 machines that run through the LinkSys Router. I want to add my BSD box, but I don't know what NIC card to get. Will someone give me some suggestions? Thanks to all who read this To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Aug 20 14:12:28 2000 Delivered-To: freebsd-net@freebsd.org Received: from security1.noc.flyingcroc.net (security1.noc.flyingcroc.net [207.246.128.54]) by hub.freebsd.org (Postfix) with ESMTP id F26CB37B424 for ; Sun, 20 Aug 2000 14:12:25 -0700 (PDT) Received: from localhost (todd@localhost) by security1.noc.flyingcroc.net (8.9.3/8.9.3) with ESMTP id OAA31632; Sun, 20 Aug 2000 14:11:36 -0700 (PDT) (envelope-from todd@flyingcroc.net) X-Authentication-Warning: security1.noc.flyingcroc.net: todd owned process doing -bs Date: Sun, 20 Aug 2000 14:11:36 -0700 (PDT) From: Todd Backman X-Sender: todd@security1.noc.flyingcroc.net To: Phiber Cc: freebsd-net@FreeBSD.ORG Subject: Re: What NIC card to get? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We have been extremely happy with the Intel 10/100 pros. May be overkill for you but the work great... - Todd On Sun, 20 Aug 2000, Phiber wrote: > > Hi, I recently put freeBSD on an old p166 with 16 megs of ram. I am on a > cable modem, and have a home network with two win 98 machines that run > through the LinkSys Router. I want to add my BSD box, but I don't know what > NIC card to get. Will someone give me some suggestions? > > > Thanks to all who read this > > > > 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 Sun Aug 20 14:21:43 2000 Delivered-To: freebsd-net@freebsd.org Received: from wopr.chc-chimes.com (wopr.chc-chimes.com [216.234.105.162]) by hub.freebsd.org (Postfix) with ESMTP id D09F537B423 for ; Sun, 20 Aug 2000 14:21:40 -0700 (PDT) Received: from localhost (matta@localhost) by wopr.chc-chimes.com (8.9.3/8.9.3) with ESMTP id RAA44158; Sun, 20 Aug 2000 17:23:00 -0400 (EDT) (envelope-from matta@unixshell.com) Date: Sun, 20 Aug 2000 17:23:00 -0400 (EDT) From: Matt Ayres X-Sender: matta@wopr.chc-chimes.com To: Phiber Cc: freebsd-net@FreeBSD.ORG Subject: Re: What NIC card to get? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Your best bet is to get an Intel EtherExpress/Pro 100(B/+) (fxp) or 3Com 3c905B (xl). These are some high quality nic's and very supported. If you are on a budget you might want to look at a SMC Epic (tx). Thanks, Matt Ayres On Sun, 20 Aug 2000, Phiber wrote: > > Hi, I recently put freeBSD on an old p166 with 16 megs of ram. I am on a > cable modem, and have a home network with two win 98 machines that run > through the LinkSys Router. I want to add my BSD box, but I don't know what > NIC card to get. Will someone give me some suggestions? > > > Thanks to all who read this > > > > 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 Sun Aug 20 14:22:14 2000 Delivered-To: freebsd-net@freebsd.org Received: from security1.noc.flyingcroc.net (security1.noc.flyingcroc.net [207.246.128.54]) by hub.freebsd.org (Postfix) with ESMTP id 7236937B422 for ; Sun, 20 Aug 2000 14:22:12 -0700 (PDT) Received: from localhost (todd@localhost) by security1.noc.flyingcroc.net (8.9.3/8.9.3) with ESMTP id OAA31656; Sun, 20 Aug 2000 14:22:08 -0700 (PDT) (envelope-from todd@flyingcroc.net) X-Authentication-Warning: security1.noc.flyingcroc.net: todd owned process doing -bs Date: Sun, 20 Aug 2000 14:22:08 -0700 (PDT) From: Todd Backman X-Sender: todd@security1.noc.flyingcroc.net To: Dan Debertin Cc: freebsd-net@freebsd.org Subject: Re: Routing firewall w/ipfw questions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 20 Aug 2000, Dan Debertin wrote: > On Sat, 19 Aug 2000, Todd Backman wrote: > > > established connection) but no access from the outside could be > > established even after adding as the last rulesets: > > > > allow ip from any to any > > If you are inserting this rule onto the end of your ruleset, you're still > going through all of your other rules before getting to this one. Yes, that hit me when I was on my way into town on the bus today. Amazing what state of mental clarity I obtain while having 15 diff conversations going on around me... ;^) (and without having 10 people calling me asking when the net is going to be back up after an outage notice had been posted) > Given that we're just trying to get the routing working, you're better > off turning off firewalling completely with: > > sysctl -w net.inet.ip.fw.enable=0 > > Once we get routing working from inside out, and from outside in, we can > throw ipfw back into the mix. Cool. Will do. Thanks for the guidance. And I must say that sysctl rocks! > > If that doesn't work, perhaps an ASCII drawing of your network, with the > relevant addresses (converted into made-up ones, of course), etc., would > be helpful. > > > ~Dan D. > -- > > ++ Dan Debertin > ++ Senior Systems Administrator > ++ Bitstream Underground, LLC > ++ airboss@bitstream.net > ++ (612)321-9290 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Aug 20 22:18: 8 2000 Delivered-To: freebsd-net@freebsd.org Received: from sofia.csl.sri.com (sofia.csl.sri.com [130.107.19.127]) by hub.freebsd.org (Postfix) with ESMTP id CE1FC37B43C for ; Sun, 20 Aug 2000 22:18:05 -0700 (PDT) Received: (from molter@localhost) by sofia.csl.sri.com (8.9.3/8.9.3) id WAA30295 for freebsd-net@freebsd.org; Sun, 20 Aug 2000 22:18:22 -0700 (PDT) (envelope-from molter) From: Marco Molteni Date: Sun, 20 Aug 2000 22:18:22 -0700 To: freebsd-net@freebsd.org Subject: question on sys/net/ip_fw.h Message-ID: <20000820221822.A30286@sofia.csl.sri.com> Mail-Followup-To: freebsd-net@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a question on file sys/netinet/ip_fw.h (revision 1.51), regarding the comment to struct ip_fw: /* * Format of an IP firewall descriptor * * fw_src, fw_dst, fw_smsk, fw_dmsk are always stored in network byte order. * fw_flg and fw_n*p are stored in host byte order (of course). * Port numbers are stored in HOST byte order. * Warning: setsockopt() will fail if sizeof(struct ip_fw) > MLEN (108) */ The last line says that MLEN is 108 bytes. According to sys/sys/mbuf.h: #define MLEN (MSIZE - sizeof(struct m_hdr)) /* normal data len */ And, according to sys/i386/include/param.h: #ifndef MSIZE #define MSIZE 256 /* size of an mbuf */ #endif /* MSIZE */ So, I think that the first comment is obsolete and refers to when MSIZE was 128, and should be updated to something like: --- ip_fw.h.old Sun Aug 20 18:20:13 2000 +++ ip_fw.h Sun Aug 20 18:20:40 2000 @@ -47,7 +47,8 @@ * fw_src, fw_dst, fw_smsk, fw_dmsk are always stored in network byte order. * fw_flg and fw_n*p are stored in host byte order (of course). * Port numbers are stored in HOST byte order. - * Warning: setsockopt() will fail if sizeof(struct ip_fw) > MLEN (108) + * Warning: setsockopt() will fail if sizeof(struct ip_fw) > MLEN + * (see sys/mbuf.h). */ Am I right? Is someone willing to commit the change? Thanks Marco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Aug 20 23:34:14 2000 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 09D8F37B424 for ; Sun, 20 Aug 2000 23:34:09 -0700 (PDT) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id IAA19062; Mon, 21 Aug 2000 08:35:47 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200008210635.IAA19062@info.iet.unipi.it> Subject: Re: question on sys/net/ip_fw.h In-Reply-To: <20000820221822.A30286@sofia.csl.sri.com> from Marco Molteni at "Aug 20, 2000 10:18:22 pm" To: Marco Molteni Date: Mon, 21 Aug 2000 08:35:47 +0200 (CEST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, yes the comments are obsolete, but because in 3.x and above setsockopt() can handle parms of arbitrary size and is not limited anymore to MLEN. So the entire comment should be removed. cheers luigi > * fw_src, fw_dst, fw_smsk, fw_dmsk are always stored in network byte order. > * fw_flg and fw_n*p are stored in host byte order (of course). > * Port numbers are stored in HOST byte order. > - * Warning: setsockopt() will fail if sizeof(struct ip_fw) > MLEN (108) > + * Warning: setsockopt() will fail if sizeof(struct ip_fw) > MLEN > + * (see sys/mbuf.h). > */ > > > Am I right? Is someone willing to commit the change? > > Thanks > Marco > > > 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 Mon Aug 21 3:11:33 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.surrealideas.net (im1.scinternet.net [208.46.64.146]) by hub.freebsd.org (Postfix) with ESMTP id 1A66437B43F for ; Mon, 21 Aug 2000 03:11:26 -0700 (PDT) Received: from phiber [24.165.247.146] by mail.surrealideas.net (SMTPD32-6.04) id AD5A7D3301BA; Mon, 21 Aug 2000 03:58:50 -0600 From: "Phiber" To: Subject: RE: What NIC card to get? Date: Mon, 21 Aug 2000 06:17:38 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ok, well, I came across an SMC 10/100 EZNET PCI NIC card. It says it works with linux and is SCO compatible. I plugged it in and no go. Can someone please explain to me how I would set this thing up to get me on the net with Free BSD 4? Thanks to anyone reading this -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Matt Ayres Sent: Sunday, August 20, 2000 2:23 PM To: Phiber Cc: freebsd-net@FreeBSD.ORG Subject: Re: What NIC card to get? Your best bet is to get an Intel EtherExpress/Pro 100(B/+) (fxp) or 3Com 3c905B (xl). These are some high quality nic's and very supported. If you are on a budget you might want to look at a SMC Epic (tx). Thanks, Matt Ayres On Sun, 20 Aug 2000, Phiber wrote: > > Hi, I recently put freeBSD on an old p166 with 16 megs of ram. I am on a > cable modem, and have a home network with two win 98 machines that run > through the LinkSys Router. I want to add my BSD box, but I don't know what > NIC card to get. Will someone give me some suggestions? > > > Thanks to all who read this > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 21 5:36: 8 2000 Delivered-To: freebsd-net@freebsd.org Received: from apollo.ocsny.com (apollo.ocsny.com [204.107.76.2]) by hub.freebsd.org (Postfix) with ESMTP id 3C2CC37B42C for ; Mon, 21 Aug 2000 05:36:01 -0700 (PDT) Received: from ocsny.com (thoth.upan.org [204.107.76.16]) by apollo.ocsny.com (8.9.2/8.9.3) with ESMTP id IAA48189; Mon, 21 Aug 2000 08:24:22 -0400 (EDT) Message-ID: <39A1221D.2DCE2239@ocsny.com> Date: Mon, 21 Aug 2000 08:35:41 -0400 From: Mikel Organization: Optimized Computer Solutions, Inc. X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en,it MIME-Version: 1.0 To: Phiber Cc: freebsd-net@FreeBSD.ORG Subject: Re: What NIC card to get? References: Content-Type: multipart/mixed; boundary="------------AE1C1D782E0A8939F91A159A" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------AE1C1D782E0A8939F91A159A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit the smc tx1211 (rl) works well but I don't thiunk many of the others do. you can get them through channel for something like $20... Phiber wrote: > ok, well, I came across an SMC 10/100 EZNET PCI NIC card. It says it works > with linux and is SCO compatible. I plugged it in and no go. Can someone > please explain to me how I would set this thing up to get me on the net with > Free BSD 4? > > Thanks to anyone reading this > > -----Original Message----- > From: owner-freebsd-net@FreeBSD.ORG > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Matt Ayres > Sent: Sunday, August 20, 2000 2:23 PM > To: Phiber > Cc: freebsd-net@FreeBSD.ORG > Subject: Re: What NIC card to get? > > Your best bet is to get an Intel EtherExpress/Pro 100(B/+) (fxp) or 3Com > 3c905B (xl). These are some high quality nic's and very supported. If you > are on a budget you might want to look at a SMC Epic (tx). > > Thanks, > Matt Ayres > > On Sun, 20 Aug 2000, Phiber wrote: > > > > > Hi, I recently put freeBSD on an old p166 with 16 megs of ram. I am on a > > cable modem, and have a home network with two win 98 machines that run > > through the LinkSys Router. I want to add my BSD box, but I don't know > what > > NIC card to get. Will someone give me some suggestions? > > > > > > Thanks to all who read this > > > > > > > > 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- Cheers, Mikel +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ | Optimized Computer Solutions, Inc http://www.ocsny.com | 39 W14th Street, Suite 203 212 727 2238 x132 | New York, NY 10011 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ --------------AE1C1D782E0A8939F91A159A Content-Type: text/x-vcard; charset=us-ascii; name="mikel.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Mikel Content-Disposition: attachment; filename="mikel.vcf" begin:vcard n:King;Mikel tel;fax:2124638402 tel;home:http://www.upan.org tel;work:2127272100 x-mozilla-html:TRUE org:Optimized Computer Solutions version:2.1 email;internet:mikel@ocsny.com title:Director of Network Operations & Technology adr;quoted-printable:;;39 W14th St.=0D=0ASte 203;New York;NY;10011;US note;quoted-printable:fBSD, PHP, MySql and OCS Rule!!!=0D=0A=0D=0AGoal is to be MS free by the end of 2k. x-mozilla-cpt:;7312 fn:Mikel King end:vcard --------------AE1C1D782E0A8939F91A159A-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 21 12:36:32 2000 Delivered-To: freebsd-net@freebsd.org Received: from wireco.net (mental.wireco.net [206.107.119.3]) by hub.freebsd.org (Postfix) with SMTP id AFB0A37B43C for ; Mon, 21 Aug 2000 12:36:26 -0700 (PDT) Received: (qmail 30416 invoked from network); 21 Aug 2000 19:36:24 -0000 Received: from d23.johnson-city.tn.us.wireco.net (HELO challenger) (206.107.119.212) by mental.wireco.net with SMTP; 21 Aug 2000 19:36:24 -0000 Reply-To: From: "Andrew C. Hornback" To: "'Phiber'" Cc: Subject: RE: What NIC card to get? Date: Mon, 21 Aug 2000 15:35:29 -0400 Message-ID: <007b01c00ba6$f6fc4b20$d4776bce@challenger> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My standard recommendation for nearly any kind of networking gear... SMC. For PCI Cards, the 9432TX (EtherPower II) is a heck of a value. For ISA, I prefer the 8216C. --- Andy > -----Original Message----- > From: owner-freebsd-net@FreeBSD.ORG > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Phiber > Sent: Sunday, August 20, 2000 8:07 PM > To: freebsd-net@freebsd.org > Subject: What NIC card to get? > > Hi, I recently put freeBSD on an old p166 with 16 megs of > ram. I am on a > cable modem, and have a home network with two win 98 machines that run > through the LinkSys Router. I want to add my BSD box, but I > don't know what > NIC card to get. Will someone give me some suggestions? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 21 17:33:38 2000 Delivered-To: freebsd-net@freebsd.org Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (Postfix) with ESMTP id 6EFC537B423 for ; Mon, 21 Aug 2000 17:33:36 -0700 (PDT) Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by gatekeeper.whistle.com (8.9.3/8.9.3) with ESMTP id RAA17118; Mon, 21 Aug 2000 17:33:35 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id RAA63962; Mon, 21 Aug 2000 17:33:35 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008220033.RAA63962@bubba.whistle.com> Subject: Re: question on sys/net/ip_fw.h In-Reply-To: <200008210635.IAA19062@info.iet.unipi.it> from Luigi Rizzo at "Aug 21, 2000 08:35:47 am" To: Luigi Rizzo Date: Mon, 21 Aug 2000 17:33:35 -0700 (PDT) Cc: Marco Molteni , freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luigi Rizzo writes: > yes the comments are obsolete, but because in > 3.x and above setsockopt() can handle parms of arbitrary size > and is not limited anymore to MLEN. So the entire comment should > be removed. Removed :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 22 8:23:59 2000 Delivered-To: freebsd-net@freebsd.org Received: from cat.acs.sk (cat.acs.sk [195.168.240.4]) by hub.freebsd.org (Postfix) with ESMTP id DDB4537B423 for ; Tue, 22 Aug 2000 08:23:56 -0700 (PDT) Received: from thpc (frodo.traco.sk [195.168.45.193]) by cat.acs.sk (8.9.3/8.9.3) with SMTP id RAA39432 for ; Tue, 22 Aug 2000 17:24:05 +0200 (CEST) (envelope-from tomas@hodan.sk) From: "Tomas Hodan" To: Subject: bridging and freebsd crash Date: Tue, 22 Aug 2000 17:22:25 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" 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) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi all, i have a problem with 4-stable. i'm using bridging with 3 ethernet adapters and when i set net.link.ether.bridge_ipfw to 1 after few second freebsd crash with panic. has this see anybody already ? thanks, tomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 22 8:26:14 2000 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id EA53637B424 for ; Tue, 22 Aug 2000 08:26:11 -0700 (PDT) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id RAA24348; Tue, 22 Aug 2000 17:27:39 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200008221527.RAA24348@info.iet.unipi.it> Subject: Re: bridging and freebsd crash In-Reply-To: from Tomas Hodan at "Aug 22, 2000 05:22:25 pm" To: Tomas Hodan Date: Tue, 22 Aug 2000 17:27:39 +0200 (CEST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > hi all, > i have a problem with 4-stable. i'm using bridging with 3 ethernet adapters > and when i set net.link.ether.bridge_ipfw to 1 after few second freebsd > crash with panic. has this see anybody already ? Darren :) cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 22 12:18:49 2000 Delivered-To: freebsd-net@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 3740637B423 for ; Tue, 22 Aug 2000 12:18:46 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id PAA08179; Tue, 22 Aug 2000 15:18:15 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 22 Aug 2000 15:18:15 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Luigi Rizzo Cc: Tomas Hodan , freebsd-net@FreeBSD.ORG Subject: Re: bridging and freebsd crash In-Reply-To: <200008221527.RAA24348@info.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 22 Aug 2000, Luigi Rizzo wrote: > > hi all, > > i have a problem with 4-stable. i'm using bridging with 3 ethernet adapters > > and when i set net.link.ether.bridge_ipfw to 1 after few second freebsd > > crash with panic. has this see anybody already ? > > Darren :) Well, Darren has seen it specifically in the context of bad (abuseive) packets, but I'd be interested in knowing whether there is another general bug in the bridging code, or whether it's a case of malformed packets confusing the ipfw code. Tomas, any chance of compiling the kernel with debugging symbols, dropping in options DDB, and giving us a stack trace at the kernel panic? I'm beginning to feel that we might want to revamp the current bridging framework, combining the best aspects of the current work with the some of the structural framework from the OpenBSD implementation. I haven't had time, recently having returned from a vacation, to look at this option seriously, however. Luigi, don't know if you have time or not, but I was wondering if you'd had a chance to look at the OpenBSD implementation, and if so, what your thoughts were with respects to it? It looks like they've used the ARP/route tables to maintain host location information, rather than a seperate bridge address cache, and that may have different performance and scalability properties, although combining the tables does substantially reduce the use of new data structures. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 22 13:39:19 2000 Delivered-To: freebsd-net@freebsd.org Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (Postfix) with ESMTP id 2D98337B423; Tue, 22 Aug 2000 13:39:17 -0700 (PDT) Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by gatekeeper.whistle.com (8.9.3/8.9.3) with ESMTP id NAA26658; Tue, 22 Aug 2000 13:39:16 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id NAA68458; Tue, 22 Aug 2000 13:39:16 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008222039.NAA68458@bubba.whistle.com> Subject: Re: bridging and freebsd crash In-Reply-To: from Robert Watson at "Aug 22, 2000 03:18:15 pm" To: Robert Watson Date: Tue, 22 Aug 2000 13:39:16 -0700 (PDT) Cc: Luigi Rizzo , Tomas Hodan , freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Robert Watson writes: > I'm beginning to feel that we might want to revamp the current bridging > framework, combining the best aspects of the current work with the some of > the structural framework from the OpenBSD implementation. I haven't had I'll restate my suggestion: rewrite the bridging code as a netgraph node. The Ethernet stuff has already been modified to make it plug & play ready, using the ng_ether(4) "upper" and "lower" hooks. Makes things nice & self-contained that way. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 22 22: 1:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 565C437B422 for ; Tue, 22 Aug 2000 22:01:22 -0700 (PDT) Received: from softweyr.com (Foolstrustident!@dyn3.softweyr.com [204.68.178.227]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA18686; Tue, 22 Aug 2000 23:01:11 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <39A35C2E.7B71E722@softweyr.com> Date: Tue, 22 Aug 2000 23:07:58 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: hornback@wireco.net Cc: "'Phiber'" , freebsd-net@FreeBSD.ORG Subject: Re: What NIC card to get? References: <007b01c00ba6$f6fc4b20$d4776bce@challenger> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Andrew C. Hornback" wrote: > > My standard recommendation for nearly any kind of networking gear... > > SMC. For PCI Cards, the 9432TX (EtherPower II) is a heck of a value. For > ISA, I prefer the 8216C. > > --- Andy > > > -----Original Message----- > > From: owner-freebsd-net@FreeBSD.ORG > > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Phiber > > Sent: Sunday, August 20, 2000 8:07 PM > > To: freebsd-net@freebsd.org > > Subject: What NIC card to get? > > > > Hi, I recently put freeBSD on an old p166 with 16 megs of > > ram. I am on a > > cable modem, and have a home network with two win 98 machines that run > > through the LinkSys Router. I want to add my BSD box, but I > > don't know what > > NIC card to get. Will someone give me some suggestions? LinkSys? If you're in the USA, what you really want is a $20-$25 PCI card. Look for one supported by the dc driver, as documented in the dc(4) man page. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 23 0:34:46 2000 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 2325537B422; Wed, 23 Aug 2000 00:34:40 -0700 (PDT) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id JAA27319; Wed, 23 Aug 2000 09:36:12 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200008230736.JAA27319@info.iet.unipi.it> Subject: Re: bridging and freebsd crash In-Reply-To: <200008222039.NAA68458@bubba.whistle.com> from Archie Cobbs at "Aug 22, 2000 01:39:16 pm" To: Archie Cobbs Date: Wed, 23 Aug 2000 09:36:12 +0200 (CEST) Cc: Robert Watson , Tomas Hodan , freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Robert Watson writes: > > I'm beginning to feel that we might want to revamp the current bridging > > framework, combining the best aspects of the current work with the some of > > the structural framework from the OpenBSD implementation. I haven't had > > I'll restate my suggestion: rewrite the bridging code as a netgraph node. Ok, sorry but at this point i think i need to say this on the list. People, do not take this as a personal attack as it is not. Archie- it's much simpler than that. Bridging+ipfw in 3.x did not have the problems that people is mentioning -- at least i have had quite a few of them in use for a long time now and no reports for weird crashes (i am specifically referring to the picobsd images available from my web site which is almost exactly the code in the RELENG_3 tree). The problems in 4.x/5.x are likely due to improper mbuf handling (specifically, these mbufs are shared between device drivers and in some cases upper layers in the protocol stack, which is fine but requires a bit of care in doing things, and timing is very much hardware dependent), and some code that was deleted, all of this is related to your ether_input() changes. As it told you at that time, I agreed on the change in principle (as we gain a lot in terms of reduced code bloat and more supported cards); however, doing the commit without testing that bridging was still working with all features after the change was really a bad idea -- and i also told you this. I don't want to look as the one who complains "i knew it" as i did not have the time (nor i do now, at least in the near future) to do the required testing and fix things, but, alas, i did not commit such code! Redoing things differently is not going to help if the problem is lack of time and testing. cheers luigi > The Ethernet stuff has already been modified to make it plug & play > ready, using the ng_ether(4) "upper" and "lower" hooks. Makes things > nice & self-contained that way. > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 23 8:27:31 2000 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 141F637B422; Wed, 23 Aug 2000 08:27:05 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.9.3/1.13) id SAA65964; Wed, 23 Aug 2000 18:26:53 +0300 (EEST) Date: Wed, 23 Aug 2000 18:26:52 +0300 From: Ruslan Ermilov To: net@FreeBSD.org Cc: Charles Mott , Erik Salander , Brian Somers , Eivind Eklund Subject: libalias(3) ICMP bugs Message-ID: <20000823182652.A65441@sunbay.com> Mail-Followup-To: net@FreeBSD.org, Charles Mott , Erik Salander , Brian Somers , Eivind Eklund Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="3MwIy2ne0vdjdPXF" X-Mailer: Mutt 1.0i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Hi! The following patch addresses some issues with aliasing/dealiasing ICMP packets. Unfortunately, I have no enough time now to describe all the possible symptoms, but if you have some spare weekend time, I would really appreciate it if you could test the following: 1) Suppose you have ed0 interface on your NAT box. 2) Bind two public IP addresses to it, say x.x.x.1 and x.x.x.2. 3) Run `natd -a x.x.x.1 -v'. 4) Run `tcpdump -n ed0 icmp'. 5) From another host x.x.x.3 on the same (ed0) network issue a `ping -n -c1 x.x.x.2' then `traceroute -q1 -n x.x.x.2' 6) Remove x.x.x.2 as an alias address from ed0 interface, on the host x.x.x.3 add the static route to x.x.x.2 via x.x.x.1. Then run `traceroute -q1 -n -m1 x.x.x.2'. Watch the tcpdump(8) and natd(8) output on the host x.x.x.1 and ping(8) and traceroute(8) output on host x.x.x.3, then compare them with and without this patch. Your comments are highly appreciated! Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: alias.c =================================================================== RCS file: /home/ncvs/src/lib/libalias/alias.c,v retrieving revision 1.21 diff -u -p -r1.21 alias.c --- alias.c 2000/07/26 23:15:46 1.21 +++ alias.c 2000/08/23 15:11:27 @@ -180,8 +180,8 @@ TcpMonitorOut(struct ip *pip, struct ali /* Protocol Specific Packet Aliasing Routines - IcmpAliasIn(), IcmpAliasIn1(), IcmpAliasIn2(), IcmpAliasIn3() - IcmpAliasOut(), IcmpAliasOut1(), IcmpAliasOut2(), IcmpAliasOut3() + IcmpAliasIn(), IcmpAliasIn1(), IcmpAliasIn2() + IcmpAliasOut(), IcmpAliasOut1(), IcmpAliasOut2() ProtoAliasIn(), ProtoAliasOut() UdpAliasIn(), UdpAliasOut() TcpAliasIn(), TcpAliasOut() @@ -222,12 +222,10 @@ the gateway machine or other machines on /* Local prototypes */ static int IcmpAliasIn1(struct ip *); static int IcmpAliasIn2(struct ip *); -static int IcmpAliasIn3(struct ip *); static int IcmpAliasIn (struct ip *); static int IcmpAliasOut1(struct ip *); static int IcmpAliasOut2(struct ip *); -static int IcmpAliasOut3(struct ip *); static int IcmpAliasOut (struct ip *); static int ProtoAliasIn(struct ip *); @@ -396,21 +394,6 @@ fragment contained in ICMP data section return(PKT_ALIAS_IGNORED); } -static int -IcmpAliasIn3(struct ip *pip) -{ - struct in_addr original_address; - - original_address = FindOriginalAddress(pip->ip_dst); - DifferentialChecksum(&pip->ip_sum, - (u_short *) &original_address, - (u_short *) &pip->ip_dst, - 2); - pip->ip_dst = original_address; - - return PKT_ALIAS_OK; -} - static int IcmpAliasIn(struct ip *pip) @@ -442,7 +425,7 @@ IcmpAliasIn(struct ip *pip) break; case ICMP_ECHO: case ICMP_TSTAMP: - iresult = IcmpAliasIn3(pip); + iresult = IcmpAliasIn1(pip); break; } return(iresult); @@ -537,7 +520,7 @@ IcmpAliasOut2(struct ip *pip) { u_short *sptr; int accumulate; - struct in_addr alias_address; + struct in_addr alias_address, icmp_alias_address; u_short alias_port; alias_address = GetAliasAddress(link); @@ -555,11 +538,15 @@ IcmpAliasOut2(struct ip *pip) ADJUST_CHECKSUM(accumulate, ic->icmp_cksum) /* Alias address in IP header */ + if (pip->ip_src.s_addr == ip->ip_dst.s_addr) + icmp_alias_address = alias_address; + else + icmp_alias_address = FindAliasAddress(pip->ip_src); DifferentialChecksum(&pip->ip_sum, - (u_short *) &alias_address, + (u_short *) &icmp_alias_address, (u_short *) &pip->ip_src, 2); - pip->ip_src = alias_address; + pip->ip_src = icmp_alias_address; /* Alias address and port number of original IP packet fragment contained in ICMP data section */ @@ -570,7 +557,7 @@ fragment contained in ICMP data section { u_short *sptr; int accumulate; - struct in_addr alias_address; + struct in_addr alias_address, icmp_alias_address; u_short alias_id; alias_address = GetAliasAddress(link); @@ -588,11 +575,15 @@ fragment contained in ICMP data section ADJUST_CHECKSUM(accumulate, ic->icmp_cksum) /* Alias address in IP header */ + if (pip->ip_src.s_addr == ip->ip_dst.s_addr) + icmp_alias_address = alias_address; + else + icmp_alias_address = FindAliasAddress(pip->ip_src); DifferentialChecksum(&pip->ip_sum, - (u_short *) &alias_address, + (u_short *) &icmp_alias_address, (u_short *) &pip->ip_src, 2); - pip->ip_src = alias_address; + pip->ip_src = icmp_alias_address; /* Alias address of original IP packet and sequence number of embedded ICMP datagram */ @@ -606,27 +597,6 @@ fragment contained in ICMP data section static int -IcmpAliasOut3(struct ip *pip) -{ -/* - Handle outgoing echo and timestamp replies. The - only thing which is done in this case is to alias - the source IP address of the packet. -*/ - struct in_addr alias_addr; - - alias_addr = FindAliasAddress(pip->ip_src); - DifferentialChecksum(&pip->ip_sum, - (u_short *) &alias_addr, - (u_short *) &pip->ip_src, - 2); - pip->ip_src = alias_addr; - - return PKT_ALIAS_OK; -} - - -static int IcmpAliasOut(struct ip *pip) { int iresult; @@ -656,7 +626,7 @@ IcmpAliasOut(struct ip *pip) break; case ICMP_ECHOREPLY: case ICMP_TSTAMPREPLY: - iresult = IcmpAliasOut3(pip); + iresult = IcmpAliasOut1(pip); } return(iresult); } Index: alias_db.c =================================================================== RCS file: /home/ncvs/src/lib/libalias/alias_db.c,v retrieving revision 1.37 diff -u -p -r1.37 alias_db.c --- alias_db.c 2000/08/14 15:24:47 1.37 +++ alias_db.c 2000/08/23 15:11:28 @@ -1401,9 +1401,22 @@ FindIcmpIn(struct in_addr dst_addr, struct in_addr alias_addr, u_short id_alias) { - return FindLinkIn(dst_addr, alias_addr, + struct alias_link *link; + + link = FindLinkIn(dst_addr, alias_addr, NO_DEST_PORT, id_alias, LINK_ICMP, 0); + if (link == NULL && !(packetAliasMode & PKT_ALIAS_DENY_INCOMING)) + { + struct in_addr target_addr; + + target_addr = FindOriginalAddress(alias_addr); + link = AddLink(target_addr, dst_addr, alias_addr, + id_alias, NO_DEST_PORT, id_alias, + LINK_ICMP); + } + + return (link); } --3MwIy2ne0vdjdPXF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 23 11:20:47 2000 Delivered-To: freebsd-net@freebsd.org Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (Postfix) with ESMTP id 02D6137B43C for ; Wed, 23 Aug 2000 11:20:40 -0700 (PDT) Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by gatekeeper.whistle.com (8.9.3/8.9.3) with ESMTP id LAA07683 for ; Wed, 23 Aug 2000 11:20:39 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id LAA79588 for freebsd-net@freebsd.org; Wed, 23 Aug 2000 11:20:39 -0700 (PDT) (envelope-from archie) Received: from whistle.com (whistle.com [207.76.205.131]) by bubba.whistle.com (8.9.3/8.9.3) with ESMTP id KAA79416 for ; Wed, 23 Aug 2000 10:27:24 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e7NHROL17115 for ; Wed, 23 Aug 2000 10:27:24 -0700 (PDT) Received: from gatekeeper.whistle.com( 207.76.204.2) by whistle.com via smap (V2.0) id xma017113; Wed, 23 Aug 2000 10:27:04 -0700 Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by gatekeeper.whistle.com (8.9.3/8.9.3) with ESMTP id KAA06966; Wed, 23 Aug 2000 10:26:25 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id KAA79356; Wed, 23 Aug 2000 10:26:24 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008231726.KAA79356@bubba.whistle.com> Subject: Re: bridging and freebsd crash In-Reply-To: <200008230736.JAA27319@info.iet.unipi.it> from Luigi Rizzo at "Aug 23, 2000 09:36:12 am" To: Luigi Rizzo Date: Wed, 23 Aug 2000 10:26:24 -0700 (PDT) Cc: Archie Cobbs , Robert Watson , Tomas Hodan , freebsd-net@FreeBSD.ORGG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luigi Rizzo writes: > > I'll restate my suggestion: rewrite the bridging code as a netgraph node. > > Ok, sorry but at this point i think i need to say this on the list. > People, do not take this as a personal attack as it is not. > > Archie- it's much simpler than that. Bridging+ipfw in 3.x did not > have the problems that people is mentioning -- at least i have had > quite a few of them in use for a long time now and no reports for > weird crashes (i am specifically referring to the picobsd images > available from my web site which is almost exactly the code in the > RELENG_3 tree). > > The problems in 4.x/5.x are likely due to improper mbuf handling > (specifically, these mbufs are shared between device drivers and > in some cases upper layers in the protocol stack, which is fine > but requires a bit of care in doing things, and timing is very much > hardware dependent), and some code that was deleted, all of this > is related to your ether_input() changes. > > As it told you at that time, I agreed on the change in principle > (as we gain a lot in terms of reduced code bloat and more supported > cards); however, doing the commit without testing that bridging > was still working with all features after the change was really > a bad idea -- and i also told you this. > > I don't want to look as the one who complains "i knew it" as i did > not have the time (nor i do now, at least in the near future) to > do the required testing and fix things, but, alas, i did not commit > such code! Luigi- No offense taken, and all of the above is a fair description. The bridging+ipfw code in 3.x did work -- but it was very messy. Each individual driver had to have an ugly hack. The ipfw code was doing filtering for non-IP packets, etc., etc. Recall that my changes removed 1,016 lines of redundant code! In my opinion that alone is a clear indication that more design and less hacking is sorely needed. In my opinion (you may disagree), these changes were worthwhile because they make the code more modular and maintainable, and removed redundant code, not to mention as a side effect adding bridging support for *all* Ethernet drivers in one fell swoop. My apologies for breaking things -- as stated on this list when proposing those changes, I have limited testing capability for bridging here. Nobody offered to help at the time. C'est la vie. In any case, let's look forward.. how can we best fix the remaining problems? In my opinion (again you may disagree), the right answer is: 1. Finish the cleanup of the bridging code by moving it into its own netgraph node. This will eliminate any code paths that result in unvalidated packets (which seems to be the current problem). 2. Have an /etc/rc.bridge or whatever that contains the relevant ngctl(8) commands to set up bridging over the desired interfaces. 3. Packets received on a bridge interface will have m->m_pkthdr.rcvif set appropriately, so ipfw filtering on a per-interface basis will still work. I'm not just saying this because I like netgraph, but rather because it has (by design) advantages that are applicable here. For example, the problem of an unvalidated packet reaching ipfw simply will not happen using netgraph. The reason this is happening now is because of the current, ill-conceived bridging+ipfw interaction. I'm willing to work with anyone interested in this project -- or some other variant, as long as it doesn't regress to the previous state of things. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 23 11:23:16 2000 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id E3C7637B423 for ; Wed, 23 Aug 2000 11:23:12 -0700 (PDT) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id UAA29351; Wed, 23 Aug 2000 20:24:51 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200008231824.UAA29351@info.iet.unipi.it> Subject: Re: bridging and freebsd crash To: freebsd-net@freebsd.org Date: Wed, 23 Aug 2000 20:24:51 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The bridging+ipfw code in 3.x did work -- but it was very messy. > Each individual driver had to have an ugly hack. The ipfw code > was doing filtering for non-IP packets, etc., etc. Recall that > my changes removed 1,016 lines of redundant code! In my opinion > that alone is a clear indication that more design and less hacking > is sorely needed. > > In my opinion (you may disagree), these changes were worthwhile I fully agree(d) on the changes to ethernet drivers - they were deeply needed. On ipfw (and bridge+ipfw interactions), opinions may differ, and i do not really think it is a technical matter. I am not a big fan of layering when it makes things more complex than they should be (and i am thinking of a firewall configuration -- i prefer to have all things in one place, rather than have to configure an etherfw, an ipfw and maybe an upper layer firewall. If you don't like the "ipfw" name change it!). And below, when you say that the interaction between bridging+ipfw was ill-conceived, can you explain where ? > In my opinion (again you may disagree), the right answer is: > > 1. Finish the cleanup of the bridging code by moving it into its > own netgraph node. This will eliminate any code paths that result > in unvalidated packets (which seems to be the current problem). but... if you cannot test things, who is going to do it ? I think the problem is not only with unvalidated packets reaching ipfw, it is also with mbufs shared between a device driver (which might pass it to a DMA engine) and the upper layers (where the code might do some NTOH*() on the same buffer, resulting in data corruption for the net -- this is the breakage for multicast packets i was referring to. I do not think moving to netgraph is going to help, you have to know that the problem is there and apply countermeasures. > happen using netgraph. The reason this is happening now is because > of the current, ill-conceived bridging+ipfw interaction. Actually passing bridged packets to ipfw with all proper tests took a handful of lines of code and did work. Yes, the commit i did also had some dead code trying to match ethernet packets -- that one had to be either removed or fixed, but that's it. I don't think the interaction was ill-conceived :) > I'm willing to work with anyone interested in this project -- or some which brings things back to square one... no volunteers aroung :( cheers luigi > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > ----- End of forwarded message from Luigi Rizzo ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 23 12:24:15 2000 Delivered-To: freebsd-net@freebsd.org Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (Postfix) with ESMTP id 324E737B43C for ; Wed, 23 Aug 2000 12:24:06 -0700 (PDT) Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by gatekeeper.whistle.com (8.9.3/8.9.3) with ESMTP id MAA08637 for ; Wed, 23 Aug 2000 12:24:06 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id MAA85629 for freebsd-net@FreeBSD.ORG; Wed, 23 Aug 2000 12:24:05 -0700 (PDT) (envelope-from archie) Received: from whistle.com (whistle.com [207.76.205.131]) by bubba.whistle.com (8.9.3/8.9.3) with ESMTP id MAA85476 for ; Wed, 23 Aug 2000 12:11:27 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e7NJBQh18368 for ; Wed, 23 Aug 2000 12:11:26 -0700 (PDT) Received: from gatekeeper.whistle.com( 207.76.204.2) by whistle.com via smap (V2.0) id xma018366; Wed, 23 Aug 2000 12:11:11 -0700 Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by gatekeeper.whistle.com (8.9.3/8.9.3) with ESMTP id MAA08446; Wed, 23 Aug 2000 12:10:38 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id MAA85466; Wed, 23 Aug 2000 12:10:38 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008231910.MAA85466@bubba.whistle.com> Subject: Re: bridging and freebsd crash In-Reply-To: <200008231823.UAA29344@info.iet.unipi.it> "from Luigi Rizzo at Aug 23, 2000 08:23:54 pm" To: Luigi Rizzo Date: Wed, 23 Aug 2000 12:10:38 -0700 (PDT) Cc: Archie Cobbs , Robert Watson , Tomas Hodan , freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luigi Rizzo writes: > And below, when you say that the interaction between bridging+ipfw > was ill-conceived, can you explain where ? I just mean that it needs to be made clear (a) whether ipfw is going to do IP-only filtering or otherwise, and (b) what is the correct path for packets to reach ipfw. IMHO packets should only go through ipfw via the function calls in ip_input() and ip_output(). > I think the problem is not only with unvalidated packets reaching > ipfw, it is also with mbufs shared between a device driver (which > might pass it to a DMA engine) and the upper layers (where the code > might do some NTOH*() on the same buffer, resulting in data > corruption for the net -- this is the breakage for multicast packets Isn't this a result of calling ipfw without going through the "normal" pathways? Or.. do we know the exact pathway that causes this to happen? Where is the m_copypacket() happening? (there must be one, right?) If so, this should be easy to fix (at the expense of speed) by using m_dup() instead of m_copypacket(). This could be a short term fix. > i was referring to. I do not think moving to > netgraph is going to help, you have to know that the problem is there > and apply countermeasures. At least, netgraph has strict rules about who "owns" an mbuf. > Actually passing bridged packets to ipfw with all proper tests > took a handful of lines of code and did work. Yes, the commit i did > also had some dead code trying to match ethernet packets -- that one > had to be either removed or fixed, but that's it. > I don't think the interaction was ill-conceived :) We can acomplish the same thing using the "normal" pathways and avoid the "handful of lines" == "hack" :-) > > I'm willing to work with anyone interested in this project -- or some > > which brings things back to square one... no volunteers aroung :( Well, first let's think about a real plan (i.e., design) for what we want to acomplish. Then we can set about asking for help. You've heard my plan. How would you suggest we address the current situation? And do even fully understand it? (I don't yet) Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 23 18: 3:16 2000 Delivered-To: freebsd-net@freebsd.org Received: from wireco.net (mental.wireco.net [206.107.119.3]) by hub.freebsd.org (Postfix) with SMTP id 8CD4837B424 for ; Wed, 23 Aug 2000 18:03:13 -0700 (PDT) Received: (qmail 22464 invoked from network); 24 Aug 2000 01:03:12 -0000 Received: from d23.johnson-city.tn.us.wireco.net (HELO challenger) (206.107.119.212) by mental.wireco.net with SMTP; 24 Aug 2000 01:03:12 -0000 Reply-To: From: "Andrew C. Hornback" To: "'Wes Peters'" Cc: Subject: RE: What NIC card to get? Date: Wed, 23 Aug 2000 21:02:18 -0400 Message-ID: <00e701c00d66$f3e6ac20$d4776bce@challenger> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 In-Reply-To: <39A35C2E.7B71E722@softweyr.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Point of reference: I'd never paid more than $20 for a NIC, and don't plan to when I can get the SMC 10/100 cards for generally half that. The 8216s are generally anywhere from $2-$8. --- Andy > -----Original Message----- > From: owner-freebsd-net@FreeBSD.ORG > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Wes Peters > Sent: Wednesday, August 23, 2000 1:08 AM > To: hornback@wireco.net > Cc: 'Phiber'; freebsd-net@FreeBSD.ORG > Subject: Re: What NIC card to get? > > "Andrew C. Hornback" wrote: > > > > My standard recommendation for nearly any kind of > networking gear... > > > > SMC. For PCI Cards, the 9432TX (EtherPower II) is > a heck of a value. For > > ISA, I prefer the 8216C. > > > > --- Andy > > > > > -----Original Message----- > > > From: owner-freebsd-net@FreeBSD.ORG > > > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Phiber > > > Sent: Sunday, August 20, 2000 8:07 PM > > > To: freebsd-net@freebsd.org > > > Subject: What NIC card to get? > > > > > > Hi, I recently put freeBSD on an old p166 with 16 megs of > > > ram. I am on a > > > cable modem, and have a home network with two win 98 > machines that run > > > through the LinkSys Router. I want to add my BSD box, but I > > > don't know what > > > NIC card to get. Will someone give me some suggestions? > > LinkSys? > > If you're in the USA, what you really want is a $20-$25 PCI card. > Look for one supported by the dc driver, as documented in the dc(4) > man page. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 23 18:30: 1 2000 Delivered-To: freebsd-net@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 96C5037B424 for ; Wed, 23 Aug 2000 18:29:58 -0700 (PDT) Received: (qmail 13583 invoked by uid 1000); 23 Aug 2000 13:30:50 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 23 Aug 2000 13:30:50 -0000 Date: Wed, 23 Aug 2000 08:30:50 -0500 (CDT) From: Mike Silbersack To: "Andrew C. Hornback" Cc: 'Wes Peters' , freebsd-net@freebsd.org Subject: RE: What NIC card to get? In-Reply-To: <00e701c00d66$f3e6ac20$d4776bce@challenger> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'd really feel bad telling people to buy ISA cards, personally. They're a lot more trouble that they're worth. (And most new boards don't have ISA slots anyway.) Mike "Silby" Silbersack On Wed, 23 Aug 2000, Andrew C. Hornback wrote: > Point of reference: > > I'd never paid more than $20 for a NIC, and don't plan to when I can get > the SMC 10/100 cards for generally half that. The 8216s are generally > anywhere from $2-$8. > > --- Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 23 18:38:21 2000 Delivered-To: freebsd-net@freebsd.org Received: from wireco.net (mental.wireco.net [206.107.119.3]) by hub.freebsd.org (Postfix) with SMTP id 78ADB37B423 for ; Wed, 23 Aug 2000 18:38:18 -0700 (PDT) Received: (qmail 26855 invoked from network); 24 Aug 2000 01:38:17 -0000 Received: from d23.johnson-city.tn.us.wireco.net (HELO challenger) (206.107.119.212) by mental.wireco.net with SMTP; 24 Aug 2000 01:38:17 -0000 Reply-To: From: "Andrew C. Hornback" To: "'Mike Silbersack'" Cc: Subject: RE: What NIC card to get? Date: Wed, 23 Aug 2000 21:37:24 -0400 Message-ID: <00ec01c00d6b$dad9ea30$d4776bce@challenger> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: Mike Silbersack [mailto:silby@silby.com] > Sent: Wednesday, August 23, 2000 9:31 AM > To: Andrew C. Hornback > Cc: 'Wes Peters'; freebsd-net@freebsd.org > Subject: RE: What NIC card to get? > > I'd really feel bad telling people to buy ISA cards, > personally. They're > a lot more trouble that they're worth. (And most new boards > don't have > ISA slots anyway.) > > Mike "Silby" Silbersack > > On Wed, 23 Aug 2000, Andrew C. Hornback wrote: > > > Point of reference: > > > > I'd never paid more than $20 for a NIC, and don't plan > to when I can get > > the SMC 10/100 cards for generally half that. The 8216s > are generally > > anywhere from $2-$8. Well, the reason I threw that in there was for a point of reference. The 8216s that I've got were used, and are in perfect working order. They may be more trouble than they're worth to some but when you have machines that don't have PCI slots (yes, I've still got a few of those in service over here), that's the best you can do. I really don't wanna tangle with EISA NICs (which are rare as can be, YMMV)... nor do I wanna seek out VLB NICs (again, QUITE rare)... --- Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 23 21:23:49 2000 Delivered-To: freebsd-net@freebsd.org Received: from defiant.quansoo.com (adsl-216-158-26-30.cust.oldcity.dca.net [216.158.26.30]) by hub.freebsd.org (Postfix) with ESMTP id 2B6B437B42C for ; Wed, 23 Aug 2000 21:23:47 -0700 (PDT) Received: from localhost (cgriffiths@localhost) by defiant.quansoo.com (8.9.3/8.9.3) with ESMTP id AAA00534 for ; Thu, 24 Aug 2000 00:23:43 -0400 (EDT) (envelope-from cgriffiths@quansoo.com) X-Authentication-Warning: defiant.quansoo.com: cgriffiths owned process doing -bs Date: Thu, 24 Aug 2000 00:23:43 -0400 (EDT) From: "Christopher T. Griffiths" To: net@freebsd.org Subject: Help with PPTP vpn server using mpd-netgraph Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have run into the following problem running mpd-netgraph port on my 4.1 -stable machine: I am getting the following error in my log: Aug 24 00:14:24 enterprise mpd: [pptp] error writing len 27 frame to bypass: No buffer space available This is the first time I have seen this error and have no idea what could be going wrong here. I have not changed anything from my config that I was using earlier and this error just started poping up. If you have any suggestions please let me know. Thanks Again. Chris --- Christopher T. Griffiths Quansoo Group Inc. cgriffiths@quansoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 24 9:21:29 2000 Delivered-To: freebsd-net@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id 6C04D37B43C for ; Thu, 24 Aug 2000 09:21:27 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Thu, 24 Aug 2000 17:21:23 +0100 Message-ID: <39A54B82.7AC1C40D@cs.ucl.ac.uk> Date: Thu, 24 Aug 2000 17:21:22 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: fbsd 4.1 crashes over pccard NICs when cards are removed... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings Dunno if anyone has experienced that but under fbsd stable (4.1) laptop installation, I tried to setup a wavelan interface and an ethernet interface The wavelan kept failing on the Tx and when I removed first the ethernet interface and then the wavelan the laptop crashed and rebooted.... Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 24 9:27: 6 2000 Delivered-To: freebsd-net@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id 83DF937B423 for ; Thu, 24 Aug 2000 09:27:03 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Thu, 24 Aug 2000 17:16:18 +0100 Message-ID: <39A54A50.1151A1A@cs.ucl.ac.uk> Date: Thu, 24 Aug 2000 17:16:16 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG, freebsd-net@freebsd.org Subject: fbsd box acting as a wavelan BS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, Has anyone managed to configure a fbsd box as a Wavelan BS ? Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 24 9:46:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id BEA0637B423 for ; Thu, 24 Aug 2000 09:46:37 -0700 (PDT) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id e7OGkYU14564; Thu, 24 Aug 2000 09:46:34 -0700 (PDT) Message-Id: <200008241646.e7OGkYU14564@ptavv.es.net> To: t.pagtzis@cs.ucl.ac.uk Cc: freebsd-net@FreeBSD.ORG Subject: Re: fbsd 4.1 crashes over pccard NICs when cards are removed... In-reply-to: Your message of "Thu, 24 Aug 2000 17:21:22 BST." <39A54B82.7AC1C40D@cs.ucl.ac.uk> Date: Thu, 24 Aug 2000 09:46:34 -0700 From: "Kevin Oberman" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Date: Thu, 24 Aug 2000 17:21:22 +0100 > From: Theo PAGTZIS > Sender: owner-freebsd-net@FreeBSD.ORG > > Greetings > > Dunno if anyone has experienced that but under fbsd stable (4.1) laptop > installation, I tried to setup a wavelan interface and an ethernet > interface > > The wavelan kept failing on the Tx and when I removed first the ethernet > interface and then the wavelan the laptop crashed and rebooted.... This is probably more appropriate to mobile. That's where the PCCARD folk hang out. In any case, you probably need to add the appropriate setup using wicontrol to /etc/pccard.conf. Put the wicontrol command(s) before running pccard_ether. If you are not familiar with pccard.conf, find the entry for your card in /etc/defaults/pccard.conf and copy it into /etc/pccard.conf. Then make the appropriate edits. In this case, add the wicontrol command(s) you need for the appropriate setup. You may also need to play with the IRQ for the WaveLAN card. If so, replace the '?' in the config line with the desired IRQ. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 24 9:54:46 2000 Delivered-To: freebsd-net@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 08D8C37B422 for ; Thu, 24 Aug 2000 09:54:44 -0700 (PDT) Received: from randy by rip.psg.com with local (Exim 3.13 #1) id 13S0H1-000PTG-00; Thu, 24 Aug 2000 09:54:39 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Kevin Oberman" Cc: t.pagtzis@cs.ucl.ac.uk, freebsd-net@FreeBSD.ORG Subject: Re: fbsd 4.1 crashes over pccard NICs when cards are removed... References: <39A54B82.7AC1C40D@cs.ucl.ac.uk> <200008241646.e7OGkYU14564@ptavv.es.net> Message-Id: Date: Thu, 24 Aug 2000 09:54:39 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org heck, two e1s will be eaten by rapidite/fulham and our office. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 24 9:55:58 2000 Delivered-To: freebsd-net@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id A816637B43C for ; Thu, 24 Aug 2000 09:55:56 -0700 (PDT) Received: from randy by rip.psg.com with local (Exim 3.13 #1) id 13S0ID-000PU2-00; Thu, 24 Aug 2000 09:55:53 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Kevin Oberman" , t.pagtzis@cs.ucl.ac.uk, freebsd-net@FreeBSD.ORG Subject: Re: fbsd 4.1 crashes over pccard NICs when cards are removed... References: <39A54B82.7AC1C40D@cs.ucl.ac.uk> <200008241646.e7OGkYU14564@ptavv.es.net> Message-Id: Date: Thu, 24 Aug 2000 09:55:53 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > heck, two e1s will be eaten by rapidite/fulham and our office. sorry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 24 10:43:53 2000 Delivered-To: freebsd-net@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by hub.freebsd.org (Postfix) with ESMTP id 1778537B423; Thu, 24 Aug 2000 10:43:49 -0700 (PDT) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id KAA13920; Thu, 24 Aug 2000 10:43:45 -0700 (PDT) Date: Thu, 24 Aug 2000 10:43:45 -0700 From: Eric Kozowski To: Theo PAGTZIS Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS Message-ID: <20000824104345.G12584@schooner.svjava.com> References: <39A54A50.1151A1A@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i In-Reply-To: <39A54A50.1151A1A@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Thu, Aug 24, 2000 at 05:16:16PM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Aug 24, 2000 at 05:16:16PM +0100, Theo PAGTZIS wrote: > Hi all, > > Has anyone managed to configure a fbsd box as a Wavelan BS ? yes it's easy. which wavelan card are you using? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 24 14:21:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id E1C6A37B42C; Thu, 24 Aug 2000 14:21:21 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e7OLLKf00983; Thu, 24 Aug 2000 14:21:20 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma000971; Thu, 24 Aug 2000 14:20:55 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id OAA01934; Thu, 24 Aug 2000 14:20:55 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008242120.OAA01934@bubba.whistle.com> Subject: Re: Help with PPTP vpn server using mpd-netgraph In-Reply-To: "from Christopher T. Griffiths at Aug 24, 2000 00:23:43 am" To: freebsd-net@FreeBSD.ORG Date: Thu, 24 Aug 2000 14:20:55 -0700 (PDT) Cc: net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christopher T. Griffiths writes: > I have run into the following problem running mpd-netgraph port on my > 4.1 -stable machine: > > I am getting the following error in my log: > > Aug 24 00:14:24 enterprise mpd: [pptp] error writing len 27 frame to > bypass: No buffer space available [ replying to the list, forgot to earlier ] This error can safely be ignored, though it can indicate that the peer is not responding or GRE packets are otherwise unable to get through. An "occasional" occurrence of this error is normal. It indicates that the GRE transmit window is full (i.e., still waiting for acknowlegements to be received from the peer for previously transmitted packets). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 24 14:21:29 2000 Delivered-To: freebsd-net@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id E1C6A37B42C; Thu, 24 Aug 2000 14:21:21 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e7OLLKf00983; Thu, 24 Aug 2000 14:21:20 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma000971; Thu, 24 Aug 2000 14:20:55 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id OAA01934; Thu, 24 Aug 2000 14:20:55 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008242120.OAA01934@bubba.whistle.com> Subject: Re: Help with PPTP vpn server using mpd-netgraph In-Reply-To: "from Christopher T. Griffiths at Aug 24, 2000 00:23:43 am" To: freebsd-net@FreeBSD.ORG Date: Thu, 24 Aug 2000 14:20:55 -0700 (PDT) Cc: net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christopher T. Griffiths writes: > I have run into the following problem running mpd-netgraph port on my > 4.1 -stable machine: > > I am getting the following error in my log: > > Aug 24 00:14:24 enterprise mpd: [pptp] error writing len 27 frame to > bypass: No buffer space available [ replying to the list, forgot to earlier ] This error can safely be ignored, though it can indicate that the peer is not responding or GRE packets are otherwise unable to get through. An "occasional" occurrence of this error is normal. It indicates that the GRE transmit window is full (i.e., still waiting for acknowlegements to be received from the peer for previously transmitted packets). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 24 14:40:22 2000 Delivered-To: freebsd-net@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 0780237B422 for ; Thu, 24 Aug 2000 14:40:21 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e7OLeK101200 for ; Thu, 24 Aug 2000 14:40:20 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma001197; Thu, 24 Aug 2000 14:40:11 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id OAA02091 for freebsd-net@freebsd.org; Thu, 24 Aug 2000 14:40:11 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008242140.OAA02091@bubba.whistle.com> Subject: "poor man's bridging" To: freebsd-net@freebsd.org Date: Thu, 24 Aug 2000 14:40:11 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On the topic of bridging.. Today I realized today that you can do "poor man's bridging" between two interfaces very easily, without even having "options BRIDGE" in your kernel config! Just use something like this script.. #!/bin/sh # Replace with your interface names IF1="de0" IF2="de1" kldstat -v | grep -wq ng_ether || kldload ng_ether ngctl connect ${IF1}: ${IF2}: lower lower ngctl msg ${IF1}: setautosrc 0 ngctl msg ${IF2}: setautosrc 0 ngctl msg ${IF1}: setpromisc 1 ngctl msg ${IF2}: setpromisc 1 ifconfig ${IF1} up ifconfig ${IF2} up Just make sure you don't physically connect the two ports, or you'll get one heck of a packet storm (that's why this is "poor man's bridging" -- no loop detection or intelligent bridging). By inserting a ng_tee(4) node, you could have it so the local machine is able to talk as well (exercise left to the reader :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 24 16: 5: 7 2000 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 4CC8C37B424 for ; Thu, 24 Aug 2000 16:05:05 -0700 (PDT) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id QAA16897 for ; Thu, 24 Aug 2000 16:04:18 -0700 (PDT) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id QAA72511 for freebsd-net@FreeBSD.ORG; Thu, 24 Aug 2000 16:03:57 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200008242303.QAA72511@whistle.com> Subject: Re: "poor man's bridging" In-Reply-To: <200008242140.OAA02091@bubba.whistle.com> from Archie Cobbs at "Aug 24, 2000 02:40:11 pm" To: freebsd-net@FreeBSD.ORG Date: Thu, 24 Aug 2000 16:03:57 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Archie Cobbs writes: | On the topic of bridging.. | | Just use something like this script.. | | #!/bin/sh | | # Replace with your interface names | IF1="de0" | IF2="de1" | | kldstat -v | grep -wq ng_ether || kldload ng_ether | ngctl connect ${IF1}: ${IF2}: lower lower | ngctl msg ${IF1}: setautosrc 0 | ngctl msg ${IF2}: setautosrc 0 | ngctl msg ${IF1}: setpromisc 1 | ngctl msg ${IF2}: setpromisc 1 | ifconfig ${IF1} up | ifconfig ${IF2} up BTW we are doing this instead of bridging for bridging vmware onto a physical wire. No panics and it works. With bridging I also couldn't bridge the interfaces I wanted. I have five Nics in the box and didn't want them all bridged. Doing the cluster thing didn't seem to work at all. Note that until something opens the "tap" interface it doesn't exist under ifconfig -a. So I do a dd if=/dev/vmnet0 bs=1 count=0 of=/dev/null to make it appear first. Then run the above connecting dc0 & vmnet0 then it works just fine. This also has an advantage that the packets don't hit the host's IP stack which is what I needed since the host is on a different "control" network and I need it to go out of the host and then back in via a router (or our product). Now if I could only run multiple vmwares. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 24 23:32:46 2000 Delivered-To: freebsd-net@freebsd.org Received: from vbook.express.ru (vbook.express.ru [212.24.37.106]) by hub.freebsd.org (Postfix) with ESMTP id 8A0FD37B42C for ; Thu, 24 Aug 2000 23:32:43 -0700 (PDT) Received: (from vova@localhost) by vbook.express.ru (8.9.3/8.9.3) id JAA19082; Fri, 25 Aug 2000 09:17:33 +0400 (MSD) (envelope-from vova) From: "Vladimir B. Grebenschikov" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14758.365.556977.53335@vbook.express.ru> Date: Fri, 25 Aug 2000 09:17:33 +0400 (MSD) To: t.pagtzis@cs.ucl.ac.uk Cc: freebsd-net@FreeBSD.ORG Subject: fbsd box acting as a wavelan BS In-Reply-To: <39A54A50.1151A1A@cs.ucl.ac.uk> References: <39A54A50.1151A1A@cs.ucl.ac.uk> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Theo PAGTZIS writes: > Has anyone managed to configure a fbsd box as a Wavelan BS ? I am not sure, what you mean under WaveLan BS, but I have fbsd box working as WaveLan bridge with one wi interface and 2 PtP radiolinks - it works fine > Theo -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 24 23:36:37 2000 Delivered-To: freebsd-net@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 8E63B37B423 for ; Thu, 24 Aug 2000 23:36:34 -0700 (PDT) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 7F83D5D07; Fri, 25 Aug 2000 08:36:29 +0200 (CEST) Date: Fri, 25 Aug 2000 08:36:29 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: "Vladimir B. Grebenschikov" Cc: t.pagtzis@cs.ucl.ac.uk, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS In-Reply-To: <14758.365.556977.53335@vbook.express.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am not sure, what you mean under WaveLan BS, but I have fbsd box > working as WaveLan bridge with one wi interface and 2 PtP radiolinks > - it works fine I'm sure you mean "WaveLan router", not "WaveLan bridge", right? And if I understand the original poster correctly, "BS" means "base station" and he asks if anybody has been able to configure the WaveLan driver for access point mode (multipoint). I don't think that's possible with the current driver, because Lucent is not at all interested in providing the neccesary information on how to do that. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Aug 25 5:50:11 2000 Delivered-To: freebsd-net@freebsd.org Received: from server.osny.com.br (osny.com.br [200.215.110.57]) by hub.freebsd.org (Postfix) with ESMTP id 2E48A37B43C for ; Fri, 25 Aug 2000 05:49:27 -0700 (PDT) Received: from osny.com.br ([172.20.185.22]) by server.osny.com.br (8.10.1/8.10.1) with ESMTP id e7PCoDb05848 for ; Fri, 25 Aug 2000 09:50:28 -0300 (EST) Message-ID: <39A64272.309D73E6@osny.com.br> Date: Fri, 25 Aug 2000 09:54:58 +0000 From: Michelangelo Pisa Organization: Agencia Maritima Osny X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: free inglish Subject: Fetchmail Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi!!! Someone know how I get messages from a POP3 server using Fetchmail , where I don't need to do a password it's include on the sintaxe of the command? which is the sintaxe? Best Regards -- Agencia Marítima Osny LTDA Mica's Michelangelo Pisa Administrador de Sistemas e Flamenguista E-mail: michelangelo@osny.com.br Fone: (0xx47) 348 2800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Aug 25 6:13:37 2000 Delivered-To: freebsd-net@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.prod.itd.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id B73D937B422; Fri, 25 Aug 2000 06:13:32 -0700 (PDT) Received: from mickey (sdn-ar-002txhousP233.dialsprint.net [168.191.154.249]) by avocet.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with SMTP id GAA17187; Fri, 25 Aug 2000 06:13:31 -0700 (PDT) Reply-To: From: "Jason Holland" To: , , Subject: Non-recoverable failure in name resolution Date: Fri, 25 Aug 2000 08:13:05 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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) X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello all, i'm having a problem i hope someone can help out with. i've searched the mailing lists, bug reports and newsgroups and haven't found much information on this problem. i've seen it reported in a few places, but with no reply to a fix or answer. i'm running Freebsd 4.1 stable, installed from the latest ISO grabbed off ftp.freebsd.org 2 days ago. i have setup a dns server, running bind 8.2.3-T5B from stable. nslookup returns correct information when i do host lookups bash-2.04# nslookup cs.selu.edu Server: localhost Address: 127.0.0.1 Name: cs.selu.edu Address: 147.174.59.5 bash-2.04# however, when i try to telnet, ssh or ftp to that address, i get this bash-2.04# telnet cs.selu.edu cs.selu.edu: Non-recoverable failure in name resolution bash-2.04# my /etc/host.conf file looks like this bash-2.04# cat /etc/host.conf order hosts,bind multi on bash-2.04# my /etc/resolv.conf file looks like this bash-2.04# cat /etc/resolv.conf search xxxxxxx.net nameserver 127.0.0.1 bash-2.04# my hostname, ip, and routes are correct, and i have network connectivity as telnet, ftp and ssh work correctly if i specify the IP address, instead of hostname. but who wants to type in an ip address everytime? :) btw, i tried adding a specific entry in my /etc/hosts file for that address, and i still get the same non-recoverable failure. and though i compiled a new kernel, it has no firewall support, so nothing is being blocked. one last point. if i shutdown the dns server, and put my isp's dns servers in resolv.conf, i get the same error. how can my dns server return a correct query via nslookup, but ftp, telnet or ssh fail??? this is very weird, not to mention annoying! if anyone could help me out, or point me in the right direction, i'd appreciate it. thanks!! jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Aug 25 7: 3: 6 2000 Delivered-To: freebsd-net@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.prod.itd.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id C255E37B423; Fri, 25 Aug 2000 07:03:02 -0700 (PDT) Received: from mickey (sdn-ar-002txhousP233.dialsprint.net [168.191.154.249]) by avocet.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with SMTP id HAA18601; Fri, 25 Aug 2000 07:02:58 -0700 (PDT) Reply-To: From: "Jason Holland" To: "Roberto Nunnari, AGIE" Cc: , , Subject: RE: Non-recoverable failure in name resolution Date: Fri, 25 Aug 2000 09:02:32 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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) X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 In-Reply-To: <39A688E5.DD1EBCC@agie.ch> Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Reverse lookup works fine > > Hi Jason. > > try this: > # nslookup 147.174.59.5 > > if that doesn't work it means that named is not set up > correctly for reverse address resolution. In fact, many > network servers do reverse address lookup. > > Cheers. > -- > Roberto Nunnari -software engineer- > mailto:roberto.nunnari@agie.ch > AGIE - http://www.agie.com > Via dei pioppi 16 tel: +41-91-8069138 > 6616 Losone """ > Switzerland (o o) > =======================oOO==(_)==OOo======================== > MY OPNIONS ARE NOT NECESSARELY THOSE OF MY EMPLOYER > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Aug 25 8: 8:40 2000 Delivered-To: freebsd-net@freebsd.org Received: from sentry.gw.tislabs.com (sentry.gw.tislabs.com [192.94.214.100]) by hub.freebsd.org (Postfix) with ESMTP id CE3B637B422 for ; Fri, 25 Aug 2000 08:08:37 -0700 (PDT) Received: by sentry.gw.tislabs.com; id LAA07868; Fri, 25 Aug 2000 11:11:02 -0400 (EDT) Received: from clipper.gw.tislabs.com(10.33.1.2) by sentry.gw.tislabs.com via smap (V5.5) id xma007866; Fri, 25 Aug 00 11:10:15 -0400 Received: from localhost by clipper.gw.tislabs.com (8.9.3/8.9.1) with SMTP id LAA24107 for ; Fri, 25 Aug 2000 11:07:08 -0400 (EDT) Date: Fri, 25 Aug 2000 11:07:08 -0400 (EDT) From: Robert Watson X-Sender: rwatson@clipper.gw.tislabs.com Reply-To: Robert Watson To: freebsd-net@FreeBSD.org Subject: Fwd: Alpine: a new protocol development tool (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Don't know if anyone has taken a look at this, but it sounds pretty cool. I'm downloading it now... Robert Watson Research Scientist NAI Labs at Network Associates ---------- Forwarded message ---------- Date: Fri, 25 Aug 2000 10:08:57 -0400 From: Olafur Gudmundsson To: iip@tislabs.com Subject: Fwd: Alpine: a new protocol development tool We may want to keep this in mind for some of our experimentations in the future. Olafur ps: Sorry for sending technical stuff to iip ;-) >X-Authentication-Warning: boron.cs.washington.edu: ely owned process doing -bs >Date: Thu, 24 Aug 2000 15:13:51 -0700 (PDT) >From: David Ely >To: end2end-interest@ISI.EDU, tcp-impl@grc.nasa.gov >Subject: Alpine: a new protocol development tool >Sender: owner-end2end-interest@ISI.EDU > >Over the past few months I've been working with David Wetherall and >Stefan Savage on a tool that allows an unaltered kernel networking >stack to run in a user-level library. It's called Alpine >(Application-Level Protocol Infrastructure for Network >Experimentation). > >Probably the most unique feature of this package is that an alternate >network stack can be used and/or debugged without modifying either the >kernel or any application binaries. Developing protocols at >user-level is much easier than traditional kernel develop because >source-level debugging is available and no reboots are required >between revisions. > >It has turned out to be a useful tool for us, so I thought some of you >might also benefit from using it. It's currently only available for >FreeBSD 3.x on Intel x86 platforms. This is an alpha release, and >there are bound to be things that don't work perfectly. Please email >me if you run into any problems. I will do my best to correct them. > >Check out http://alpine.cs.washington.edu/ for more information. > >Cheers, > >David > >P.S. I will be at SIGCOMM next week if you're interested in talking >to me about Alpine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Aug 25 14:41: 4 2000 Delivered-To: freebsd-net@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 66CC837B424; Fri, 25 Aug 2000 14:41:00 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA17490; Fri, 25 Aug 2000 14:41:00 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 25 Aug 2000 14:41:00 -0700 (PDT) From: Kris Kennaway To: Jason Holland Cc: freebsd-net@freebsd.org Subject: Re: Non-recoverable failure in name resolution In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 25 Aug 2000, Jason Holland wrote: > however, when i try to telnet, ssh or ftp to that address, i get this > > bash-2.04# telnet cs.selu.edu > cs.selu.edu: Non-recoverable failure in name resolution Be sure your telnet binary is from 4.1-STABLE. Older telnet binaries will not work. Please do not cross-post to three mailing lists for your questions - pick the appropriate one according to the charter and send it there only. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Aug 25 19:42: 8 2000 Delivered-To: freebsd-net@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.prod.itd.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id BCD5A37B43F for ; Fri, 25 Aug 2000 19:42:02 -0700 (PDT) Received: from mickey (sdn-ar-002txhousP226.dialsprint.net [168.191.154.242]) by scaup.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with SMTP id TAA14319; Fri, 25 Aug 2000 19:41:58 -0700 (PDT) Reply-To: From: "Jason Holland" To: "Roberto Nunnari, AGIE" , Subject: RE: Non-recoverable failure in name resolution Date: Fri, 25 Aug 2000 21:41:28 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org thanks for everyones help. it turns out my /etc/host.conf file was in an incorrect format. a word of advice, take off you "linux cap" BEFORE you put on your "bsd cap" :) thanks again for the quick response jason > > Reverse lookup works fine > > > > > Hi Jason. > > > > try this: > > # nslookup 147.174.59.5 > > > > if that doesn't work it means that named is not set up > > correctly for reverse address resolution. In fact, many > > network servers do reverse address lookup. > > > > Cheers. > > -- > > Roberto Nunnari -software engineer- > > mailto:roberto.nunnari@agie.ch > > AGIE - http://www.agie.com > > Via dei pioppi 16 tel: +41-91-8069138 > > 6616 Losone """ > > Switzerland (o o) > > =======================oOO==(_)==OOo======================== > > MY OPNIONS ARE NOT NECESSARELY THOSE OF MY EMPLOYER > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Aug 25 20: 1:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from fatbastard.zialink.com (fatbastard.zialink.com [63.227.239.3]) by hub.freebsd.org (Postfix) with ESMTP id 2A10937B422 for ; Fri, 25 Aug 2000 20:01:39 -0700 (PDT) Received: from localhost (tucka@localhost) by fatbastard.zialink.com (8.9.3/8.9.3) with ESMTP id VAA03558 for ; Fri, 25 Aug 2000 21:01:44 -0600 (MDT) (envelope-from tucka@fatbastard.zialink.com) Date: Fri, 25 Aug 2000 21:01:43 -0600 (MDT) From: tucka To: freebsd-net@freebsd.org Subject: ipnat fails under load Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You can add me to the list of people who have problems with ipfilter under load. 3 boxes, 2 with 4.1-S ipf 3.4.8 and 1 with 4.0-S ipf 3.3.8. It doesn't seem to be so much a problem with how many clients are accessing the server, but rather just a matter of time. All 3 boxes consistently fail after 2 to 4 hours of use. Some can be "saved" via an ipf -Fa and reloading, but usually they need to be restarted. I've had to go back to SUSE *blech* on one box because it was just unusable. If there is any other info I can provide to help resolve this issue please don't hesitate to ask. Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Aug 26 11: 1:15 2000 Delivered-To: freebsd-net@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id F036C37B42C; Sat, 26 Aug 2000 11:01:08 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Sat, 26 Aug 2000 19:00:58 +0100 Message-ID: <39A805D7.95A813AF@cs.ucl.ac.uk> Date: Sat, 26 Aug 2000 19:00:55 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: Eric Kozowski Cc: Theo PAGTZIS , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS References: <39A54A50.1151A1A@cs.ucl.ac.uk> <20000824104345.G12584@schooner.svjava.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Eric Kozowski wrote: > On Thu, Aug 24, 2000 at 05:16:16PM +0100, Theo PAGTZIS wrote: > > Hi all, > > > > Has anyone managed to configure a fbsd box as a Wavelan BS ? > > yes it's easy. which wavelan card are you using? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Wavelan Orinoco...Silver (with the ISA bridge) I would like to know how but ...do you really mean that the fbsd box is acting a base station with the wavelan card in *infrastructure* mode or do you mean that the box operates in ad-hoc (peer to peer ) mode. Adhoc mode is very easy...what I want is to have the fbsd base station act as an access point where _many_ clients can associate....not just one.... so which of the two does the fbsd "wavelan BS" do ...adhoc mode (peer to peer connection ) or infrastructure mode...??? If it works in ad-hoc mode the PCF and DCF functions are not really happening...which is what a BS is all about... Don't you agree? (or anyone else) Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Aug 26 11: 6:14 2000 Delivered-To: freebsd-net@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id AC4D937B424 for ; Sat, 26 Aug 2000 11:06:12 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Sat, 26 Aug 2000 19:06:06 +0100 Message-ID: <39A8070B.5F3E4DFE@cs.ucl.ac.uk> Date: Sat, 26 Aug 2000 19:06:03 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: Blaz Zupan Cc: "Vladimir B. Grebenschikov" , t.pagtzis@cs.ucl.ac.uk, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Blaz Zupan wrote: > > I am not sure, what you mean under WaveLan BS, but I have fbsd box > > working as WaveLan bridge with one wi interface and 2 PtP radiolinks > > - it works fine > > I'm sure you mean "WaveLan router", not "WaveLan bridge", right? And if I > understand the original poster correctly, "BS" means "base station" and he > asks if anybody has been able to configure the WaveLan driver for access point > mode (multipoint). I don't think that's possible with the current driver, > because Lucent is not at all interested in providing the neccesary information > on how to do that. > > Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia > E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 Blaz, I see you catch my drift....cheers. That's exactly what I am referring to...I know Lucent is pretty tight in giving out info on the Hermes firmware API...adhoc mode is not good...it is just a ptp connection... I was just wandering whether any geezer has gone into the pain of squeezing any info to make DCF and PCF a reality...but I guess the kernel on the lucent wavelan bridge must have something more than just the hermes firmware of the RF card in place to do that .. If anyone has got any info on it it would be cool to see what's in it.. :) Cheers guys Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Aug 26 11:14:35 2000 Delivered-To: freebsd-net@freebsd.org Received: from peony.ezo.net (peony.ezo.net [206.102.130.11]) by hub.freebsd.org (Postfix) with ESMTP id 954B137B423; Sat, 26 Aug 2000 11:14:25 -0700 (PDT) Received: from localhost (jflowers@localhost) by peony.ezo.net (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e7QIdja02282; Sat, 26 Aug 2000 14:39:45 -0400 (EDT) Date: Sat, 26 Aug 2000 14:39:45 -0400 (EDT) From: Jim Flowers To: Theo PAGTZIS Cc: Eric Kozowski , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS In-Reply-To: <39A805D7.95A813AF@cs.ucl.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Last I checked the wi driver will not do IBSS and says so in the documentation. I also tried it and couldn't get anywhere. Would be nice. Even better would be to use the algos in their office router stuff. We're looking at that now. We currently use a fbsd box to connect the Internet to a WavePointII on one frequency and then on a second frequency we connect multipoint users with fbsd boxes. Works very well although the WavePointII has to be monitored continuously. Bandwidth varies from 600 kbps to about 3000 kbps. Jim Flowers #4 ranked ISP on C|NET #1 in Ohio On Sat, 26 Aug 2000, Theo PAGTZIS wrote: > Eric Kozowski wrote: > > > On Thu, Aug 24, 2000 at 05:16:16PM +0100, Theo PAGTZIS wrote: > > > Hi all, > > > > > > Has anyone managed to configure a fbsd box as a Wavelan BS ? > > > > yes it's easy. which wavelan card are you using? > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > Wavelan Orinoco...Silver (with the ISA bridge) > > I would like to know how but ...do you really mean that the fbsd box is > acting a base station with the wavelan card in *infrastructure* mode or > do you mean that the box operates in ad-hoc (peer to peer ) mode. Adhoc > mode is very easy...what I want is to have the fbsd base station act as > an access point where _many_ clients can associate....not just one.... > > so which of the two does the fbsd "wavelan BS" do ...adhoc mode (peer to > peer connection ) or infrastructure mode...??? > > If it works in ad-hoc mode the PCF and DCF functions are not really > happening...which is what a BS is all about... > > Don't you agree? (or anyone else) > > > Theo > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" 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 Sat Aug 26 11:28:16 2000 Delivered-To: freebsd-net@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id 6E74837B43C; Sat, 26 Aug 2000 11:28:09 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Sat, 26 Aug 2000 19:28:04 +0100 Message-ID: <39A80C31.2FB487D5@cs.ucl.ac.uk> Date: Sat, 26 Aug 2000 19:28:01 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: Jim Flowers Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jim Flowers wrote: > Last I checked the wi driver will not do IBSS and says so in the > documentation. I also tried it and couldn't get anywhere. Would be nice. > Jim, do you mean Bill's driver doesn't do adhoc mode...? IBSS is independent BSS which is adhoc mode...did you mean to say BSS ?? > > Even better would be to use the algos in their office router stuff. We're > looking at that now. > Couldn't agree more... > > We currently use a fbsd box to connect the Internet to a WavePointII on > one frequency and then on a second frequency we connect multipoint users > with fbsd boxes. > wait a minute...a single WPII bridge is connected behind a fbsd router box.....fine...now one freq is to act as a portal for the ...Internet?? and the other is to act as an AP for the nodes... but the BS can operate in a single freq...cannot switch between different frequencies (unless you set it manually but this is a different cell altogether...from the portal cell to Inet..) something is not quite right here...could you explain a little? > > Works very well although the WavePointII has to be monitored > continuously. Bandwidth varies from 600 kbps to about 3000 kbps. why does the WPII have to be monitored? In any case the AP function is not effected in the fbsd box but on lucent's bridge...well that is what I am doing....for the moment... Do you have any code that is checking out the office router algos? I would appreciate a peek.... :) Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Aug 26 18:23:12 2000 Delivered-To: freebsd-net@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by hub.freebsd.org (Postfix) with ESMTP id 8C29D37B43E; Sat, 26 Aug 2000 18:23:04 -0700 (PDT) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id SAA06785; Sat, 26 Aug 2000 18:23:01 -0700 (PDT) Date: Sat, 26 Aug 2000 18:23:01 -0700 From: Eric Kozowski To: Theo PAGTZIS Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS Message-ID: <20000826182301.C6587@schooner.svjava.com> References: <39A54A50.1151A1A@cs.ucl.ac.uk> <20000824104345.G12584@schooner.svjava.com> <39A805D7.95A813AF@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i In-Reply-To: <39A805D7.95A813AF@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Sat, Aug 26, 2000 at 07:00:55PM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Aug 26, 2000 at 07:00:55PM +0100, Theo PAGTZIS wrote: > Eric Kozowski wrote: > > > On Thu, Aug 24, 2000 at 05:16:16PM +0100, Theo PAGTZIS wrote: > > > Hi all, > > > > > > Has anyone managed to configure a fbsd box as a Wavelan BS ? > > > > yes it's easy. which wavelan card are you using? > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > Wavelan Orinoco...Silver (with the ISA bridge) > > I would like to know how but ...do you really mean that the fbsd box is > acting a base station with the wavelan card in *infrastructure* mode or > do you mean that the box operates in ad-hoc (peer to peer ) mode. Adhoc > mode is very easy...what I want is to have the fbsd base station act as > an access point where _many_ clients can associate....not just one.... > > so which of the two does the fbsd "wavelan BS" do ...adhoc mode (peer to > peer connection ) or infrastructure mode...??? a wavelan accesspoint operates in infrastructe mode, which means that the client can only talk to the base station/accesspoint. ad-hoc means clients can contact each other directly. the wi driver supports both modes. i'm running my wavelan gold card in BSS mode to an apple airport base station. > If it works in ad-hoc mode the PCF and DCF functions are not really > happening...which is what a BS is all about... not sure what you mean by pcf and dcf. i do know that power saving mode will not work in ad-hoc mode. > Don't you agree? (or anyone else) with what? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message