From owner-freebsd-net Sun Dec 5 4:46:38 1999 Delivered-To: freebsd-net@freebsd.org Received: from seu.edu.cn. (seic3.seu.edu.cn [202.119.24.13]) by hub.freebsd.org (Postfix) with ESMTP id 290AC1540B for ; Sun, 5 Dec 1999 04:43:50 -0800 (PST) (envelope-from bxgu@seu.edu.cn) Received: from mars_atm ([202.119.28.185]) by seu.edu.cn. (8.9.3/8.9.3) with SMTP id UAA09879 for ; Sun, 5 Dec 1999 20:44:23 +0800 (CST) Message-ID: <000701bf3f1f$c0a8fea0$b902a8c0@mars_atm.seu.edu.cn> From: "bxgu" To: Subject: hellO! Date: Sun, 5 Dec 1999 20:53:39 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01BF3F62.CEA30BC0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0004_01BF3F62.CEA30BC0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable I want to join the mailinglist of freebsd-net.how can I do ? thank u! Sincerely! Alex ------=_NextPart_000_0004_01BF3F62.CEA30BC0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable
I want to join the mailinglist of=20 freebsd-net.how can I do ?
thank u!
Sincerely!
Alex
------=_NextPart_000_0004_01BF3F62.CEA30BC0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Dec 5 4:49:15 1999 Delivered-To: freebsd-net@freebsd.org Received: from seu.edu.cn. (seic3.seu.edu.cn [202.119.24.13]) by hub.freebsd.org (Postfix) with ESMTP id B83EC14BD7 for ; Sun, 5 Dec 1999 04:49:07 -0800 (PST) (envelope-from bxgu@seu.edu.cn) Received: from mars_atm ([202.119.28.185]) by seu.edu.cn. (8.9.3/8.9.3) with SMTP id UAA09936 for ; Sun, 5 Dec 1999 20:46:54 +0800 (CST) Message-ID: <000701bf3f20$1ada9820$b902a8c0@mars_atm.seu.edu.cn> From: "bxgu" To: Subject: the driver of fore runnerle 25 and 155 ATM adapter over freebsd Date: Sun, 5 Dec 1999 20:56:10 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01BF3F63.28DC4660" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0004_01BF3F63.28DC4660 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable hello! I want to get the the driver of fore runnerle 25 and 155 atm adapter = over freebsd 3.0. where I can download it? sincerely! alex ------=_NextPart_000_0004_01BF3F63.28DC4660 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable
hello!
I want to get the the driver of fore = runnerle 25=20 and 155 atm adapter over freebsd 3.0.
where I can download it?
sincerely!
alex
------=_NextPart_000_0004_01BF3F63.28DC4660-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Dec 5 16:43:19 1999 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (dustdevil.waterspout.com [208.13.60.151]) by hub.freebsd.org (Postfix) with ESMTP id 94C4A14DCF; Sun, 5 Dec 1999 16:43:11 -0800 (PST) (envelope-from csg@waterspout.com) Received: by dustdevil.waterspout.com (Postfix, from userid 1000) id A36069E; Sun, 5 Dec 1999 19:45:39 -0500 (EST) To: FreeBSD-gnats-submit@freebsd.org Cc: ajk@waterspout.com, freebsd-net@freebsd.org Subject: Bug in Hardware VLAN Tag Support From: csg@waterspout.com Reply-To: csg@waterspout.com X-send-pr-version: 3.2 Message-Id: <19991206004539.A36069E@dustdevil.waterspout.com> Date: Sun, 5 Dec 1999 19:45:39 -0500 (EST) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Submitter-Id: current-users >Originator: C. Stephen Gunn >Organization: Waterspout Communications, Inc. >Confidential: no >Synopsis: Bug in Hardware VLAN Tag Support >Severity: non-critical >Priority: medium >Category: kern >Release: FreeBSD 3.3-STABLE i386 >Class: sw-bug >Environment: FreeBSD 4.0-CURRENT. This doesn't apply to FreeBSD 3-STABLE (yet) since VLAN's are completely broken in stable with the ti0 device. >Description: sys/net/if_vlan.c contains support for ethernet hardware that support tagged VLANs in hardware. Currently (AFAIK) only the "ti" driver written by Bill Paul has support for these features. Apparently, when the ethernet driver detects a tagged frame from the hardware, it passes the frame, along with the tag to vlan_input_tag() instead of the normal vlan_input() call from inside ether_input(). The problem arrises in an attempt to log errors on the parent device. vlan_input_tag() walks the list of vlan devices, looking for a matching and tries to log the error on the parent device if appropriately. Unfortunatly, the current code incorrectly assumes that all vlans are configured, and/or associated with a parent device. If you receive a frame for a VLAN that's not in the list, you walk off the end of the list. Boom. >How-To-Repeat: 1. Setup a host with multiple VLAN's on an 802.1Q trunk to the machine, with a ti0 ethernet interface. 2. Configure some but not all of the vlan interfaces: # ifconfig up # ifconfig vlan0 vlandev vlan # ifconfig vlan1 vlandev vlan 3. Wait for traffic on an as-of-yet unconfigured vlan number. 4. Watch your machine crashdump.. >Fix: This patch modifies vlan_input_tag to return -1 in the event of an error so the parent device can maintain its counters for us. - BEGIN PATCH ----------------------------------------------------------------- Index: pci/if_ti.c =================================================================== RCS file: /usr/local/share/cvs/FreeBSD/src/sys/pci/if_ti.c,v retrieving revision 1.24 diff -u -r1.24 if_ti.c --- if_ti.c 1999/09/23 03:32:54 1.24 +++ if_ti.c 1999/12/05 22:28:44 @@ -1887,7 +1887,8 @@ * to vlan_input() instead of ether_input(). */ if (have_tag) { - vlan_input_tag(eh, m, vlan_tag); + if (vlan_input_tag(eh, m, vlan_tag) < 0) + ifp->if_data.ifi_noproto++; have_tag = vlan_tag = 0; continue; } Index: if_vlan.c =================================================================== RCS file: /usr/local/share/cvs/FreeBSD/src/sys/net/if_vlan.c,v retrieving revision 1.10 diff -u -r1.10 if_vlan.c --- if_vlan.c 1999/09/25 12:05:57 1.10 +++ if_vlan.c 1999/12/06 00:17:05 @@ -272,7 +272,7 @@ return; } -void +int vlan_input_tag(struct ether_header *eh, struct mbuf *m, u_int16_t t) { int i; @@ -284,10 +284,9 @@ break; } - if (i >= NVLAN || (ifv->ifv_if.if_flags & IFF_UP) == 0) { - m_freem(m); - ifv->ifv_p->if_data.ifi_noproto++; - return; + if (i >= NVLAN) { + m_free(m); + return -1; /* So the parent can take note */ } /* @@ -312,7 +311,7 @@ } ifv->ifv_if.if_ipackets++; ether_input(&ifv->ifv_if, eh, m); - return; + return 0; } int Index: if_vlan_var.h =================================================================== RCS file: /usr/local/share/cvs/FreeBSD/src/sys/net/if_vlan_var.h,v retrieving revision 1.3 diff -u -r1.3 if_vlan_var.h --- if_vlan_var.h 1999/08/28 00:48:24 1.3 +++ if_vlan_var.h 1999/12/05 22:19:22 @@ -85,7 +85,7 @@ /* shared with if_ethersubr.c: */ extern u_int vlan_proto; extern int vlan_input(struct ether_header *eh, struct mbuf *m); -extern void vlan_input_tag(struct ether_header *eh, +extern int vlan_input_tag(struct ether_header *eh, struct mbuf *m, u_int16_t t); #endif - END PATCH ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Dec 5 20:37:46 1999 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (dustdevil.waterspout.com [208.13.60.151]) by hub.freebsd.org (Postfix) with ESMTP id B178014DF1 for ; Sun, 5 Dec 1999 20:37:19 -0800 (PST) (envelope-from csg@waterspout.com) Received: by dustdevil.waterspout.com (Postfix, from userid 1000) id 472AA9E; Sun, 5 Dec 1999 23:39:47 -0500 (EST) Received: from waterspout.com (localhost [127.0.0.1]) by dustdevil.waterspout.com (Postfix) with ESMTP id 3BAB4BAB1 for ; Sun, 5 Dec 1999 23:39:46 -0500 (EST) To: freebsd-net@freebsd.org From: "C. Stephen Gunn" Subject: Who's using 802.1Q VLAN Support? Date: Sun, 05 Dec 1999 23:39:41 -0500 Message-Id: <19991206043947.472AA9E@dustdevil.waterspout.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just a straw poll here. I've had some need (and personal interest) in getting the 802.1Q VLAN support in FreeBSD working well. I've got access to a couple of good Cisco Switches, and xl0, de0, and ti0 hardware to try it all out on. Who else out there is trying to make use of VLANs? What success have you had. I'll try to keep the list posted on the progress that I make, in the interim, I've send-pr'd three problems with patches that you might want to check out: kern/15290 vlan fails to maintain IFF_RUNNING kern/15291 Bug in Hardware VLAN Tag Support kern/15298 Problems with 802.1Q VLANs in -STABLE Please let me know if you're making use of VLAN's and what problems you've seen. I've been given some resources by my day job to work on it. - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc. Email: csg@waterspout.com 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Dec 5 21: 8:39 1999 Delivered-To: freebsd-net@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id D77F114DF1 for ; Sun, 5 Dec 1999 21:08:37 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id VAA15844; Sun, 5 Dec 1999 21:07:43 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id VAA26351; Sun, 5 Dec 1999 21:07:43 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA24700; Sun, 5 Dec 99 21:07:25 PST Message-Id: <384B44A2.D0C9D130@softweyr.com> Date: Sun, 05 Dec 1999 22:07:46 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: bxgu Cc: freebsd-net@FreeBSD.ORG Subject: Re: the driver of fore runnerle 25 and 155 ATM adapter over freebsd References: <000701bf3f20$1ada9820$b902a8c0@mars_atm.seu.edu.cn> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > bxgu wrote: > > hello! > I want to get the the driver of fore runnerle 25 and 155 atm adapter over freebsd 3.0. > where I can download it? > sincerely! I don't see a driver for the cards, but there is a fore_dnld program to download code into the Fore cards. The authors of that are listed in the manpage as: AUTHORS John Cavanaugh, Minnesota Supercomputer Center, Inc. Mike Spengler, Minnesota Supercomputer Center, Inc. Joe Thomas, Minnesota Supercomputer Center, Inc. You many want to contact them about drivers for the Fore cards. 3.3 does include drivers for the Midway-based cards from Efficient Networks. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 6 7:48:22 1999 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id ECA8215341 for ; Mon, 6 Dec 1999 07:48:17 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA31953; Mon, 6 Dec 1999 10:48:06 -0500 (EST) (envelope-from wollman) Date: Mon, 6 Dec 1999 10:48:06 -0500 (EST) From: Garrett Wollman Message-Id: <199912061548.KAA31953@khavrinen.lcs.mit.edu> To: "C. Stephen Gunn" Cc: freebsd-net@FreeBSD.ORG Subject: Who's using 802.1Q VLAN Support? In-Reply-To: <19991206043947.472AA9E@dustdevil.waterspout.com> References: <19991206043947.472AA9E@dustdevil.waterspout.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Who else out there is trying to make use of VLANs? I wrote the code, checked it in as a work-in-progress, and never got back to it. (It didn't work at that time, which is why there was never any support in ifconfig for it.) Bill Paul extended the code, with the results you have already seen. I have not yet had the time to try out your patches to see whether they do the right thing or not. -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 Mon Dec 6 11:19:54 1999 Delivered-To: freebsd-net@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1911C15050 for ; Mon, 6 Dec 1999 11:19:43 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA02056; Mon, 6 Dec 1999 10:45:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Garrett Wollman Cc: "C. Stephen Gunn" , freebsd-net@freebsd.org Subject: Re: Who's using 802.1Q VLAN Support? In-reply-to: Your message of "Mon, 06 Dec 1999 10:48:06 EST." <199912061548.KAA31953@khavrinen.lcs.mit.edu> Date: Mon, 06 Dec 1999 10:45:50 -0800 Message-ID: <2053.944505950@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, given that we're coming up on a deadline here, I may just bring them in without review unless you can take a look at them in a timely fashion. - Jordan > < said: > > > Who else out there is trying to make use of VLANs? > > I wrote the code, checked it in as a work-in-progress, and never got > back to it. (It didn't work at that time, which is why there was > never any support in ifconfig for it.) > > Bill Paul extended the code, with the results you have already seen. > > I have not yet had the time to try out your patches to see whether > they do the right thing or not. > > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the sa me > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 6 11:28:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1]) by hub.freebsd.org (Postfix) with ESMTP id 654D7154E9 for ; Mon, 6 Dec 1999 11:28:10 -0800 (PST) (envelope-from mks@us.networkcs.com) Received: from us.networkcs.com (us.networkcs.com [137.66.11.15]) by marcos.networkcs.com (8.9.3/8.9.3) with ESMTP id NAA44368; Mon, 6 Dec 1999 13:28:04 -0600 (CST) (envelope-from mks@us.networkcs.com) Received: (from mks@localhost) by us.networkcs.com (8.9.2/8.8.7) id NAA88406; Mon, 6 Dec 1999 13:27:58 -0600 (CST) From: Mike Spengler Message-Id: <199912061927.NAA88406@us.networkcs.com> Subject: Re: the driver of fore runnerle 25 and 155 ATM adapter over freebsd In-Reply-To: <000701bf3f20$1ada9820$b902a8c0@mars_atm.seu.edu.cn> from bxgu at "Dec 5, 99 08:56:10 pm" To: bxgu@seu.edu.cn (bxgu) Date: Mon, 6 Dec 1999 13:27:58 -0600 (CST) 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 bxgu said: > hello! > I want to get the the driver of fore runnerle 25 and 155 atm adapter over freebsd 3.0. > where I can download it? > sincerely! > alex The FORE driver in FreeBSD3/4 currently only supports the FORE PCA-200E card, not the FORE LE series. It is located in sys/dev/hfa. The ATM "core" code (signalling, IP over ATM, etc) is in sys/netatm. There is a driver for the ForeRunner LE for FreeBSD available from http://www.cs.ndsu.NoDak.edu/~tinguely/. -- Mike Spengler Network Computing Services, Inc. Email: mks@networkcs.com 1200 Washington Ave. So. Phone: +1 612 337 3557 Minneapolis MN 55415 FAX: +1 612 337 3400 (aka Minnesota Supercomputer Center) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 6 17:25:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.6.4]) by hub.freebsd.org (Postfix) with ESMTP id F10E814EE2 for ; Mon, 6 Dec 1999 17:25:25 -0800 (PST) (envelope-from bg24484@binghamton.edu) Received: from localhost (bg24484@localhost) by bingsun2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id UAA19040 for ; Mon, 6 Dec 1999 20:25:21 -0500 (EST) X-Authentication-Warning: bingsun2.cc.binghamton.edu: bg24484 owned process doing -bs Date: Mon, 6 Dec 1999 20:25:20 -0500 (EST) From: X-Sender: bg24484@bingsun2 To: freebsd-net@FreeBSD.ORG Subject: NMBUFCLUSTER and maxusers problem. 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 Hi, I have been troubled by this problem for days. I have written an echo server which echoes data from 200 bytes to 8000 bytes sent by the client in increments of 200 bytes. The problem occurs when the client sends 7800 bytes. In this case the server hangs and doesnt echo the 7800 bytes. On killing the server I get the following displayed on the console "Out of mbuf cluster - Adjust NMBCLUSTER or increase maxusers" So I modified the "LINT" file in the /sys/i386/conf directory with maxusers = 256 and NMBCLUSTER = 6144 and NBUF = 3072 After building the kernel I see that the problem still persists. Can anyone tell me why this behavior? I am working on "FreeBSD v3.3". No other network applications are running except the echo server. Thanks in advance, Any help would be appreciated. Roshan D'Mello. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 6 18: 1:10 1999 Delivered-To: freebsd-net@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D1471510C for ; Mon, 6 Dec 1999 18:01:07 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id VAA28754; Mon, 6 Dec 1999 21:01:04 -0500 (EST) Date: Mon, 6 Dec 1999 21:01:04 -0500 (EST) From: Bosko Milekic To: bg24484@binghamton.edu Cc: freebsd-net@FreeBSD.ORG Subject: Re: NMBUFCLUSTER and maxusers problem. 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, 6 Dec 1999 bg24484@binghamton.edu wrote: !> !>Hi, !> !>I have been troubled by this problem for days. I have written an echo !>server which echoes data from 200 bytes to 8000 bytes sent by the client !>in increments of 200 bytes. You're running out of mbufs with this. Revisit your implementation, something may not be quite efficient -- especially since this is an `echo' server, it shouldn't be holding on to sb space this much... assuming that this is what the problem is. Are you forgetting to close something somewhere that could be causing this sort of leak? !>The problem occurs when the client sends 7800 bytes. In this case the !>server hangs and doesnt echo the 7800 bytes. On killing the server I get !>the following displayed on the console !>"Out of mbuf cluster - Adjust NMBCLUSTER or increase maxusers" Do you ever get a panic()? What does 'netstat -m' display? !> !>So I modified the "LINT" file in the /sys/i386/conf directory with !>maxusers = 256 and NMBCLUSTER = 6144 and NBUF = 3072 You probably shouldn't be modifying the LINT file. That file is used to illustrate all of the different kernel config file options and the way in which they should be used. Instead, you should have your own kernel config file, after which point you should add something like `MAXUSERS 128' and `NMBCLUSTERS=2048' -- in any case, if you're having trouble with anything like this, I would recommend checking out the FreeBSD handbook (http://www.freebsd.org/handbook/) or posting a detailed message to freebsd-questions. !> !>After building the kernel I see that the problem still persists. I hope that you're not actually building a LINT kernel. :-) !> !>Can anyone tell me why this behavior? I am working on "FreeBSD v3.3". !>No other network applications are running except the echo server. !> !> !>Thanks in advance, !>Any help would be appreciated. !>Roshan D'Mello. !> !> Later, Bosko. -- Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 7 9:47:49 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail2.gmx.net (mail2.gmx.net [194.221.183.62]) by hub.freebsd.org (Postfix) with SMTP id 083DE14C99 for ; Tue, 7 Dec 1999 09:47:26 -0800 (PST) (envelope-from pons@gmx.li) Received: (qmail 30230 invoked by uid 0); 7 Dec 1999 17:47:01 -0000 Received: from unknown (HELO gmx.li) (212.38.131.194) by mail2.gmx.net with SMTP; 7 Dec 1999 17:47:01 -0000 Message-ID: <384D4708.A69AF00B@gmx.li> Date: Tue, 07 Dec 1999 19:42:32 +0200 From: pons X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,arabic MIME-Version: 1.0 To: freebsd-net@FreeBSD.org Subject: WAN Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I need information about this subject: "Requirments and Design for WAN" any input would be really appreciated. -- pons@gmx.li To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 7 10:27:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail2.gmx.net (mail2.gmx.net [194.221.183.62]) by hub.freebsd.org (Postfix) with SMTP id 6B5C614DC5 for ; Tue, 7 Dec 1999 10:27:37 -0800 (PST) (envelope-from pons@gmx.li) Received: (qmail 6966 invoked by uid 0); 7 Dec 1999 18:27:32 -0000 Received: from unknown (HELO gmx.li) (212.38.131.194) by mail2.gmx.net with SMTP; 7 Dec 1999 18:27:32 -0000 Message-ID: <384D5089.19F66C27@gmx.li> Date: Tue, 07 Dec 1999 20:23:05 +0200 From: pons X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,arabic MIME-Version: 1.0 To: freebsd-net@FreeBSD.org Subject: Central Server Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I would like to setup a central server for our Banking system (huge dyn. data). The 2x machines contain the following: . 2 Motorola 604e RISC CPU . 1 MB of level 2 cache memory . 256 MB central memory . 1x 2GB SCSI disk, designed to serve as a boot disk and hold the OS . 6x 4GB SCSI disks, designed to hold database and other data requred by the Company . 3x SCSI host adapters, 2x of which are ultra-Wide SCSI3 adapters 40MB/s and the third a Wide SCSI 2 adapters 20MB/s . 1x 8mm VDAT tape, 12/24 GB tape capacity, to be used for back up and software installation and updates . 2x full duplex Fast Ethernet adapters 100Mbps The 2 sets of 6x 4GB disks are shared between the 2 machines using RAID 1. Would the 2 servers do the task, or should i rewrite the Hardware application of the 2 machines? -- pons@gmx.li To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 7 13:31:11 1999 Delivered-To: freebsd-net@freebsd.org Received: from smtp.tsi-net.com (smtp.tsi-net.com [207.202.145.135]) by hub.freebsd.org (Postfix) with ESMTP id BF59814E73 for ; Tue, 7 Dec 1999 13:31:09 -0800 (PST) (envelope-from james3838@tsi-net.com) Received: from mins05 ([131.107.88.65]) by smtp.tsi-net.com (8.9.1/8.9.1) with SMTP id NAA05059 for ; Tue, 7 Dec 1999 13:31:08 -0800 (PST) Message-ID: <01b501bf40fa$25766120$41586b83@mins05> From: "James Webster" To: Subject: IP Nat problems Date: Tue, 7 Dec 1999 13:28:57 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.4200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.4200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just realized I was asking this question on the wrong mailing list. I'm having problems getting NAT working for a slowlink test I'm setting up. I'm more familiar with NAT on netBSD, but for some reasone the driver for my nic wouldn't work in netBSD. I currently have firewall, gateway and nat enabled. This is my scenario: 172.30.224.9 (ex0) is the address that machines will connect to on port 80. All of those connections need to be redirected to 10.0.0.2 port 80 through 10.0.0.1 (ppp0). IPnat would be: rdr ex0 172.30.224.9/32 port 80 -> 10.0.0.2 port 80 natd I have: redirect_port tcp 10.0.0.2:80 172.30.224.9:80 I also added: redirect_port tcp 10.0.0.2:23 172.30.224.9:23 and tried to telnet to the box through 172.30.224.9. The local telnetd server answered indicating that Nat is not redirecting the ports. I may be missing some configuration settings though. Any help troubleshooting would be appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 7 14:27:17 1999 Delivered-To: freebsd-net@freebsd.org Received: from smtp.tsi-net.com (smtp.tsi-net.com [207.202.145.135]) by hub.freebsd.org (Postfix) with ESMTP id 6F1AB14E4A for ; Tue, 7 Dec 1999 14:27:14 -0800 (PST) (envelope-from james3838@tsi-net.com) Received: from mins05 ([131.107.88.65]) by smtp.tsi-net.com (8.9.1/8.9.1) with SMTP id OAA05127 for ; Tue, 7 Dec 1999 14:27:12 -0800 (PST) Message-ID: <01cf01bf4101$fa387540$41586b83@mins05> From: "James Webster" To: Subject: Re: IP Nat problems Date: Tue, 7 Dec 1999 14:25:00 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.4200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.4200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Did some more digging and found a problem, but don't know the solution - /sbin/ipfw add divert natd all from any to any via ex0 0000 divert 868 ip from any to any via ex0 ip_fw_ctl: invalid command ipfw: setsockopt(IP_FW_ADD): Invalid argument ----- Original Message ----- From: "James Webster" To: Sent: Tuesday, December 07, 1999 1:28 PM Subject: IP Nat problems > I just realized I was asking this question on the wrong mailing list. I'm > having problems getting NAT working for a slowlink test I'm setting up. I'm > more familiar with NAT on netBSD, but for some reasone the driver for my nic > wouldn't work in netBSD. > > I currently have firewall, gateway and nat enabled. This is my scenario: > > 172.30.224.9 (ex0) is the address that machines will connect to on port 80. > All of those connections need to be redirected to 10.0.0.2 port 80 through > 10.0.0.1 (ppp0). > > IPnat would be: rdr ex0 172.30.224.9/32 port 80 -> 10.0.0.2 port 80 > natd I have: redirect_port tcp 10.0.0.2:80 172.30.224.9:80 > I also added: redirect_port tcp 10.0.0.2:23 172.30.224.9:23 > and tried to telnet to the box through 172.30.224.9. The local telnetd > server answered indicating that Nat is not redirecting the ports. I may be > missing some configuration settings though. Any help troubleshooting would > be appreciated. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 7 19:31:15 1999 Delivered-To: freebsd-net@freebsd.org Received: from eembox.ee.ncku.edu.tw (eembox.ee.ncku.edu.tw [140.116.72.15]) by hub.freebsd.org (Postfix) with ESMTP id D7CAE154CE for ; Tue, 7 Dec 1999 19:30:30 -0800 (PST) (envelope-from ckwen@eembox.ee.ncku.edu.tw) Received: (from ckwen@localhost) by eembox.ee.ncku.edu.tw (8.9.1a/8.9.1) id LAA09166 for freebsd-net@freebsd.org; Wed, 8 Dec 1999 11:24:54 +0800 (CST) From: ckwen Message-Id: <199912080324.LAA09166@eembox.ee.ncku.edu.tw> Subject: fiber network adapter ? To: freebsd-net@freebsd.org Date: Wed, 8 Dec 1999 11:24:54 +0800 (CST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Does anyone know freebsd 3.3 support fiber ethernet card ? For instance, DFE-500FX ? Regards, Cheng-Kang Wen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 7 19:40:45 1999 Delivered-To: freebsd-net@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id D8EBA14EAD for ; Tue, 7 Dec 1999 19:40:43 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id TAA28880; Tue, 7 Dec 1999 19:39:12 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id TAA16864; Tue, 7 Dec 1999 19:39:11 -0800 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA00437; Tue, 7 Dec 99 19:39:06 PST Message-Id: <384DD2FB.497D7637@softweyr.com> Date: Tue, 07 Dec 1999 20:39:39 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: ckwen Cc: freebsd-net@FreeBSD.ORG Subject: Re: fiber network adapter ? References: <199912080324.LAA09166@eembox.ee.ncku.edu.tw> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ckwen wrote: > > Hello, > > Does anyone know freebsd 3.3 support fiber ethernet card ? > For instance, DFE-500FX ? wes@homer$ cd /usr/src/sys/pci wes@homer$ grep -i fddi *.c if_fpa.c: * DEC PDQ FDDI Controller; code for BSD derived operating systems if_fpa.c: * This module supports the DEC DEFPA PCI FDDI Controller if_fpa.c: return "Digital DEFPA PCI FDDI Controller"; wes@homer$ man -k fddi fpa(4), fea(4) - Device Drivers for DEC FDDI Controllers Was that really so hard? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 7 19:56:20 1999 Delivered-To: freebsd-net@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id 3D80514F9F for ; Tue, 7 Dec 1999 19:56:18 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id TAA22883; Tue, 7 Dec 1999 19:55:08 -0800 (PST) Message-Id: <199912080355.TAA22883@lestat.nas.nasa.gov> To: Wes Peters Cc: ckwen , freebsd-net@FreeBSD.ORG Subject: Re: fiber network adapter ? Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 07 Dec 1999 19:55:07 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 07 Dec 1999 20:39:39 -0700 Wes Peters wrote: > > Does anyone know freebsd 3.3 support fiber ethernet card ? > > For instance, DFE-500FX ? > > wes@homer$ cd /usr/src/sys/pci > wes@homer$ grep -i fddi *.c > if_fpa.c: * DEC PDQ FDDI Controller; code for BSD derived operating systems > if_fpa.c: * This module supports the DEC DEFPA PCI FDDI Controller > if_fpa.c: return "Digital DEFPA PCI FDDI Controller"; > wes@homer$ man -k fddi > fpa(4), fea(4) - Device Drivers for DEC FDDI Controllers > > Was that really so hard? DFE-500FX isn't an FDDI card. It's a 100base-FX card. He was even quite clear in his message that he was looking for "fiber ethernet". It's probably based on the Tulip (considering that the DFE-500TX was), and should work with the `de' driver in both NetBSD and FreeBSD, and possibly also the `tlp' driver in NetBSD (which is a rewritten-from-scratch unified driver that supports the Tulip and the Tulip clone clips). -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 7 21:57:15 1999 Delivered-To: freebsd-net@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 092CB14E38 for ; Tue, 7 Dec 1999 21:57:12 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id VAA29710; Tue, 7 Dec 1999 21:56:10 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id VAA19563; Tue, 7 Dec 1999 21:56:09 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA03076; Tue, 7 Dec 99 21:56:01 PST Message-Id: <384DF316.26C9B786@softweyr.com> Date: Tue, 07 Dec 1999 22:56:38 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Jason Thorpe Cc: ckwen , freebsd-net@FreeBSD.ORG Subject: Re: fiber network adapter ? References: <199912080355.TAA22883@lestat.nas.nasa.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jason Thorpe wrote: > > DFE-500FX isn't an FDDI card. It's a 100base-FX card. > > He was even quite clear in his message that he was looking for > "fiber ethernet". Er, oops. Sorry, I kind of have FDDI on the brain today. > It's probably based on the Tulip (considering that the DFE-500TX was), > and should work with the `de' driver in both NetBSD and FreeBSD, and > possibly also the `tlp' driver in NetBSD (which is a rewritten-from-scratch > unified driver that supports the Tulip and the Tulip clone clips). According to http://www.megabyte.de/Megabyte/3316.htm it contains a 21140. The `de' driver does indeed support 100Base-FX media: case TULIP_MEDIA_100BASEFX: case TULIP_MEDIA_100BASET4: case TULIP_MEDIA_100BASETX: { So it looks like this card should be a go. Let me know if you need a good switch to plug it into. ;^) Thanks for the "boot to the head" Jason. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 8 3:36:49 1999 Delivered-To: freebsd-net@freebsd.org Received: from smtp.shellnet.co.uk (smtp.shellnet.co.uk [194.129.209.14]) by hub.freebsd.org (Postfix) with ESMTP id 02E9514CB6 for ; Wed, 8 Dec 1999 03:36:45 -0800 (PST) (envelope-from stevenf@shellnet.co.uk) Received: from stevenf (eth2-fw1.bolton.shellnet.co.uk [194.129.209.8]) by smtp.shellnet.co.uk (8.9.3/8.9.1-shellnet.stevenf) with SMTP id LAA06489 for ; Wed, 8 Dec 1999 11:36:44 GMT From: Steven Fletcher Posted-Date: Wed, 8 Dec 1999 11:36:44 GMT To: Subject: Very odd problem with email. Date: Wed, 8 Dec 1999 11:36:43 -0000 Message-ID: <277A0E0FE38ED311A66A00A0C9D43A3D0781F5@data.shellnet.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all; Wonder if anyone can advise here. We have been running sendmail/QPOP now for 3 years on FreeBSD-2.2.5 and have had no big problems untill now. Since the start of this month, a few of our customers have been having problems with their POP3 access - certain emails are just jamming dead. These don't containt any attachments, they're just plaintext emails. When I try to check the mail files over POP3, from certain hosts (shells in the US etc), I can get all the mail messages fine. However some of our customers dial other ISP's in the UK: Netcom UK, Virgin, some have leased lines - they are by no means busy though. From these accounts I can login over POP3, send "RETR 1", and the mail stops being sent at the same charachter, every time - it's 100% reproducible now on 3 UK ISP's trying to access our servers. However from machines based on JAnet (MCC) I am able to pull down the affected mail file with no problem, as I am also able to pull from various machines in the US with success. The same again works perfectly on our local network. I have now tried what I consider to be 'everything' - swapping the mailserver hardware, swapping the POP3 server that we use (tried QPOP & Cucipop - QPOP emails are getting slightly further than those delivered via Cucipop). Running tcpdump on both the affected machines (the mailserver & the external machine) shows that ACK's don't seem to be getting through: 16:42:31.530365 194.129.209.11.pop3 > www5.shellnet.co.uk.4969: P 1590:2928(1338) ack 35 win 17520 (DF) Is repeated at increasing intervals after the file stops. In the last 5 minutes though, I've noticed that the file can't be transferred over FTP either, failing at the same point for the given machines each time. Quick tests are also showing that the file won't work when transferring between an NT machine here and another NT machine at the same location as the test FreeBSD machine. Thus, in the time I've been writing this email, it certainly looks like the problem lies with our upstream provider (UUnet) - they've got 7 people working on it now - but I'm now wondering if anyone here has ever seen such a problem before - it looks like a very descreet problem to me indeed. If anyone can shed *any* light I'd be most appreciative, but could you please reply direct to myself also as I am not subscribed to -net at this address. Many thanks; Steven Fletcher stevenf@shellnet.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 8 6: 4:41 1999 Delivered-To: freebsd-net@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 3E4F315514 for ; Wed, 8 Dec 1999 06:04:26 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id QAA81133; Wed, 8 Dec 1999 16:03:51 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199912081403.QAA81133@zibbi.mikom.csir.co.za> Subject: Re: Very odd problem with email. In-Reply-To: <277A0E0FE38ED311A66A00A0C9D43A3D0781F5@data.shellnet.co.uk> from Steven Fletcher at "Dec 8, 1999 11:36:43 am" To: stevenf@shellnet.co.uk (Steven Fletcher) Date: Wed, 8 Dec 1999 16:03:51 +0200 (SAT) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 > > I have now tried what I consider to be 'everything' - swapping the > mailserver hardware, swapping the POP3 server that we use (tried QPOP & > Cucipop - QPOP emails are getting slightly further than those delivered via > Cucipop). Running tcpdump on both the affected machines (the mailserver & > the external machine) shows that ACK's don't seem to be getting through: > > 16:42:31.530365 194.129.209.11.pop3 > www5.shellnet.co.uk.4969: P > 1590:2928(1338) ack 35 win 17520 (DF) > > Is repeated at increasing intervals after the file stops. One possibility is that the path mtu discovery is getting screwed up somewhere. That may happen if some link have a smaller mtu that your local net and icmp NEEDFRAG packets are blocked. 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 Wed Dec 8 6:31: 0 1999 Delivered-To: freebsd-net@freebsd.org Received: from smtp.shellnet.co.uk (smtp.shellnet.co.uk [194.129.209.14]) by hub.freebsd.org (Postfix) with ESMTP id B3377150D5 for ; Wed, 8 Dec 1999 06:30:48 -0800 (PST) (envelope-from stevenf@shellnet.co.uk) Received: from stevenf (eth2-fw1.bolton.shellnet.co.uk [194.129.209.8]) by smtp.shellnet.co.uk (8.9.3/8.9.1-shellnet.stevenf) with SMTP id OAA16557; Wed, 8 Dec 1999 14:30:23 GMT From: Steven Fletcher Posted-Date: Wed, 8 Dec 1999 14:30:23 GMT To: "'John Hay'" Cc: Subject: RE: Very odd problem with email. Date: Wed, 8 Dec 1999 14:30:21 -0000 Message-ID: <277A0E0FE38ED311A66A00A0C9D43A3D0781F9@data.shellnet.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: <277A0E0FE38ED311A66A00A0C9D43A3D0524C8@data.shellnet.co.uk> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hiya Thanks for the reply. You are somewhat correct.... just 20 minutes ago we recived a phonecall from UUnet who told us what was going on. It was in fact, one of the oddest problems that they've ever seen, caused by many ~'s in the that is being transferred (belive it or not, I've verified this and to my amazements it's true!) - it's just not getting through at the Linx. Thanks for the reply anyhow. Steven Fletcher stevenf@shellnet.co.uk > -----Original Message----- > From: John Hay [mailto:jhay@mikom.csir.co.za] > Sent: 08 December 1999 14:04 > To: Steven Fletcher > Cc: freebsd-net@FreeBSD.ORG > Subject: Re: Very odd problem with email. > > > > > > I have now tried what I consider to be 'everything' - swapping the > > mailserver hardware, swapping the POP3 server that we use > (tried QPOP & > > Cucipop - QPOP emails are getting slightly further than > those delivered via > > Cucipop). Running tcpdump on both the affected machines > (the mailserver & > > the external machine) shows that ACK's don't seem to be > getting through: > > > > 16:42:31.530365 194.129.209.11.pop3 > www5.shellnet.co.uk.4969: P > > 1590:2928(1338) ack 35 win 17520 (DF) > > > > Is repeated at increasing intervals after the file stops. > > One possibility is that the path mtu discovery is getting screwed up > somewhere. That may happen if some link have a smaller mtu that your > local net and icmp NEEDFRAG packets are blocked. > > 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 Wed Dec 8 7:36:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 7523614D47 for ; Wed, 8 Dec 1999 07:36:10 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id KAA29987; Wed, 8 Dec 1999 10:36:20 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199912081536.KAA29987@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Steven Fletcher Cc: "'John Hay'" , net@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Very odd problem with email. References: <277A0E0FE38ED311A66A00A0C9D43A3D0781F9@data.shellnet.co.uk> In-reply-to: Your message of "Wed, 08 Dec 1999 14:30:21 GMT." <277A0E0FE38ED311A66A00A0C9D43A3D0781F9@data.shellnet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Dec 1999 10:36:19 -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hiya > > Thanks for the reply. You are somewhat correct.... just 20 minutes ago we > recived a phonecall from UUnet who told us what was going on. It was in > fact, one of the oddest problems that they've ever seen, caused by many ~'s > in the that is being transferred (belive it or not, I've verified this and > to my amazements it's true!) - it's just not getting through at the Linx. I've run into pattern sensitivity problems like this before. This is likely caused by a marginal or mis-provisioning access circuit. The encoding of '~' is 0x7e. There could be a PPP implementation problem since I think that's the async "flag" character which need to be byte-stuffed. On a leased line circuit, you might be provoking a 1's density problem on the circuit. If the CSU/DSU is configured to assume a B8ZS (rather than AMI) provisioned T-1, then it won't do anything special in the DSU when framing up the data to ensure adequate 1's density. If the circuit is actually provisioned as AMI, this could cause problems. Take a look at the CSU/DSU statistics at either end if possible, and look for line code violations, framing loss or frame slips as you try to deliver that kind of message. Depending on the direction, you might not have access to the CSU/DSU (e.g., the provider's end). louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 8 10:22:47 1999 Delivered-To: freebsd-net@freebsd.org Received: from tomts1-srv.bellnexxia.net (tomts1.bellnexxia.net [209.226.175.139]) by hub.freebsd.org (Postfix) with ESMTP id C8D3F15773 for ; Wed, 8 Dec 1999 10:20:22 -0800 (PST) (envelope-from wun@globalserve.net) Received: from globalserve.net ([216.209.56.91]) by tomts2-srv.bellnexxia.net (InterMail vM.4.01.02.07 201-229-116-107) with ESMTP id <19991205011120.BZHR29836.tomts2-srv.bellnexxia.net@globalserve.net> for ; Sat, 4 Dec 1999 20:11:20 -0500 Message-ID: <3849BECF.79B5E8BB@globalserve.net> Date: Sat, 04 Dec 1999 20:24:32 -0500 From: Felix Wun Organization: . X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: netgraph 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 currently having trouble installing netgraph for my freebsd3.3 release. i did a fresh install to get freebsd3.3 release to prepear for installing netgraph by installing "bin" and "src->sys" packages. after i untar netgraph, and follow the inistructions patch -I < netgraph-patch.3.3 it doesnt seem to work.... (it keeps askin me what file i want to patch, and if i just hit enter, ask if i want to skip that file... then when done, give me some *.rej *.rej.org files) anybody can help me with abouve problem? all i want is the pppoe application, is there any easier way i can get that working? do i have to have the freebsd4 current to be able to use netgraph? is there any other programs out there that support pppoe for freebsd? and i hate bell adsl... make me go through so much trouble... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 8 14:48:22 1999 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 832EB151D7 for ; Wed, 8 Dec 1999 14:48:11 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id OAA53677; Wed, 8 Dec 1999 14:48:09 -0800 (PST) From: Archie Cobbs Message-Id: <199912082248.OAA53677@bubba.whistle.com> Subject: Re: netgraph In-Reply-To: <3849BECF.79B5E8BB@globalserve.net> from Felix Wun at "Dec 4, 1999 08:24:32 pm" To: wun@globalserve.net (Felix Wun) Date: Wed, 8 Dec 1999 14:48:09 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Felix Wun writes: > i m currently having trouble installing netgraph for my freebsd3.3 > release. i did a fresh install to get freebsd3.3 release to prepear for > installing netgraph by installing "bin" and "src->sys" packages. after i > untar netgraph, and follow the inistructions > patch -I < netgraph-patch.3.3 > it doesnt seem to work.... > (it keeps askin me what file i want to patch, and if i just hit enter, > ask if i want to skip that file... then when done, give me some *.rej > *.rej.org files) > anybody can help me with abouve problem? > all i want is the pppoe application, is there any easier way i can get > that working? > do i have to have the freebsd4 current to be able to use netgraph? > is there any other programs out there that support pppoe for freebsd? > and i hate bell adsl... make me go through so much trouble... You don't need to patch anything anymore because netgraph is now part of -stable and -current.. so use CVS if you can. Otherwise, the simplest thing is probably just to wait until FreeBSD 3.4 is released, which is happening soon. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 8 15:40:23 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 488D4152AD for ; Wed, 8 Dec 1999 15:40:20 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA68337; Wed, 8 Dec 1999 15:40:09 -0800 (PST) Date: Wed, 8 Dec 1999 15:40:08 -0800 (PST) From: Julian Elischer To: Archie Cobbs Cc: Felix Wun , freebsd-net@FreeBSD.ORG Subject: Re: netgraph In-Reply-To: <199912082248.OAA53677@bubba.whistle.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 You can load the latest 3.x SNAPSHOT and do an 'upgrade' and get it.. If you do want to do it from 3.3.... On Wed, 8 Dec 1999, Archie Cobbs wrote: > Felix Wun writes: > > i m currently having trouble installing netgraph for my freebsd3.3 > > release. i did a fresh install to get freebsd3.3 release to prepear for > > installing netgraph by installing "bin" and "src->sys" packages. after i > > untar netgraph, and follow the inistructions > > patch -I < netgraph-patch.3.3 > > it doesnt seem to work.... > > (it keeps askin me what file i want to patch, and if i just hit enter, > > ask if i want to skip that file... then when done, give me some *.rej > > *.rej.org files) sounds like you are cd'd to the wrong place? > > anybody can help me with abouve problem? > > all i want is the pppoe application, is there any easier way i can get > > that working? > > do i have to have the freebsd4 current to be able to use netgraph? > > is there any other programs out there that support pppoe for freebsd? > > and i hate bell adsl... make me go through so much trouble... There is a slow userland pppoe front-end. but i don't recommend it. the patch file you have is in fact old. it doesn't have the pppoe module, nor does it have the pppoe mods to the ppp daemon. You need the following: /usr/src/lib/libnetgraph /usr/src/sys /usr/src/usr.sbin/ppp /usr/src/share/examples/ppp mkdir /usr/include/netgraph cp /sys/netgraph/*.h /usr/include/netgraph cp /usr/src/lib/libnetgraph/netgraph.h /usr/include cd /usr/lib/lib/libnetgraph make make install cd /sys (make your kernel with options NETGRAPH NETGRAPH_SOCKET and NETGRPAH_PPPOE) cd /usr/src/usr.sbin/ppp make; make install Follow examples > > You don't need to patch anything anymore because netgraph is now > part of -stable and -current.. so use CVS if you can. > > Otherwise, the simplest thing is probably just to wait until > FreeBSD 3.4 is released, which is happening soon. > > -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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 8 15:41:29 1999 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 4224514F55; Wed, 8 Dec 1999 15:41:25 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id PAA54148; Wed, 8 Dec 1999 15:41:24 -0800 (PST) From: Archie Cobbs Message-Id: <199912082341.PAA54148@bubba.whistle.com> Subject: New mpd with netgraph and PPTP To: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Date: Wed, 8 Dec 1999 15:41:24 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (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 A new version of 'mpd', a multi-link PPP daemon, is available as a beta release from Whistle Communications under the Whistle license (BSD style). * This new version is completely netgraph(4) based, which means that all of the negotiation protocols (IPCP, LCP, etc) are handled in user-land, while all data transmission, compression, encryption, etc. is handled strictly in the kernel. This approach combines the configuration flexibility of a user-mode PPP daemon with the speed of a kernel-only PPP daemon, not to mention the wide device type and protocol support of netgraph. * This version also includes support for the Point-to-Point Tunneling Protocol (PPTP), in both client "dial-in" mode and LAN-LAN VPN, and is compatible with Microsoft's Dial-Up Networking VPN adapter. To get the new mpd: 1. Update your -stable or -current system from CVS (ie, today's!) and make world (or at least build and install a new kernel, kernel includes, netgraph modules, and libnetgraph). 2. Run pkg_delete on any existing mpd port on your machine 3. Blow away /usr/ports/net/mpd, and replace it with this: ftp://ftp.whistle.com/pub/archie/mpd/port.tgz 4. Build and install the new port. Any bug reports, suggestions, etc. are greatly appreciated. I'd also be interested to hear if anyone does any speed comparisions between this version of mpd and other FreeBSD PPP implementations. Cheers, -Archie PS: We also have an MPPE (Microsoft Point-to-Point encryption) implementation (as a netgraph module). This allows Microsoft clients' PPTP connections to be encrypted, though the security of MPPE is not very strong. However, it includes RC4, which is patented, so you must get your own implementation of RC4 (legally!) and compile the node yourself. Let me know by email if you're interested in trying this out too. PPS: Does not understand PPPoE yet.. use 'ppp' for that. ___________________________________________________________________________ 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 Dec 9 0:42:58 1999 Delivered-To: freebsd-net@freebsd.org Received: from esebh03nok.ntc.nokia.com (esebh03nok.ntc.nokia.com [131.228.118.244]) by hub.freebsd.org (Postfix) with ESMTP id 12D231515E for ; Thu, 9 Dec 1999 00:42:55 -0800 (PST) (envelope-from yu.shi@nokia.com) Received: by esebh03nok with Internet Mail Service (5.5.2650.10) id ; Thu, 9 Dec 1999 10:30:31 +0200 Message-ID: <95A2D1413F29D311B3450008C773628968C704@beeis03nok> From: yu.shi@nokia.com To: freebsd-net@FreeBSD.ORG Subject: Ethernet driver Date: Thu, 9 Dec 1999 10:30:30 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.10) Content-Type: text/plain; charset="gb2312" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I'm digging into ethernet driver. where can I find the DEC DC21040 chip user's manual OR tulip Network card specification? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 9 8:42:49 1999 Delivered-To: freebsd-net@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 4054114F9E for ; Thu, 9 Dec 1999 08:42:45 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id IAA29725; Thu, 9 Dec 1999 08:42:35 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id IAA14625; Thu, 9 Dec 1999 08:42:34 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA27155; Thu, 9 Dec 99 08:42:30 PST Message-Id: <384FDC21.F600D4BE@softweyr.com> Date: Thu, 09 Dec 1999 09:43:13 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: yu.shi@nokia.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: Ethernet driver References: <95A2D1413F29D311B3450008C773628968C704@beeis03nok> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org yu.shi@nokia.com wrote: > > Hello, > > I'm digging into ethernet driver. > where can I find the DEC DC21040 chip user's manual OR tulip Network card > specification? http://www.developer.intel.com/ -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 9 11:38:56 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.snowcrest.net (mail.snowcrest.net [216.102.43.227]) by hub.freebsd.org (Postfix) with ESMTP id 7E8251515C for ; Thu, 9 Dec 1999 11:38:54 -0800 (PST) (envelope-from djewett@snowcrest.net) Received: from ws2494 (stkppB051.snowcrest.net [209.78.170.51]) by mail.snowcrest.net (8.9.0/8.9.0) with SMTP id LAA02038 for ; Thu, 9 Dec 1999 11:38:53 -0800 (PST) Message-ID: <000801bf4275$1b93ef70$0164a8c0@ws2494> From: "dj" To: Subject: DNS problems.... Date: Thu, 9 Dec 1999 10:41:49 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Using 3.1-R setup as a DNS forwarder only, it has been working for years now, our problem is now for some reason when we try to query it from a workstation or from nslookup on the box itself we get "Cant find server name for 127.0.0.1: " We added two DNS forwder entires into the named.conf file and now we get this error... We are using a bogus dmain name and bogus host names and have all along. What causes this error.. I put several entries into the hosts file for this address and several host names and aliases but no success.. Any help would be greatly appreciated!! thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 9 19:49:32 1999 Delivered-To: freebsd-net@freebsd.org Received: from esebh02nok.ntc.nokia.com (esebh02nok.ntc.nokia.com [131.228.118.151]) by hub.freebsd.org (Postfix) with ESMTP id D58781523C for ; Thu, 9 Dec 1999 19:49:28 -0800 (PST) (envelope-from yu.shi@nokia.com) Received: by esebh02nok with Internet Mail Service (5.5.2650.10) id ; Fri, 10 Dec 1999 05:49:27 +0200 Message-ID: <95A2D1413F29D311B3450008C773628968CAB3@beeis03nok> From: yu.shi@nokia.com To: wes@softweyr.com Cc: freebsd-net@FreeBSD.ORG Subject: RE: Ethernet driver Date: Fri, 10 Dec 1999 05:46:13 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.10) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry, I can not find it on developer.intel.com.(not www.developer.intel.com) Would u make it a little specific ? Thanks! -----Original Message----- From: EXT Wes Peters [mailto:wes@softweyr.com] Sent: 09 December, 1999 18:43 To: yu.shi@nokia.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: Ethernet driver yu.shi@nokia.com wrote: > > Hello, > > I'm digging into ethernet driver. > where can I find the DEC DC21040 chip user's manual OR tulip Network card > specification? http://www.developer.intel.com/ -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 9 22: 4:18 1999 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (dustdevil.waterspout.com [208.13.60.151]) by hub.freebsd.org (Postfix) with ESMTP id 7382914FE2; Thu, 9 Dec 1999 22:04:14 -0800 (PST) (envelope-from csg@waterspout.com) Received: by dustdevil.waterspout.com (Postfix, from userid 1000) id CB18D59; Fri, 10 Dec 1999 01:07:31 -0500 (EST) Received: from waterspout.com (localhost [127.0.0.1]) by dustdevil.waterspout.com (Postfix) with ESMTP id 63774BAB6; Fri, 10 Dec 1999 01:07:31 -0500 (EST) To: "Jordan K. Hubbard" Cc: wollman@lcd.mit.edu, wpaul@freebsd.org, freebsd-net@freebsd.org Subject: Re: Who's using 802.1Q VLAN Support? In-Reply-To: Your message of "Mon, 06 Dec 1999 10:45:50 PST." <2053.944505950@zippy.cdrom.com> From: csg@waterspout.com (C. Stephen Gunn) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <60440.944806045.1@waterspout.com> Date: Fri, 10 Dec 1999 01:07:26 -0500 Message-Id: <19991210060731.CB18D59@dustdevil.waterspout.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 06 Dec 1999 10:45:50 PST, "Jordan K. Hubbard" wrote: > Well, given that we're coming up on a deadline here, I may just > bring them in without review unless you can take a look at them > in a timely fashion. Jordan, With lots of further testing, these patches do defintely help. I still can't reliably debug an mbuf crash that happens within 5-10 minutes of bringing up the vlans with some traffic though. All the backtrace tells me is that someone smashed the buffer. At the very least, I'd like to see the ability to compile a kernel with ti0 and vlan turned on in 3.4-RELEASE. A kernel config that doesn't link is pretty embarassing. The ifconfig support is required as well to actually configure and use the vlan devices. I understand that 3.0 was -CURRENT (and bleeding edge) when this was originally committed. (Garrett's work in progress). Bill Paul, who's been graciously chatting with me on IRC about these issues, added some hardware tag support (also incomplete). Now it's in the -STABLE branch, which it ain't. My patches do fix problems in the code, but it's not functional enough for -STABLE IMNSHO. (No Offense to Bill & Garrett's free-time-constraied, and appreciated efforts) If you're not willing to commit (which I fully understand), then I recommend removal if_vlan.c and the hooks in ti0 from -STABLE, until it's a little less volatile. - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc. Email: csg@waterspout.com 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Dec 10 14: 5:36 1999 Delivered-To: freebsd-net@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 3F22C14A10 for ; Fri, 10 Dec 1999 14:05:32 -0800 (PST) (envelope-from pekkas@netcore.fi) Received: from localhost (pekkas@localhost) by netcore.fi (8.9.3/8.9.3) with ESMTP id AAA11693 for ; Sat, 11 Dec 1999 00:05:30 +0200 Date: Sat, 11 Dec 1999 00:05:30 +0200 (EET) From: Pekka Savola To: freebsd-net@freebsd.org Subject: FreeBSD ipsec VPNs / pipsecd problems. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, This might be related to freebsd-ports too. First, I'd like to know about experiences using FreeBSD for IPSEC VPN's. There seems to be two current alternatives: Kame and pipsecd. A port from OpenBSD seems to be outdated. Kame is a big package, but doesn't probably fit well in a dynamic environment, where patches and sourcecodes are updated daily, make world done now and then, etc. In the other hand, pipsecd looked pretty tiny and neat. Too bad its documentation is still next to nonexistant. I decided to try this to create a VPN between my Linux box (FreeS/WAN 1.1) and this (FreeBSD 3.3-RELEASE). This box had successfully been the other end of the VPN when it still ran Linux. I got into problems using pipsecd. More of this below. Has anyone gotten pipsecd to work properly? Has anyone managed to interoperate it with other VPN implementations ? Are there any other VPN implementations to try? Second, I got loads of warnings when compiling the pipsecd port. These might relate to the non-operability of this.: ------ ===> Building for pipsecd-19991014 gcc -Wall -I/usr/local/include/openssl -I/usr/local/include -g -o pipsecd tunip.c -L/usr/local/lib -lcrypto -lRSAglue -lrsaref -DFILE_PREFIX=\"/usr/local\" tunip.c:367: warning: initialization from incompatible pointer type tunip.c:367: warning: initialization from incompatible pointer type tunip.c:368: warning: initialization from incompatible pointer type tunip.c:372: warning: initialization from incompatible pointer type tunip.c:372: warning: initialization from incompatible pointer type tunip.c:373: warning: initialization from incompatible pointer type tunip.c:377: warning: initialization from incompatible pointer type tunip.c:377: warning: initialization from incompatible pointer type tunip.c:378: warning: initialization from incompatible pointer type tunip.c: In function `parse_secret': tunip.c:932: warning: int format, pointer arg (arg 3) tunip.c:944: warning: int format, pointer arg (arg 3) tunip.c: In function `config_read': tunip.c:980: warning: passing arg 1 of `strsep' from incompatible pointer type tunip.c:984: warning: passing arg 1 of `strsep' from incompatible pointer type tunip.c:1024: warning: passing arg 1 of `strsep' from incompatible pointer type tunip.c:1142: warning: passing arg 1 of `strsep' from incompatible pointer type tunip.c: In function `my_des_cbc_encrypt': tunip.c:2009: warning: passing arg 5 of `des_cbc_encrypt' from incompatible pointer type tunip.c: In function `my_des_cbc_decrypt': tunip.c:2021: warning: passing arg 5 of `des_cbc_encrypt' from incompatible pointer type tunip.c: In function `my_des_setkey': tunip.c:2032: warning: passing arg 1 of `des_set_key' from incompatible pointer type tunip.c: In function `my_des3_cbc_encrypt': tunip.c:2041: warning: passing arg 7 of `des_ede3_cbc_encrypt' from incompatible pointer type tunip.c: In function `my_des3_cbc_decrypt': tunip.c:2049: warning: passing arg 7 of `des_ede3_cbc_encrypt' from incompatible pointer type tunip.c: In function `my_des3_setkey': tunip.c:2057: warning: passing arg 1 of `des_set_key' from incompatible pointer type tunip.c:2059: warning: passing arg 1 of `des_set_key' from incompatible pointer type tunip.c:2061: warning: passing arg 1 of `des_set_key' from incompatible pointer type ------ I remember seeing similar errors (des_ede3_cbc_encrypt) when some Linux application was designed for SSLeay but compiled against OpenSSL. Has anyone else gotten into troubles like this? RSAref and OpenSSL 0.94 are installed as they should be. The actual non-operativity occurs as follows: I have disabled ESP etc. in the configuration to make this as simple as possible: sa ipah spi=0x1000 auth=hmac-md5-96 akey=d0-------- key ---------------b8 sa ipah spi=0x1000 auth=hmac-md5-96 akey=d0-------- key ---------------b8 dest=bbb.bbb.bbb.bbb if /dev/tun0 local_spi=0x1000 remote_spi=0x1000 Configured the interface and the route: ifconfig tun0 10.0.0.1 10.0.0.2 mtu 1440 route add -host 10.0.0.2 10.0.0.1 -interface As a result, when I ping the other end's virtual address, I can see with tcpdump that packets are sent and are received: [pinger] 23:56:39.772813 aaa.aaa.aaa.aaa > bbb.bbb.bbb.bbb : ip-proto-51 108 [pingee] 23:58:20.970713 aaa.aaa.aaa.aaa > bbb.bbb.bbb.bbb : ip-proto-51 108 [dates are off by purpose] The same occurs if the situation is reversed. However, it seems like neither host can open each other's AH'ed packets. Could this be caused by wrong SPI's? Are there any good diagnostic utilities to see whether ipsec programs actually got those but discarded them because of a wrong key, wrong encryption, or such ? HTH, Pekka Savola Btw, I just started using FreeBSD yesterday, so be gentle :) Also, I'm not subscribing to this list, so if anything comes up, please CC it to me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Dec 10 15:30:51 1999 Delivered-To: freebsd-net@freebsd.org Received: from netcom.com (netcom1.netcom.com [199.183.9.101]) by hub.freebsd.org (Postfix) with ESMTP id E91B5153C3 for ; Fri, 10 Dec 1999 15:30:45 -0800 (PST) (envelope-from stanb@netcom.com) Received: (from stanb@localhost) by netcom.com (8.9.3/8.9.3) id PAA03975 for freebsd-net@FreeBSD.ORG; Fri, 10 Dec 1999 15:30:44 -0800 (PST) From: Stan Brown Message-Id: <199912102330.PAA03975@netcom.com> Subject: New computer won't talk to cablemodem To: freebsd-net@FreeBSD.ORG (FreeBSD Networking) Date: Fri, 10 Dec 1999 18:30:44 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] 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 I am in the process of setting up a "new" computer to use as a gatewy to the world for my home network. I am presently accessing the world through an @home cablemodem via a FreeBSD 2.2.8 machine, and natd. Works great. I have scrounged up an old 486 to take this machines place. I built 3.3-STABLE on it, and started trying to make a similar setup work. Unfortunately I can't seem to get as far as pinging the cabemodem providers gateway machine :-( I must be doing something dumbe here. Here is what I see: Script started on Fri Dec 10 18:17:24 1999 netgate# ifconfig -a ed0: flags=8843 mtu 1500 inet 205.159.77.201 netmask 0xffffff00 broadcast 205.159.77.255 ether 00:80:ad:08:2b:80 ed1: flags=8843 mtu 1500 inet 24.6.61.166 netmask 0xffffff00 broadcast 24.6.61.255 ether 00:40:05:72:e8:7a tun0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 ppp0: flags=8010 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 ds0: flags=8008 mtu 65532 netgate# netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 205.159.77.234 UGSc 1 0 ed0 24.6.61/24 link#2 UC 0 0 ed1 24.6.61.255 ff:ff:ff:ff:ff:ff UHLWb 0 2 ed1 127.0.0.1 127.0.0.1 UH 1 32 lo0 205.159.77 link#1 UC 0 0 ed0 205.159.77.232 8:0:9:78:ea:56 UHLW 0 0 ed0 1118 205.159.77.234 0:80:ad:7:f9:75 UHLW 2 0 ed0 1130 205.159.77.236 8:0:9:92:55:11 UHLW 1 55 ed0 1188 205.159.77.239 8:0:9:10:6:a5 UHLW 0 0 ed0 1118 205.159.77.240 8:0:9:11:e5:a UHLW 0 3 ed0 1135 205.159.77.255 ff:ff:ff:ff:ff:ff UHLWb 1 2 ed0 netgate# arp -a ^C netgate# arp -an ? (24.6.61.255) at ff:ff:ff:ff:ff:ff permanent [ethernet] ? (205.159.77.232) at 8:0:9:78:ea:56 [ethernet] ? (205.159.77.234) at 0:80:ad:7:f9:75 [ethernet] ? (205.159.77.236) at 8:0:9:92:55:11 [ethernet] ? (205.159.77.239) at 8:0:9:10:6:a5 [ethernet] ? (205.159.77.240) at 8:0:9:11:e5:a [ethernet] ? (205.159.77.255) at ff:ff:ff:ff:ff:ff permanent [ethernet] netgate# tcpdump -i ed1 tcpdump: listening on ed1 18:18:29.270832 0:10:7b:ed:bb:3a 0:10:7b:ed:bb:3a loopback 60: 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 18:18:39.202007 0:10:7b:ed:bb:3a 0:10:7b:ed:bb:3a loopback 60: 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 18:18:40.444554 0:10:7b:ed:bb:3a > 1:0:c:cc:cc:cc sap aa ui/C len=296 b000 0100 0853 4f48 4f00 0200 0800 0000 0000 0300 0d45 7468 6572 6e65 7430 0004 0008 0000 0002 0005 00e6 43 18:18:49.133081 0:10:7b:ed:bb:3a 0:10:7b:ed:bb:3a loopback 60: 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 18:18:50.457849 arp who-has 24.6.61.1 tell cc69528-a.mtpls1.sc.home.com 18:18:50.471223 arp reply 24.6.61.1 is-at 0:50:3e:e2:10:40 18:18:50.471836 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:50.483070 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:50.483532 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:51.462580 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:51.498028 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:51.498590 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:52.472213 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:52.484483 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:52.484968 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:53.482327 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:53.494285 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:53.494761 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:54.492188 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:54.503960 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:54.504433 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:55.502202 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:55.513625 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:55.514100 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:56.512361 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:56.525432 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:56.525919 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:57.522376 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:57.534981 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:57.535461 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:58.532254 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:58.544974 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:58.545444 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:59.064220 0:10:7b:ed:bb:3a 0:10:7b:ed:bb:3a loopback 60: 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 18:18:59.542392 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:59.554555 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:59.555052 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:00.552362 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:00.563595 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:00.564111 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:01.562479 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:01.573677 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:01.574175 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:02.572310 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:02.585841 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:02.586317 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:03.582316 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:03.596282 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:03.596753 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:04.592452 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:04.604005 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:04.604479 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:05.602498 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:05.729409 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:05.729890 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:06.612610 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:06.647877 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:06.648446 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:07.622379 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:07.635591 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:07.636071 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:08.632406 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:08.645040 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:08.645515 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:09.075354 0:10:7b:ed:bb:3a 0:10:7b:ed:bb:3a loopback 60: 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 18:19:09.642513 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:09.657203 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:09.657683 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:10.652479 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:10.664401 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:10.664990 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:11.662454 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:11.674152 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:11.674631 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:12.672466 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:12.683606 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:12.684081 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:13.684169 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:13.695409 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:13.695888 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:14.694244 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:14.707283 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:14.707765 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:15.702689 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:15.714665 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:15.715198 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:16.712998 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:16.723866 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:16.724419 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:17.722770 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:17.733463 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:17.733968 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:18.732666 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:18.745474 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:18.745967 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:19.007319 0:10:7b:ed:bb:3a 0:10:7b:ed:bb:3a loopback 60: 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 18:19:19.327740 cc69528-a.mtpls1.sc.home.com.who > 24.6.61.255.who: udp 108 18:19:19.328111 cc69528-a.mtpls1.sc.home.com.who > 24.6.61.255.who: udp 108 18:19:19.742667 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:19.774964 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:19.775479 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:20.752812 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:20.764995 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:20.765496 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:21.762881 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:21.774269 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:21.774784 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:22.772740 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:22.784133 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:22.784625 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:23.782706 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:23.796475 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:23.796961 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:24.792970 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:24.805616 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:24.806108 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:25.802859 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:25.814742 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:25.815230 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a ^C 119 packets received by filter 0 packets dropped by kernel netgate# arp -a ^C netgate# arp -an ? (24.6.61.1) at 0:50:3e:e2:10:40 [ethernet] ? (24.6.61.255) at ff:ff:ff:ff:ff:ff permanent [ethernet] ? (205.159.77.232) at 8:0:9:78:ea:56 [ethernet] ? (205.159.77.234) at 0:80:ad:7:f9:75 [ethernet] ? (205.159.77.236) at 8:0:9:92:55:11 [ethernet] ? (205.159.77.239) at 8:0:9:10:6:a5 [ethernet] ? (205.159.77.240) at 8:0:9:11:e5:a [ethernet] ? (205.159.77.255) at ff:ff:ff:ff:ff:ff permanent [ethernet] netgate# ping 24.6.61.1 PING 24.6.61.1 (24.6.61.1): 56 data bytes ^C --- 24.6.61.1 ping statistics --- 6 packets transmitted, 0 packets received, 100% packet loss netgate# traceroute 24.6.61.1 traceroute to 24.6.61.1 (24.6.61.1), 30 hops max, 40 byte packets 1 * * * ^C netgate# ^Dexit Script done on Fri Dec 10 18:20:36 1999 As you can see the new machine is asking for an arp of the gateway, and it apperars to be making it into the arp table. Still ping doesn;t work. Simply removing the cable from the "new" machine and puting it back in the old one causes pings from it to start working. I am at a loss here. Has anyone got any troubleshooting advice for me? Thanks. -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Dec 10 15:55:35 1999 Delivered-To: freebsd-net@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 7120514C0A for ; Fri, 10 Dec 1999 15:55:31 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA83746; Fri, 10 Dec 1999 18:55:28 -0500 (EST) (envelope-from bsdx@looksharp.net) Date: Fri, 10 Dec 1999 18:55:28 -0500 (EST) From: Adam To: Stan Brown Cc: FreeBSD Networking Subject: Re: New computer won't talk to cablemodem In-Reply-To: <199912102330.PAA03975@netcom.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 If you used a different nic, did you reset or power off/on the cable modem to flush the old mac address of the nic? You said: I am in the process of setting up a "new" computer to use as a gatewy to the world for my home network. I am presently accessing the world through an @home cablemodem via a FreeBSD 2.2.8 machine, and natd. Works great. I have scrounged up an old 486 to take this machines place. I built 3.3-STABLE on it, and started trying to make a similar setup work. Unfortunately I can't seem to get as far as pinging the cabemodem providers gateway machine :-( I must be doing something dumbe here. Here is what I see: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Dec 10 16: 9:11 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 6F18414CAD for ; Fri, 10 Dec 1999 16:09:09 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id QAA43879; Fri, 10 Dec 1999 16:09:06 -0800 (PST) Date: Fri, 10 Dec 1999 16:09:04 -0800 (PST) From: Julian Elischer To: Stan Brown Cc: FreeBSD Networking Subject: Re: New computer won't talk to cablemodem In-Reply-To: <199912102330.PAA03975@netcom.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 On Fri, 10 Dec 1999, Stan Brown wrote: > I am in the process of setting up a "new" computer to use as a gatewy > to the world for my home network. > > I am presently accessing the world through an @home cablemodem via a > FreeBSD 2.2.8 machine, and natd. Works great. > > I have scrounged up an old 486 to take this machines place. I built > 3.3-STABLE on it, and started trying to make a similar setup work. > Unfortunately I can't seem to get as far as pinging the cabemodem > providers gateway machine :-( I must be doing something dumbe here. > Here is what I see: On cable modems I have tried, I had to power down the modem and power it back up. It remembers the MAC address it wants to talk to and won't talk to any others. Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Dec 10 16:28:37 1999 Delivered-To: freebsd-net@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id C71F214FA4 for ; Fri, 10 Dec 1999 16:28:30 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id QAA25830; Fri, 10 Dec 1999 16:28:25 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA14991; Fri, 10 Dec 1999 16:28:25 -0800 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA20743; Fri, 10 Dec 99 16:27:45 PST Message-Id: <38508346.307BA88@softweyr.com> Date: Thu, 09 Dec 1999 21:36:22 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: yu.shi@nokia.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: Ethernet driver References: <95A2D1413F29D311B3450008C773628968CAB3@beeis03nok> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org yu.shi@nokia.com wrote: > > > Wes Peters scribbled: > > > > yu.shi@nokia.com wrote: > > > > > > Hello, > > > > > > I'm digging into ethernet driver. > > > where can I find the DEC DC21040 chip user's manual OR tulip Network card > > > specification? > > > > http://www.developer.intel.com/ > > Sorry, I can not find it on developer.intel.com.(not > www.developer.intel.com) > Would u make it a little specific ? > > Thanks! There's nothing magic about this, just go to the intel site, hit the "search" button, and be a little creative. They don't make the 21040 anymore, the closest you can come is the 21143. See http://developer.intel.com/design/network/datashts/index.htm for the complete line of network "datashts" from Intel. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Dec 10 18:37:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from futhermucker.com (dhcp021.57.lvcm.com [24.234.57.21]) by hub.freebsd.org (Postfix) with ESMTP id 5749214CE5 for ; Fri, 10 Dec 1999 18:37:42 -0800 (PST) (envelope-from hfmic@futhermucker.com) Received: from hulk (ws069.inner.futhermucker.com [172.16.251.69]) by futhermucker.com (8.9.3/8.9.3) with SMTP id CAA03790 for ; Sat, 11 Dec 1999 02:33:52 -0800 (PST) (envelope-from hfmic@futhermucker.com) Reply-To: From: "David Nelson" To: Subject: RE: New computer won't talk to cablemodem Date: Fri, 10 Dec 1999 18:34:03 -0800 Message-ID: <002101bf4380$3175ecb0$45fb10ac@inner.futhermucker.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199912102330.PAA03975@netcom.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Looks like your default gateway is wrong... breezing through your tcpdump, it looks like your default gateway is 24.6.61.1, not 205.159.77.234. Change the default gateway in /etc/rc.conf and see if that doesn't clear it up. -- Dave -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Stan Brown Sent: Friday, December 10, 1999 3:31 PM To: FreeBSD Networking Subject: New computer won't talk to cablemodem I am in the process of setting up a "new" computer to use as a gatewy to the world for my home network. I am presently accessing the world through an @home cablemodem via a FreeBSD 2.2.8 machine, and natd. Works great. I have scrounged up an old 486 to take this machines place. I built 3.3-STABLE on it, and started trying to make a similar setup work. Unfortunately I can't seem to get as far as pinging the cabemodem providers gateway machine :-( I must be doing something dumbe here. Here is what I see: Script started on Fri Dec 10 18:17:24 1999 netgate# ifconfig -a ed0: flags=8843 mtu 1500 inet 205.159.77.201 netmask 0xffffff00 broadcast 205.159.77.255 ether 00:80:ad:08:2b:80 ed1: flags=8843 mtu 1500 inet 24.6.61.166 netmask 0xffffff00 broadcast 24.6.61.255 ether 00:40:05:72:e8:7a tun0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 ppp0: flags=8010 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 ds0: flags=8008 mtu 65532 netgate# netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 205.159.77.234 UGSc 1 0 ed0 24.6.61/24 link#2 UC 0 0 ed1 24.6.61.255 ff:ff:ff:ff:ff:ff UHLWb 0 2 ed1 127.0.0.1 127.0.0.1 UH 1 32 lo0 205.159.77 link#1 UC 0 0 ed0 205.159.77.232 8:0:9:78:ea:56 UHLW 0 0 ed0 1118 205.159.77.234 0:80:ad:7:f9:75 UHLW 2 0 ed0 1130 205.159.77.236 8:0:9:92:55:11 UHLW 1 55 ed0 1188 205.159.77.239 8:0:9:10:6:a5 UHLW 0 0 ed0 1118 205.159.77.240 8:0:9:11:e5:a UHLW 0 3 ed0 1135 205.159.77.255 ff:ff:ff:ff:ff:ff UHLWb 1 2 ed0 netgate# arp -a ^C netgate# arp -an ? (24.6.61.255) at ff:ff:ff:ff:ff:ff permanent [ethernet] ? (205.159.77.232) at 8:0:9:78:ea:56 [ethernet] ? (205.159.77.234) at 0:80:ad:7:f9:75 [ethernet] ? (205.159.77.236) at 8:0:9:92:55:11 [ethernet] ? (205.159.77.239) at 8:0:9:10:6:a5 [ethernet] ? (205.159.77.240) at 8:0:9:11:e5:a [ethernet] ? (205.159.77.255) at ff:ff:ff:ff:ff:ff permanent [ethernet] netgate# tcpdump -i ed1 tcpdump: listening on ed1 18:18:29.270832 0:10:7b:ed:bb:3a 0:10:7b:ed:bb:3a loopback 60: 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 18:18:39.202007 0:10:7b:ed:bb:3a 0:10:7b:ed:bb:3a loopback 60: 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 18:18:40.444554 0:10:7b:ed:bb:3a > 1:0:c:cc:cc:cc sap aa ui/C len=296 b000 0100 0853 4f48 4f00 0200 0800 0000 0000 0300 0d45 7468 6572 6e65 7430 0004 0008 0000 0002 0005 00e6 43 18:18:49.133081 0:10:7b:ed:bb:3a 0:10:7b:ed:bb:3a loopback 60: 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 18:18:50.457849 arp who-has 24.6.61.1 tell cc69528-a.mtpls1.sc.home.com 18:18:50.471223 arp reply 24.6.61.1 is-at 0:50:3e:e2:10:40 18:18:50.471836 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:50.483070 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:50.483532 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:51.462580 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:51.498028 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:51.498590 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:52.472213 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:52.484483 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:52.484968 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:53.482327 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:53.494285 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:53.494761 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:54.492188 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:54.503960 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:54.504433 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:55.502202 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:55.513625 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:55.514100 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:56.512361 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:56.525432 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:56.525919 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:57.522376 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:57.534981 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:57.535461 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:58.532254 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:58.544974 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:58.545444 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:18:59.064220 0:10:7b:ed:bb:3a 0:10:7b:ed:bb:3a loopback 60: 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 18:18:59.542392 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:18:59.554555 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:18:59.555052 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:00.552362 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:00.563595 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:00.564111 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:01.562479 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:01.573677 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:01.574175 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:02.572310 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:02.585841 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:02.586317 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:03.582316 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:03.596282 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:03.596753 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:04.592452 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:04.604005 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:04.604479 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:05.602498 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:05.729409 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:05.729890 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:06.612610 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:06.647877 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:06.648446 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:07.622379 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:07.635591 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:07.636071 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:08.632406 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:08.645040 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:08.645515 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:09.075354 0:10:7b:ed:bb:3a 0:10:7b:ed:bb:3a loopback 60: 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 18:19:09.642513 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:09.657203 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:09.657683 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:10.652479 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:10.664401 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:10.664990 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:11.662454 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:11.674152 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:11.674631 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:12.672466 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:12.683606 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:12.684081 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:13.684169 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:13.695409 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:13.695888 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:14.694244 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:14.707283 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:14.707765 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:15.702689 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:15.714665 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:15.715198 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:16.712998 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:16.723866 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:16.724419 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:17.722770 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:17.733463 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:17.733968 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:18.732666 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:18.745474 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:18.745967 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:19.007319 0:10:7b:ed:bb:3a 0:10:7b:ed:bb:3a loopback 60: 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 18:19:19.327740 cc69528-a.mtpls1.sc.home.com.who > 24.6.61.255.who: udp 108 18:19:19.328111 cc69528-a.mtpls1.sc.home.com.who > 24.6.61.255.who: udp 108 18:19:19.742667 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:19.774964 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:19.775479 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:20.752812 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:20.764995 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:20.765496 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:21.762881 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:21.774269 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:21.774784 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:22.772740 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:22.784133 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:22.784625 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:23.782706 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:23.796475 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:23.796961 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:24.792970 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:24.805616 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:24.806108 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a 18:19:25.802859 cc69528-a.mtpls1.sc.home.com > 24.6.61.1: icmp: echo request 18:19:25.814742 arp who-has cc69528-a.mtpls1.sc.home.com (0:40:5:72:e8:7a) tell 24.6.61.1 18:19:25.815230 arp reply cc69528-a.mtpls1.sc.home.com is-at 0:40:5:72:e8:7a ^C 119 packets received by filter 0 packets dropped by kernel netgate# arp -a ^C netgate# arp -an ? (24.6.61.1) at 0:50:3e:e2:10:40 [ethernet] ? (24.6.61.255) at ff:ff:ff:ff:ff:ff permanent [ethernet] ? (205.159.77.232) at 8:0:9:78:ea:56 [ethernet] ? (205.159.77.234) at 0:80:ad:7:f9:75 [ethernet] ? (205.159.77.236) at 8:0:9:92:55:11 [ethernet] ? (205.159.77.239) at 8:0:9:10:6:a5 [ethernet] ? (205.159.77.240) at 8:0:9:11:e5:a [ethernet] ? (205.159.77.255) at ff:ff:ff:ff:ff:ff permanent [ethernet] netgate# ping 24.6.61.1 PING 24.6.61.1 (24.6.61.1): 56 data bytes ^C --- 24.6.61.1 ping statistics --- 6 packets transmitted, 0 packets received, 100% packet loss netgate# traceroute 24.6.61.1 traceroute to 24.6.61.1 (24.6.61.1), 30 hops max, 40 byte packets 1 * * * ^C netgate# ^Dexit Script done on Fri Dec 10 18:20:36 1999 As you can see the new machine is asking for an arp of the gateway, and it apperars to be making it into the arp table. Still ping doesn;t work. Simply removing the cable from the "new" machine and puting it back in the old one causes pings from it to start working. I am at a loss here. Has anyone got any troubleshooting advice for me? Thanks. -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. 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 Sat Dec 11 1:34:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id AD6CB14E53 for ; Sat, 11 Dec 1999 01:34:06 -0800 (PST) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 2.12 #1) id 11wiuc-000EdA-00 for freebsd-net@freebsd.org; Sat, 11 Dec 1999 15:33:58 +0600 Date: Sat, 11 Dec 1999 15:33:58 +0600 (ALMT) From: Boris Popov To: freebsd-net@freebsd.org Subject: [patch for review] ifunit() and subinterfaces Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Current implementation of ifunit() function does not allow using interface names like 'ed0blah2', eg. it finds first numeric character and starts calculation of unit number. However it is usable in some cases to have names which looks like subinterfaces (ed0f1, ed0f2) of existing interface. So I'm propose the following patch to do it (as a side effect function also getting a little bit smaller): diff -u org/if.c ./if.c --- org/if.c Sat Dec 11 12:04:08 1999 +++ ./if.c Sat Dec 11 13:49:36 1999 @@ -597,41 +597,36 @@ * interface structure pointer. */ struct ifnet * -ifunit(name) - register char *name; +ifunit(char *name) { char namebuf[IFNAMSIZ + 1]; - register char *cp, *cp2; - char *end; - register struct ifnet *ifp; + char *cp; + struct ifnet *ifp; int unit; - unsigned len; - register char c = '\0'; + unsigned len, m; + char c; - /* - * Look for a non numeric part - */ - end = name + IFNAMSIZ; - cp2 = namebuf; - cp = name; - while ((cp < end) && (c = *cp)) { - if (c >= '0' && c <= '9') - break; - *cp2++ = c; - cp++; - } - if ((cp == end) || (c == '\0') || (cp == name)) - return ((struct ifnet *)0); - *cp2 = '\0'; - /* - * check we have a legal number (limit to 7 digits?) - */ + len = strlen(name); + if (len < 2 || len > IFNAMSIZ) + return NULL; + cp = name + len - 1; + c = *cp; + if (c < '0' || c > '9') + return NULL; /* trailing garbage */ + unit = 0; + m = 1; + do { + if (cp == name) + return NULL; /* no interface name */ + unit += (c - '0') * m; + if (unit > 1000000) + return NULL; /* number is unreasonable */ + m *= 10; + c = *--cp; + } while (c >= '0' && c <= '9'); len = cp - name + 1; - for (unit = 0; - ((c = *cp) >= '0') && (c <= '9') && (unit < 1000000); cp++ ) - unit = (unit * 10) + (c - '0'); - if (*cp != '\0') - return 0; /* no trailing garbage allowed */ + bcopy(name, namebuf, len); + namebuf[len++] = '\0'; /* * Now search all the interfaces for this name/number */ -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Dec 11 12: 4:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id CDAD915043 for ; Sat, 11 Dec 1999 12:04:38 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id PAA77078; Sat, 11 Dec 1999 15:04:22 -0500 (EST) (envelope-from wollman) Date: Sat, 11 Dec 1999 15:04:22 -0500 (EST) From: Garrett Wollman Message-Id: <199912112004.PAA77078@khavrinen.lcs.mit.edu> To: Boris Popov Cc: freebsd-net@FreeBSD.ORG Subject: [patch for review] ifunit() and subinterfaces In-Reply-To: References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > So I'm propose the following patch to do it (as a side effect > function also getting a little bit smaller): I don't like it but won't object. -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 Sat Dec 11 12:22:30 1999 Delivered-To: freebsd-net@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7B9B214DA3; Sat, 11 Dec 1999 12:22:28 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA91413; Sat, 11 Dec 1999 12:21:30 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: csg@waterspout.com (C. Stephen Gunn) Cc: wollman@LITTLE-CHOCOLATE-DONUTS.MIT.EDU, wpaul@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Who's using 802.1Q VLAN Support? In-reply-to: Your message of "Fri, 10 Dec 1999 01:07:26 EST." <19991210060731.CB18D59@dustdevil.waterspout.com> Date: Sat, 11 Dec 1999 12:21:30 -0800 Message-ID: <91409.944943690@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > With lots of further testing, these patches do defintely help. I > still can't reliably debug an mbuf crash that happens within 5-10 > minutes of bringing up the vlans with some traffic though. All > the backtrace tells me is that someone smashed the buffer. Can you send them to me in one batch, ready to commit relative to -stable? It would save me some time in aggregating PRs, and you should be able to pull them out with a cvs diff on the relevant portion of your local tree. > Now it's in the -STABLE branch, which it ain't. My patches do fix > problems in the code, but it's not functional enough for -STABLE > IMNSHO. (No Offense to Bill & Garrett's free-time-constraied, and > appreciated efforts) Understood, but since it's there already we might as well at least make it something less than an open manhole, waiting to swallow the unwary pedestrian. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message