From owner-freebsd-net Mon Nov 16 01:46:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13890 for freebsd-net-outgoing; Mon, 16 Nov 1998 01:46:21 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13885 for ; Mon, 16 Nov 1998 01:46:19 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.59.188]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA53B5; Mon, 16 Nov 1998 10:45:54 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 16 Nov 1998 10:50:23 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Jim Cassata Subject: Re: Netware client for FreeBSD Cc: FreeBSD Net Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 13-Nov-98 Jim Cassata wrote: > On Fri, 13 Nov 1998, Bill Fumerola wrote: > >> On Fri, 13 Nov 1998, Joao Carlos Mendes Luis wrote: > This is extremely important for all of us FreeBSD proponents out there! > Caldera has the right idea, because it is their bundling of Netware > services with their Linux distribution that incents MIS people to > introduce a new OS into their environment. Just about all of our > customers are Netware environments, and it is precisely this lack of a > Netware client or integration into NDS that usually halts any FreeBSD box > from being introduced. Just look at what is happening in our industyr > right now. Sun is integrating NT services into it's OS, Novell will run > its NDS on Novell or NT, .... etc etc. Integration into heterogeneous > environments is critical to any OS being adopted, and I am surprised by > the fact that only Caldera (and obviously UNIXWare) are doing the Novell > thing. Just to let ye know some things: I was recently at Novell's tech Center in Dusseldorf for a NDS Advanced training and there I was told that Caldera is intregrating NDS for Caldera's Linux. As far other things, I am currently trying to get some documents of the floor for FreeBSD and Novell integrating as well as trying to port some code/make some code myself for NLSP and god knows what else that NetWare uses... Any help is offcourse always appreciated, that's what makes FreeBSD tick ;) For information, we deploy FreeBSD as firewalls/nameservers and for the rest we only use Novell NetWare (about 400-500 servers nationwide), almost all 4.11. So ye can see my interest at integration. Hope this is of help to people, --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 01:48:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14069 for freebsd-net-outgoing; Mon, 16 Nov 1998 01:48:58 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14064 for ; Mon, 16 Nov 1998 01:48:55 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.59.188]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA55FB for ; Mon, 16 Nov 1998 10:48:30 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 16 Nov 1998 10:53:00 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Net Subject: Frametypes (was: Re: Netware client for FreeBSD) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On a sidenote, which fraemetypes do we support for IPX traffic? If we only support Eth_II at this point then we need to integrate 802.2/3 too. But I can remember a previous post about these frametypes. Anyone care to refresh my mind? --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 02:31:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17779 for freebsd-net-outgoing; Mon, 16 Nov 1998 02:31:17 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from msf1.swe.ids.dps.casa.es (h029196.nexo.es [195.235.29.196]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17769 for ; Mon, 16 Nov 1998 02:31:06 -0800 (PST) (envelope-from jlfreniche@acm.org) Received: from is1.casa.es (is1.casa.es [128.3.50.250]) by msf1.swe.ids.dps.casa.es (8.8.8/8.8.8) with ESMTP id JAA01077 for ; Mon, 16 Nov 1998 09:52:43 +0100 (CET) (envelope-from jlfreniche@acm.org) Received: from acm.org (localhost [127.0.0.1]) by is1.casa.es (8.8.8/8.8.8) with ESMTP id JAA06847 for ; Mon, 16 Nov 1998 09:50:40 +0100 (CET) (envelope-from jlfreniche@acm.org) Message-ID: <364FE760.C4EEBAA0@acm.org> Date: Mon, 16 Nov 1998 09:50:40 +0100 From: "Juan L. Freniche" X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: Re: Netware client for FreeBSD References: <18342.910995606@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm getting a little bit confused by this topic. The discussion started when someone (I deleted the message so I can't remember who, sorry) asked for a Netware Client for FreeBSD. Some other stated that mars_nwe is a server, not a client. To me, the key question is: if I install mars_nwe in our FreeBSD boxes, can they use the Netware services already available in other boxes with other OS? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 02:32:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17933 for freebsd-net-outgoing; Mon, 16 Nov 1998 02:32:35 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17918 for ; Mon, 16 Nov 1998 02:32:29 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id MAA14186; Mon, 16 Nov 1998 12:31:42 +0200 (SAT) From: John Hay Message-Id: <199811161031.MAA14186@zibbi.mikom.csir.co.za> Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) In-Reply-To: from Jeroen Ruigrok/Asmodai at "Nov 16, 98 10:53:00 am" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Mon, 16 Nov 1998 12:31:42 +0200 (SAT) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 > > which fraemetypes do we support for IPX traffic? If we only support Eth_II at > this point then we need to integrate 802.2/3 too. > > But I can remember a previous post about these frametypes. Anyone care to > refresh my mind? Well at the moment FreeBSD only supports Ethernet_II. I do have patches for 802.3 support, but that is using a single sysctl to switch between E_II and 802.3 for the whole machine (all its interfaces). Support for the different frames isn't too difficult. It is the mechanism to make different interfaces use different frames in a nice way that I'm stuck with. Ie. have ed0 use 802.3 and ed1 use E_II and ed3 use 802.2 or even run two or more frames on the same interface. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 02:44:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19167 for freebsd-net-outgoing; Mon, 16 Nov 1998 02:44:42 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA19162 for ; Mon, 16 Nov 1998 02:44:39 -0800 (PST) (envelope-from tseidmann@simultan.ch) Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53]) by SIMULTAN.CH (8.9.1a/8.9.1) with ESMTP id LAA09448; Mon, 16 Nov 1998 11:44:09 +0100 (CET) Message-ID: <365001F6.B641DC8@simultan.ch> Date: Mon, 16 Nov 1998 11:44:06 +0100 From: Thomas Seidmann X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Jeroen Ruigrok/Asmodai CC: FreeBSD Net Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeroen Ruigrok/Asmodai wrote: > > On a sidenote, > > which fraemetypes do we support for IPX traffic? If we only support Eth_II at > this point then we need to integrate 802.2/3 too. I have written a small patch to if_ethersubr.c to recognize any type of IPX frames on input and to send out always 802.3 frames. Do you care for it? Regards, Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 02:56:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20270 for freebsd-net-outgoing; Mon, 16 Nov 1998 02:56:35 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20265 for ; Mon, 16 Nov 1998 02:56:33 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.190]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1DB8; Mon, 16 Nov 1998 11:56:08 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811161031.MAA14186@zibbi.mikom.csir.co.za> Date: Mon, 16 Nov 1998 12:00:32 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: John Hay Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) Cc: freebsd-net@FreeBSD.ORG Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 16-Nov-98 John Hay wrote: >> >> which fraemetypes do we support for IPX traffic? If we only support Eth_II >> at >> this point then we need to integrate 802.2/3 too. >> >> But I can remember a previous post about these frametypes. Anyone care to >> refresh my mind? > > Well at the moment FreeBSD only supports Ethernet_II. I do have patches > for 802.3 support, but that is using a single sysctl to switch between > E_II and 802.3 for the whole machine (all its interfaces). Support for > the different frames isn't too difficult. It is the mechanism to make > different interfaces use different frames in a nice way that I'm stuck > with. Ie. have ed0 use 802.3 and ed1 use E_II and ed3 use 802.2 or > even run two or more frames on the same interface. Care to provide me with the patches? =) Well there has to be a nice idea how to solve it. Most likely as an extension to rc.conf to the interfaces. --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 04:15:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA00622 for freebsd-net-outgoing; Mon, 16 Nov 1998 04:15:13 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA00616 for ; Mon, 16 Nov 1998 04:15:11 -0800 (PST) (envelope-from tseidmann@simultan.ch) Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53]) by SIMULTAN.CH (8.9.1a/8.9.1) with ESMTP id NAA09945; Mon, 16 Nov 1998 13:14:43 +0100 (CET) Message-ID: <3650172F.37AF7F2D@simultan.ch> Date: Mon, 16 Nov 1998 13:14:39 +0100 From: Thomas Seidmann X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "Juan L. Freniche" CC: freebsd-net@FreeBSD.ORG Subject: Re: Netware client for FreeBSD References: <18342.910995606@zippy.cdrom.com> <364FE760.C4EEBAA0@acm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Juan L. Freniche" wrote: > The discussion started when someone (I deleted the message so I can't > remember who, sorry) asked for a Netware Client for FreeBSD. Some other > stated that mars_nwe is a server, not a client. > > To me, the key question is: if I install mars_nwe in our FreeBSD boxes, > can they use the Netware services already available in other boxes with > other OS? No, you can't. mars_nwe emulates a NetWare server. Regards, Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 05:02:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA06194 for freebsd-net-outgoing; Mon, 16 Nov 1998 05:02:43 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from bsdi.netcon.com ([206.27.114.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA06183 for ; Mon, 16 Nov 1998 05:02:39 -0800 (PST) (envelope-from tony@netcon.com) Received: from netcon.com ([206.27.114.196]) by bsdi.netcon.com (8.7.4/8.7.3) with ESMTP id GAA22682; Mon, 16 Nov 1998 06:26:51 -0500 (EST) Message-ID: <3650214B.19CE4C2A@netcon.com> Date: Mon, 16 Nov 1998 07:57:47 -0500 From: Tony Ardolino Organization: NetCon Corp. X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: Cam Johnson CC: Boris Popov , Jim Cassata , FreeBSD Net Subject: Re: [Fwd: Netware client for FreeBSD] References: <364D6702.3B3CBCF2@solidsys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Ok! OK! My name is Tony Ardolino and I own NetCon along Frank Whitsell, we have been considering release NetCon to the FreeBSD community for a long time. Can someone referrer me to a license that would allow the following; 1.) Free distribution for non-commerical use only. 2.) A enhancements must be returned to FreeBSD. 3.) Commerical use or Resale requires a license from NetCon Corp. 4.) NetCon Corp. will always own NetCon Software and all clanges. 5.) Cannot be ported to any other platform Like SCO, or Sun. I also need a committment from a group of people to keep NetCon updated with the changes in NetWare and Freebsd (About a month a year). We will train and support all who are intreasted. Get me this and you will get NetWare for FreeBSD. Tony Ardolino President NetCon Corporation Cam Johnson wrote: > FYI > > Cam > > ------------------------------------------------------------------------ > > Subject: Re: Netware client for FreeBSD > Date: Sat, 14 Nov 1998 08:27:11 +0600 (ALMT) > From: Boris Popov > To: "Jordan K. Hubbard" > CC: Jim Cassata ,FreeBSD Net > > On Fri, 13 Nov 1998, Jordan K. Hubbard wrote: > > > > This is extremely important for all of us FreeBSD proponents out there! > > > Caldera has the right idea, because it is their bundling of Netware > > > services with their Linux distribution that incents MIS people to > > > > They can do this because they have an agreement with Novell to do so. > But Mars_nwe was written by Martin Stover from scratch. > > > > > introduce a new OS into their environment. Just about all of our > > > customers are Netware environments, and it is precisely this lack of a > > > Netware client or integration into NDS that usually halts any FreeBSD box > > > from being introduced. Just look at what is happening in our industyr > > > > That's just silly. The netcon product has been out for *3 years* now > > and delivers more than adequate Netware client, server and IPX gateway > > functionality at a reasonable price. It has been on our commercial > > software pages and in the commerce distribution since almost day one as > > well so nobody can say we didn't publicise it as an option. > > Yes, price is reasonable, but some peoples and organizations > still can't by it. In addition, netcon product does not support (at least > for now) FreeBSD 3.0 and miss some functions in server implementation. > In general, FreeBSD need some improvements to IPX stack and > routing daemon (I wrote about that to Jhon Hay). > > -- > Boris Popov > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- Tony Ardolino President NetCon Corp. 605 North Lake Circle Crystal River, Florida 34429 Voice: 352/563-5300 Fax: 352/795-6783 Email: tony@netcon.com http://www.netcon.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 05:42:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11109 for freebsd-net-outgoing; Mon, 16 Nov 1998 05:42:50 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from vidar.erilab.com (mpk104.erilab.com [208.224.156.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11102 for ; Mon, 16 Nov 1998 05:42:47 -0800 (PST) (envelope-from Rainer.Enders@erilab.com) Received: from erilab.com (willow.erilab.com [192.168.174.2]) by vidar.erilab.com (8.9.1a/8.9.1) with ESMTP id FAA29370 for ; Mon, 16 Nov 1998 05:42:03 -0800 (PST) Message-ID: <36502C22.3CB016A5@erilab.com> Date: Mon, 16 Nov 1998 05:44:02 -0800 From: Rainer Enders Organization: Ericsson Cyberlab West X-Mailer: Mozilla 4.06 [en] (X11; U; SunOS 5.6 sun4m) MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: (no subject) Content-Type: multipart/mixed; boundary="------------F058C7C92BBDF91E9EE07F71" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------F058C7C92BBDF91E9EE07F71 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit auth 33a0b40c unsubscribe freebsd-net Rainer.Enders@erilab.com --------------F058C7C92BBDF91E9EE07F71 Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Rainer Enders Content-Disposition: attachment; filename="vcard.vcf" begin: vcard fn: Rainer Enders n: Enders;Rainer org: Ericsson Inc. adr: 1555 Adams Drive;;;Menlo Park;CA;94025;U.S.A. email;internet: Rainer.Enders@erilab.com title: Senior Systems Engineer tel;work: (650) 853-4303 tel;fax: (650) 853-4333 tel;home: (510) 409-1365 x-mozilla-cpt: ;0 x-mozilla-html: FALSE version: 2.1 end: vcard --------------F058C7C92BBDF91E9EE07F71-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 06:13:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14039 for freebsd-net-outgoing; Mon, 16 Nov 1998 06:13:28 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from arthur.axion.bt.co.uk (arthur.axion.bt.co.uk [132.146.5.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14022 for ; Mon, 16 Nov 1998 06:13:24 -0800 (PST) (envelope-from graeme.brown@bt-sys.bt.co.uk) Received: from rambo (actually rambo.futures.bt.co.uk) by arthur (local) with SMTP; Mon, 16 Nov 1998 14:12:07 +0000 Received: from maczebedee (actually macsmtp) by rambo with SMTP (PP); Mon, 16 Nov 1998 14:13:17 +0000 Message-ID: Date: 16 Nov 1998 14:10:09 +0100 From: Graeme Brown Subject: Is there a device which provides an IP-in-IP tunnel interface which is visible to routing ? To: "FreeBSD-Net (FreeBSD.Org) List" X-Mailer: Mail*Link SMTP for Quarterdeck Mail; Version 4.0.0 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear List Can anyone enlighten me as how I can install an IP-in-IP tunnel between two FreeBSD boxes such that the tunnel end points effectively look like network interfaces which routing protocols such as routed will see. I am aware of the tunnel driver giving tun0, tun1 interfaces to be used with PPP dialup lines. However can tun interfaces be used more generally for things other than PPP dialup lines. Is there any other means to configure an IP-in-IP tunnel interface ? TIA Graeme Brown BT Labs, UK email: graeme.brown@bt-sys.bt.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 08:04:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25301 for freebsd-net-outgoing; Mon, 16 Nov 1998 08:04:23 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25296 for ; Mon, 16 Nov 1998 08:04:21 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id IAA20137; Mon, 16 Nov 1998 08:04:47 -0800 (PST) Message-Id: <199811161604.IAA20137@root.com> To: Graeme Brown cc: "FreeBSD-Net (FreeBSD.Org) List" Subject: Re: Is there a device which provides an IP-in-IP tunnel interface which is visible to routing ? In-reply-to: Your message of "16 Nov 1998 14:10:09 +0100." From: David Greenman Reply-To: dg@root.com Date: Mon, 16 Nov 1998 08:04:47 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Can anyone enlighten me as how I can install an IP-in-IP tunnel >between two FreeBSD boxes such that the tunnel end points >effectively look like network interfaces which routing protocols >such as routed will see. I am aware of the tunnel driver giving tun0, tun1 >interfaces to be used with PPP dialup lines. However can >tun interfaces be used more generally for things other than PPP >dialup lines. > >Is there any other means to configure an IP-in-IP tunnel interface ? nos-tun(8) ? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 10:48:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14771 for freebsd-net-outgoing; Mon, 16 Nov 1998 10:48:14 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14737 for ; Mon, 16 Nov 1998 10:48:09 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id UAA21802; Mon, 16 Nov 1998 20:47:27 +0200 (SAT) From: John Hay Message-Id: <199811161847.UAA21802@zibbi.mikom.csir.co.za> Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) In-Reply-To: from Jeroen Ruigrok/Asmodai at "Nov 16, 98 12:00:32 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Mon, 16 Nov 1998 20:47:27 +0200 (SAT) Cc: jhay@mikom.csir.co.za, freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 > >> > >> which fraemetypes do we support for IPX traffic? If we only support Eth_II > >> at > >> this point then we need to integrate 802.2/3 too. > >> > >> But I can remember a previous post about these frametypes. Anyone care to > >> refresh my mind? > > > > Well at the moment FreeBSD only supports Ethernet_II. I do have patches > > for 802.3 support, but that is using a single sysctl to switch between > > E_II and 802.3 for the whole machine (all its interfaces). Support for > > the different frames isn't too difficult. It is the mechanism to make > > different interfaces use different frames in a nice way that I'm stuck > > with. Ie. have ed0 use 802.3 and ed1 use E_II and ed3 use 802.2 or > > even run two or more frames on the same interface. > > Care to provide me with the patches? =) Ok, I add it at the end. > Well there has to be a nice idea how to solve it. Most likely as an extension > to rc.conf to the interfaces. Patches welcome. :-) It's not just rc.conf, but also how to send it down into the kernel and where to store it in there because preferably you should be able to configure more than one frame per interface so that you can use a FreeBSD machine to do frame translation. John -- John Hay -- John.Hay@mikom.csir.co.za --- if_ethersubr.c.v2.2.org Wed Jul 2 07:56:33 1997 +++ if_ethersubr.c Sun Jul 27 10:18:58 1997 @@ -101,6 +101,11 @@ extern u_char aarp_org_code[ 3 ]; #endif NETATALK +SYSCTL_NODE(_net_link_ether, PF_IPX, ipx, CTLFLAG_RW, 0, ""); +static int ipx8023; /* Should we do Ethernet_II framing for IPX? */ +SYSCTL_INT(_net_link_ether_ipx, OID_AUTO, framing8023, CTLFLAG_RW, + &ipx8023, 0, ""); + u_char etherbroadcastaddr[6] = { 0xff, 0xff, 0xff, 0xff, 0xff, 0xff }; #define senderr(e) { error = (e); goto bad;} @@ -177,7 +182,10 @@ { struct ifaddr *ia; - type = htons(ETHERTYPE_IPX); + if (ipx8023) + type = htons(m->m_pkthdr.len); + else + type = htons(ETHERTYPE_IPX); bcopy((caddr_t)&(((struct sockaddr_ipx *)dst)->sipx_addr.x_host), (caddr_t)edst, sizeof (edst)); for (ia = ifp->if_addrlist; ia != NULL; ia = ia->ifa_next) @@ -467,8 +475,13 @@ #endif #ifdef IPX case ETHERTYPE_IPX: - schednetisr(NETISR_IPX); - inq = &ipxintrq; + if (ipx8023 == 0) { + schednetisr(NETISR_IPX); + inq = &ipxintrq; + } else { + m_freem(m); + return; + } break; #endif #ifdef NS @@ -489,6 +502,18 @@ return; #endif NETATALK default: +#ifdef IPX + { + struct ipx *ipxp = mtod(m, struct ipx *); + + if (ipx8023 && (ipxp->ipx_sum == 0xffff) && + (ntohs(ipxp->ipx_len) <= m->m_pkthdr.len)) { + schednetisr(NETISR_IPX); + inq = &ipxintrq; + break; + } + } +#endif #ifdef NS checksum = mtod(m, ushort *); /* Novell 802.3 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 11:05:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19739 for freebsd-net-outgoing; Mon, 16 Nov 1998 11:05:02 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19707 for ; Mon, 16 Nov 1998 11:04:53 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id OAA12159; Mon, 16 Nov 1998 14:03:42 -0500 (EST) Date: Mon, 16 Nov 1998 14:03:41 -0500 (EST) From: "Matthew N. Dodd" To: Jeroen Ruigrok/Asmodai cc: John Hay , freebsd-net@FreeBSD.ORG Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) 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 Mon, 16 Nov 1998, Jeroen Ruigrok/Asmodai wrote: > Well there has to be a nice idea how to solve it. Most likely as an > extension to rc.conf to the interfaces. How about something like this: ed0: flags=8843 mtu 1500 frame 0: Ethernet_II inet 10.0.1.60 netmask 0xffffff00 broadcast 10.0.1.255 ipx d3343.e8c4a06f frame 1: Ethernet_802.2 inet 10.5.1.20 netmask 0xffffff00 broadcast 10.5.1.255 ipx dead3.beef0000 ether 00:00:e8:c4:a0:6f ifconfig ed0 frame 2 ethernet_802.3 By default, the first frame type allocated would be Ethernet_II (no changes would be required for existing systems; ifconfig ed0 inet ... would work as normal.) -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 11:45:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28403 for freebsd-net-outgoing; Mon, 16 Nov 1998 11:45:29 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28331 for ; Mon, 16 Nov 1998 11:44:21 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.8]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA3206; Mon, 16 Nov 1998 20:43:53 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3650214B.19CE4C2A@netcon.com> Date: Mon, 16 Nov 1998 20:48:18 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Tony Ardolino Subject: Re: [Fwd: Netware client for FreeBSD] Cc: FreeBSD Net Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 16-Nov-98 Tony Ardolino wrote: > Hello, G'day > Ok! OK! My name is Tony Ardolino and I own NetCon along Frank Whitsell, we > have > been considering release NetCon to the FreeBSD community for a long time. Can > someone referrer me to a license that would allow the following; Let's see... > 1.) Free distribution for non-commerical use only. Elimates GPL and BSD style licenses... MPL a candidate? > 2.) A enhancements must be returned to FreeBSD. Tough one. > 3.) Commerical use or Resale requires a license from NetCon Corp. Ehm, MPL ? > 4.) NetCon Corp. will always own NetCon Software and all clanges. Elimanates GPL/BSD again... MPL mayhaps? > 5.) Cannot be ported to any other platform Like SCO, or Sun. > I also need a committment from a group of people to keep NetCon updated with > the > changes in NetWare and Freebsd (About a month a year). We will train and > support > all who are intreasted. > Get me this and you will get NetWare for FreeBSD. Care to elaborate on the update part ? --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 16 15:40:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05976 for freebsd-net-outgoing; Mon, 16 Nov 1998 15:40:20 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from lodgenet.com (cline.lodgenet.com [204.124.122.251]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05971 for ; Mon, 16 Nov 1998 15:40:17 -0800 (PST) (envelope-from lmckenna@lodgenet.com) Received: from chaplin.lodgenet.com (chaplin.lodgenet.com [10.0.104.215]) by lodgenet.com (8.7.5/8.7.3) with SMTP id RAA31257 for ; Mon, 16 Nov 1998 17:19:09 -0600 Received: by chaplin.lodgenet.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52) id <01BE1185.96F65080@chaplin.lodgenet.com>; Mon, 16 Nov 1998 17:21:47 -0600 Message-ID: From: "McKenna, Lee" To: "'John Hay'" , "'asmodai@wxs.nl'" Cc: "'freebsd-net@FreeBSD.ORG'" Subject: RE: Frametypes (was: Re: Netware client for FreeBSD) Date: Mon, 16 Nov 1998 17:21:46 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52 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 You know...it may be easier just to add support for the additional frame type to your Novell server :) -- Novell supports multiple frame types bound to the same adapter for running IPX...beware that this doubles the SAP/RIP traffic on your net since it does SAPs/RIPs on each frame type...although I recall you can filter much of the unwanted broadcasts starting with Novell 4.x?? --Lee -----Original Message----- From: John Hay [mailto:jhay@mikom.csir.co.za] Sent: Monday, November 16, 1998 12:47 PM To: asmodai@wxs.nl Cc: jhay@mikom.csir.co.za; freebsd-net@FreeBSD.ORG Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) > >> > >> which fraemetypes do we support for IPX traffic? If we only support Eth_II > >> at > >> this point then we need to integrate 802.2/3 too. > >> > >> But I can remember a previous post about these frametypes. Anyone care to > >> refresh my mind? > > > > Well at the moment FreeBSD only supports Ethernet_II. I do have patches > > for 802.3 support, but that is using a single sysctl to switch between > > E_II and 802.3 for the whole machine (all its interfaces). Support for > > the different frames isn't too difficult. It is the mechanism to make > > different interfaces use different frames in a nice way that I'm stuck > > with. Ie. have ed0 use 802.3 and ed1 use E_II and ed3 use 802.2 or > > even run two or more frames on the same interface. > > Care to provide me with the patches? =) Ok, I add it at the end. > Well there has to be a nice idea how to solve it. Most likely as an extension > to rc.conf to the interfaces. Patches welcome. :-) It's not just rc.conf, but also how to send it down into the kernel and where to store it in there because preferably you should be able to configure more than one frame per interface so that you can use a FreeBSD machine to do frame translation. John -- John Hay -- John.Hay@mikom.csir.co.za --- if_ethersubr.c.v2.2.org Wed Jul 2 07:56:33 1997 +++ if_ethersubr.c Sun Jul 27 10:18:58 1997 @@ -101,6 +101,11 @@ extern u_char aarp_org_code[ 3 ]; #endif NETATALK +SYSCTL_NODE(_net_link_ether, PF_IPX, ipx, CTLFLAG_RW, 0, ""); +static int ipx8023; /* Should we do Ethernet_II framing for IPX? */ +SYSCTL_INT(_net_link_ether_ipx, OID_AUTO, framing8023, CTLFLAG_RW, + &ipx8023, 0, ""); + u_char etherbroadcastaddr[6] = { 0xff, 0xff, 0xff, 0xff, 0xff, 0xff }; #define senderr(e) { error = (e); goto bad;} @@ -177,7 +182,10 @@ { struct ifaddr *ia; - type = htons(ETHERTYPE_IPX); + if (ipx8023) + type = htons(m->m_pkthdr.len); + else + type = htons(ETHERTYPE_IPX); bcopy((caddr_t)&(((struct sockaddr_ipx *)dst)->sipx_addr.x_host), (caddr_t)edst, sizeof (edst)); for (ia = ifp->if_addrlist; ia != NULL; ia = ia->ifa_next) @@ -467,8 +475,13 @@ #endif #ifdef IPX case ETHERTYPE_IPX: - schednetisr(NETISR_IPX); - inq = &ipxintrq; + if (ipx8023 == 0) { + schednetisr(NETISR_IPX); + inq = &ipxintrq; + } else { + m_freem(m); + return; + } break; #endif #ifdef NS @@ -489,6 +502,18 @@ return; #endif NETATALK default: +#ifdef IPX + { + struct ipx *ipxp = mtod(m, struct ipx *); + + if (ipx8023 && (ipxp->ipx_sum == 0xffff) && + (ntohs(ipxp->ipx_len) <= m->m_pkthdr.len)) { + schednetisr(NETISR_IPX); + inq = &ipxintrq; + break; + } + } +#endif #ifdef NS checksum = mtod(m, ushort *); /* Novell 802.3 */ 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 Nov 16 20:55:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13943 for freebsd-net-outgoing; Mon, 16 Nov 1998 20:55:27 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13937 for ; Mon, 16 Nov 1998 20:55:20 -0800 (PST) (envelope-from bp@butya.kz) Received: from localhost (bp@localhost) by lion.butya.kz (8.8.8/8.8.8) with SMTP id IAA06284; Tue, 17 Nov 1998 08:14:11 +0600 (ALMT) Date: Tue, 17 Nov 1998 08:14:11 +0600 (ALMT) From: Boris Popov To: "McKenna, Lee" cc: "'freebsd-net@FreeBSD.ORG'" Subject: RE: Frametypes (was: Re: Netware client for FreeBSD) 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 Mon, 16 Nov 1998, McKenna, Lee wrote: > You know...it may be easier just to add support for the additional frame > type to your Novell server :) -- Novell supports multiple frame types > bound to the same adapter for running IPX...beware that this doubles the > SAP/RIP traffic on your net since it does SAPs/RIPs on each frame > type...although I recall you can filter much of the unwanted broadcasts > starting with Novell 4.x?? At this moment this a good solution for many cases. But there always "good old 386" with ipx.com file tuned only for 802.3 frame. In my opinion, it is better to keep separate network configuration for each frame. BTW, netcon supports all of the frames, but as I understand it replace XNS protocol stack. -- Boris Popov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 01:01:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12031 for freebsd-net-outgoing; Tue, 17 Nov 1998 01:01:25 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from pike.cdrom.com (pike.cdrom.com [204.216.28.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12026; Tue, 17 Nov 1998 01:01:24 -0800 (PST) (envelope-from murray@pike.cdrom.com) Received: from localhost (murray@localhost) by pike.cdrom.com (8.9.1a/8.9.1) with SMTP id BAA03364; Tue, 17 Nov 1998 01:03:19 -0800 (PST) Date: Tue, 17 Nov 1998 01:03:19 -0800 (PST) From: Murray Stokely To: questions@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Wide DHCP client and @home cable modem service 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'm unable to use FreeBSD to connect to the Internet via the @home cable service. I've configured my hostname to be the "identifier" that Windows 98 uses to connect just fine (same system, dual boot). In FreeBSD I type /usr/local/sbin/dhcpc -r fxp0 /usr/local/sbin/dhcpm fxp0 ~/logfile and basically it just keeps sending the DHCPDISCOVER message over and over again without ever getting a DHCPOFFER message. This is what the logfile created by dhcpm looks like. I notice that nowhere is my hostname (the secret 'c#######-a' identifier) mentioned. Am I missing some configuration step? "Nov 15 16:06:31.593862" DHCPDISCOVER src_haddr: 00a0c957b4a3, dst_haddr: ffffffffffff src_IP: 0.0.0.0, dst_IP: 255.255.255.255 requested_IP: None requested/assigned lease: 3600 dhcp_t1: 0 dhcp_t2: 0 op: 1, xid: 295d8164, secs: 61, BRDCST flag: 0 ciaddr: 0.0.0.0, yiaddr: 0.0.0.0, siaddr: 0.0.0.0, giaddr: 0.0.0.0 broadcast: None subnetmask: None server_id: None default router: None Thanks! - Murray To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 01:53:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16843 for freebsd-net-outgoing; Tue, 17 Nov 1998 01:53:19 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alcatel.fr (ns.transport.gecalsthom.com [194.133.58.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16822; Tue, 17 Nov 1998 01:53:13 -0800 (PST) (envelope-from Thierry.Herbelot@alcatel.fr) From: Thierry.Herbelot@alcatel.fr Received: from alcatel.fr (gatekeeper-ssn.alcatel.fr [155.132.180.244]) by mailgate.alcatel.fr (ALCANET/SMTP) with ESMTP id LAA21102; Tue, 17 Nov 1998 11:50:32 +0100 Received: from lune.telspace.alcatel.fr (lune.telspace.alcatel.fr [155.132.144.65]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id KAA29318; Tue, 17 Nov 1998 10:49:38 +0100 (MET) Received: from telss1 (telss1.telspace.alcatel.fr [155.132.51.4]) by lune.telspace.alcatel.fr (8.9.1a/8.9.1) with SMTP id KAA03604; Tue, 17 Nov 1998 10:32:27 +0100 (MET) Received: from telspace.alcatel.fr by telss1 (4.1/SMI-4.1) id AA21710; Tue, 17 Nov 98 10:35:43 +0100 Received: from localhost by telspace.alcatel.fr with SMTP (1.40.112.12/16.2) id AA271874913; Tue, 17 Nov 1998 10:28:33 +0100 X-Openmail-Hops: 1 Date: Tue, 17 Nov 98 10:26:44 +0100 Message-Id: In-Reply-To: Subject: Wide DHCP client and @home cable modem service Mime-Version: 1.0 To: murray@pike.cdrom.com Cc: freebsd-net@FreeBSD.ORG, questions@FreeBSD.ORG Content-Type: text/plain; charset=US-ASCII; name="Wide" Content-Disposition: inline; filename="Wide" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Just checking : you have configured bpf filters in your kernel and MAKEDEV'd them in /dev - haven't you ? (I've just reconfigured my home box with a similar setting and got bitten by the missing bpf's) TfH > I'm unable to use FreeBSD to connect to the Internet via the > @home cable service. I've configured my hostname to be the > "identifier" that Windows 98 uses to connect just fine (same system, > dual boot). In FreeBSD I type > > /usr/local/sbin/dhcpc -r fxp0 > /usr/local/sbin/dhcpm fxp0 ~/logfile > > and basically it just keeps sending the DHCPDISCOVER message over and > over again without ever getting a DHCPOFFER message. This is what the > logfile created by dhcpm looks like. I notice that nowhere is my > hostname (the secret 'c#######-a' identifier) mentioned. Am I missing > some configuration step? > > "Nov 15 16:06:31.593862" DHCPDISCOVER > src_haddr: 00a0c957b4a3, dst_haddr: ffffffffffff > src_IP: 0.0.0.0, dst_IP: 255.255.255.255 > requested_IP: None > requested/assigned lease: 3600 > dhcp_t1: 0 dhcp_t2: 0 > op: 1, xid: 295d8164, secs: 61, BRDCST flag: 0 > ciaddr: 0.0.0.0, yiaddr: 0.0.0.0, siaddr: 0.0.0.0, giaddr: > 0.0.0.0 > broadcast: None subnetmask: None > server_id: None > default router: None > > Thanks! > > - Murray > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" 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 Tue Nov 17 05:31:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11391 for freebsd-net-outgoing; Tue, 17 Nov 1998 05:31:01 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11386 for ; Tue, 17 Nov 1998 05:30:59 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.47]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA48B4; Tue, 17 Nov 1998 14:30:32 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 17 Nov 1998 14:35:05 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "McKenna, Lee" Subject: RE: Frametypes (was: Re: Netware client for FreeBSD) Cc: "freebsd-net@FreeBSD.ORG" , "freebsd-net@FreeBSD.ORG" , John Hay Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 16-Nov-98 McKenna, Lee wrote: > You know...it may be easier just to add support for the additional frame > type to your Novell server :) -- Novell supports multiple frame types > bound to the same adapter for running IPX...beware that this doubles the > SAP/RIP traffic on your net since it does SAPs/RIPs on each frame > type...although I recall you can filter much of the unwanted broadcasts > starting with Novell 4.x?? Mayhaps... But I was thinking of allowing clients to use the Novell services on a UNIX box... That might require additional frametypes on the box. And sometimes RIP/SAP filtering is NOT what we want... ;) (Long story involving IPX/SPX, TCP/IP and NetWare/IP) --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 05:37:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA12257 for freebsd-net-outgoing; Tue, 17 Nov 1998 05:37:53 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12252 for ; Tue, 17 Nov 1998 05:37:51 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.47]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA4EA6; Tue, 17 Nov 1998 14:37:23 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 17 Nov 1998 14:41:55 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "Matthew N. Dodd" Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) Cc: freebsd-net@FreeBSD.ORG, John Hay Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 16-Nov-98 Matthew N. Dodd wrote: > On Mon, 16 Nov 1998, Jeroen Ruigrok/Asmodai wrote: >> Well there has to be a nice idea how to solve it. Most likely as an >> extension to rc.conf to the interfaces. > > How about something like this: > > ed0: flags=8843 mtu 1500 > frame 0: Ethernet_II > inet 10.0.1.60 netmask 0xffffff00 broadcast 10.0.1.255 > ipx d3343.e8c4a06f > frame 1: Ethernet_802.2 > inet 10.5.1.20 netmask 0xffffff00 broadcast 10.5.1.255 > ipx dead3.beef0000 > ether 00:00:e8:c4:a0:6f > > ifconfig ed0 frame 2 ethernet_802.3 > > By default, the first frame type allocated would be Ethernet_II (no > changes would be required for existing systems; ifconfig ed0 inet ... > would work as normal.) In my opinion that would be great, and simple to extend to the ifconfig source afaik. Simple, elegant and workable ;) --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 07:59:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28039 for freebsd-net-outgoing; Tue, 17 Nov 1998 07:59:30 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from isi.co.jp (mail.isi.co.jp [202.214.62.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28021; Tue, 17 Nov 1998 07:59:26 -0800 (PST) (envelope-from john@isi.co.jp) Received: by ns.isi.co.jp id <21890>; Wed, 18 Nov 1998 00:58:06 +0900 Date: Wed, 18 Nov 1998 00:51:36 +0900 From: john cooper To: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: BIND/Mail/MX Question.. Cc: john@isi.co.jp, tfujii@isi.co.jp Message-Id: <98Nov18.005806jst.21890@ns.isi.co.jp> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been trying to get a firewall cobbled together with 2.2.7. The problem I'm now having appears to center around maintaining internal and external DNS databases on the firewall [this is the way our current black-box firewall does it, I don't know if there is an easier way..] For example, outside the firewall there are 202.214.* addresses and inside 192.168.* addresses. Aside from the issue of exposing internal machine info externally, at least at this stage I could live with putting all info in one space. The trouble I'm having is that if I use: isi.co.jp. IN MX 50 ms.isi.co.jp. ; local mail host IN MX 100 ws.isi.co.jp. where ms.isi.co.jp's address is internal [192.168.*], mail coming from outside our domain gets deflected to ws.isi.co.jp. sitting on the external side of the FW [202.214.*]. As I understand, the MX record is required to relay mail from the FW/DNS server to the internal mail server. However if this local MX info gets exposed externally, the above problem occurs. This seems to me to be a fairly normal thing to do. Would someone kindly clue me in on the standard way this is solved? Thanks, -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 08:42:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03357 for freebsd-net-outgoing; Tue, 17 Nov 1998 08:42:23 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03344 for ; Tue, 17 Nov 1998 08:42:19 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA03445; Tue, 17 Nov 1998 11:41:53 -0500 (EST) Date: Tue, 17 Nov 1998 11:41:53 -0500 (EST) From: "Matthew N. Dodd" To: Jeroen Ruigrok/Asmodai cc: freebsd-net@FreeBSD.ORG, John Hay Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) 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 Tue, 17 Nov 1998, Jeroen Ruigrok/Asmodai wrote: > On 16-Nov-98 Matthew N. Dodd wrote: > > On Mon, 16 Nov 1998, Jeroen Ruigrok/Asmodai wrote: > >> Well there has to be a nice idea how to solve it. Most likely as an > >> extension to rc.conf to the interfaces. > > > > How about something like this: > > > > ed0: flags=8843 mtu 1500 > > frame 0: Ethernet_II > > inet 10.0.1.60 netmask 0xffffff00 broadcast 10.0.1.255 > > ipx d3343.e8c4a06f > > frame 1: Ethernet_802.2 > > inet 10.5.1.20 netmask 0xffffff00 broadcast 10.5.1.255 > > ipx dead3.beef0000 > > ether 00:00:e8:c4:a0:6f > > > > ifconfig ed0 frame 2 ethernet_802.3 > > > > By default, the first frame type allocated would be Ethernet_II (no > > changes would be required for existing systems; ifconfig ed0 inet ... > > would work as normal.) > > In my opinion that would be great, and simple to extend to the > ifconfig source afaik. > > Simple, elegant and workable ;) Very 'Netware' ish. :) The problem is not extending ifconfig but creating a new structure to hang off of the struct ifnet that would contain the various ifaddr structs. struct ifframe { int frame; /* frame type */ struct ifaddr *if_addrlist; /* address of interface */ struct ifnet *ifa_ifp; /* back-pointer to interface */ struct ifframe *iff_next; /* next frame type */ }; Of course this means that a great deal of code has to be changed; code that expects fp->if_addrlist to be the list of addresses, and won't know how to deal with parsing addresses out of the above struct. In addition, how would routing b/t different frame types on a single board work? In my example I showed an IP address on an Ethernet_II frame and an Ethernet_802.2 frame; would routing work as normal? I'm guessing it would jsut dow the right thing but I'm not positive (not having looked at the code in question yet.) Anyhow, someone with more time should look at this as I've got to make progress on other things before I can divert my attention to this. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 08:44:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03707 for freebsd-net-outgoing; Tue, 17 Nov 1998 08:44:32 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ns.wan (trltech.demon.co.uk [194.222.7.191]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03678; Tue, 17 Nov 1998 08:44:24 -0800 (PST) (envelope-from richard@jezebel.demon.co.uk) Received: from jezebel.demon.co.uk (rdls.dhcp.sw.wan [192.9.201.75]) by ns.wan (8.8.8/8.8.8) with ESMTP id QAA11087; Tue, 17 Nov 1998 16:40:48 GMT (envelope-from richard@jezebel.demon.co.uk) Message-ID: <3651A72B.D1F8E96D@jezebel.demon.co.uk> Date: Tue, 17 Nov 1998 16:41:15 +0000 From: Richard Smith Organization: http://www.trltech.co.uk X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: john cooper CC: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, tfujii@isi.co.jp Subject: Re: BIND/Mail/MX Question.. References: <98Nov18.005806jst.21890@ns.isi.co.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org john cooper wrote: > [snip] > > The trouble I'm having is that if I use: > > isi.co.jp. IN MX 50 ms.isi.co.jp. ; local mail host > IN MX 100 ws.isi.co.jp. > > where ms.isi.co.jp's address is internal [192.168.*], mail > coming from outside our domain gets deflected to ws.isi.co.jp. > sitting on the external side of the FW [202.214.*]. You shouldn't expose 192.168/16 outside of your intranet. > As I understand, the MX record is required to relay mail from > the FW/DNS server to the internal mail server. However if > this local MX info gets exposed externally, the above problem > occurs. FWIW, I run sendmail on the FW and use mailertable to route mail to the 'true' internal mail hub. If you only have one internal mail hub and you are using natd, you could use a -redirect_port to point to the internal mail hub. Either way, the external IP of the FW is exposed in the MX. > This seems to me to be a fairly normal thing to do. Would > someone kindly clue me in on the standard way this is solved? > > Thanks, > > -john > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message richard. _______________________________________________________________________ Richard Smith Assistant Chief Engineer TRL Technology Limited To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 09:48:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13709 for freebsd-net-outgoing; Tue, 17 Nov 1998 09:48:38 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13704 for ; Tue, 17 Nov 1998 09:48:36 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA26273; Tue, 17 Nov 1998 12:47:50 -0500 (EST) (envelope-from wollman) Date: Tue, 17 Nov 1998 12:47:50 -0500 (EST) From: Garrett Wollman Message-Id: <199811171747.MAA26273@khavrinen.lcs.mit.edu> To: "Matthew N. Dodd" Cc: Jeroen Ruigrok/Asmodai , freebsd-net@FreeBSD.ORG, John Hay Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) In-Reply-To: References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > struct ifframe { > int frame; /* frame type */ > struct ifaddr *if_addrlist; /* address of interface */ > struct ifnet *ifa_ifp; /* back-pointer to interface */ > struct ifframe *iff_next; /* next frame type */ > }; Given the limited utility, I would rather see this information simply stored as a part of the interface address struct for IPX. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 10:08:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16413 for freebsd-net-outgoing; Tue, 17 Nov 1998 10:08:00 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16391 for ; Tue, 17 Nov 1998 10:07:55 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id NAA05505; Tue, 17 Nov 1998 13:07:24 -0500 (EST) Date: Tue, 17 Nov 1998 13:07:23 -0500 (EST) From: "Matthew N. Dodd" To: Garrett Wollman cc: Jeroen Ruigrok/Asmodai , freebsd-net@FreeBSD.ORG, John Hay Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) In-Reply-To: <199811171747.MAA26273@khavrinen.lcs.mit.edu> 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, 17 Nov 1998, Garrett Wollman wrote: > < said: > > > struct ifframe { > > int frame; /* frame type */ > > struct ifaddr *if_addrlist; /* address of interface */ > > struct ifnet *ifa_ifp; /* back-pointer to interface */ > > struct ifframe *iff_next; /* next frame type */ > > }; > > Given the limited utility, I would rather see this information simply > stored as a part of the interface address struct for IPX. So running IP over 802.2 framing woudn't be supported? -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 10:14:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17672 for freebsd-net-outgoing; Tue, 17 Nov 1998 10:14:41 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17661 for ; Tue, 17 Nov 1998 10:14:38 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id NAA26414; Tue, 17 Nov 1998 13:13:27 -0500 (EST) (envelope-from wollman) Date: Tue, 17 Nov 1998 13:13:27 -0500 (EST) From: Garrett Wollman Message-Id: <199811171813.NAA26414@khavrinen.lcs.mit.edu> To: "Matthew N. Dodd" Cc: Garrett Wollman , Jeroen Ruigrok/Asmodai , freebsd-net@FreeBSD.ORG, John Hay Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) In-Reply-To: References: <199811171747.MAA26273@khavrinen.lcs.mit.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: >> Given the limited utility, I would rather see this information simply >> stored as a part of the interface address struct for IPX. > So running IP over 802.2 framing woudn't be supported? The standard way of running IP is not over 802.2 framing. (Remember we're talking Ethernet here; obviously, other technologies have different link layers.) (In point of fact, the right way to implement `IP over 802.2' would be to use the ARP protocol and save the frame type in each ARP entry.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 10:16:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17939 for freebsd-net-outgoing; Tue, 17 Nov 1998 10:16:20 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17928 for ; Tue, 17 Nov 1998 10:16:13 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.169]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA18B8; Tue, 17 Nov 1998 19:15:45 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811171747.MAA26273@khavrinen.lcs.mit.edu> Date: Tue, 17 Nov 1998 19:20:18 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Garrett Wollman Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) Cc: John Hay , freebsd-net@FreeBSD.ORG, "Matthew N. Dodd" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 17-Nov-98 Garrett Wollman wrote: > < said: > >> struct ifframe { >> int frame; /* frame type */ >> struct ifaddr *if_addrlist; /* address of interface */ >> struct ifnet *ifa_ifp; /* back-pointer to interface */ >> struct ifframe *iff_next; /* next frame type */ >> }; > > Given the limited utility, I would rather see this information simply > stored as a part of the interface address struct for IPX. I am bound to have missed a RFC, but here goes ;) It's a must to send/receive RFC 894 Eth encapsulation. It should be able to receive 802.2/3 encapsulation May send 802.2/3, yet default to RFC 894. So as far as I can see it really ought to be in the `if' sources. Except the two things we're bound to get is: put it in the struct of IPX and make IPX support later on tougher (integration with NDS et al) put it in the if stuff and be prone to break TCP/IP. What is wisdom? =) --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 10:18:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18380 for freebsd-net-outgoing; Tue, 17 Nov 1998 10:18:40 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18341 for ; Tue, 17 Nov 1998 10:18:27 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.169]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA5F95; Tue, 17 Nov 1998 19:17:58 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811171813.NAA26414@khavrinen.lcs.mit.edu> Date: Tue, 17 Nov 1998 19:22:32 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Garrett Wollman Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) Cc: John Hay , freebsd-net@FreeBSD.ORG, "Matthew N. Dodd" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 17-Nov-98 Garrett Wollman wrote: > < said: > >>> Given the limited utility, I would rather see this information simply >>> stored as a part of the interface address struct for IPX. > >> So running IP over 802.2 framing woudn't be supported? > > The standard way of running IP is not over 802.2 framing. (Remember > we're talking Ethernet here; obviously, other technologies have > different link layers.) (In point of fact, the right way to implement > `IP over 802.2' would be to use the ARP protocol and save the frame > type in each ARP entry.) Ehm, Ethernet is 802.2/3 (aka eth_snap, eth_llc and eth_mac), also Eth_II and the original ethernet afaik... Ethernet is not ONE standard... --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 10:20:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18904 for freebsd-net-outgoing; Tue, 17 Nov 1998 10:20:48 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18812 for ; Tue, 17 Nov 1998 10:20:40 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id NAA26469; Tue, 17 Nov 1998 13:20:11 -0500 (EST) (envelope-from wollman) Date: Tue, 17 Nov 1998 13:20:11 -0500 (EST) From: Garrett Wollman Message-Id: <199811171820.NAA26469@khavrinen.lcs.mit.edu> To: Jeroen Ruigrok/Asmodai Cc: freebsd-net@FreeBSD.ORG Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) In-Reply-To: References: <199811171813.NAA26414@khavrinen.lcs.mit.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Ehm, Ethernet is 802.2/3 (aka eth_snap, eth_llc and eth_mac), also Eth_II and > the original ethernet afaik... Ethernet is not ONE standard... Yes it is. ISO 8802-3 is a different standard. ISO 8802-2 is a layer which sits on top of ISO 8802-3. Novell found a way to break both. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 10:25:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19712 for freebsd-net-outgoing; Tue, 17 Nov 1998 10:25:11 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19697 for ; Tue, 17 Nov 1998 10:25:05 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.169]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1EB4; Tue, 17 Nov 1998 19:24:35 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811171820.NAA26469@khavrinen.lcs.mit.edu> Date: Tue, 17 Nov 1998 19:29:10 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Garrett Wollman Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) Cc: freebsd-net@FreeBSD.ORG Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 17-Nov-98 Garrett Wollman wrote: > < said: > >> Ehm, Ethernet is 802.2/3 (aka eth_snap, eth_llc and eth_mac), also Eth_II >> and >> the original ethernet afaik... Ethernet is not ONE standard... > > Yes it is. ISO 8802-3 is a different standard. ISO 8802-2 is a layer > which sits on top of ISO 8802-3. Novell found a way to break both. Fast answer btw ;) Yeah, but with regard to the prospects of heterogeneous networks we cannot stick our head in the sand and plainly ignore other frametypes, at least in my opinion... Care to elaborate on Novell's breaking of the IEEE specs? AFAIK, they just used the standard (IEEE's). Surely others disagree... But the eliteness of such stances was the thing that got other projects/stuff into problems in the first place. I think there must be a way to work it all out with the least fuss and yet with great extensibility, hence I value yer advice as much as the others... geez, I love the UNIX community ;) --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 11:09:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25463 for freebsd-net-outgoing; Tue, 17 Nov 1998 11:09:29 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from pike.cdrom.com (pike.cdrom.com [204.216.28.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25446; Tue, 17 Nov 1998 11:09:27 -0800 (PST) (envelope-from murray@pike.cdrom.com) Received: from localhost (murray@localhost) by pike.cdrom.com (8.9.1a/8.9.1) with SMTP id LAA10997; Tue, 17 Nov 1998 11:11:20 -0800 (PST) Date: Tue, 17 Nov 1998 11:11:20 -0800 (PST) From: Murray Stokely To: Thierry.Herbelot@alcatel.fr cc: freebsd-net@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Wide DHCP client and @home cable modem service 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 Yes I've got all the bpf stuff setup correctly. It gives good error messages when you forget to do that. Any other suggestions? On Tue, 17 Nov 1998 Thierry.Herbelot@alcatel.fr wrote: % Hello, % % Just checking : you have configured bpf filters in your kernel and % MAKEDEV'd them in /dev - haven't you ? (I've just reconfigured my home % box with a similar setting and got bitten by the missing bpf's) % % TfH % % > I'm unable to use FreeBSD to connect to the Internet via the % > @home cable service. I've configured my hostname to be the % > "identifier" that Windows 98 uses to connect just fine (same system, % > dual boot). In FreeBSD I type % > % > /usr/local/sbin/dhcpc -r fxp0 % > /usr/local/sbin/dhcpm fxp0 ~/logfile % > % > and basically it just keeps sending the DHCPDISCOVER message over and % > over again without ever getting a DHCPOFFER message. This is what the % > logfile created by dhcpm looks like. I notice that nowhere is my % > hostname (the secret 'c#######-a' identifier) mentioned. Am I missing % > some configuration step? % > % > "Nov 15 16:06:31.593862" DHCPDISCOVER % > src_haddr: 00a0c957b4a3, dst_haddr: ffffffffffff % > src_IP: 0.0.0.0, dst_IP: 255.255.255.255 % > requested_IP: None % > requested/assigned lease: 3600 % > dhcp_t1: 0 dhcp_t2: 0 % > op: 1, xid: 295d8164, secs: 61, BRDCST flag: 0 % > ciaddr: 0.0.0.0, yiaddr: 0.0.0.0, siaddr: 0.0.0.0, giaddr: % > 0.0.0.0 % > broadcast: None subnetmask: None % > server_id: None % > default router: None % > % > Thanks! % > % > - Murray % > % > % > To Unsubscribe: send mail to majordomo@FreeBSD.org % > with "unsubscribe freebsd-questions" in the body of the message % - Murray To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 12:35:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08427 for freebsd-net-outgoing; Tue, 17 Nov 1998 12:35:09 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from messenger.cacheflow.com (messenger.cacheflow.com [208.2.250.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08422 for ; Tue, 17 Nov 1998 12:35:07 -0800 (PST) (envelope-from krowett@verio.com) Received: from rowettpc (208.2.250.25) by messenger.cacheflow.com (Worldmail 1.3.167); 17 Nov 1998 12:32:11 -0800 Message-Id: <4.1.19981117123137.00a24400@pop.ncal.verio.com> X-Sender: krowett@pop.ncal.verio.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 17 Nov 1998 12:34:46 -0800 To: Jeroen Ruigrok/Asmodai , Garrett Wollman From: "Kevin J. Rowett" Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) Cc: freebsd-net@FreeBSD.ORG In-Reply-To: References: <199811171820.NAA26469@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Care to elaborate on Novell's breaking of the IEEE specs? AFAIK, they just used >the standard (IEEE's). > In one "mode" NetWare sets the type field (Eth II lingo), or the length field (802.3 lingo) to a value of zero. The type/length field has been the major difference between Ethernet II and 802.3. What it's used for, how the values are chosen, and what those values truely mean is never clear. However, almost everyone agrees that a type/length field = broken Netware packet to follow. KR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 13:00:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12667 for freebsd-net-outgoing; Tue, 17 Nov 1998 13:00:36 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12658 for ; Tue, 17 Nov 1998 13:00:26 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id SAA06285; Tue, 17 Nov 1998 18:14:51 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199811172014.SAA06285@roma.coe.ufrj.br> Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) In-Reply-To: from Jeroen Ruigrok/Asmodai at "Nov 17, 98 07:29:10 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Tue, 17 Nov 1998 18:14:51 -0200 (EDT) Cc: wollman@khavrinen.lcs.mit.edu, freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (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 #define quoting(Jeroen Ruigrok/Asmodai) // Care to elaborate on Novell's breaking of the IEEE specs? AFAIK, they just used // the standard (IEEE's). 802.3 was never meant to be used directly by network level protocol. It was designed to be used together with 802.2. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 13:00:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12702 for freebsd-net-outgoing; Tue, 17 Nov 1998 13:00:45 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12677 for ; Tue, 17 Nov 1998 13:00:37 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id SAA06248; Tue, 17 Nov 1998 18:12:28 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199811172012.SAA06248@roma.coe.ufrj.br> Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) In-Reply-To: from "Matthew N. Dodd" at "Nov 17, 98 11:41:53 am" To: winter@jurai.net (Matthew N. Dodd) Date: Tue, 17 Nov 1998 18:12:28 -0200 (EDT) Cc: asmodai@wxs.nl, freebsd-net@FreeBSD.ORG, jhay@mikom.csir.co.za X-Mailer: ELM [version 2.4ME+ PL40 (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 #define quoting(Matthew N. Dodd) // On Tue, 17 Nov 1998, Jeroen Ruigrok/Asmodai wrote: // > On 16-Nov-98 Matthew N. Dodd wrote: // > > On Mon, 16 Nov 1998, Jeroen Ruigrok/Asmodai wrote: // > >> Well there has to be a nice idea how to solve it. Most likely as an // > >> extension to rc.conf to the interfaces. // > > // > > How about something like this: // > > // > > ed0: flags=8843 mtu 1500 // > > frame 0: Ethernet_II // > > inet 10.0.1.60 netmask 0xffffff00 broadcast 10.0.1.255 // > > ipx d3343.e8c4a06f // > > frame 1: Ethernet_802.2 // > > inet 10.5.1.20 netmask 0xffffff00 broadcast 10.5.1.255 // > > ipx dead3.beef0000 // > > ether 00:00:e8:c4:a0:6f // > > // > > ifconfig ed0 frame 2 ethernet_802.3 // > > // > > By default, the first frame type allocated would be Ethernet_II (no // > > changes would be required for existing systems; ifconfig ed0 inet ... // > > would work as normal.) // > // > In my opinion that would be great, and simple to extend to the // > ifconfig source afaik. // > // > Simple, elegant and workable ;) // // Very 'Netware' ish. :) // // The problem is not extending ifconfig but creating a new structure to hang // off of the struct ifnet that would contain the various ifaddr structs. // // struct ifframe { // int frame; /* frame type */ // struct ifaddr *if_addrlist; /* address of interface */ // struct ifnet *ifa_ifp; /* back-pointer to interface */ // struct ifframe *iff_next; /* next frame type */ // }; I think that an interface for each frame is an easier way to go. ed0: -> Standard Ethernet_II, historical. llc0: -> LLC (802.2) over any interface (how to attach ?) snap: -> SNAP over LLC (Could there be a fast path, obviously) ipx0: -> Novell's 802.3, as it should never be used by anybody else. This would eliminate the problems with routing between frames, if_addrlist parsing and arp table lookup. A similar approach could then be used for other interfaces supporting llc and snap, like Token Ring, FDDI, or any other 802 local net. I'm doing something like that in Slowlaris as part of my thesis. The interesting thing is that I may now run IP over Ethernet SNAP without touching the IP code (for which I don't have the sources, anyway). Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 14:38:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00386 for freebsd-net-outgoing; Tue, 17 Nov 1998 14:38:22 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mailmtx.acnet.net (mailmtx.acnet.net [170.76.16.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00375 for ; Tue, 17 Nov 1998 14:38:20 -0800 (PST) (envelope-from denp@acnet.net) Received: from denpmfe.acnet.net ([170.76.16.29]) by mailmtx.acnet.net (Post.Office MTA v3.5.3 release 223 ID# 0-52476U50000L50000S0V35) with SMTP id net for ; Tue, 17 Nov 1998 16:37:45 -0600 X-Sender: denp@mailmtx.acnet.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 17 Nov 1998 16:38:05 -0600 To: freebsd-net@FreeBSD.ORG From: Ivan Villalobos Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <19981117223745.AAA1211@mailmtx.acnet.net@denpmfe.acnet.net> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi guys... I have something that keeps diving me nuts and I still can not find an answer... I have a FreeBSD R30.0 inside a network protected by a firewall. Such firewall is configured to expire TCP sessions after 15 min. of inactivity. When I login to the FreeBSD box, I frequently forget the session and -obviously- the firewall expires (terminate) my session. Neither my Win95 telnet program or the telnetd realize this really soon enough so I have to manually kill the telnetd session. I need to know how to tweak this parameters. As I understand it, I have three options: 1.- Tweak the firewall's TCP timeout. 2.- Tweak FreeBSD's tcp.keepalives. 3.- Tweak telnetd's keepalives. I do not want to go for options 1 & 2 since it would affect not only my session but all my traffic. So I figured that the right thing to do is just to tweak telnetd's keepalive. Now, does anybody know what the "1" means in this line?, taken from /usr/src/libexec/telnetd/telnetd.c int keepalive = 1; I also figured this would be the line to mess with, right? Could anyone, please please please shed some light here? Could you please answer (if any) to denp@acnet.net Best Regards... Ivan Villalobos Ashton Communications Corp. NOC McAllen, TX. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 20:15:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14117 for freebsd-net-outgoing; Tue, 17 Nov 1998 20:15:14 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mail.pinboard.com (mail.pinboard.com [194.209.195.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14111 for ; Tue, 17 Nov 1998 20:15:12 -0800 (PST) (envelope-from Kurt@pinboard.com) Received: (from uucp@localhost) by mail.pinboard.com (8.9.1/8.9.1/19980920-01/KK) with UUCP id FAA01284; Wed, 18 Nov 1998 05:14:33 +0100 (CET) (envelope-from: Kurt@pinboard.com) Received: from beaver.pbdhome.pinboard.com ([192.168.0.7]) by squirrel.pbdhome.pinboard.com (8.9.1/8.9.1-19980817-01/KK) with SMTP id WAA10641; Tue, 17 Nov 1998 22:26:07 +0100 (CET) (envelope-from: Kurt@pinboard.com) Message-Id: <3.0.5.16.19981117215601.483f79b8@pop.pbdhome.pinboard.com> Organization: PINBOARD - http://www.pinboard.com/ X-Sender: kurt@pop.pbdhome.pinboard.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (16) Date: Tue, 17 Nov 1998 21:56:01 To: john cooper From: Kurt Keller Subject: Re: BIND/Mail/MX Question.. Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <98Nov18.005806jst.21890@ns.isi.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id UAA14112 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You should not expose the 192.168.* address to the outside. Hosts on the internet can not connect to it and might instead even try to connect to the internal 192.168.* hosts in their own intranet. The solution is to mention ws.isi.co.jp as the official mailhost and use sendmail rules to redirect mail for *.isi.co.jp to ms.isi.co.jp. ms.isi.co.jp itself needs some sendmail rule adjustments as well. If you are using BIND 8, it is possible to serve both, the internet and intranet from the same DNS server, provided you use a subdomain for the intranet. With BIND 8 it is easily possible to make info about certain domains only accessible to a certain IP range. Cheers, Kurt >For example, outside the firewall there are 202.214.* addresses >and inside 192.168.* addresses. Aside from the issue of exposing >... >The trouble I'm having is that if I use: > >isi.co.jp. IN MX 50 ms.isi.co.jp. ; local mail host > IN MX 100 ws.isi.co.jp. > >where ms.isi.co.jp's address is internal [192.168.*], mail >coming from outside our domain gets deflected to ws.isi.co.jp. >sitting on the external side of the FW [202.214.*]. > >As I understand, the MX record is required to relay mail from >the FW/DNS server to the internal mail server. However if >... >This seems to me to be a fairly normal thing to do. Would >someone kindly clue me in on the standard way this is solved? -- -------------------------------------------------------------------- ¦ Kurt@pinboard.com http://www.pinboard.com/ business ¦ ¦ http://www.pinboard.com/kurt/ private ¦ ¦--------------------------------------------------------------------¦ ¦ Unix and Internet Specialist ¦ -------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 17 23:07:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25885 for freebsd-net-outgoing; Tue, 17 Nov 1998 23:07:23 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25880 for ; Tue, 17 Nov 1998 23:07:21 -0800 (PST) (envelope-from tseidmann@simultan.ch) Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53]) by SIMULTAN.CH (8.9.1a/8.9.1) with ESMTP id IAA19071 for ; Wed, 18 Nov 1998 08:06:52 +0100 (CET) Message-ID: <3652720B.F9306004@simultan.ch> Date: Wed, 18 Nov 1998 08:06:51 +0100 From: Thomas Seidmann X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: Re: Frametypes (was: Re: Netware client for FreeBSD) References: <199811171747.MAA26273@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Garrett Wollman wrote: > Given the limited utility, I would rather see this information simply > stored as a part of the interface address struct for IPX. Correct, the frame info should go into struct ipx_ifaddr (/sys/netipx/ipx_if.h) > -GAWollman Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Nov 18 01:58:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10545 for freebsd-net-outgoing; Wed, 18 Nov 1998 01:58:08 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from isi.co.jp (mail.isi.co.jp [202.214.62.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10507 for ; Wed, 18 Nov 1998 01:58:04 -0800 (PST) (envelope-from john@isi.co.jp) Received: by ns.isi.co.jp id <21897>; Wed, 18 Nov 1998 18:56:34 +0900 Date: Wed, 18 Nov 1998 18:50:10 +0900 From: john cooper To: Kurt@pinboard.com, john@isi.co.jp Subject: BIND 8 ? Cc: freebsd-net@FreeBSD.ORG Message-Id: <98Nov18.185634jst.21897@ns.isi.co.jp> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, I'm sold on the dual DNS bind 8 approach. Unfortunately I can't seem to find any comprehensive documentation on the [apparent] new configuration file formats in general, nor on how to make a single server feed solely off one network interface. I have rummaged through www.isc.org without finding what I need. Any pointers greatly appreciated. -john > Date: Wed, 18 Nov 1998 06:56:01 +0900 > To: john cooper > From: Kurt Keller > Subject: Re: BIND/Mail/MX Question.. > Cc: freebsd-net@FreeBSD.ORG : > If > you are using BIND 8, it is possible to serve both, the internet and > intranet from the same DNS server, provided you use a subdomain for the > intranet. With BIND 8 it is easily possible to make info about certain > domains only accessible to a certain IP range. > > Cheers, > > Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Nov 18 05:33:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03552 for freebsd-net-outgoing; Wed, 18 Nov 1998 05:33:20 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA03544 for ; Wed, 18 Nov 1998 05:33:18 -0800 (PST) (envelope-from mike@seidata.com) From: mike@seidata.com Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id IAA05519; Wed, 18 Nov 1998 08:32:20 -0500 (EST) Date: Wed, 18 Nov 1998 08:32:20 -0500 (EST) To: john cooper cc: Kurt@pinboard.com, freebsd-net@FreeBSD.ORG Subject: Re: BIND 8 ? In-Reply-To: <98Nov18.185634jst.21897@ns.isi.co.jp> 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 Wed, 18 Nov 1998, john cooper wrote: > Ok, I'm sold on the dual DNS bind 8 approach. Unfortunately > I can't seem to find any comprehensive documentation on the > [apparent] new configuration file formats in general, nor on Maybe this will help, zone "xxx.xxx.xxx.IN-ADDR.ARPA" { type master; file "db.xxx.xxx.xxx"; }; zone "domain.com" { type slave; file "virtuals/db.domain.com"; masters { xxx.xxx.xxx.xxx; }; }; > how to make a single server feed solely off one network interface. I believe you're looking for listen-on, listen-on { xxx.xxx.xxx.xxx; }; Put that in your options {}; block (I.e. listen-on { 10.0.0.1; }; would cause the server to only 'hear' DNS requests on the interface with the 10.0.0.1 IP (no matter how many interfaces are present in the server)). > I have rummaged through www.isc.org without finding what I need. Lots of documentation is there, it just requires more effort than it used to (a bad thing for sysadmins, where laziness is a virtue ;). If you download the documentation (bind-8.1.2-doc.tar.gz, goto the 'BIND 8.1.2 Documentation' link from http://www.isc.org/new-bind.html) and gunzip|tar the sucker, you'll get HTML documentation, the BOG, etc. - lots of useful info. All of that used to be available online, I suppose they're trying to reduce the load on their system(s). *shrug* Later, -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Nov 18 09:02:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01130 for freebsd-net-outgoing; Wed, 18 Nov 1998 09:02:11 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from carp.gbr.epa.gov (carp.gbr.epa.gov [204.46.159.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01113 for ; Wed, 18 Nov 1998 09:02:05 -0800 (PST) (envelope-from mjenkins@carp.gbr.epa.gov) Received: (from mjenkins@localhost) by carp.gbr.epa.gov (8.8.8/8.8.8) id LAA18886; Wed, 18 Nov 1998 11:01:32 -0600 (CST) (envelope-from mjenkins) Date: Wed, 18 Nov 1998 11:01:32 -0600 (CST) From: Mike Jenkins Message-Id: <199811181701.LAA18886@carp.gbr.epa.gov> To: john@isi.co.jp Subject: Re: BIND 8 ? Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <98Nov18.185634jst.21897@ns.isi.co.jp> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Date: Wed, 18 Nov 1998 18:50:10 +0900 > From: john cooper > > Ok, I'm sold on the dual DNS bind 8 approach. Unfortunately > I can't seem to find any comprehensive documentation on the > [apparent] new configuration file formats in general, nor on > how to make a single server feed solely off one network interface. > > I have rummaged through www.isc.org without finding what I need. > > Any pointers greatly appreciated. You're right. I searched Yahoo, Alta Vista, etc. and didn't find much. I think two nameservers on dual-homed bastion host works something like: /usr/sbin/named /etc/namedb/named.external.conf /usr/sbin/named /etc/namedb/named.internal.conf // // External nameserver config file // options { pid-file "/var/run/named.external.pid"; listen-on { ; }; // other options }; zone "my.domain" { type master; file "external.zone"; }; // // Internal nameserver config file // options { pid-file "/var/run/named.internal.pid"; listen-on { ; }; forwarders { ; }; forward only; }; zone "my.domain" { type master; file "internal.zone"; }; # /etc/resolv.conf nameserver Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Nov 18 14:49:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22848 for freebsd-net-outgoing; Wed, 18 Nov 1998 14:49:31 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22841 for ; Wed, 18 Nov 1998 14:49:28 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA07179; Wed, 18 Nov 1998 14:46:58 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma007171; Wed, 18 Nov 98 14:46:32 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA28154; Wed, 18 Nov 1998 14:46:28 -0800 (PST) From: Archie Cobbs Message-Id: <199811182246.OAA28154@bubba.whistle.com> Subject: Re: BIND 8 ? In-Reply-To: <98Nov18.185634jst.21897@ns.isi.co.jp> from john cooper at "Nov 18, 98 06:50:10 pm" To: john@isi.co.jp (john cooper) Date: Wed, 18 Nov 1998 14:46:27 -0800 (PST) Cc: Kurt@pinboard.com, freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 john cooper writes: > Ok, I'm sold on the dual DNS bind 8 approach. Unfortunately > I can't seem to find any comprehensive documentation on the > [apparent] new configuration file formats in general, nor on Huh? There's plenty of documentation on the new format there. Is http://www.isc.org/bind8/config.html not what you're looking for? -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 Nov 19 08:12:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14330 for freebsd-net-outgoing; Thu, 19 Nov 1998 08:12:50 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from carp.gbr.epa.gov (carp.gbr.epa.gov [204.46.159.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14323 for ; Thu, 19 Nov 1998 08:12:48 -0800 (PST) (envelope-from mjenkins@carp.gbr.epa.gov) Received: (from mjenkins@localhost) by carp.gbr.epa.gov (8.8.8/8.8.8) id KAA20429; Thu, 19 Nov 1998 10:12:02 -0600 (CST) (envelope-from mjenkins) Date: Thu, 19 Nov 1998 10:12:02 -0600 (CST) From: Mike Jenkins Message-Id: <199811191612.KAA20429@carp.gbr.epa.gov> To: archie@whistle.com Subject: Re: BIND 8 ? Cc: freebsd-net@FreeBSD.ORG, john@isi.co.jp In-Reply-To: <199811182246.OAA28154@bubba.whistle.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 18 Nov 1998 Archie Cobbs wrote: > john cooper writes: > > Ok, I'm sold on the dual DNS bind 8 approach. Unfortunately > > I can't seem to find any comprehensive documentation on the > > [apparent] new configuration file formats in general, nor on > > Huh? There's plenty of documentation on the new format there. > Is http://www.isc.org/bind8/config.html not what you're looking for? I think what he was looking for was documentation on how to do split DNS on a single dual-homed host by using bind8. I searched around quite a bit yesterday and couldn't find any clear info, just bits and pieces. Seems like this should be well documented on some web page or FAQ. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 19 12:07:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13891 for freebsd-net-outgoing; Thu, 19 Nov 1998 12:07:39 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13884 for ; Thu, 19 Nov 1998 12:07:35 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id PAA25195 for ; Thu, 19 Nov 1998 15:08:01 -0500 (EST) Message-Id: <4.1.19981119144046.00a562c0@206.25.93.69> Message-Id: <4.1.19981119144046.00a562c0@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 19 Nov 1998 14:45:50 -0500 To: freebsd-net@FreeBSD.ORG From: Forrest Aldrich Subject: Ip_masquerading, NATD & Internet (more questions) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems my posting to FreeBSD-Questions was either censored or rejected. There's no charter listing for freebsd-net, but this is very technical in nature, so I hope someone here will be able to help. ============================= I have a few things to add to this, after having toyed with building this configuration all day yesterday (and losing some hair in the process). The manpage for natd could be better. And I'm hoping that somewhere there is an IP_MASQUERADING doc that applies to using FreeBSD, natd, and ipfw (Darren Reed's IPFIlter is yet another possibility). There are lots of other caveats involved here, especially when your IP address is dynamically allocated from, say, a cable modem service. Below is some detail of my questions.... (fasten your seatbelts) STAGE 1 ====================================== I have 2 NICs on my FreeBSD system: xl0 and xl1. xl0 is the outbound interface (connected to the cable modem), xl1 is the private network (hooked to a hub) I imported in some firewall rules and added, at the beginning of them: $fwcmd add divert natd all from any to any via xl0 This was tried with the firewall rules and as an OPEN system (yes, I have DIVERT and all the rest of the definitions in /usr/src/sys/i386/conf). From what I was able to gleen from the manpage (3.0-RELEASE), I used: /usr/sbin/natd -dynamic -interface xl0 Which I'm not clear is correct. I did toy around with the firewall rules and natd, eventually I was able to get out to the internet, but not through the hub I had connected to xl1. I think that failed because I didn't hook in a straight-through cable from xl1 to the uplink port on the hub. It's not clear about whether you need to add specific IPFW rules for the internal interface (in this case 10.0.0.3). STAGE 1.5 :-) ======================================= I have been able to get the dhclient to work properly when booting to obtain the IP address. But don't screw with it afterwards, as you'll hose everything. Aside from not being able to get a carrier on xl1 (again, I think due the cable type, I'll try it again), I wasn't able to get isc-dhcpd2 to work. It complained that I had no subnet declaration for my ISP's address (the host) -- even though I've told it only to run on xl1. This part is particularly important, as the Windoze hosts I have hooked in the hub are used on other nets and need dhcpd. STAGE 2 ======================================= While using the dhclient for your IP address does work, using this with a firewall presents a few gotchyas. As I recall: You need to somehow obtain the network, netmask, host IP, etc. for use in /etc/rc.firewall. I would imagine you could obtain variables from /etc/dhclient-script and save them to a file on bootup. There was a point where I could ping the external networks, but could not get to 127.0.0.1... I got a /kernel error (damn, didn't write it down) regarding inability to arpret. But ifconfig showed that it was okay... this happened with f/w rules and an "OPEN" f/w. There were surely a few other issues I ran into that I can't recall here. It was a LONG day and I had everything ripped apart. I will surely be grateful if someone can shed light on this. I suppose the other option is to use Darren Reed's IPFilter (this is all on FreeBSD-3.0-RELEASE) which uses a different ACL format and approach. How about Linux ipfwadm? :) :) Thanks......... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 19 20:15:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07084 for freebsd-net-outgoing; Thu, 19 Nov 1998 20:15:15 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mail.pinboard.com (mail.pinboard.com [194.209.195.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07079 for ; Thu, 19 Nov 1998 20:15:13 -0800 (PST) (envelope-from Kurt@pinboard.com) Received: (from uucp@localhost) by mail.pinboard.com (8.9.1/8.9.1/19980920-01/KK) with UUCP id FAA04491 for freebsd-net@freebsd.org; Fri, 20 Nov 1998 05:14:42 +0100 (CET) (envelope-from: Kurt@pinboard.com) Received: from beaver.pbdhome.pinboard.com ([192.168.0.7]) by squirrel.pbdhome.pinboard.com (8.9.1/8.9.1-19980817-01/KK) with SMTP id WAA14347 for ; Thu, 19 Nov 1998 22:55:55 +0100 (CET) (envelope-from: Kurt@pinboard.com) Message-Id: <3.0.5.16.19981119221415.39cfddc0@pop.pbdhome.pinboard.com> Organization: PINBOARD - http://www.pinboard.com/ X-Sender: kurt@pop.pbdhome.pinboard.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (16) Date: Thu, 19 Nov 1998 22:14:15 To: freebsd-net@FreeBSD.ORG From: Kurt Keller Subject: Re: BIND 8 ? In-Reply-To: <199811191612.KAA20429@carp.gbr.epa.gov> References: <199811182246.OAA28154@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id UAA07080 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I think what he was looking for was documentation on how to do >split DNS on a single dual-homed host by using bind8. I searched In the restricted zones, use allow-query allow-transfer and only allow your intranet to query the internal subdomain. Cheers, Kurt -- -------------------------------------------------------------------- ¦ Kurt@pinboard.com http://www.pinboard.com/ business ¦ ¦ http://www.pinboard.com/kurt/ private ¦ ¦--------------------------------------------------------------------¦ ¦ Unix and Internet Specialist ¦ -------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 20 08:13:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18721 for freebsd-net-outgoing; Fri, 20 Nov 1998 08:13:56 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from arthur.axion.bt.co.uk (arthur.axion.bt.co.uk [132.146.5.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18657 for ; Fri, 20 Nov 1998 08:13:40 -0800 (PST) (envelope-from graeme.brown@bt-sys.bt.co.uk) Received: from rambo (actually rambo.futures.bt.co.uk) by arthur (local) with SMTP; Fri, 20 Nov 1998 16:12:20 +0000 Received: from maczebedee (actually macsmtp) by rambo with SMTP (PP); Fri, 20 Nov 1998 16:14:42 +0000 Message-ID: Date: 20 Nov 1998 16:10:56 +0100 From: Graeme Brown Subject: FreeBSD Driver for G-NIC II Gigabit Ethernet card To: "FreeBSD-Net (FreeBSD.Org) List" X-Mailer: Mail*Link SMTP for Quarterdeck Mail; Version 4.0.0 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Folks The Packet Engines G-NIC II Gigabit Ethernet card (http://www.packetengines.com/products/gnic/default.htm) is suppose to have a FreeBSD driver but according to Packet Engines web site this driver is not available from a third party and is not shipped with the card. Does anyone on the list know of a source for this driver ? TIA Graeme N Brown BT Labs, UK email : graeme.brown@bt-sys.bt.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 20 09:10:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23680 for freebsd-net-outgoing; Fri, 20 Nov 1998 09:10:50 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from babelfish.axion.bt.co.uk (babelfish.axion.bt.co.uk [132.146.17.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23675 for ; Fri, 20 Nov 1998 09:10:47 -0800 (PST) (envelope-from antonio.herrera-alcantara@bt.com) Message-Id: <199811201710.JAA23675@hub.freebsd.org> Received: from sb48mhnt23.comnet.bt.co.uk by babelfish.axion.bt.co.uk (local) with ESMTP; Fri, 20 Nov 1998 16:49:22 +0000 Received: by sb48mhnt23.comnet.bt.co.uk with Internet Mail Service (5.5.2232.9) id ; Fri, 20 Nov 1998 16:50:12 -0000 From: Herrera-Alcantara HERRERA2 M To: "'freebsd-net@freebsd.org'" Subject: RSVP APIs Date: Fri, 20 Nov 1998 16:50:35 -0000 X-Mailer: Internet Mail Service (5.5.2232.9) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear all, trying to install a new RSVP application I found that it requires support for the APIs RAPI and SCRAPI. Do you know whether there's any implementation of those API available for FreeBSD 2.2.7? and where to get those libraries from?. Thak you in advance, Antonio HERRERA ALCANTARA Network Intelligence & Internet Engineering MLB 4/54 BT Laboratories Martlesham Heath IPSWICH IP5 3RE UK phone: 01473 649446 (International: +44 1473 649446) e-mail: antonio.herrera-alcantara@bt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 20 11:48:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08272 for freebsd-net-outgoing; Fri, 20 Nov 1998 11:48:31 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from friley-185-114.res.iastate.edu (friley-185-114.res.iastate.edu [129.186.185.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08265 for ; Fri, 20 Nov 1998 11:48:29 -0800 (PST) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Received: from friley-185-114.res.iastate.edu (loopback [127.0.0.1]) by friley-185-114.res.iastate.edu (8.9.1/8.9.1) with ESMTP id NAA02754; Fri, 20 Nov 1998 13:47:51 -0600 (CST) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Message-Id: <199811201947.NAA02754@friley-185-114.res.iastate.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Graeme Brown cc: "FreeBSD-Net (FreeBSD.Org) List" Subject: Re: FreeBSD Driver for G-NIC II Gigabit Ethernet card In-reply-to: Your message of "20 Nov 1998 16:10:56 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Nov 1998 13:47:50 -0600 From: Chris Csanady Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Folks > >The Packet Engines G-NIC II Gigabit Ethernet card >(http://www.packetengines.com/products/gnic/default.htm) >is suppose to >have a FreeBSD driver but according to Packet Engines web site >this driver is not available from a third party and is not shipped >with the card. > >Does anyone on the list know of a source for this driver ? Take a look at ftp.scl.ameslab.gov:/pub/drivers/pe-gnic2.tar.gz. It is a very alpha driver, although I have seen fairly decent performance from it. Currently, some of the performance features are disabled, so you can expect it to get better as well. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 20 13:10:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18363 for freebsd-net-outgoing; Fri, 20 Nov 1998 13:10:31 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mathserv.mps.ohio-state.edu (mathserv.mps.ohio-state.edu [128.146.111.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18341 for ; Fri, 20 Nov 1998 13:10:21 -0800 (PST) (envelope-from alden@math.ohio-state.edu) Received: from math.mps.ohio-state.edu (math.mps.ohio-state.edu [128.146.111.30]) by mathserv.mps.ohio-state.edu (8.9.1a/8.9.1) with ESMTP id QAA19431 for ; Fri, 20 Nov 1998 16:09:52 -0500 (EST) From: Dave Alden Received: (from alden@localhost) by math.mps.ohio-state.edu (8.9.1a/8.9.1) id QAA06927 for freebsd-net@freebsd.org; Fri, 20 Nov 1998 16:09:47 -0500 (EST) Date: Fri, 20 Nov 1998 16:09:47 -0500 (EST) Message-Id: <199811202109.QAA06927@math.mps.ohio-state.edu> To: freebsd-net@FreeBSD.ORG Subject: bridging hints? Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm planning on using a FreeBSD box as our departmental firewall. I just started playing around with it and have a box configured with 2 Intel EtherExpress 100+ cards, our LAN on one and a workstation (call 'wkstn') on the other. I'm trying to learn ipfw, so I setup the FreeBSD box as a "client" firewall. I then did: ipfw add deny tcp from any to wkstn This works as expected. But if I try to just turn of certain ports with: ipfw add deny tcp from any to wkstn 1-1024 it doesn't work as I would expect (it allows me to telnet to the machine). Can someone tell me what I'm doing wrong? :-) ...thnx, ...dave ps I have set net.link.ether.bridge_ipfw=1. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 20 17:22:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17961 for freebsd-net-outgoing; Fri, 20 Nov 1998 17:22:18 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from MailAndNews.com (TKYca-0416p06.ppp.odn.ad.jp [143.90.173.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17955 for ; Fri, 20 Nov 1998 17:22:15 -0800 (PST) (envelope-from tetsuji@MailAndNews.com) Received: (from tetsuji@localhost) by MailAndNews.com (8.8.8/8.8.8) id KAA00463; Sat, 21 Nov 1998 10:23:24 +0900 (JST) (envelope-from tetsuji) Date: Sat, 21 Nov 1998 10:23:24 +0900 (JST) Message-Id: <199811210123.KAA00463@MailAndNews.com> From: Tetsuji Rai To: freebsd-net@FreeBSD.ORG Subject: connect LAN and Internet by ppp Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Title says it all. I'm trying to connect LAN with only 2 machines and Internet by ppp like the one noted in Handbook 14.1.2. But I have some problems on it. First of all my configuration is as follows: [local2] <--ether--> [Local1] <--ppp--> [ISP-serv] (10.0.0.2) (10.0.0.1) First, I tested with only these two machines without configuring default route. This worked very fine. Anything works between these machines; telnet, nfs, etc... As a matter of course, Local1 is configured as a gateway. On both machines, correct /etc/resolv.conf is placed. Second, I set default route on local2, which is Local1 (10.0.0.1). Then most things don't work properly. eg. telnet from local1 to local2 takes time. telnet or ping doesn't work from local2 to local1. However, ping from local1 to local2 works properly. When Local1 is connected to ISP by ppp, these still don't work. But anything from local1 to Internet work. I guess something is missing in my settings. Does anyone tell me the correct settings or what is wrong with mine. Any help would be appreciated. -Tetsuji Rai To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 20 18:15:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25030 for freebsd-net-outgoing; Fri, 20 Nov 1998 18:15:47 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25005; Fri, 20 Nov 1998 18:15:43 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id SAA10182; Fri, 20 Nov 1998 18:15:11 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id SAA07887; Fri, 20 Nov 1998 18:15:10 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id TAA25480; Fri, 20 Nov 1998 19:15:09 -0700 Message-ID: <3656222D.69BD3FB8@softweyr.com> Date: Fri, 20 Nov 1998 19:15:09 -0700 From: Wes Peters Reply-To: freebsd-questions@FreeBSD.ORG Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Tetsuji Rai CC: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: connect LAN and Internet by ppp References: <199811210123.KAA00463@MailAndNews.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tetsuji Rai wrote: > > Hi, Title says it all. I'm trying to connect LAN with only 2 machines and > Internet by ppp like the one noted in Handbook 14.1.2. But I have some > problems on it. > First of all my configuration is as follows: > > [local2] <--ether--> [Local1] <--ppp--> [ISP-serv] > (10.0.0.2) (10.0.0.1) > > First, I tested with only these two machines without configuring default > route. This worked very fine. Anything works between these machines; > telnet, nfs, etc... As a matter of course, Local1 is configured as > a gateway. On both machines, correct /etc/resolv.conf is placed. > > Second, I set default route on local2, which is Local1 (10.0.0.1). Then > most things don't work properly. eg. telnet from local1 to local2 takes > time. telnet or ping doesn't work from local2 to local1. However, ping > from local1 to local2 works properly. When Local1 is connected to ISP > by ppp, these still don't work. But anything from local1 to Internet > work. > > I guess something is missing in my settings. Does anyone tell me the > correct settings or what is wrong with mine. Any help would be appreciated. These questions should be asked on the freebsd-questions mailing list; I have forwarded this message there and directed replies there as well. The short answer is you cannot connect network 10.0.0.0 directly to the internet; you will need to setup network address translation on your PPP router in order for this work. The user-mode PPP utility in FreeBSD will do this for you, or if you use the kernel-mode 'pppd' you may also use 'natd' to accomplish this. If these pointers and the handbook entries aren't enough to get you up and running, ask more questions on the questions list. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 20 21:58:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12922 for freebsd-net-outgoing; Fri, 20 Nov 1998 21:58:05 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA12917 for ; Fri, 20 Nov 1998 21:58:02 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id FAA28620; Sat, 21 Nov 1998 05:00:59 +0100 From: Luigi Rizzo Message-Id: <199811210400.FAA28620@labinfo.iet.unipi.it> Subject: Re: bridging hints? To: alden@math.ohio-state.edu (Dave Alden) Date: Sat, 21 Nov 1998 05:00:58 +0100 (MET) Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <199811202109.QAA06927@math.mps.ohio-state.edu> from "Dave Alden" at Nov 20, 98 04:09:28 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > I'm planning on using a FreeBSD box as our departmental firewall. I > just started playing around with it and have a box configured with 2 Intel > EtherExpress 100+ cards, our LAN on one and a workstation (call 'wkstn') > on the other. I'm trying to learn ipfw, so I setup the FreeBSD box as a > "client" firewall. I then did: i am not sure what you mean by "client" firewall -- i suppose that you are setting the firewall on the machine acting as a bridge. > ipfw add deny tcp from any to wkstn > > This works as expected. But if I try to just turn of certain ports with: > > ipfw add deny tcp from any to wkstn 1-1024 > > it doesn't work as I would expect (it allows me to telnet to the machine). i have never tried this... have you tried, by chance, to block single ports as opposed to a range and see if it makes a difference ? If it does it could be a bug in ipfw.c, otherwhise it is in the way the bridge code uses ipfw luigi > Can someone tell me what I'm doing wrong? :-) > > ...thnx, > ...dave > > ps I have set net.link.ether.bridge_ipfw=1. :-) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 20 23:03:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17981 for freebsd-net-outgoing; Fri, 20 Nov 1998 23:03:26 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from tomcat.webber.net.ua (S2-1.GWN-KVC2.ukrpack.net [195.230.151.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17972 for ; Fri, 20 Nov 1998 23:03:22 -0800 (PST) (envelope-from apl@webber.net.ua) Received: from opera.webber.net.ua (root@opera.webber.net.ua [195.230.145.41]) by tomcat.webber.net.ua (8.9.1/8.9.1) with ESMTP id JAA19331 for ; Sat, 21 Nov 1998 09:02:46 +0200 (EET) Received: from webber.net.ua (apl@opera.webber.net.ua [195.230.145.41]) by opera.webber.net.ua (8.9.1/8.9.1) with ESMTP id JAA13386 for ; Sat, 21 Nov 1998 09:02:46 +0200 (EET) Message-ID: <365664E1.B7589F88@webber.net.ua> Date: Sat, 21 Nov 1998 08:59:45 +0200 From: Andrew Petrenko Organization: Andy, inc. X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: FBSNET Subject: Bridge and Dummynet in FreeBSD 3.0.0 RELEASE Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can i set up Bridge and Dummynet in FreeBSD-3.0.0-RELEASE and haw can i do it? -- Andrew Petrenko JSCB "Pravex-BANK" apl@webber.net.ua +380-44-2610251 --FBSD026630 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Nov 21 01:01:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24441 for freebsd-net-outgoing; Sat, 21 Nov 1998 01:01:57 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24436 for ; Sat, 21 Nov 1998 01:01:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1a/8.9.1) with ESMTP id BAA12836; Sat, 21 Nov 1998 01:01:07 -0800 (PST) To: Tony Ardolino cc: Cam Johnson , Boris Popov , Jim Cassata , FreeBSD Net Subject: Re: [Fwd: Netware client for FreeBSD] In-reply-to: Your message of "Mon, 16 Nov 1998 07:57:47 EST." <3650214B.19CE4C2A@netcon.com> Date: Sat, 21 Nov 1998 01:01:07 -0800 Message-ID: <12832.911638867@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 1.) Free distribution for non-commerical use only. > 2.) A enhancements must be returned to FreeBSD. > 3.) Commerical use or Resale requires a license from NetCon Corp. > 4.) NetCon Corp. will always own NetCon Software and all clanges. > 5.) Cannot be ported to any other platform Like SCO, or Sun. I don't think you'll get any canned license with quite this many subclauses already written out, but a good starter point would certainly be the Netscape Public License, or NPL. It sounds to me like what you're basically looking for is a way to release it without enabling someone else to outright compete with you by redeploying it as a commercial solution without paying $$$. That's essentially the same thing Kirk McKusick wanted for his soft updates code license (see top of /sys/ufs/ffs/ffs_softdep.c) since he wanted FreeBSD (and OpenBSD, and NetBSD, etc) to be able to use it freely without allowing the likes of Sun to also incorporate it into Solaris without paying him something for his work. That's also essentially what Netscape were trying to prevent and this is reflected in the NPL. > I also need a committment from a group of people to keep NetCon updated with the > changes in NetWare and Freebsd (About a month a year). We will train and supp The best of all possible people to do this would be existing Netcon customers who are also somewhat technically competent, of course, if such could be found. They'll have access to the proper testing environment and also have the desire to see something like this function properly. Given that you're likely to know the composition of the existing FreeBSD customer base better than I, do you have any ideas? We ripped the last of our IPX network out of Walnut Creek CDROM about 3 months ago so I can't even test it locally myself in any kind of meaningful way. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Nov 21 08:07:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21912 for freebsd-net-outgoing; Sat, 21 Nov 1998 08:07:27 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21905 for ; Sat, 21 Nov 1998 08:07:25 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id HAA05687; Sat, 21 Nov 1998 07:58:06 -0800 (PST) (envelope-from marcs@znep.com) Date: Sat, 21 Nov 1998 07:58:06 -0800 (PST) From: Marc Slemko To: "Jordan K. Hubbard" cc: Tony Ardolino , FreeBSD Net Subject: Re: [Fwd: Netware client for FreeBSD] In-Reply-To: <12832.911638867@zippy.cdrom.com> 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 (somewhat offtopic for net so followups may be best taken to chat, but just to make the important point so more people don't get tricked into the MPL without fully understanding some of its bad parts...) On Sat, 21 Nov 1998, Jordan K. Hubbard wrote: > > 1.) Free distribution for non-commerical use only. > > 2.) A enhancements must be returned to FreeBSD. > > 3.) Commerical use or Resale requires a license from NetCon Corp. > > 4.) NetCon Corp. will always own NetCon Software and all clanges. > > 5.) Cannot be ported to any other platform Like SCO, or Sun. > > I don't think you'll get any canned license with quite this many > subclauses already written out, but a good starter point would > certainly be the Netscape Public License, or NPL. It sounds to me Just be very careful with the NPL because it has a somewhat hidden patent clause that has a horrible impact on anyone from any medium to large company, University, etc. trying to contribute. Essentially, it requires that if you contribute a change to any part of the code, you give a license for any patents that you (ie. your company if this is done as part of your job) holds that are used _anywhere_ in the code, not just in the section you modified or even looked at. Because of how you can take parts of MPLed code and use it for other things, this in some ways ends up giving people rights to use your patent for any completely unrelated code they want. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Nov 21 19:28:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22670 for freebsd-net-outgoing; Sat, 21 Nov 1998 19:28:46 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22661 for ; Sat, 21 Nov 1998 19:28:44 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id TAA01406; Sat, 21 Nov 1998 19:29:17 -0800 (PST) Message-Id: <199811220329.TAA01406@root.com> To: Dave Alden cc: freebsd-net@FreeBSD.ORG Subject: Re: bridging hints? In-reply-to: Your message of "Fri, 20 Nov 1998 16:09:47 EST." <199811202109.QAA06927@math.mps.ohio-state.edu> From: David Greenman Reply-To: dg@root.com Date: Sat, 21 Nov 1998 19:29:16 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm planning on using a FreeBSD box as our departmental firewall. I >just started playing around with it and have a box configured with 2 Intel >EtherExpress 100+ cards, our LAN on one and a workstation (call 'wkstn') >on the other. I'm trying to learn ipfw, so I setup the FreeBSD box as a >"client" firewall. I then did: > >ipfw add deny tcp from any to wkstn > >This works as expected. But if I try to just turn of certain ports with: > >ipfw add deny tcp from any to wkstn 1-1024 > >it doesn't work as I would expect (it allows me to telnet to the machine). >Can someone tell me what I'm doing wrong? :-) Here's a guess: You need to be careful about the precedence. Lower number filter rules have higher precendence. Since you didn't specify a specific rule number, the system assigned a number that was greater than a previous allow rule, and that wasn't what you wanted. See ipfw(8). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message