From owner-freebsd-net Sun Feb 18 5:30:48 2001 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 4FA3337B4EC; Sun, 18 Feb 2001 05:30:40 -0800 (PST) Received: by relay.butya.kz (Postfix, from userid 1000) id A6EC528E9F; Sun, 18 Feb 2001 19:30:31 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 85D6A28E76; Sun, 18 Feb 2001 19:30:31 +0600 (ALMT) Date: Sun, 18 Feb 2001 19:30:28 +0600 (ALMT) From: Boris Popov To: Ian Dowse Cc: freebsd-arch@freebsd.org, freebsd-net@freebsd.org Subject: CFR2: Sequential mbuf read/write extensions In-Reply-To: <200102121409.aa34378@salmon.maths.tcd.ie> 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, Well, I've tried to take into account most of the suggestions and placed an updated versions of files to http://www.butya.kz/~bp/mbuf/ If no serious problems will be found I would like to commit this on next week (this version of functions included in the upcoming smbfs-1.3.6). -- 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 Sun Feb 18 6: 9: 1 2001 Delivered-To: freebsd-net@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id 995B237B491 for ; Sun, 18 Feb 2001 06:08:57 -0800 (PST) Received: (from cjsabatier@localhost) by cx344940-a.meta1.la.home.com (8.11.2/8.11.2) id f1IEC4B03021 for freebsd-net@FreeBSD.ORG; Sun, 18 Feb 2001 08:12:04 -0600 (CST) (envelope-from cjsabatier) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 18 Feb 2001 08:12:04 -0600 (CST) Organization: @Home Network From: Conrad Sabatier To: freebsd-net@FreeBSD.ORG Subject: RE: Using pppd to gateway another box via null modem serial line Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org OK, I've got the two machines (my Unix box and a Mac using FreePPP) talking to each other. Now, one last question: How can I setup a route to enable the Mac to talk directly to the Internet. Right now I have it talking to squid on the FreeBSD box, but any attempts to do direct connects fail. I do have gateway_enable="YES" in /etc/rc.conf. Here's the output of netstat -ran: Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 24.6.21.1 UGSc 19 4 fxp0 24.0.95.81 24.6.21.1 UGHW3 0 24 fxp0 2389 24.0.95.85 24.6.21.1 UGHW3 0 34 fxp0 3590 24.0.95.86 24.6.21.1 UGHW3 0 47 fxp0 3586 24.0.95.87 24.6.21.1 UGHW3 0 13 fxp0 3289 24.0.95.88 24.6.21.1 UGHW3 0 13 fxp0 2685 24.0.95.89 24.6.21.1 UGHW3 0 23 fxp0 2990 24.4.62.33 24.6.21.1 UGHW 1 84 fxp0 24.4.62.34 24.6.21.1 UGHW3 0 67 fxp0 3546 24.6.21/24 link#1 UC 0 0 fxp0 => 24.6.21.1 0:4:28:24:ec:70 UHLW 19 0 fxp0 1042 24.6.21.74 0:90:27:65:67:c9 UHLW 2 173 lo0 24.14.77.6 24.6.21.1 UGHW 3 1140 fxp0 64.236.8.10 24.6.21.1 UGHW3 0 58 fxp0 2929 127.0.0.1 127.0.0.1 UH 3 1466 lo0 152.163.180.24 24.6.21.1 UGHW3 0 22 fxp0 3003 152.163.180.56 24.6.21.1 UGHW3 0 29 fxp0 3003 192.168.1.1 24.6.21.74 UH 1 2358 ppp0 205.188.140.185 24.6.21.1 UGHW3 0 16 fxp0 2999 205.188.140.249 24.6.21.1 UGHW3 0 24 fxp0 2948 205.188.153.105 24.6.21.1 UGHW 1 82 fxp0 205.188.153.139 24.6.21.1 UGHW3 0 6 fxp0 2179 205.188.212.121 24.6.21.1 UGHW 2 1196 fxp0 207.200.75.206 24.6.21.1 UGHW3 0 17 fxp0 2937 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%fxp0/64 link#1 UC fxp0 fe80::%lo0/64 fe80::1%lo0 Uc lo0 ff01::/32 ::1 U lo0 ff02::%fxp0/32 link#1 UC fxp0 ff02::%lo0/32 fe80::1%lo0 UC lo0 -- Conrad Sabatier cjsabatier@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 18 8:54:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id D90A037B491 for ; Sun, 18 Feb 2001 08:54:19 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14UXGE-00009h-00; Sun, 18 Feb 2001 10:04:34 -0700 Message-ID: <3A9000A2.97659309@softweyr.com> Date: Sun, 18 Feb 2001 10:04:34 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Conrad Sabatier Cc: freebsd-net@FreeBSD.ORG Subject: Re: Using pppd to gateway another box via null modem serial line References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Conrad Sabatier wrote: > > OK, I've got the two machines (my Unix box and a Mac using FreePPP) talking to > each other. Now, one last question: > > How can I setup a route to enable the Mac to talk directly to the Internet. > Right now I have it talking to squid on the FreeBSD box, but any attempts to do > direct connects fail. This is not the correct forum for learning how IP routing works. If the Mac is the "196.168" address in your routing table, you will need to configure your FreeBSD box to perform Network Address Translation (NAT) for your Mac. Please consult a good book on IP routing and NAT to learn how to do this, or read the appropriate man pages. Ted Mittelstaedt covers how to configure a NAT router using FreeBSD and natd in chapter 5 of "The FreeBSD Corporate Networker's Guide", which is only $30 at fatbrain.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 Sun Feb 18 9:24:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id E741E37B491 for ; Sun, 18 Feb 2001 09:24:37 -0800 (PST) Received: (from cjsabatier@localhost) by cx344940-a.meta1.la.home.com (8.11.2/8.11.2) id f1IHRha08186; Sun, 18 Feb 2001 11:27:43 -0600 (CST) (envelope-from cjsabatier) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A9000A2.97659309@softweyr.com> Date: Sun, 18 Feb 2001 11:27:43 -0600 (CST) Organization: @Home Network From: Conrad Sabatier To: Wes Peters Subject: Re: Using pppd to gateway another box via null modem serial line Cc: freebsd-net@FreeBSD.ORG Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 18-Feb-01 Wes Peters wrote: > > This is not the correct forum for learning how IP routing works. Sorry. I did figure it out later (yes, with NAT). -- Conrad Sabatier cjsabatier@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 18 9:25:15 2001 Delivered-To: freebsd-net@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id 08C6837B503 for ; Sun, 18 Feb 2001 09:25:13 -0800 (PST) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id f1IHNmA93159; Sun, 18 Feb 2001 18:23:49 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.1/8.11.0) id f1IHNjL91719; Sun, 18 Feb 2001 18:23:46 +0100 (CET) (envelope-from asmodai) Date: Sun, 18 Feb 2001 18:23:45 +0100 From: Jeroen Ruigrok/Asmodai To: Dan Debertin Cc: Bosko Milekic , "net@freebsd.org" Subject: Re: buffer problems with ep Message-ID: <20010218182344.B67327@daemon.ninth-circle.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from airboss@bitstream.net on Fri, Feb 16, 2001 at 08:44:16AM -0600 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20010216 16:00], Dan Debertin (airboss@bitstream.net) wrote: >flags=8c43 mtu 1500 OK, so it is setting the output active flag and quite possibly never returns from that state. Hmmm, if you don't do an ifconfig down/up or just up it won't come back, right? I mean, you can sit it there for days if you want, you have to up it to get it back? -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 18 12:33:30 2001 Delivered-To: freebsd-net@freebsd.org Received: from barabas.bitstream.net (barabas.bitstream.net [216.243.128.159]) by hub.freebsd.org (Postfix) with SMTP id 87C5B37B503 for ; Sun, 18 Feb 2001 12:33:22 -0800 (PST) Received: (qmail 86215 invoked from network); 18 Feb 2001 20:33:20 -0000 Received: from unknown (HELO chicka) (216.243.128.155) by barabas with SMTP; 18 Feb 2001 20:33:20 -0000 Date: Sun, 18 Feb 2001 14:33:22 -0600 (CST) From: Dan Debertin To: Jeroen Ruigrok/Asmodai Cc: Bosko Milekic , "net@freebsd.org" Subject: Re: buffer problems with ep In-Reply-To: <20010218182344.B67327@daemon.ninth-circle.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 18 Feb 2001, Jeroen Ruigrok/Asmodai wrote: > -On [20010216 16:00], Dan Debertin (airboss@bitstream.net) wrote: > >flags=8c43 mtu 1500 > > OK, so it is setting the output active flag and quite possibly never > returns from that state. Quite so. > > Hmmm, if you don't do an ifconfig down/up or just up it won't come back, > right? I mean, you can sit it there for days if you want, you have to > up it to get it back? Yes, and have done so. I've left it hung for as long as 2 days; it doesn't pick back up until I ifconfig down/up. Strangely, this only way I can reproduce the problem is by installing Solaris patch-clusters on my diskless workstation via NFS. Every other network activity, no matter how strenuous, won't trigger it. ~Dan D. -- ++ Dan Debertin ++ Senior Systems Administrator ++ Bitstream Underground, LLC ++ airboss@bitstream.net ++ (612)321-9290 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 18 13:25:53 2001 Delivered-To: freebsd-net@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id B05E937B4EC; Sun, 18 Feb 2001 13:25:47 -0800 (PST) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id f1ILPf248914; Sun, 18 Feb 2001 22:25:41 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.1/8.11.0) id f1ILPdr04500; Sun, 18 Feb 2001 22:25:39 +0100 (CET) (envelope-from asmodai) Date: Sun, 18 Feb 2001 22:25:38 +0100 From: Jeroen Ruigrok/Asmodai To: Dan Debertin Cc: "net@freebsd.org" , mdodd@freebsd.org, wpaul@freebsd.org Subject: Re: buffer problems with ep Message-ID: <20010218222538.D67327@daemon.ninth-circle.org> References: <20010218182344.B67327@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from airboss@bitstream.net on Sun, Feb 18, 2001 at 02:33:22PM -0600 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Bill Paul and Matthew Dodd cc:'d. Sorry for this intrusion guys, but I just want you opinions on some of the blabbering I exclaim] -On [20010218 21:37], Dan Debertin (airboss@bitstream.net) wrote: >On Sun, 18 Feb 2001, Jeroen Ruigrok/Asmodai wrote: > >> -On [20010216 16:00], Dan Debertin (airboss@bitstream.net) wrote: >> >flags=8c43 mtu 1500 >> >> OK, so it is setting the output active flag and quite possibly never >> returns from that state. > >Quite so. Matthew Dodd said that NetBSD might've a workaround/solution for this. His guess was that the hardware wedges for some reason. >> Hmmm, if you don't do an ifconfig down/up or just up it won't come back, >> right? I mean, you can sit it there for days if you want, you have to >> up it to get it back? > >Yes, and have done so. I've left it hung for as long as 2 days; it doesn't >pick back up until I ifconfig down/up. During this time the OACTIVE flag stays there all the time? Which FreeBSD version? What is the dmesg line for the ep card you have? [grep ep0 /var/run/dmesg.boot] >Strangely, this only way I can reproduce the problem is by installing >Solaris patch-clusters on my diskless workstation via NFS. Every other >network activity, no matter how strenuous, won't trigger it. Try nmap scans. I got an ep here too: ep0: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 10 on isa0 which I can have `hanging' too after I did some nmap scans. I haven't checked for the OACTIVE flag yet. I'll try to reproduce this during the week. I have been looking if I could find a solution for the problem. When you do the ifconfig ep0 up you will trigger the ep_if_init(sc) line in if_ep.c: case SIOCSIFFLAGS: if (((ifp->if_flags & IFF_UP) == 0) && (ifp->if_flags & IFF_RUNNING)) { ifp->if_flags &= ~IFF_RUNNING; epstop(sc); } else { /* reinitialize card on any parameter change */ ep_if_init(sc); } break; Since your card is already in RUNNING and UP status and those bits are set in the ifp.if_flags. in ep_if_init() we find: ifp->if_flags |= IFF_RUNNING; ifp->if_flags &= ~IFF_OACTIVE; /* just in case */ Which effectively sets RUNNING and clears OACTIVE and then proceeds to ep_if_start(). I need to look further, but I have had other things to do as well... Ideas/thoughts welcome. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 18 13:54:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from barabas.bitstream.net (barabas.bitstream.net [216.243.128.159]) by hub.freebsd.org (Postfix) with SMTP id 3DED237B491 for ; Sun, 18 Feb 2001 13:54:55 -0800 (PST) Received: (qmail 98879 invoked from network); 18 Feb 2001 21:54:49 -0000 Received: from unknown (HELO chicka) (216.243.128.155) by barabas with SMTP; 18 Feb 2001 21:54:49 -0000 Date: Sun, 18 Feb 2001 15:54:51 -0600 (CST) From: Dan Debertin To: Jeroen Ruigrok/Asmodai Cc: "net@freebsd.org" , "mdodd@freebsd.org" , "wpaul@freebsd.org" Subject: Re: buffer problems with ep In-Reply-To: <20010218222538.D67327@daemon.ninth-circle.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 18 Feb 2001, Jeroen Ruigrok/Asmodai wrote: > During this time the OACTIVE flag stays there all the time? Yes. > > Which FreeBSD version? > This is 4.1.1-RELEASE. > What is the dmesg line for the ep card you have? [grep ep0 > /var/run/dmesg.boot] ep0: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 5 on isa0 ep0: Ethernet address 00:20:af:23:68:1c > > >Strangely, this only way I can reproduce the problem is by installing > >Solaris patch-clusters on my diskless workstation via NFS. Every other > >network activity, no matter how strenuous, won't trigger it. > > Try nmap scans. Sure, I'll give it a go. I've since switched my workstation from solaris to NetBSD, so I'm going to need another way to reproduce the problem if I'm going to continue to be helpful here ;) ~Dan D. -- ++ Dan Debertin ++ Senior Systems Administrator ++ Bitstream Underground, LLC ++ airboss@bitstream.net ++ (612)321-9290 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 18 19: 1:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 29ED637B401 for ; Sun, 18 Feb 2001 19:01:52 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id TAA35526 for ; Sun, 18 Feb 2001 19:01:51 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id TAA93280 for freebsd-net@freebsd.org; Sun, 18 Feb 2001 19:01:51 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102190301.TAA93280@curve.dellroad.org> Subject: /usr/share/examples/netgraph/ether.bridge To: freebsd-net@freebsd.org Date: Sun, 18 Feb 2001 19:01:51 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Someone emailed me some patches to the netgraph bridging script /usr/share/examples/netgraph/ether.bridge but I lost them. If you are that someone please re-send. Thanks, -Archie P.S. Has anyone actually used this script? __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 18 20: 6:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from mine.kame.net (kame195.kame.net [203.178.141.195]) by hub.freebsd.org (Postfix) with ESMTP id CB81937B491 for ; Sun, 18 Feb 2001 20:06:50 -0800 (PST) Received: from localhost ([202.249.11.124]) by mine.kame.net (8.9.3/3.7W) with ESMTP id NAA51816; Mon, 19 Feb 2001 13:18:32 +0900 (JST) To: narai@kies.co.kr Cc: freebsd-net@FreeBSD.ORG, sakane@kame.net Subject: Re: How to get AH working? In-Reply-To: Your message of "Wed, 14 Feb 2001 11:27:23 +0900" <002201c0962d$aa0bf920$d30110ac@narai> References: <002201c0962d$aa0bf920$d30110ac@narai> X-Mailer: Cue version 0.6 (010125-0306/sakane) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Message-Id: <20010219130857U.sakane@ydc.co.jp> Date: Mon, 19 Feb 2001 13:08:57 +0900 From: "Shoichi 'Ne' Sakane" X-Dispatcher: imput version 990905(IM130) Lines: 21 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > i installed freebsd4.2 and kame-20010212-freebsd42-snap and tried IPSEC connecti > ons. > ESP mode worked fine with kame(racoon) but I couldn't get AH mode connection. > Following is the error messages. > > keTest# Feb 14 10:48:31 IkeTest /kernel: checksum mismatch in IPv4 > AH input: packet(SPI=225667595 src=172.16.1.211 dst=172.16.1.210) > SA(SPI=225667595 src=172.16.1.211 dst=172.16.1.210) The sender calculates the checksum of the packet by mixing the cipher key negotiated, adds the checksum to the packet, and then sends the packet to the receiver. The receiver re-calculates the checksum of the packet by mixing the cipher key negotiated, and compares the checksum from the sender and the one re-calculated. The above error happened when the receiver compared the checksums. The cipher key might mismatch in this case. Could you show me the BOTH hosts's SAD during the error messages are printing. The way to catching the SAD is the following. # setkey -D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 18 23: 1:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id E69DC37B503 for ; Sun, 18 Feb 2001 23:01:15 -0800 (PST) Received: (qmail 17144 invoked by uid 666); 19 Feb 2001 07:13:08 -0000 Received: from i076-193.nv.iinet.net.au (HELO elischer.org) (203.59.76.193) by mail.m.iinet.net.au with SMTP; 19 Feb 2001 07:13:08 -0000 Message-ID: <3A90C4A2.F5E7FDE@elischer.org> Date: Sun, 18 Feb 2001 23:00:50 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Archie Cobbs Cc: freebsd-net@freebsd.org Subject: Re: /usr/share/examples/netgraph/ether.bridge References: <200102190301.TAA93280@curve.dellroad.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Archie Cobbs wrote: > > Someone emailed me some patches to the netgraph bridging script > /usr/share/examples/netgraph/ether.bridge but I lost them. If you > are that someone please re-send. > > Thanks, > -Archie > > P.S. Has anyone actually used this script? yes I know people have used it as a basis for their own script.. > > __________________________________________________________________________ > Archie Cobbs * Packet Design * http://www.packetdesign.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 3:50:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 3F1C637B4EC for ; Mon, 19 Feb 2001 03:50:09 -0800 (PST) Received: (qmail 14642 invoked by uid 666); 19 Feb 2001 12:02:50 -0000 Received: from i074-022.nv.iinet.net.au (HELO elischer.org) (203.59.74.22) by mail.m.iinet.net.au with SMTP; 19 Feb 2001 12:02:50 -0000 Message-ID: <3A910856.CE68FEAC@elischer.org> Date: Mon, 19 Feb 2001 03:49:42 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Satyajeet Seth Cc: net@freebsd.org Subject: Re: Using netgraph to implement pseudo interfaces References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satyajeet Seth wrote: > > Hi > > I wished to implement pseudo interfaces with the following requirements: > > 1. There is a ethernet interface fxp0 having MAC address MAC0. It also > receives packets with destination MAC address MAC1 and MAC2. > > 2. The packets with destination MAC address MAC1 are sent to a pseudo > interface 1 and packets with destination MAC address MAC2 are sent to > pseudo interface 2. > > 3. The packets addressed to MAC0 should be sent to sent to fxp0. > > I plan to design a netgraph as follows: > > iface1 > / > fxp0 <-> bpf > \ > iface2 I forgot to add in my previous response that you'd have to do this like: fxp0: <--> bpf <--> bpf <--> interface0 \ \ \ ------>interface1 \ \------------>interface2 as each bpfnode hook only selects between a "match" and "no match" hook. you could do it with one node as follows: +----------------------------+ | | +->(hook2)[ ] | fxp0:(lower)<->(hook1)[bpf](nomatch1)----+ [ ](match1)<-------->(upper)fxp0: [ ](nomatch2)<------>(hook)iface1: [ ](match2)<-------->(hook)iface2: i.e. loop the data back through the same node twice to effect two rules on the same data. > > fxp0, iface1, iface2, bpf are nodes of type ng_ether, ng_iface, ng_iface > and ng_bpf respectively. > > The packets with destination addresses MAC1 and MAC2 are sent to > interfaces iface1 and iface2 respectively by bpf. Remaining are sent to > fxp0. > > Could you suggest some pitfalls/improvements in the above scheme? > > I am using FreeBSD 4.0. > > Thanks > Satya > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 4:15:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [212.61.40.17]) by hub.freebsd.org (Postfix) with ESMTP id 64B6A37B401 for ; Mon, 19 Feb 2001 04:15:22 -0800 (PST) Received: by gvr.gvr.org (Postfix, from userid 657) id 7E4EA5807; Mon, 19 Feb 2001 13:15:20 +0100 (CET) Date: Mon, 19 Feb 2001 13:15:20 +0100 From: Guido van Rooij To: freebsd-net@freebsd.org Subject: fxp media change question Message-ID: <20010219131520.A76608@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wonder if it possible to have 8255{7,9} based boards generate an interrupt on media changes? If so: how? (I couldn't find it in the public Linux driver Intel provides). -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 4:17:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from samar.sasi.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id F413337B491 for ; Mon, 19 Feb 2001 04:17:46 -0800 (PST) Received: from samar (samar.sasi.com [164.164.56.2]) by samar.sasi.com (8.9.3/8.9.3) with SMTP id RAA25706; Mon, 19 Feb 2001 17:47:38 +0530 (IST) Received: from suns3.sasi.com ([10.0.36.3]) by samar.sasi.com; Mon, 19 Feb 2001 17:47:37 +0000 (IST) Received: from localhost (sseth@localhost) by suns3.sasi.com (8.9.3/8.9.3) with ESMTP id RAA06295; Mon, 19 Feb 2001 17:47:37 +0530 (IST) Date: Mon, 19 Feb 2001 17:47:37 +0530 (IST) From: Satyajeet Seth To: Julian Elischer Cc: Subject: Re: Using netgraph to implement pseudo interfaces In-Reply-To: <3A910856.CE68FEAC@elischer.org> 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 A node of type ng_bpf uses BPF. How is a packet passed onto the BPF? I believe a copy of the packet is sent. Is this correct? Once a packet is sent to the BPF, will the driver process the packet further and queue it to the IP layer? If so, in our case, there will be duplication of packets. Here the BPF will pass the packets onto pseudo ethernet interfaces. These interfaces will in turn queue the packets to the IP layer. Thanks Satya > > I wished to implement pseudo interfaces with the following requirements: > > > > 1. There is a ethernet interface fxp0 having MAC address MAC0. It also > > receives packets with destination MAC address MAC1 and MAC2. > > > > 2. The packets with destination MAC address MAC1 are sent to a pseudo > > interface 1 and packets with destination MAC address MAC2 are sent to > > pseudo interface 2. > > > > 3. The packets addressed to MAC0 should be sent to sent to fxp0. > > > > I plan to design a netgraph as follows: > > > > iface1 > > / > > fxp0 <-> bpf > > \ > > iface2 > > I forgot to add in my previous response that you'd have to do this like: > > fxp0: <--> bpf <--> bpf <--> interface0 > \ \ > \ ------>interface1 > \ > \------------>interface2 > > as each bpfnode hook only selects between a > "match" and "no match" hook. > > you could do it with one node as follows: > > > +----------------------------+ > | | > +->(hook2)[ ] | > fxp0:(lower)<->(hook1)[bpf](nomatch1)----+ > [ ](match1)<-------->(upper)fxp0: > [ ](nomatch2)<------>(hook)iface1: > [ ](match2)<-------->(hook)iface2: > > i.e. loop the data back through the same node twice to effect two rules on > the same data. > > > > > > fxp0, iface1, iface2, bpf are nodes of type ng_ether, ng_iface, ng_iface > > and ng_bpf respectively. > > > > The packets with destination addresses MAC1 and MAC2 are sent to > > interfaces iface1 and iface2 respectively by bpf. Remaining are sent to > > fxp0. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 4:44:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 4426937B401 for ; Mon, 19 Feb 2001 04:44:45 -0800 (PST) Received: from elischer.org (i074-022.nv.iinet.net.au [203.59.74.22]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id UAA02457; Mon, 19 Feb 2001 20:44:25 +0800 Message-ID: <3A911511.8897BEC3@elischer.org> Date: Mon, 19 Feb 2001 04:44:01 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Satyajeet Seth Cc: net@freebsd.org Subject: Re: Using netgraph to implement pseudo interfaces References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satyajeet Seth wrote: > > Hi > > A node of type ng_bpf uses BPF. How is a packet passed onto the > BPF? I believe a copy of the packet is sent. Is this correct? man ng_bpf. the ng_bpf node takes a packet as input and applies a bpf 'filter' to it. if the filter succeeds, the packet is sent out the hook marked for success in that filter. If the filter fails is is passed out the hook marked for failure in that filter. If the correct hook is NULL, the packet is discarded. It is a PACKET. it is not a copy unless you first copied it, which is irrelevent and beyond the knowledge of the ng_bpf node. (the ng_bpf node gets it's packets from netgraph in the usual netgraph way and NOT by the usual bpf hooks in the drivers.) > > Once a packet is sent to the BPF, will the driver process the > packet further and queue it to the IP layer? No, not unless you send it back to the interface to be processed further. please read the netgraph man page man 4 netgraph and the ng_ether man page man 4 ng_ether > > If so, in our case, there will be duplication of packets. Here the BPF > will pass the packets onto pseudo ethernet interfaces. These interfaces > will in turn queue the packets to the IP layer. There is no duplication. Netgraph produces a non directed graph (in math-speak) of connected nodes to process arbitrary data in arbitrary ways. There is a 'hook' in the ethernet framework that allows ethernet packets to be TOTALY DIVERTED into netgraph (or only diverted if unrecognised). netgraph in turn has a means to feed the packets back into the normal stream after it has completed processing. (useful for wrapping for VPNs etc) It can feed them back into the ethernet framework to cntinue upwards as if nothing has happenned, into a virtual interface, out a socket, into another node, or out the transmit side of the original (or any other) interface. What it does depends entirely how you hook it toghther. Think of LEGO for networking. > > Thanks > Satya > -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 10:21:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from ams1.aignet.ro (ams1.aignet.ro [194.176.168.1]) by hub.freebsd.org (Postfix) with ESMTP id 490E837B503 for ; Mon, 19 Feb 2001 10:21:41 -0800 (PST) Received: from aignet.ro (ws3.aignet.ro [194.176.168.34]) by ams1.aignet.ro (8.11.0/8.11.0) with SMTP id f1JILo414491 for ; Mon, 19 Feb 2001 20:21:50 +0200 Message-ID: <3A91648E.C6B58389@aignet.ro> Date: Mon, 19 Feb 2001 20:23:11 +0200 From: Mihai Claudiu Capatina Organization: AIG S.A. X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: bridge+altq Content-Type: multipart/alternative; boundary="------------0B52C9A5216EFE488323ED01" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------0B52C9A5216EFE488323ED01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Can you please help me out with a problem. I am running ALTQ on a FreeBSD 4.2 which acts now as a router, but due to changes in the network i want this machine to act as a bridge and to make those traffic adjustments. Does this work...? If yes , what i have to do(???)....in FreeBSD doc it says the I have to make a new kernel with BRIDGE and DUMMYNET options and to add some lines to sysctl.conf Best Regards, -- Mihai Claudiu Capatina Wireless Network Manager & Network Administrator AIG S.A. ( http://www.aignet.ro ) Phone : +40 95 102862 / +40 1 3102895 Fax : +40 1 3102896 --------------0B52C9A5216EFE488323ED01 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  
Hi,

Can you please help me out with a problem.

I am running ALTQ on a FreeBSD 4.2 which acts now as a router, but due to changes

in the network i want this machine to act as a bridge and to make those traffic adjustments.

Does this work...?

If yes , what i have to do(???)....in FreeBSD doc it says the I have to make a new kernel

with BRIDGE and DUMMYNET options and to add some lines to sysctl.conf

Best Regards, 

-- 
Mihai Claudiu Capatina
Wireless Network Manager & Network Administrator

AIG S.A. ( http://www.aignet.ro )

Phone : +40 95 102862 / +40 1 3102895
Fax   : +40 1 3102896
  --------------0B52C9A5216EFE488323ED01-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 10:47:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from cicero2.cybercity.dk (cicero2.cybercity.dk [212.242.40.53]) by hub.freebsd.org (Postfix) with ESMTP id 45A2E37B684 for ; Mon, 19 Feb 2001 10:47:45 -0800 (PST) Received: from usr02.cybercity.dk (usr02.cybercity.dk [212.242.40.82]) by cicero2.cybercity.dk (Postfix) with ESMTP id AD98AFFFF5; Mon, 19 Feb 2001 19:47:40 +0100 (CET) Received: from asdf.dk (port18.ds1-noe.adsl.cybercity.dk [212.242.52.19]) by usr02.cybercity.dk (8.9.3/8.9.3) with ESMTP id TAA22053; Mon, 19 Feb 2001 19:47:34 +0100 (CET) (envelope-from hroi@asdf.dk) Message-ID: <3A916B97.1E817C26@asdf.dk> Date: Mon, 19 Feb 2001 19:53:11 +0100 From: Hroi Sigurdsson Organization: Expert Knob Twiddlers X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Archie Cobbs Cc: freebsd-net@FreeBSD.ORG Subject: Re: /usr/share/examples/netgraph/ether.bridge References: <200102190301.TAA93280@curve.dellroad.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Archie Cobbs wrote: > P.S. Has anyone actually used this script? Yep. Could you perhaps provide a sample pptpgre script? -- Hroi Sigurdsson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 14:41:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from klima.physik.uni-mainz.de (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by hub.freebsd.org (Postfix) with ESMTP id 79FD937B401; Mon, 19 Feb 2001 14:41:06 -0800 (PST) Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.physik.uni-mainz.de [134.93.180.54]) by klima.physik.uni-mainz.de (8.11.2/8.11.2) with ESMTP id f1JMiA909361; Mon, 19 Feb 2001 23:44:11 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Mon, 19 Feb 2001 23:44:10 +0100 (CET) From: "O. Hartmann" X-X-Sender: To: Cc: Subject: NIS/YP massiv problems, HELP! 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 Dear Sirs. Again, I would like to ask for some hints about NIS/YP. I already set up our domain and it contains a master and several slaves. Setting up master NIS server was easy, but slaves seems to be a great deal. Two of three servers should be slaves, and they also should be NIS clients. I also set up SecureRPC as described in the manpages, have inetd running with tcpwrapper facility for both internal and external services (inetd -lwW) and running IPFW. But the below described symptomes are still present when disabling tcpwrapping, ipfw and SecureRPC (means: switching off all related daemons, deleting all related files like /etc/publickey and /etc/.rootkey, ipfilter is transparent for all traffic coming from all over the net). On machines running ypserv (either ypserv -n or ypserv) and acting as slave servers I can not bind ypbind to this system nor running ypbind anyway. I tried to use ypbind -s -S Domain,Host1,host2 as host1 and host2 are names located in /etc/hosts (I use the same base file on master and slaves to avoid mistakes for especially this testing purpose) and ypbind -s or simply ypbind - but it is everytime the same: NIS does not work! On a client machine I can rund ypbind, but it never attaches to its master. ypbind is not able to communicate with the on the same host running ypserv daemon (why??). I tried prior to install a NIS/YP environment completely free of secure stuff (no IPFW, no warpper, no SecureRPC), but every time I ran make in /var/yp I got an error message: can not create UDP handle to slave server, host unknown or similar. Another very curious phenomenon is when trying to connect via ssh or telnet to a host running ypbind: telnet timed out after typing the loginname after a while when coming up and ssh crashes (seen on the console of the apropriate host, SIG 11) and dumps a core. On another machine, acting as DHCP server and boot server for our diskless X-terminals, tftp does not work, the x-client always reports a tftp timeout after it got its IP from the dhcp server. The communication with each of the faulty hosts is clear without NIS/YP, but it gets harsh when running ypbind ... -- MfG O. Hartmann ohartman@mail.physik.uni-mainz.de ---------------------------------------------------------------- IT-Administration des Institut fuer Physik der Atmosphaere (IPA) ---------------------------------------------------------------- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 14:49:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 84EA037B401 for ; Mon, 19 Feb 2001 14:49:47 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id OAA41732; Mon, 19 Feb 2001 14:49:43 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id OAA00665; Mon, 19 Feb 2001 14:49:43 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102192249.OAA00665@curve.dellroad.org> Subject: Re: /usr/share/examples/netgraph/ether.bridge In-Reply-To: <3A916B97.1E817C26@asdf.dk> "from Hroi Sigurdsson at Feb 19, 2001 07:53:11 pm" To: Hroi Sigurdsson Date: Mon, 19 Feb 2001 14:49:42 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hroi Sigurdsson writes: > > P.S. Has anyone actually used this script? > > Yep. Could you perhaps provide a sample pptpgre script? Sure.. but doing what? ng_pptpgre is normally used with PPTP (which requires a PPP daemon) and is automatically set up by that daemon, e.g. mpd. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 15: 4:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from secure.webhotel.net (secure.webhotel.net [195.41.202.80]) by hub.freebsd.org (Postfix) with SMTP id B82DB37B401 for ; Mon, 19 Feb 2001 15:04:50 -0800 (PST) Received: (qmail 84220013 invoked from network); 19 Feb 2001 23:07:24 -0000 Received: from mail-gateway.webhotel.net (195.41.202.215) by mail.webhotel.net with SMTP; 19 Feb 2001 23:07:24 -0000 X-Authenticated-Timestamp: 00:07:24(CET) on February 20, 2001 Received: (from hroi@localhost) by chewbacca.netgroup.dk (8.11.2/8.9.3) id f1JN4wH93395; Tue, 20 Feb 2001 00:04:58 +0100 (CET) (envelope-from hroi) Date: Tue, 20 Feb 2001 00:04:58 +0100 From: Hroi Sigurdsson To: Archie Cobbs Cc: Hroi Sigurdsson , freebsd-net@FreeBSD.ORG Subject: Re: /usr/share/examples/netgraph/ether.bridge Message-ID: <20010220000458.A91564@chewbacca.netgroup.dk> References: <3A916B97.1E817C26@asdf.dk> <200102192249.OAA00665@curve.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102192249.OAA00665@curve.dellroad.org>; from archie@dellroad.org on Mon, Feb 19, 2001 at 02:49:42PM -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Feb 19, 2001 at 02:49:42PM -0800, Archie Cobbs wrote: > Hroi Sigurdsson writes: > > > P.S. Has anyone actually used this script? > > > > Yep. Could you perhaps provide a sample pptpgre script? > > Sure.. but doing what? ng_pptpgre is normally used with PPTP (which > requires a PPP daemon) and is automatically set up by that daemon, > e.g. mpd. I was thinking of a script that set up the basic netgraph fiddlery and sockets for mpd to use with similar options as ether.bridge (up, down, stats). Maybe a script each for server and client configurations (if that makes sense). -- Hroi Sigurdsson hroi@netgroup.dk Netgroup A/S http://www.netgroup.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 15:21:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from panther.unisys.com.br (panther.unisys.com.br [200.220.64.10]) by hub.freebsd.org (Postfix) with ESMTP id 6FDAE37B6DC for ; Mon, 19 Feb 2001 15:21:24 -0800 (PST) Received: from router111sul (ppp205-bsace7009.telebrasilia.net.br [200.181.88.205]) by panther.unisys.com.br (8.11.1/8.11.1) with SMTP id f1JNJcH12782 for ; Mon, 19 Feb 2001 20:19:38 -0300 (BDB) Message-ID: <007b01c09ac9$a80be630$cd58b5c8@isiteleinformatica.com.br> From: "Romualdo Arcoverde" To: Subject: WAVELAN IBSS 2 Cards Date: Mon, 19 Feb 2001 20:14:05 -0300 Organization: UNINet Brasilia MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0078_01C09AB0.821E4F80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0078_01C09AB0.821E4F80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi. I am trying to put two pccards running in one unique machine and i get = this message: Feb 19 21:16:48 roteador111sul /kernel: wi0: Ethernet address: = 00:02:2d:02:83:59 Feb 19 21:16:48 roteador111sul pccardd[49]: wi0: Lucent Technologies = (WaveLAN/IE EE) inserted. Feb 19 21:16:51 roteador111sul /kernel: wi0: failed to allocate 1594 = bytes on NI C Feb 19 21:16:51 roteador111sul /kernel: wi0: tx buffer allocation failed Feb 19 21:16:51 roteador111sul /kernel: wi0: failed to allocate 1594 = bytes on NI C Feb 19 21:16:51 roteador111sul /kernel: wi0: mgmt. buffer allocation = failed=20 everytime, they are running anyway but something its wrong any help will = be good. Files: PCCARD.CONF # Generally available IO ports io 0x240-0x360 # Generally available IRQs (Built-in sound-card owners remove 5) irq 7 10 11 13 15 # Available memory slots memory 0xd0000 96k # Lucent WaveLAN/IEEE card "Lucent Technologies" "WaveLAN/IEEE" config auto "wi0" 7 config auto "wi1" 9 insert echo WaveLAN/IEEE inserted insert /etc/pccard_ether wi0 insert /etc/pccard_ether wi1 insert . /etc/wavelan.conf remove echo WaveLAN/IEEE removed remove /sbin/ifconfig wi0 delete remove /sbin/ifconfig wi1 delete=20 WAVELAN.CONF # Servidor AP wicontrol -i wi0 -p 1 wicontrol -i wi0 -c 1 wicontrol -i wi0 -n Servidor-AP wicontrol -i wi0 -s Router1 wicontrol -i wi0 -t 1 wicontrol -i wi0 -f 1 # Client AP wicontrol -i wi0 -p 1 wicontrol -i wi0 -n RedeTest wicontrol -i wi0 -s Test wicontrol -i wi0 -t 3=20 =20 Thanks Romualdo Arcoverde Unisys Network - Brasilia +55 (61) 4432768 ------=_NextPart_000_0078_01C09AB0.821E4F80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi.


I am trying to put two pccards running in one = unique=20 machine and i get this message:
 
 
Feb 19 21:16:48 roteador111sul /kernel: = wi0:=20 Ethernet address: 00:02:2d:02:83:59
Feb 19 21:16:48 roteador111sul=20 pccardd[49]: wi0: Lucent Technologies (WaveLAN/IE
EE) = inserted.
Feb 19=20 21:16:51 roteador111sul /kernel: wi0: failed to allocate 1594 bytes on=20 NI
C
Feb 19 21:16:51 roteador111sul /kernel: wi0: tx buffer = allocation=20 failed
Feb 19 21:16:51 roteador111sul /kernel: wi0: failed to = allocate 1594=20 bytes on NI
C
Feb 19 21:16:51 roteador111sul /kernel: wi0: mgmt. = buffer=20 allocation failed
 
everytime, they are running anyway but something its wrong any help = will be=20 good.
 
Files:
 
PCCARD.CONF
 
# Generally available IO=20 ports
io      0x240-0x360
# Generally = available=20 IRQs (Built-in sound-card owners remove = 5)
irq     7 10=20 11 13 15
# Available memory slots
memory  0xd0000 =20 96k
 
# Lucent WaveLAN/IEEE
card "Lucent = Technologies"=20 "WaveLAN/IEEE"
        = config  auto=20 "wi0" 7
        config  auto = "wi1"=20 9
        insert  echo = WaveLAN/IEEE=20 inserted
        insert =20 /etc/pccard_ether wi0
        = insert =20 /etc/pccard_ether wi1
        = insert =20 . /etc/wavelan.conf
        = remove =20 echo WaveLAN/IEEE removed
       =20 remove  /sbin/ifconfig wi0=20 delete
        remove  = /sbin/ifconfig=20 wi1 delete

WAVELAN.CONF
 
# Servidor AP
wicontrol -i wi0 -p = 1
wicontrol=20 -i wi0 -c 1
wicontrol -i wi0 -n Servidor-AP
wicontrol -i wi0 -s = Router1
wicontrol -i wi0 -t 1
wicontrol -i = wi0 -f=20 1
 
# Client AP
wicontrol -i wi0 -p = 1
wicontrol=20 -i wi0 -n RedeTest
wicontrol -i wi0 -s Test
wicontrol -i wi0 -t 3=20
           &nb= sp;       =20
Thanks
 
Romualdo Arcoverde
Unisys Network - Brasilia
+55 (61)=20 4432768
------=_NextPart_000_0078_01C09AB0.821E4F80-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 19:16:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from proxy.outblaze.com (proxy.outblaze.com [202.77.223.120]) by hub.freebsd.org (Postfix) with SMTP id CA91037B67D for ; Mon, 19 Feb 2001 19:16:36 -0800 (PST) Received: (qmail 19514 invoked from network); 20 Feb 2001 03:16:33 -0000 Received: from unknown (HELO yusufg.portal2.com) (202.77.181.217) by proxy.outblaze.com with SMTP; 20 Feb 2001 03:16:33 -0000 Received: (qmail 26380 invoked by uid 500); 20 Feb 2001 03:21:54 -0000 Date: Tue, 20 Feb 2001 11:21:54 +0800 From: Yusuf Goolamabbas To: Joao Carlos Mendes Luis Cc: Luigi Rizzo , freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, phk@FreeBSD.ORG, dwmalone@FreeBSD.ORG Subject: Re: Solved: Bridging and dummynet seems to destroy dmesg output Message-ID: <20010220112154.A26373@outblaze.com> References: <200101312212.f0VMCHj08290@iguana.aciri.org> <3A79B707.3DF0B6D@jonny.eng.br> <20010207142853.A30058@outblaze.com> <3A814168.533ADAFC@jonny.eng.br> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <3A814168.533ADAFC@jonny.eng.br>; from jonny@jonny.eng.br on Wed, Feb 07, 2001 at 10:36:56AM -0200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luigi, PHK Any resolution on this ? Regards, Yusuf > Hi Yusuf, > > As described by cvsweb, the patches to IPFW did not change the behavior > with log messages. To be more exactly, either netinet/ip_fw.c either > kern/subr_prf.c should be changed to match each other. In my local setup I > use a patch script after cvsup to fix ip_fw.c, removing all instances of > "LOG_SECURITY |". > > Luigi/Poul, have you at least decided where the changes should be made? > There's no log(9) man page to decide which one is the correct syntax. IMHO, > -stable is not stable while this bug persists. > > Yusuf Goolamabbas wrote: > > > > Hi, I cvsupped today and got all of Luigi's commit [the one where he > > does 1.16.2.13 of bridge.c alongwith a few others], I also have David > > Malone's fix to syslogd.c [1.59.2.5] > > > > If I don't have the following sysctl > > > > net.inet.ip.fw.verbose_limit=10 > > > > then dmesg gets busted as mentioned earlier and if I do a sync;reboot > > then I get a huge amount of ipfw messages scrolling on the console [It's > > as if they were backlogged in some buffer somewhere] and after a few > > seconds the syncing disk messages comes along > > > > I have the following in my kernel config > > > > options IPFIREWALL > > options IPFIREWALL_DEFAULT_TO_ACCEPT > > options BRIDGE > > options DUMMYNET > > > > my /etc/sysctl.conf is as follows > > > > net.link.ether.bridge_ipfw=1 > > net.link.ether.bridge=1 > > net.inet.ip.fw.verbose=1 > > net.inet.ip.fw.verbose_limit=10 > > > > > Luigi Rizzo wrote: > > > > > > > > > I tried only removing DUMMYNET from config, and the bug continues. Should > > > > > I try the changes below? > > > > > > > > no-they only affect dummynet. But this seems to suggest that > > > > the problem is unrelated to my changes... > > > > > > > > cheers > > > > luigi > > > > > > Hi, > > > > > > I found the problem! > > > > > > I started searching for the point where ipfw writes to the msgbuf, and > > > like all other kernel modules, it uses the log(9) function. But differently > > > from the other modules, ip_fw.c uses a LOG_SECURITY argument. I removed it, > > > recompiled, reboot, and BINGO! Probably the log(9) function does not expect a > > > facility parameter, as it is assumed to be LOG_KERNEL. > > > > > > Searching the cvsweb tree, I assume the changes that made it fail were > > > made to kern/subr_prf.c, and not directly to netinet/ip_fw.c. Probably a > > > longer search should be made to detect if any other call to log(9) uses this > > > approach. (CC: to phk, who made the change to kern/subr_prf.c, 1.61.2.1, at > > > 2000.01.16) > > > > > > Hoping this is the final solution and waiting for the cvs commit, thanks > > > to everybody, > > > > > > Jonny > > > > > > -- > > > João Carlos Mendes Luís jonny@embratel.net.br > > > Networking Engineer jonny@jonny.eng.br > > > Internet via Embratel jcml@ieee.org > > > > -- > > Yusuf Goolamabbas > > yusufg@outblaze.com > > -- > > Jonny > > -- > João Carlos Mendes Luís jonny@embratel.net.br > Networking Engineer jonny@jonny.eng.br > Internet via Embratel jcml@ieee.org -- Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 19:30:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 2B72C37B491; Mon, 19 Feb 2001 19:30:30 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f1K3UJC42482; Mon, 19 Feb 2001 19:30:19 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102200330.f1K3UJC42482@iguana.aciri.org> Subject: Re: Solved: Bridging and dummynet seems to destroy dmesg output In-Reply-To: <20010220112154.A26373@outblaze.com> from Yusuf Goolamabbas at "Feb 20, 2001 11:21:54 am" To: yusufg@outblaze.com (Yusuf Goolamabbas) Date: Mon, 19 Feb 2001 19:30:19 -0800 (PST) Cc: jonny@jonny.eng.br, rizzo@aciri.org, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, phk@FreeBSD.ORG, dwmalone@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Luigi, PHK > > Any resolution on this ? for sure there is no bug in ip_fw.c -- the change mentioned below just happens to change some symptoms but is no fix. The message buffer is not "busted" as the report says, just has some NULs here and there that (probably) dmesg is not handling correctly. Poul, do you know more ? cheers luigi > Regards, Yusuf > > > Hi Yusuf, > > > > As described by cvsweb, the patches to IPFW did not change the behavior > > with log messages. To be more exactly, either netinet/ip_fw.c either > > kern/subr_prf.c should be changed to match each other. In my local setup I > > use a patch script after cvsup to fix ip_fw.c, removing all instances of > > "LOG_SECURITY |". > > > > Luigi/Poul, have you at least decided where the changes should be made? > > There's no log(9) man page to decide which one is the correct syntax. IMHO, > > -stable is not stable while this bug persists. > > > > Yusuf Goolamabbas wrote: > > > > > > Hi, I cvsupped today and got all of Luigi's commit [the one where he > > > does 1.16.2.13 of bridge.c alongwith a few others], I also have David > > > Malone's fix to syslogd.c [1.59.2.5] > > > > > > If I don't have the following sysctl > > > > > > net.inet.ip.fw.verbose_limit=10 > > > > > > then dmesg gets busted as mentioned earlier and if I do a sync;reboot > > > then I get a huge amount of ipfw messages scrolling on the console [It's > > > as if they were backlogged in some buffer somewhere] and after a few > > > seconds the syncing disk messages comes along > > > > > > I have the following in my kernel config > > > > > > options IPFIREWALL > > > options IPFIREWALL_DEFAULT_TO_ACCEPT > > > options BRIDGE > > > options DUMMYNET > > > > > > my /etc/sysctl.conf is as follows > > > > > > net.link.ether.bridge_ipfw=1 > > > net.link.ether.bridge=1 > > > net.inet.ip.fw.verbose=1 > > > net.inet.ip.fw.verbose_limit=10 > > > > > > > Luigi Rizzo wrote: > > > > > > > > > > > I tried only removing DUMMYNET from config, and the bug continues. Should > > > > > > I try the changes below? > > > > > > > > > > no-they only affect dummynet. But this seems to suggest that > > > > > the problem is unrelated to my changes... > > > > > > > > > > cheers > > > > > luigi > > > > > > > > Hi, > > > > > > > > I found the problem! > > > > > > > > I started searching for the point where ipfw writes to the msgbuf, and > > > > like all other kernel modules, it uses the log(9) function. But differently > > > > from the other modules, ip_fw.c uses a LOG_SECURITY argument. I removed it, > > > > recompiled, reboot, and BINGO! Probably the log(9) function does not expect a > > > > facility parameter, as it is assumed to be LOG_KERNEL. > > > > > > > > Searching the cvsweb tree, I assume the changes that made it fail were > > > > made to kern/subr_prf.c, and not directly to netinet/ip_fw.c. Probably a > > > > longer search should be made to detect if any other call to log(9) uses this > > > > approach. (CC: to phk, who made the change to kern/subr_prf.c, 1.61.2.1, at > > > > 2000.01.16) > > > > > > > > Hoping this is the final solution and waiting for the cvs commit, thanks > > > > to everybody, > > > > > > > > Jonny > > > > > > > > -- > > > > João Carlos Mendes Luís jonny@embratel.net.br > > > > Networking Engineer jonny@jonny.eng.br > > > > Internet via Embratel jcml@ieee.org > > > > > > -- > > > Yusuf Goolamabbas > > > yusufg@outblaze.com > > > > -- > > > > Jonny > > > > -- > > João Carlos Mendes Luís jonny@embratel.net.br > > Networking Engineer jonny@jonny.eng.br > > Internet via Embratel jcml@ieee.org > > -- > Yusuf Goolamabbas > yusufg@outblaze.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 20: 0:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from thor.oit.pdx.edu (thor.oit.pdx.edu [131.252.120.40]) by hub.freebsd.org (Postfix) with ESMTP id 38EA037B4EC; Mon, 19 Feb 2001 20:00:16 -0800 (PST) Received: from freke.odin.pdx.edu (freke.odin.pdx.edu [131.252.120.43]) by thor.oit.pdx.edu (8.11.1/8.11.1) with ESMTP id f1K40DU25438; Mon, 19 Feb 2001 20:00:13 -0800 (PST) Received: from localhost (singh@localhost) by freke.odin.pdx.edu (8.11.1/8.11.1) with ESMTP id f1K40Dj27087; Mon, 19 Feb 2001 20:00:13 -0800 (PST) X-Authentication-Warning: freke.odin.pdx.edu: singh owned process doing -bs Date: Mon, 19 Feb 2001 20:00:13 -0800 (PST) From: Harkirat Singh X-X-Sender: To: Cc: , Subject: Mobile Network 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 made one ad-hoc network with three mobile nodes all are running with FreeBSD 3.2 and Lucent WaveLan. Brief setup is as follows: x x x (node A) (node B) (node C) B is acting as a router, A and C both have B as a default entry. I also delete C from A's routing table and A from C's routing table so that though they are phically near to each other but are logically apart and forced to go through B. I am doing all these things manually with route(8) command. I want to have one more router "D" and after every t sec I want to change route to D, means route from A to C would be as A -> D -> C not A -> B -> C. I want to know as how can I do this automatically. Any advise will be highly appreciated. Thanks, Harkirat Singh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 19 23:30: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id E5A4A37B503 for ; Mon, 19 Feb 2001 23:30:00 -0800 (PST) (envelope-from archie@dellroad.org) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id XAA45340; Mon, 19 Feb 2001 23:29:59 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.11.2/8.11.2) id f1K7TwH04201; Mon, 19 Feb 2001 23:29:58 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102200729.f1K7TwH04201@curve.dellroad.org> Subject: Re: /usr/share/examples/netgraph/ether.bridge In-Reply-To: <20010220000458.A91564@chewbacca.netgroup.dk> "from Hroi Sigurdsson at Feb 20, 2001 00:04:58 am" To: Hroi Sigurdsson Date: Mon, 19 Feb 2001 23:29:58 -0800 (PST) Cc: Archie Cobbs , Hroi Sigurdsson , freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hroi Sigurdsson writes: > > > > P.S. Has anyone actually used this script? > > > > > > Yep. Could you perhaps provide a sample pptpgre script? > > > > Sure.. but doing what? ng_pptpgre is normally used with PPTP (which > > requires a PPP daemon) and is automatically set up by that daemon, > > e.g. mpd. > > I was thinking of a script that set up the basic netgraph fiddlery > and sockets for mpd to use with similar options as ether.bridge > (up, down, stats). Maybe a script each for server and client > configurations (if that makes sense). You could do that if you wanted to, but there's not much point since mpd already handles it for you. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 2:41:29 2001 Delivered-To: freebsd-net@freebsd.org Received: from ausmtp02.au.ibm.com (ausmtp02.au.ibm.COM [202.135.136.105]) by hub.freebsd.org (Postfix) with ESMTP id 1B97537B503 for ; Tue, 20 Feb 2001 02:41:25 -0800 (PST) (envelope-from skodati@in.ibm.com) Received: from f03n05e.au.ibm.com by ausmtp02.au.ibm.com (IBM AP 1.0) with ESMTP id VAA183052 for ; Tue, 20 Feb 2001 21:32:20 +1100 From: skodati@in.ibm.com Received: from d73mta05.au.ibm.com (f06n05s [9.185.166.67]) by f03n05e.au.ibm.com (8.8.8m3/NCO v4.95) with SMTP id VAA35138 for ; Tue, 20 Feb 2001 21:41:22 +1100 Received: by d73mta05.au.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id CA2569F9.003AB73A ; Tue, 20 Feb 2001 21:41:19 +1100 X-Lotus-FromDomain: IBMIN@IBMAU To: freebsd-net@freebsd.org Message-ID: Date: Tue, 20 Feb 2001 16:04:11 +0530 Subject: Query: SIOCGIFAFLAGS_IN6 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Iam a newbie to FreeBSD and iam working on DHCPv6. i would like to know the importance of SIOCGIFAFLAGS_IN6 defined in in6_var.h The definition of structure in6_ifreq differs from the definition of in6_ifreq defined in Linux 2.4.0, and creates woes to port it. Do i have any alternatives for the above for Linux . thanks and regards Suresh Kodati Email:- skodati@in.ibm.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 2:57:35 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 86A1137B491 for ; Tue, 20 Feb 2001 02:57:32 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id TAA17794; Tue, 20 Feb 2001 19:57:22 +0900 (JST) To: skodati@in.ibm.com Cc: freebsd-net@freebsd.org In-reply-to: skodati's message of Tue, 20 Feb 2001 16:04:11 +0530. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: Query: SIOCGIFAFLAGS_IN6 From: itojun@iijlab.net Date: Tue, 20 Feb 2001 19:57:22 +0900 Message-ID: <17792.982666642@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Iam a newbie to FreeBSD and iam working on DHCPv6. i would like to know the >importance of SIOCGIFAFLAGS_IN6 defined in in6_var.h >The definition of structure in6_ifreq differs from the definition of >in6_ifreq defined in Linux 2.4.0, and creates woes to port it. >Do i have any alternatives for the above for Linux . interface management ioctls are not standardized in any place (as far as I know of). if you would like to support both *BSD and linux, you definitely need some #ifdef in your code, or use /sbin/ifconfig. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 3:35: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from stewart.chicago.il.us (dsl-64-128-23-213.telocity.com [64.128.23.213]) by hub.freebsd.org (Postfix) with ESMTP id DBC8537B4EC for ; Tue, 20 Feb 2001 03:35:03 -0800 (PST) (envelope-from randall@stewart.chicago.il.us) Received: from stewart.chicago.il.us (IDENT:randall@stewart.chicago.il.us [10.1.1.1]) by stewart.chicago.il.us (8.9.3/8.8.7) with ESMTP id FAA04279; Tue, 20 Feb 2001 05:33:53 -0600 Message-ID: <3A925620.358EAA4C@stewart.chicago.il.us> Date: Tue, 20 Feb 2001 05:33:52 -0600 From: "Randall R. Stewart" X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: Romualdo Arcoverde Cc: freebsd-net@FreeBSD.ORG Subject: Re: WAVELAN IBSS 2 Cards References: <007b01c09ac9$a80be630$cd58b5c8@isiteleinformatica.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Romualdo: If I remember correctly one of my co-workers has had a similar problem. It is due to the fact that the pccard only allocates one and only one instance of a card (I am re-iterating things he told me mind you). I remember he said he was going to hack the pccard stuff to allow two cards but I don't remember how far he has gotten.. Peter, how far did you get? R > Romualdo Arcoverde wrote: > > Hi. > > I am trying to put two pccards running in one unique machine and i get > this message: > > > Feb 19 21:16:48 roteador111sul /kernel: wi0: Ethernet address: > 00:02:2d:02:83:59 > Feb 19 21:16:48 roteador111sul pccardd[49]: wi0: Lucent Technologies > (WaveLAN/IE > EE) inserted. > Feb 19 21:16:51 roteador111sul /kernel: wi0: failed to allocate 1594 > bytes on NI > C > Feb 19 21:16:51 roteador111sul /kernel: wi0: tx buffer allocation > failed > Feb 19 21:16:51 roteador111sul /kernel: wi0: failed to allocate 1594 > bytes on NI > C > Feb 19 21:16:51 roteador111sul /kernel: wi0: mgmt. buffer allocation > failed > > everytime, they are running anyway but something its wrong any help > will be good. > > Files: > > PCCARD.CONF > > # Generally available IO ports > io 0x240-0x360 > # Generally available IRQs (Built-in sound-card owners remove 5) > irq 7 10 11 13 15 > # Available memory slots > memory 0xd0000 96k > > # Lucent WaveLAN/IEEE > card "Lucent Technologies" "WaveLAN/IEEE" > config auto "wi0" 7 > config auto "wi1" 9 > insert echo WaveLAN/IEEE inserted > insert /etc/pccard_ether wi0 > insert /etc/pccard_ether wi1 > insert . /etc/wavelan.conf > remove echo WaveLAN/IEEE removed > remove /sbin/ifconfig wi0 delete > remove /sbin/ifconfig wi1 delete > > WAVELAN.CONF > > # Servidor AP > wicontrol -i wi0 -p 1 > wicontrol -i wi0 -c 1 > wicontrol -i wi0 -n Servidor-AP > wicontrol -i wi0 -s Router1 > wicontrol -i wi0 -t 1 > wicontrol -i wi0 -f 1 > > # Client AP > wicontrol -i wi0 -p 1 > wicontrol -i wi0 -n RedeTest > wicontrol -i wi0 -s Test > wicontrol -i wi0 -t 3 > > Thanks > > Romualdo Arcoverde > Unisys Network - Brasilia > +55 (61) 4432768 -- Randall R. Stewart randall@stewart.chicago.il.us or rrs@cisco.com 815-342-5222 (cell) 815-477-2127 (work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 4:11:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail2.netvision.com.br (nv37.netvision.com.br [200.215.94.37]) by hub.freebsd.org (Postfix) with ESMTP id 2544A37B401 for ; Tue, 20 Feb 2001 04:11:20 -0800 (PST) (envelope-from andre@netvision.com.br) Received: from nv12.netvision.com.br (nv12.netvision.com.br [200.247.217.134]) by mail2.netvision.com.br (Postfix) with SMTP id 68432175D for ; Tue, 20 Feb 2001 10:10:21 -0300 (BET) Content-Type: text/plain; charset="iso-8859-1" From: =?iso-8859-1?q?Andr=E9=20Luiz=20dos=20Santos?= Reply-To: andre@netvision.com.br To: freebsd-net@FreeBSD.ORG Subject: Finding what rule match on IPFW. Date: Mon, 19 Feb 2001 20:39:22 +0000 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01021920392200.00796@nv12.netvision.com.br> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there a program that does for ipfw what "route get" does for the route table? I couldn't find anything like the get option for route on ipfw. I've too many ipfw rules on one machine here and finding where a certain packet match is not very easy when looking rule by rule. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 4:15:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E90A737B491 for ; Tue, 20 Feb 2001 04:15:44 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1KCFdV17621; Tue, 20 Feb 2001 04:15:39 -0800 (PST) Date: Tue, 20 Feb 2001 04:15:39 -0800 From: Alfred Perlstein To: =?iso-8859-1?Q?Andr=E9_Luiz_dos_Santos?= Cc: freebsd-net@FreeBSD.ORG Subject: Re: Finding what rule match on IPFW. Message-ID: <20010220041539.U6641@fw.wintelcom.net> References: <01021920392200.00796@nv12.netvision.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <01021920392200.00796@nv12.netvision.com.br>; from andre@netvision.com.br on Mon, Feb 19, 2001 at 08:39:22PM +0000 X-all-your-base: are belong to us. Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * André Luiz dos Santos [010220 04:11] wrote: > > Is there a program that does for ipfw what "route get" does for the route > table? I couldn't find anything like the get option for route on ipfw. > I've too many ipfw rules on one machine here and finding where a certain > packet match is not very easy when looking rule by rule. I'm pretty sure you can play with the logging options while debugging and look at /var/log/security for it. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 4:28:30 2001 Delivered-To: freebsd-net@freebsd.org Received: from panther.unisys.com.br (panther.unisys.com.br [200.220.64.10]) by hub.freebsd.org (Postfix) with ESMTP id 3DB4C37B401; Tue, 20 Feb 2001 04:28:17 -0800 (PST) (envelope-from romualdo@uninet.com.br) Received: from router111sul (ppp205-bsace7009.telebrasilia.net.br [200.181.88.205]) by panther.unisys.com.br (8.11.1/8.11.1) with SMTP id f1KCQTT16074; Tue, 20 Feb 2001 09:26:29 -0300 (BDB) Message-ID: <002901c09b37$95e5b620$cd58b5c8@isiteleinformatica.com.br> From: "Romualdo Arcoverde" To: "Randall R. Stewart" Cc: , References: <007b01c09ac9$a80be630$cd58b5c8@isiteleinformatica.com.br> <3A925620.358EAA4C@stewart.chicago.il.us> Subject: Re: WAVELAN IBSS 2 Cards Date: Tue, 20 Feb 2001 09:20:59 -0300 Organization: UNINet Brasilia 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.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I dont change any thing and its work the only problem i have to reset the box some times. I believe some thing its wrong at my pccard.conf Romualdo Arcoverde Unisys Network - Brasilia +55 (61) 4432768 ----- Original Message ----- From: "Randall R. Stewart" To: "Romualdo Arcoverde" Cc: Sent: Tuesday, February 20, 2001 8:33 AM Subject: Re: WAVELAN IBSS 2 Cards > Romualdo: > > If I remember correctly one of my co-workers has > had a similar problem. It is due to the fact that > the pccard only allocates one and only one instance > of a card (I am re-iterating things he told me mind > you). I remember he said he was going to hack the > pccard stuff to allow two cards but I don't remember > how far he has gotten.. > > Peter, how far did you get? > > R > > > Romualdo Arcoverde wrote: > > > > Hi. > > > > I am trying to put two pccards running in one unique machine and i get > > this message: > > > > > > Feb 19 21:16:48 roteador111sul /kernel: wi0: Ethernet address: > > 00:02:2d:02:83:59 > > Feb 19 21:16:48 roteador111sul pccardd[49]: wi0: Lucent Technologies > > (WaveLAN/IE > > EE) inserted. > > Feb 19 21:16:51 roteador111sul /kernel: wi0: failed to allocate 1594 > > bytes on NI > > C > > Feb 19 21:16:51 roteador111sul /kernel: wi0: tx buffer allocation > > failed > > Feb 19 21:16:51 roteador111sul /kernel: wi0: failed to allocate 1594 > > bytes on NI > > C > > Feb 19 21:16:51 roteador111sul /kernel: wi0: mgmt. buffer allocation > > failed > > > > everytime, they are running anyway but something its wrong any help > > will be good. > > > > Files: > > > > PCCARD.CONF > > > > # Generally available IO ports > > io 0x240-0x360 > > # Generally available IRQs (Built-in sound-card owners remove 5) > > irq 7 10 11 13 15 > > # Available memory slots > > memory 0xd0000 96k > > > > # Lucent WaveLAN/IEEE > > card "Lucent Technologies" "WaveLAN/IEEE" > > config auto "wi0" 7 > > config auto "wi1" 9 > > insert echo WaveLAN/IEEE inserted > > insert /etc/pccard_ether wi0 > > insert /etc/pccard_ether wi1 > > insert . /etc/wavelan.conf > > remove echo WaveLAN/IEEE removed > > remove /sbin/ifconfig wi0 delete > > remove /sbin/ifconfig wi1 delete > > > > WAVELAN.CONF > > > > # Servidor AP > > wicontrol -i wi0 -p 1 > > wicontrol -i wi0 -c 1 > > wicontrol -i wi0 -n Servidor-AP > > wicontrol -i wi0 -s Router1 > > wicontrol -i wi0 -t 1 > > wicontrol -i wi0 -f 1 > > > > # Client AP > > wicontrol -i wi0 -p 1 > > wicontrol -i wi0 -n RedeTest > > wicontrol -i wi0 -s Test > > wicontrol -i wi0 -t 3 > > > > Thanks > > > > Romualdo Arcoverde > > Unisys Network - Brasilia > > +55 (61) 4432768 > > -- > Randall R. Stewart > randall@stewart.chicago.il.us or rrs@cisco.com > 815-342-5222 (cell) 815-477-2127 (work) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 4:53:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from panther.unisys.com.br (panther.unisys.com.br [200.220.64.10]) by hub.freebsd.org (Postfix) with ESMTP id CB9B937B401 for ; Tue, 20 Feb 2001 04:53:27 -0800 (PST) (envelope-from freebsd@isiteleinformatica.com.br) Received: from router111sul (ppp205-bsace7009.telebrasilia.net.br [200.181.88.205]) by panther.unisys.com.br (8.11.1/8.11.1) with SMTP id f1KCpjT01873 for ; Tue, 20 Feb 2001 09:51:46 -0300 (BDB) Message-ID: <003401c09b3b$1d9df200$cd58b5c8@isiteleinformatica.com.br> From: "Romualdo Arcoverde" To: Subject: subscribe Date: Tue, 20 Feb 2001 09:46:15 -0300 Organization: UNINet Brasilia MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0031_01C09B21.F7626260" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0031_01C09B21.F7626260 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0031_01C09B21.F7626260 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0031_01C09B21.F7626260-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 5:58:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from hera.drwilco.net (isis.drwilco.net [194.109.63.159]) by hub.freebsd.org (Postfix) with ESMTP id 075AF37B401 for ; Tue, 20 Feb 2001 05:58:53 -0800 (PST) (envelope-from drwilco@drwilco.nl) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.2/8.11.1) with ESMTP id f1G73to37497 for ; Fri, 16 Feb 2001 08:03:56 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010216074025.00dbc710@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 16 Feb 2001 07:40:32 +0100 To: freebsd-net@FreeBSD.ORG From: "Rogier R. Mulhuijzen" Subject: Re: Do I need to run RouteD/GateD? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 19:11 15-2-01 -0800, you wrote: >Hello there, > > I am trying to set up a simple net work at home. >Here is my exisiting setup: >1) I have a DSL router which does NAT which everyone >on the LAN connects to. The address for the DSL >router is 1.2.3.1 Bad idea. For internal networks you should use an IP block in the range of 10.0.0.0-10.255.255.255.255, 172.16.0.0-172.31.255.255 or 192.168.0.0-192.168.255.255. You will find a lot of people use 192.168.1.* netmask 255.255.255.0 >2) Everyone on the LAN connects to the router and uses >1.2.3.1 as gateway (net mast 255.255.255.0) >3) I have a FreeBSD box (1.2.3.10), which I have my >mail server, webserver, and other goodies on it, which >everyone is happily connected to. >4) I set up DHCPD already, so everyone is getting >their addresses in the range I specified. > > Now, I want to use my FreeBSD box as a public >wireless base station using Orinoco card (wi0). In >theory, everyone close to me can connect to the >wireless interface. So, here is what I am thinking >about doing: > >1) I have recompiled my BSD box with ipfw on, and ipfw >working, and I have set "gateway_enable=YES" in my >rc.conf >2) I want to take my laptop and connect to my BSD box >wirelessly and get address from the DHCPD, and I want >to be able to access all the resource on my wired LAN. > e.g. the mail server, webserver, or chat with another >person on the wired LAN. >3) I am semi paranoid about all the hackers in my >neighborhood, so, I want to use IPFW on some of the >traffic from my wireless interface. And since IPFW >can ony block base on IP addresses, not ETHERNET >address, this basically forced me to use DHCPD to >assign FIXED ADDRESS to known ETHERNET ADDRESS. (this >makes DHCPD looks like an overkill.) So, now I can >finally use IPFW rules to block evil traffics from the >wireless interface > > So, finally, my question: on the wireless side, >everyone uses the FREEBSD as the gateway, so I can see >the traffic can go from wireless side->FreeBSD->DSL >Router->Internet. But, how about coming back? if the traffic goes through any network > Do I >need to run routed, or gated so that everyone on the >wired LAN knows to use the BSD box as a router? No, gated/routed are daemons that are used for dynamic routing. A rather complicated matter. Most clients will not absolutely not listen to the protocol they use to communicate with other routers. DHCP however can be used for this purpose. > How >does the DSL router know how to send packets back to >the wireless side? You will need to setup a route in the DSL router telling it where to send stuff. But that would be hard to do since right now you have the same IP block on your wired LAN as on your wireless LAN. What you should do is use 2 different IP blocks. Say for instance 10.190.1.* on wired, and 10.190.2.* on wireless. Now DSL router would be 10.190.1.1, FreeBSD machine 10.190.1.10 on wired side. On the wireless side FreeBSD would have 10.190.2.1. All other machines on wireless would need an IP in the same range of course, and use 10.190.2.1 as default gateway. Then you make a new entry in the routing table on the DSL router, telling it to send all packets for 10.190.2.0 netmask 255.255.255.0 (usually written as 10.190.2.0/24 or 10.190.2/24) to 10.190.1.10. And then you're set. (I use 10.* a lot because in my neck of the woods 192.* 193.* and 195.* are pretty common, and 10.* looks sufficiently different, so I can tell internal IPs from external IPs at a glance, YMMV) >Thanks, >Howard > >P.S : Any good security suggestions are welcomed as >well. :) Don't use any cleartext authentication over wireless. Furthermore, you should know that on wired networks, spoofing a MAC (ethernet) address is relatively easy (if you know what you're doing). I'm not up to speed however on the wireless stuff. Maybe they can do some encryption, and use a certain key to protect networks from "intruders". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 6:15:51 2001 Delivered-To: freebsd-net@freebsd.org Received: from relay.tecc.co.uk (luggage.tecc.co.uk [193.128.6.129]) by hub.freebsd.org (Postfix) with SMTP id C0CCA37B6AF for ; Tue, 20 Feb 2001 06:15:44 -0800 (PST) (envelope-from andy@tecc.co.uk) Received: from fw-smtp.tecc.co.uk [195.217.37.39] by relay.tecc.co.uk with esmtp (Exim 1.70 #1) id 14VDZv-0004b7-00; Tue, 20 Feb 2001 14:15:43 +0000 Received: from [195.217.37.155] (helo=southampton) by fw-smtp.tecc.co.uk with smtp (Exim 2.12 #3) id 14VDY1-00039b-00 for freebsd-net@freebsd.org; Tue, 20 Feb 2001 14:13:45 +0000 From: "Andy [TECC NOPS]" To: Subject: Question Date: Tue, 20 Feb 2001 14:18:48 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello All, I'm currently working on adding functionality to FreeBSD that is provided by Cisc0's product range called "Local Director" to allow FreeBSD to act as a high availability router. Now, I have in place the VRRP code/protocol to enable redundent router boxes and was moving onto the backend. So, what's my question? Well, the libalias.a library has a function called PacketAliasAddServer() which natd uses to create a pool of backend server addresses. However, there does not seem to be an associated function PacketAliasRemoveServer(). Is there a reason for this? I guess I'll deleve in more and write it if required (only seems to be a linked list) and send the patch to the list for inclusion if required. I only ask this as I'm somewhat bemused that's it's not already there? Is there some fundamental reason that I am missing? Regards Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 6:18: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id 1A62637B401 for ; Tue, 20 Feb 2001 06:18:05 -0800 (PST) (envelope-from jcv@vbc.net) Received: from localhost (jcv@localhost) by brunel.uk1.vbc.net (8.11.0/8.11.0) with ESMTP id f1KEI3d59254 for ; Tue, 20 Feb 2001 14:18:03 GMT X-Authentication-Warning: brunel.uk1.vbc.net: jcv owned process doing -bs Date: Tue, 20 Feb 2001 14:18:03 +0000 (GMT) From: Jean-Christophe Varaillon X-Sender: jcv@brunel.uk1.vbc.net To: freebsd-net@FreeBSD.ORG Subject: - RISCom card: lcp illegal conf-req in state initial - In-Reply-To: <4.3.2.7.0.20010216074025.00dbc710@mail.bsdchicks.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 Hi all, I am actualy trying to establish the communication between a cisco router and my Free BSD machine. +-------+ +---------------+ | cisco |serial interface | FreeBSD 4.1 | | 3600 +-----------------------+ | | | RISCom | | +-------+ card +---------------+ x.x.x.145 x.x.x.146 I beleive that the router is correclty configured but NOT the FreeBSD machine. This is what dmesg | grep sr1 shows: -------- sr1: Adapter 0, port 1. sr1 XXX: driver didn't set ifq_maxlen sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. ... sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. sr1: Down event, taking interface down. ... sr1: Down event, taking interface down. sr1: Down event, taking interface down. sr1: lcp illegal conf-req in state initial ... sr1: lcp illegal conf-req in state initial sr1: lcp illegal conf-req in state initial -------- This is the ifconfig: ------- sr1: flags=8451 mtu 1500 inet6 fe80::2d0:b7ff:fe09:3333%sr1 --> :: prefixlen 64 scopeid 0x2 inet x.x.x.146 --> x.x.x.145 netmask 0xfffffffc ------ any suggestion... Thanks, JC. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 6:38:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from relay.tecc.co.uk (luggage.tecc.co.uk [193.128.6.129]) by hub.freebsd.org (Postfix) with SMTP id BC6E437B491 for ; Tue, 20 Feb 2001 06:38:32 -0800 (PST) (envelope-from andy@tecc.co.uk) Received: from fw-smtp.tecc.co.uk [195.217.37.39] by relay.tecc.co.uk with esmtp (Exim 1.70 #1) id 14VDvz-0004uW-00; Tue, 20 Feb 2001 14:38:31 +0000 Received: from [195.217.37.155] (helo=southampton) by fw-smtp.tecc.co.uk with smtp (Exim 2.12 #3) id 14VDu5-0003HZ-00; Tue, 20 Feb 2001 14:36:33 +0000 From: "Andy [TECC NOPS]" To: "Jean-Christophe Varaillon" , Subject: RE: - RISCom card: lcp illegal conf-req in state initial - Date: Tue, 20 Feb 2001 14:41:37 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Think I know more about Cisco than RISCom cards but here's my 2p worth:- 1. I take it the connecting cable is an X21 null modem cable? If so, you have got it the right way round cos the connectors are the same and one end is dce the other dte. 2. The cisco will be expecting the serial clock rate to be applied by the ntu. However, I don't know whether the RISCom card is providing this. In this case you'll need a clock, which the cisco 3600 can do, aka:- >cisco# conf t >cisco(conf)# int s0 >cisco(conf-int)# clockrate 64000 (or whatever in multipls of 64) You'll now be sourcing the sync clock. 3. What card have you in the 3600 slot? If it's one of those 8 serial port cards the max clock rate is 128Kbps I've fallen foul of this one before! Hope that helps Regards Andy > -----Original Message----- > From: owner-freebsd-net@FreeBSD.ORG > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Jean-Christophe > Varaillon > Sent: 20 February 2001 14:18 > To: freebsd-net@FreeBSD.ORG > Subject: - RISCom card: lcp illegal conf-req in state initial - > > > Hi all, > > I am actualy trying to establish the communication between a cisco router > and my Free BSD machine. > > +-------+ +---------------+ > | cisco |serial interface | FreeBSD 4.1 | > | 3600 +-----------------------+ | > | | RISCom | | > +-------+ card +---------------+ > x.x.x.145 x.x.x.146 > > I beleive that the router is correclty configured but NOT the FreeBSD > machine. > > This is what dmesg | grep sr1 shows: > -------- > sr1: Adapter 0, port 1. > sr1 XXX: driver didn't set ifq_maxlen > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > ... > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > sr1: Down event, taking interface down. > ... > sr1: Down event, taking interface down. > sr1: Down event, taking interface down. > sr1: lcp illegal conf-req in state initial > ... > sr1: lcp illegal conf-req in state initial > sr1: lcp illegal conf-req in state initial > -------- > > This is the ifconfig: > ------- > sr1: flags=8451 mtu 1500 > inet6 fe80::2d0:b7ff:fe09:3333%sr1 --> :: prefixlen 64 > scopeid 0x2 > inet x.x.x.146 --> x.x.x.145 netmask 0xfffffffc > ------ > > > > any suggestion... > > Thanks, > > JC. > > > 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 Tue Feb 20 7: 4:21 2001 Delivered-To: freebsd-net@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id C7C0D37B401 for ; Tue, 20 Feb 2001 07:04:16 -0800 (PST) (envelope-from jcv@vbc.net) Received: from localhost (jcv@localhost) by brunel.uk1.vbc.net (8.11.0/8.11.0) with ESMTP id f1KF4Fm59588; Tue, 20 Feb 2001 15:04:15 GMT X-Authentication-Warning: brunel.uk1.vbc.net: jcv owned process doing -bs Date: Tue, 20 Feb 2001 15:04:14 +0000 (GMT) From: Jean-Christophe Varaillon X-Sender: jcv@brunel.uk1.vbc.net To: "Andy [TECC NOPS]" Cc: freebsd-net@FreeBSD.ORG Subject: RE: - RISCom card: lcp illegal conf-req in state initial - 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 Thanks for your prompt repply. On Tue, 20 Feb 2001, Andy [TECC NOPS] wrote: > Hi > > Think I know more about Cisco than RISCom cards > but here's my 2p worth:- > > 1. I take it the connecting cable is an X21 null > modem cable? If so, you have got it the right > way round cos the connectors are the same and one > end is dce the other dte. I have 2 cables plugged together: 1 2 Cisco }------{ }------{ Free BSD a b Cable 1: On the cisco end: X21 DCE On the other extremity (a): Female like this: ........ ...... Cable 2 On the extremity (b): Male like that: ........ ...... On the FreeBSD end: It is a male like this: ........ ........ ....... > 2. Serial0/0 is up, line protocol is down The clock is set (by the router) at clockrate 2015232 > > -----Original Message----- > > From: owner-freebsd-net@FreeBSD.ORG > > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Jean-Christophe > > Varaillon > > Sent: 20 February 2001 14:18 > > To: freebsd-net@FreeBSD.ORG > > Subject: - RISCom card: lcp illegal conf-req in state initial - > > > > > > Hi all, > > > > I am actualy trying to establish the communication between a cisco router > > and my Free BSD machine. > > > > +-------+ +---------------+ > > | cisco |serial interface | FreeBSD 4.1 | > > | 3600 +-------------------+ | > > | | RISCom | | > > +-------+ card +---------------+ > > x.x.x.145 x.x.x.146 > > > > I beleive that the router is correclty configured but NOT the FreeBSD > > machine. > > > > This is what dmesg | grep sr1 shows: > > -------- > > sr1: Adapter 0, port 1. > > sr1 XXX: driver didn't set ifq_maxlen > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > ... > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > sr1: Down event, taking interface down. > > ... > > sr1: Down event, taking interface down. > > sr1: Down event, taking interface down. > > sr1: lcp illegal conf-req in state initial > > ... > > sr1: lcp illegal conf-req in state initial > > sr1: lcp illegal conf-req in state initial > > -------- > > > > This is the ifconfig: > > ------- > > sr1: flags=8451 mtu 1500 > > inet6 fe80::2d0:b7ff:fe09:3333%sr1 --> :: prefixlen 64 > > scopeid 0x2 > > inet x.x.x.146 --> x.x.x.145 netmask 0xfffffffc > > ------ > > > > Thanks, > > > > JC. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 7:21:25 2001 Delivered-To: freebsd-net@freebsd.org Received: from relay.tecc.co.uk (luggage.tecc.co.uk [193.128.6.129]) by hub.freebsd.org (Postfix) with SMTP id 02FFF37B4EC for ; Tue, 20 Feb 2001 07:21:19 -0800 (PST) (envelope-from andy@tecc.co.uk) Received: from fw-smtp.tecc.co.uk [195.217.37.39] by relay.tecc.co.uk with esmtp (Exim 1.70 #1) id 14VEbN-0005Xo-00; Tue, 20 Feb 2001 15:21:17 +0000 Received: from [195.217.37.155] (helo=southampton) by fw-smtp.tecc.co.uk with smtp (Exim 2.12 #3) id 14VEZT-0003TU-00; Tue, 20 Feb 2001 15:19:19 +0000 From: "Andy [TECC NOPS]" To: "Jean-Christophe Varaillon" Cc: Subject: RE: - RISCom card: lcp illegal conf-req in state initial - Date: Tue, 20 Feb 2001 15:24:23 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org OK, getting somewhere. The Cisco "clockrate" command only works so long as the cable end connecting to it is DCE. Now, your reply says that it's DCE. You must make sure that it is as this is a non standard cable confiuration for a Cisco (in normal working practice with telcos anyway). I am puzzled by your diagrams for connectors (a) and (b) thou?? With that layout, how do they mate?? Also, your clock rate looks funny, it's supposed to be in direct multiples of 64000. OK, reading the docs/man page I see the default protocol for the sr driver is ppp whereas I know it's hdlc for cisco. Have you set either end so they match? in the ifconfig command you'll need the "link2" option to get sr to do hdlc or on the cisco specify : (conf-int)# encapsulation ppp in order to make the cisco do ppp. Can you send me a full "show int s0/0" and a full ifconfig -a please. Regards Andy > -----Original Message----- > From: Jean-Christophe Varaillon [mailto:jcv@vbc.net] > Sent: 20 February 2001 15:04 > To: Andy [TECC NOPS] > Cc: freebsd-net@FreeBSD.ORG > Subject: RE: - RISCom card: lcp illegal conf-req in state initial - > > > > Thanks for your prompt repply. > > On Tue, 20 Feb 2001, Andy [TECC NOPS] wrote: > > > Hi > > > > Think I know more about Cisco than RISCom cards > > but here's my 2p worth:- > > > > 1. I take it the connecting cable is an X21 null > > modem cable? If so, you have got it the right > > way round cos the connectors are the same and one > > end is dce the other dte. > > I have 2 cables plugged together: > 1 2 > Cisco }------{ }------{ Free BSD > a b > Cable 1: > On the cisco end: X21 DCE > On the other extremity (a): Female like this: > ........ > ...... > > Cable 2 > On the extremity (b): Male like that: > ........ > ...... > > On the FreeBSD end: It is a male like this: > ........ > ........ > ....... > > > 2. > Serial0/0 is up, line protocol is down > The clock is set (by the router) at clockrate 2015232 > > > > -----Original Message----- > > > From: owner-freebsd-net@FreeBSD.ORG > > > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Jean-Christophe > > > Varaillon > > > Sent: 20 February 2001 14:18 > > > To: freebsd-net@FreeBSD.ORG > > > Subject: - RISCom card: lcp illegal conf-req in state initial - > > > > > > > > > Hi all, > > > > > > I am actualy trying to establish the communication between a > cisco router > > > and my Free BSD machine. > > > > > > +-------+ +---------------+ > > > | cisco |serial interface | FreeBSD 4.1 | > > > | 3600 +-------------------+ | > > > | | RISCom | | > > > +-------+ card +---------------+ > > > x.x.x.145 x.x.x.146 > > > > > > I beleive that the router is correclty configured but NOT the FreeBSD > > > machine. > > > > > > This is what dmesg | grep sr1 shows: > > > -------- > > > sr1: Adapter 0, port 1. > > > sr1 XXX: driver didn't set ifq_maxlen > > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > > ... > > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > > sr1: Down event, taking interface down. > > > ... > > > sr1: Down event, taking interface down. > > > sr1: Down event, taking interface down. > > > sr1: lcp illegal conf-req in state initial > > > ... > > > sr1: lcp illegal conf-req in state initial > > > sr1: lcp illegal conf-req in state initial > > > -------- > > > > > > This is the ifconfig: > > > ------- > > > sr1: flags=8451 mtu 1500 > > > inet6 fe80::2d0:b7ff:fe09:3333%sr1 --> :: prefixlen 64 > > > scopeid 0x2 > > > inet x.x.x.146 --> x.x.x.145 netmask 0xfffffffc > > > ------ > > > > > > Thanks, > > > > > > JC. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 7:48:15 2001 Delivered-To: freebsd-net@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id 7033037B401 for ; Tue, 20 Feb 2001 07:48:08 -0800 (PST) (envelope-from jcv@vbc.net) Received: from localhost (jcv@localhost) by brunel.uk1.vbc.net (8.11.0/8.11.0) with ESMTP id f1KFm7x59891; Tue, 20 Feb 2001 15:48:07 GMT X-Authentication-Warning: brunel.uk1.vbc.net: jcv owned process doing -bs Date: Tue, 20 Feb 2001 15:48:07 +0000 (GMT) From: Jean-Christophe Varaillon X-Sender: jcv@brunel.uk1.vbc.net To: "Andy [TECC NOPS]" Cc: freebsd-net@FreeBSD.ORG Subject: RE: - RISCom card: lcp illegal conf-req in state initial - 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 Andy, I think the cables are ok. > OK, reading the docs/man page I see the default protocol > for the sr driver is ppp whereas I know it's hdlc for > cisco. Have you set either end so they match? I specified "encapsulation ppp" on the cisco. > in the ifconfig command you'll need the "link2" option > to get sr to do hdlc or on the cisco specify : > (conf-int)# encapsulation ppp > in order to make the cisco do ppp. > > Can you send me a full "show int s0/0" and a full > ifconfig -a please. show int s0/0: ------------- kg2uk1#sho int ser 0/0 Serial0/0 is up, line protocol is down Hardware is M4T Description: ZEBRA TEST LINK Internet address is x.x.x.145/30 MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec, rely 255/255, load 1/255 Encapsulation PPP, crc 16, loopback not set, keepalive set (10 sec) LCP REQsent Closed: IPCP, CDPCP Last input never, output 00:00:01, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0 (size/max/drops); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 1 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 1168 packets output, 16352 bytes, 0 underruns 0 output errors, 0 collisions, 314 interface resets 0 output buffer failures, 0 output buffers swapped out 326 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up ---- homer# ifconfig -a: ------------------ The sr1 change from UP to DOWN after 5 min. sr0: flags=8010 mtu 1500 sr1: flags=8410 mtu 1500 inet x.x.x.146 --> x.x.x.145 netmask 0xfffffffc inet6 fe80::2d0:b7ff:fe09:3333%sr1 --> :: prefixlen 64 scopeid 0x2 fxp0: flags=8843 mtu 1500 inet6 fe80::2d0:b7ff:fe09:3333%fxp0 prefixlen 64 scopeid 0x3 inet x.x.x.50 netmask 0xffffff80 broadcast x.x.x.127 ether 00:d0:b7:09:33:33 media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP lp0: flags=8810 mtu 1500 sl0: flags=c010 mtu 552 ppp0: flags=8010 mtu 1500 lo0: flags=8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 gif0: flags=8010 mtu 1280 gif1: flags=8010 mtu 1280 gif2: flags=8010 mtu 1280 gif3: flags=8010 mtu 1280 faith0: flags=8000 mtu 1500 homer# Thanks a lot, JC. > > Regards > Andy > > > -----Original Message----- > > From: Jean-Christophe Varaillon [mailto:jcv@vbc.net] > > Sent: 20 February 2001 15:04 > > To: Andy [TECC NOPS] > > Cc: freebsd-net@FreeBSD.ORG > > Subject: RE: - RISCom card: lcp illegal conf-req in state initial - > > > > > > > > Thanks for your prompt repply. > > > > On Tue, 20 Feb 2001, Andy [TECC NOPS] wrote: > > > > > Hi > > > > > > Think I know more about Cisco than RISCom cards > > > but here's my 2p worth:- > > > > > > 1. I take it the connecting cable is an X21 null > > > modem cable? If so, you have got it the right > > > way round cos the connectors are the same and one > > > end is dce the other dte. > > > > I have 2 cables plugged together: > > 1 2 > > Cisco }------{ }------{ Free BSD > > a b > > Cable 1: > > On the cisco end: X21 DCE > > On the other extremity (a): Female like this: > > ........ > > ...... > > > > Cable 2 > > On the extremity (b): Male like that: > > ........ > > ...... > > > > On the FreeBSD end: It is a male like this: > > ........ > > ........ > > ....... > > > > > 2. > > Serial0/0 is up, line protocol is down > > The clock is set (by the router) at clockrate 2015232 > > > > > > -----Original Message----- > > > > From: owner-freebsd-net@FreeBSD.ORG > > > > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Jean-Christophe > > > > Varaillon > > > > Sent: 20 February 2001 14:18 > > > > To: freebsd-net@FreeBSD.ORG > > > > Subject: - RISCom card: lcp illegal conf-req in state initial - > > > > > > > > > > > > Hi all, > > > > > > > > I am actualy trying to establish the communication between a > > cisco router > > > > and my Free BSD machine. > > > > > > > > +-------+ +---------------+ > > > > | cisco |serial interface | FreeBSD 4.1 | > > > > | 3600 +-------------------+ | > > > > | | RISCom | | > > > > +-------+ card +---------------+ > > > > x.x.x.145 x.x.x.146 > > > > > > > > I beleive that the router is correclty configured but NOT the FreeBSD > > > > machine. > > > > > > > > This is what dmesg | grep sr1 shows: > > > > -------- > > > > sr1: Adapter 0, port 1. > > > > sr1 XXX: driver didn't set ifq_maxlen > > > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > > > ... > > > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > > > sr1: Down event, taking interface down. > > > > ... > > > > sr1: Down event, taking interface down. > > > > sr1: Down event, taking interface down. > > > > sr1: lcp illegal conf-req in state initial > > > > ... > > > > sr1: lcp illegal conf-req in state initial > > > > sr1: lcp illegal conf-req in state initial > > > > -------- > > > > > > > > This is the ifconfig: > > > > ------- > > > > sr1: flags=8451 mtu 1500 > > > > inet6 fe80::2d0:b7ff:fe09:3333%sr1 --> :: prefixlen 64 > > > > scopeid 0x2 > > > > inet x.x.x.146 --> x.x.x.145 netmask 0xfffffffc > > > > ------ > > > > > > > > Thanks, > > > > > > > > JC. > > > > > > 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 Tue Feb 20 8: 3: 2 2001 Delivered-To: freebsd-net@freebsd.org Received: from relay.tecc.co.uk (luggage.tecc.co.uk [193.128.6.129]) by hub.freebsd.org (Postfix) with SMTP id 6299337B491 for ; Tue, 20 Feb 2001 08:02:54 -0800 (PST) (envelope-from andy@tecc.co.uk) Received: from fw-smtp.tecc.co.uk [195.217.37.39] by relay.tecc.co.uk with esmtp (Exim 1.70 #1) id 14VFFd-00060n-00; Tue, 20 Feb 2001 16:02:53 +0000 Received: from [195.217.37.155] (helo=southampton) by fw-smtp.tecc.co.uk with smtp (Exim 2.12 #3) id 14VFDi-0003gA-00; Tue, 20 Feb 2001 16:00:54 +0000 From: "Andy [TECC NOPS]" To: "Jean-Christophe Varaillon" Cc: Subject: RE: - RISCom card: lcp illegal conf-req in state initial - Date: Tue, 20 Feb 2001 16:05:58 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Well, having look thro all of that it really does seem fine. The only give away is the cisco msg "line protocol down". Since the config at each end seems ok the last thing really must be those two cables you are joining. Either the cisco end is not really dce and thus preventing the clock or, more likely, the pins are not compatable at the joint in the middle. Time to get the continuity checker out and buzz out the cable (unless there is someone with more experience of the sr driver around who can shed more light on your dmesg output but from what I can tell the setup looks fine). Soz, can't really help much more, hope the next person along is more use. Regards Andy > -----Original Message----- > From: Jean-Christophe Varaillon [mailto:jcv@vbc.net] > Sent: 20 February 2001 15:48 > To: Andy [TECC NOPS] > Cc: freebsd-net@FreeBSD.ORG > Subject: RE: - RISCom card: lcp illegal conf-req in state initial - > > > Andy, > > I think the cables are ok. > > > > OK, reading the docs/man page I see the default protocol > > for the sr driver is ppp whereas I know it's hdlc for > > cisco. Have you set either end so they match? > > I specified "encapsulation ppp" on the cisco. > > > in the ifconfig command you'll need the "link2" option > > to get sr to do hdlc or on the cisco specify : > > (conf-int)# encapsulation ppp > > in order to make the cisco do ppp. > > > > Can you send me a full "show int s0/0" and a full > > ifconfig -a please. > > show int s0/0: > ------------- > > kg2uk1#sho int ser 0/0 > Serial0/0 is up, line protocol is down > Hardware is M4T > Description: ZEBRA TEST LINK > Internet address is x.x.x.145/30 > MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec, rely 255/255, load 1/255 > Encapsulation PPP, crc 16, loopback not set, keepalive set (10 sec) > LCP REQsent > Closed: IPCP, CDPCP > Last input never, output 00:00:01, output hang never > Last clearing of "show interface" counters never > Input queue: 0/75/0 (size/max/drops); Total output drops: 0 > Queueing strategy: weighted fair > Output queue: 0/1000/64/0 (size/max total/threshold/drops) > Conversations 0/1/256 (active/max active/max total) > Reserved Conversations 0/0 (allocated/max allocated) > 5 minute input rate 0 bits/sec, 0 packets/sec > 5 minute output rate 0 bits/sec, 0 packets/sec > 0 packets input, 0 bytes, 0 no buffer > Received 0 broadcasts, 0 runts, 1 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > 1168 packets output, 16352 bytes, 0 underruns > 0 output errors, 0 collisions, 314 interface resets > 0 output buffer failures, 0 output buffers swapped out > 326 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up > ---- > > > homer# ifconfig -a: > ------------------ > The sr1 change from UP to DOWN after 5 min. > > sr0: flags=8010 mtu 1500 > sr1: flags=8410 mtu 1500 > inet x.x.x.146 --> x.x.x.145 netmask 0xfffffffc > inet6 fe80::2d0:b7ff:fe09:3333%sr1 --> :: prefixlen 64 > scopeid 0x2 > fxp0: flags=8843 mtu 1500 > inet6 fe80::2d0:b7ff:fe09:3333%fxp0 prefixlen 64 scopeid 0x3 > inet x.x.x.50 netmask 0xffffff80 broadcast x.x.x.127 > ether 00:d0:b7:09:33:33 > media: autoselect (10baseT/UTP) status: active > supported media: autoselect 100baseTX 100baseTX > 10baseT/UTP 10baseT/UTP > lp0: flags=8810 mtu 1500 > sl0: flags=c010 mtu 552 > ppp0: flags=8010 mtu 1500 > lo0: flags=8049 mtu 16384 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > gif0: flags=8010 mtu 1280 > gif1: flags=8010 mtu 1280 > gif2: flags=8010 mtu 1280 > gif3: flags=8010 mtu 1280 > faith0: flags=8000 mtu 1500 > homer# > > > Thanks a lot, > JC. > > > > > > > Regards > > Andy > > > > > -----Original Message----- > > > From: Jean-Christophe Varaillon [mailto:jcv@vbc.net] > > > Sent: 20 February 2001 15:04 > > > To: Andy [TECC NOPS] > > > Cc: freebsd-net@FreeBSD.ORG > > > Subject: RE: - RISCom card: lcp illegal conf-req in state initial - > > > > > > > > > > > > Thanks for your prompt repply. > > > > > > On Tue, 20 Feb 2001, Andy [TECC NOPS] wrote: > > > > > > > Hi > > > > > > > > Think I know more about Cisco than RISCom cards > > > > but here's my 2p worth:- > > > > > > > > 1. I take it the connecting cable is an X21 null > > > > modem cable? If so, you have got it the right > > > > way round cos the connectors are the same and one > > > > end is dce the other dte. > > > > > > I have 2 cables plugged together: > > > 1 2 > > > Cisco }------{ }------{ Free BSD > > > a b > > > Cable 1: > > > On the cisco end: X21 DCE > > > On the other extremity (a): Female like this: > > > ........ > > > ...... > > > > > > Cable 2 > > > On the extremity (b): Male like that: > > > ........ > > > ...... > > > > > > On the FreeBSD end: It is a male like this: > > > ........ > > > ........ > > > ....... > > > > > > > 2. > > > Serial0/0 is up, line protocol is down > > > The clock is set (by the router) at clockrate 2015232 > > > > > > > > -----Original Message----- > > > > > From: owner-freebsd-net@FreeBSD.ORG > > > > > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Jean-Christophe > > > > > Varaillon > > > > > Sent: 20 February 2001 14:18 > > > > > To: freebsd-net@FreeBSD.ORG > > > > > Subject: - RISCom card: lcp illegal conf-req in state initial - > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > I am actualy trying to establish the communication between a > > > cisco router > > > > > and my Free BSD machine. > > > > > > > > > > +-------+ +---------------+ > > > > > | cisco |serial interface | FreeBSD 4.1 | > > > > > | 3600 +-------------------+ | > > > > > | | RISCom | | > > > > > +-------+ card +---------------+ > > > > > x.x.x.145 x.x.x.146 > > > > > > > > > > I beleive that the router is correclty configured but NOT > the FreeBSD > > > > > machine. > > > > > > > > > > This is what dmesg | grep sr1 shows: > > > > > -------- > > > > > sr1: Adapter 0, port 1. > > > > > sr1 XXX: driver didn't set ifq_maxlen > > > > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > > > > ... > > > > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > > > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > > > > sr1: Down event, taking interface down. > > > > > ... > > > > > sr1: Down event, taking interface down. > > > > > sr1: Down event, taking interface down. > > > > > sr1: lcp illegal conf-req in state initial > > > > > ... > > > > > sr1: lcp illegal conf-req in state initial > > > > > sr1: lcp illegal conf-req in state initial > > > > > -------- > > > > > > > > > > This is the ifconfig: > > > > > ------- > > > > > sr1: flags=8451 mtu 1500 > > > > > inet6 fe80::2d0:b7ff:fe09:3333%sr1 --> :: prefixlen 64 > > > > > scopeid 0x2 > > > > > inet x.x.x.146 --> x.x.x.145 netmask 0xfffffffc > > > > > ------ > > > > > > > > > > Thanks, > > > > > > > > > > JC. > > > > > > > > > > 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 Tue Feb 20 11:36:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 32DBD37B4EC for ; Tue, 20 Feb 2001 11:36:50 -0800 (PST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.1/8.11.1) id f1KJaJj91966; Tue, 20 Feb 2001 21:36:19 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200102201936.f1KJaJj91966@zibbi.icomtek.csir.co.za> Subject: Re: - RISCom card: lcp illegal conf-req in state initial - In-Reply-To: from Jean-Christophe Varaillon at "Feb 20, 2001 02:18:03 pm" To: jcv@vbc.net (Jean-Christophe Varaillon) Date: Tue, 20 Feb 2001 21:36:19 +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 am actualy trying to establish the communication between a cisco router > and my Free BSD machine. > > +-------+ +---------------+ > | cisco |serial interface | FreeBSD 4.1 | > | 3600 +-----------------------+ | > | | RISCom | | > +-------+ card +---------------+ > x.x.x.145 x.x.x.146 > > I beleive that the router is correclty configured but NOT the FreeBSD > machine. > > This is what dmesg | grep sr1 shows: > -------- > sr1: Adapter 0, port 1. > sr1 XXX: driver didn't set ifq_maxlen > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > ... > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. There is 2 things you should make sure of. 1. If it is an ISA card that you are getting the interrupts. You can check this with vmstat -i and make sure they do arrive. Some motherboards need configuration in the BIOS to make isa interrupts work. 2. That the cisco is providing a clock. The sr driver configure the card to expect a clock and it won't work without it. > sr1: Down event, taking interface down. > ... > sr1: Down event, taking interface down. > sr1: Down event, taking interface down. > sr1: lcp illegal conf-req in state initial > ... > sr1: lcp illegal conf-req in state initial > sr1: lcp illegal conf-req in state initial This is a bug in the state machine of sppp. I have fixed it in -current, but haven't merged it into stable yet. > -------- > > This is the ifconfig: > ------- > sr1: flags=8451 mtu 1500 > inet6 fe80::2d0:b7ff:fe09:3333%sr1 --> :: prefixlen 64 > scopeid 0x2 > inet x.x.x.146 --> x.x.x.145 netmask 0xfffffffc > ------ You can also enable the debug flag in ifconfig, then you will see the ppp packets, that should also help debuging the problem. John -- John Hay -- John.Hay@icomtek.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 Tue Feb 20 13:30:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from office.atnet.at (media.atnet.at [194.152.160.66]) by hub.freebsd.org (Postfix) with ESMTP id 0E82037B491 for ; Tue, 20 Feb 2001 13:30:36 -0800 (PST) (envelope-from chaoztc@office.atnet.at) Received: from localhost (chaoztc@localhost) by office.atnet.at (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id WAA10770 for ; Tue, 20 Feb 2001 22:30:35 +0100 Date: Tue, 20 Feb 2001 22:30:35 +0100 (CET) From: Ingo Flaschberger To: freebsd-net@FreeBSD.ORG Subject: maximum number of routes? 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 how could i modify the amount of the maximum routes that freebsd allow? i have seen, that with more memory i could use more routes. some results from me: ram routes 128mb 75k 196mb 110k 256mb 150k is it possible to modify the maximum ammount and does it make sense? i would need that for some routers speaking bgp. 120k routes with 128mb ram would be nice, if possible. currently, adding more routes than supportet ends with: extern# route add 20.0.0.0/24 10.0.0.1 route: writing to routing socket: No buffer space available add net 20.0.0.0: gateway 10.0.0.1: routing table overflow kind regards, Ingo Flaschberger www.atnet.at To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 14:56:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from lotl.clari.net.au (lotl.clari.net.au [203.26.127.210]) by hub.freebsd.org (Postfix) with ESMTP id D520537B491 for ; Tue, 20 Feb 2001 14:56:08 -0800 (PST) (envelope-from stephen@clari.net.au) Received: from theforce.clari.net.au (theforce.clari.net.au [203.8.14.120]) by lotl.clari.net.au (8.9.3/8.9.1) with ESMTP id JAA72639 for ; Wed, 21 Feb 2001 09:55:47 +1100 (EST) (envelope-from stephen@clari.net.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 21 Feb 2001 10:00:09 +1100 (EST) Organization: ClariNET Internet Solutions From: Stephen Cimarelli To: freebsd-net@freebsd.org Subject: Help with IPSEC Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All I'm starting to look into using IPSEC to setup VPN's I have the FreeBSD IPsec mini-HOWTO and Henk Wevers's VPN Tunnel howto Which have most of the info I need :) But I have some questions :) * Most users seem to use gif devices to setup the tunnels instead of IPsec tunnels, Why? What ports/protocols do I need to allow through a firewall to allow gif and IPsec to work? Thanks, Stephen ---------------------------------- E-Mail: Stephen Cimarelli Date: 21-Feb-01 Time: 09:50:49 ClariNet Internet Solutions +61 3 9486 0811 www.clari.net.au ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 17:15:56 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 65BFC37B491 for ; Tue, 20 Feb 2001 17:15:53 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1L1FRp63075; Tue, 20 Feb 2001 19:15:27 -0600 (CST) (envelope-from jlemon) Date: Tue, 20 Feb 2001 19:15:27 -0600 (CST) From: Jonathan Lemon Message-Id: <200102210115.f1L1FRp63075@prism.flugsvamp.com> To: chaoztc@media.atnet.at, net@freebsd.org Subject: Re: maximum number of routes? X-Newsgroups: local.mail.freebsd-net In-Reply-To: Organization: Cc: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: >Hi > >how could i modify the amount of the maximum routes that freebsd allow? Add more memory. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 20 18:57:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from proxy.outblaze.com (proxy.outblaze.com [202.77.223.120]) by hub.freebsd.org (Postfix) with SMTP id A7C9B37B401 for ; Tue, 20 Feb 2001 18:57:42 -0800 (PST) (envelope-from yusufg@outblaze.com) Received: (qmail 58852 invoked from network); 21 Feb 2001 02:57:39 -0000 Received: from unknown (HELO yusufg.portal2.com) (202.77.181.217) by proxy.outblaze.com with SMTP; 21 Feb 2001 02:57:39 -0000 Received: (qmail 14337 invoked by uid 500); 21 Feb 2001 03:02:55 -0000 Date: Wed, 21 Feb 2001 11:02:55 +0800 From: Yusuf Goolamabbas To: Luigi Rizzo Cc: jonny@jonny.eng.br, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, phk@FreeBSD.ORG, dwmalone@FreeBSD.ORG Subject: Re: Solved: Bridging and dummynet seems to destroy dmesg output Message-ID: <20010221110255.A14313@outblaze.com> References: <20010220112154.A26373@outblaze.com> <200102200330.f1K3UJC42482@iguana.aciri.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200102200330.f1K3UJC42482@iguana.aciri.org>; from rizzo@aciri.org on Mon, Feb 19, 2001 at 07:30:19PM -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luigi, PHK In case you might not be on -stable Thomas Moestl just wrote a mesg to -stable trying to explain "dmesg flakyness". cut/paste from his message Have you tried "dmesg -a"? It seems like the above message is from syslog (if something is printed on into /dev/console, this is also recorded in the message buffer). dmesg by default ignores messages that are not from the kernel, but it cannot determine this if the first characters of a line are missing. The missing characters get lost when the oldest messages are partly overwritten by new ones (the message buffer is a ring buffer). > > Luigi, PHK > > > > Any resolution on this ? > > for sure there is no bug in ip_fw.c -- the change mentioned below just > happens to change some symptoms but is no fix. > > The message buffer is not "busted" as the report says, just has > some NULs here and there that (probably) dmesg is not handling > correctly. Poul, do you know more ? > > cheers > luigi > > > > Regards, Yusuf > > > > > Hi Yusuf, > > > > > > As described by cvsweb, the patches to IPFW did not change the behavior > > > with log messages. To be more exactly, either netinet/ip_fw.c either > > > kern/subr_prf.c should be changed to match each other. In my local setup I > > > use a patch script after cvsup to fix ip_fw.c, removing all instances of > > > "LOG_SECURITY |". > > > > > > Luigi/Poul, have you at least decided where the changes should be made? > > > There's no log(9) man page to decide which one is the correct syntax. IMHO, > > > -stable is not stable while this bug persists. > > > > > > Yusuf Goolamabbas wrote: > > > > > > > > Hi, I cvsupped today and got all of Luigi's commit [the one where he > > > > does 1.16.2.13 of bridge.c alongwith a few others], I also have David > > > > Malone's fix to syslogd.c [1.59.2.5] > > > > > > > > If I don't have the following sysctl > > > > > > > > net.inet.ip.fw.verbose_limit=10 > > > > > > > > then dmesg gets busted as mentioned earlier and if I do a sync;reboot > > > > then I get a huge amount of ipfw messages scrolling on the console [It's > > > > as if they were backlogged in some buffer somewhere] and after a few > > > > seconds the syncing disk messages comes along > > > > > > > > I have the following in my kernel config > > > > > > > > options IPFIREWALL > > > > options IPFIREWALL_DEFAULT_TO_ACCEPT > > > > options BRIDGE > > > > options DUMMYNET > > > > > > > > my /etc/sysctl.conf is as follows > > > > > > > > net.link.ether.bridge_ipfw=1 > > > > net.link.ether.bridge=1 > > > > net.inet.ip.fw.verbose=1 > > > > net.inet.ip.fw.verbose_limit=10 > > > > > > > > > Luigi Rizzo wrote: > > > > > > > > > > > > > I tried only removing DUMMYNET from config, and the bug continues. Should > > > > > > > I try the changes below? > > > > > > > > > > > > no-they only affect dummynet. But this seems to suggest that > > > > > > the problem is unrelated to my changes... > > > > > > > > > > > > cheers > > > > > > luigi > > > > > > > > > > Hi, > > > > > > > > > > I found the problem! > > > > > > > > > > I started searching for the point where ipfw writes to the msgbuf, and > > > > > like all other kernel modules, it uses the log(9) function. But differently > > > > > from the other modules, ip_fw.c uses a LOG_SECURITY argument. I removed it, > > > > > recompiled, reboot, and BINGO! Probably the log(9) function does not expect a > > > > > facility parameter, as it is assumed to be LOG_KERNEL. > > > > > > > > > > Searching the cvsweb tree, I assume the changes that made it fail were > > > > > made to kern/subr_prf.c, and not directly to netinet/ip_fw.c. Probably a > > > > > longer search should be made to detect if any other call to log(9) uses this > > > > > approach. (CC: to phk, who made the change to kern/subr_prf.c, 1.61.2.1, at > > > > > 2000.01.16) > > > > > > > > > > Hoping this is the final solution and waiting for the cvs commit, thanks > > > > > to everybody, > > > > > > > > > > Jonny > > > > > > > > > > -- > > > > > João Carlos Mendes Luís jonny@embratel.net.br > > > > > Networking Engineer jonny@jonny.eng.br > > > > > Internet via Embratel jcml@ieee.org > > > > > > > > -- > > > > Yusuf Goolamabbas > > > > yusufg@outblaze.com > > > > > > -- > > > > > > Jonny > > > > > > -- > > > João Carlos Mendes Luís jonny@embratel.net.br > > > Networking Engineer jonny@jonny.eng.br > > > Internet via Embratel jcml@ieee.org > > > > -- > > Yusuf Goolamabbas > > yusufg@outblaze.com > > > -- Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 21 2:50:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id 43AFE37B401 for ; Wed, 21 Feb 2001 02:50:33 -0800 (PST) (envelope-from jcv@vbc.net) Received: from localhost (jcv@localhost) by brunel.uk1.vbc.net (8.11.0/8.11.0) with ESMTP id f1LAo5n64174; Wed, 21 Feb 2001 10:50:09 GMT X-Authentication-Warning: brunel.uk1.vbc.net: jcv owned process doing -bs Date: Wed, 21 Feb 2001 10:50:05 +0000 (GMT) From: Jean-Christophe Varaillon X-Sender: jcv@brunel.uk1.vbc.net To: John Hay Cc: freebsd-net@FreeBSD.ORG Subject: Re: - RISCom card: lcp illegal conf-req in state initial - In-Reply-To: <200102201936.f1KJaJj91966@zibbi.icomtek.csir.co.za> 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 Thanks for your prompt repply. > > I am actualy trying to establish the communication between a cisco router > > and my Free BSD machine. > > > > +-------+ +---------------+ > > | cisco |serial interface | FreeBSD 4.1 | > > | 3600 +-------------------+ | > > | | RISCom | | > > +-------+ card +---------------+ > > x.x.x.145 x.x.x.146 > > > > I beleive that the router is correclty configured but NOT the FreeBSD > > machine. I am using a PCI card, I configured it this way in my kernel called ZEBRA: "device sr0 at pci? port 0x300 irq 3 iomem 0xd0000" "pseudo-device sppp" The irq 3 is unique, it is not used by any other device in this kernel. > 2. That the cisco is providing a clock. The sr driver configure the card > to expect a clock and it won't work without it. NETGRAPH does not exist in this kernel, therfore I specified "encaps ppp" on the cisco config, and it also provides a clock of 2 Mhz. > > sr1: Down event, taking interface down. > > ... > > sr1: Down event, taking interface down. > > sr1: Down event, taking interface down. > > sr1: lcp illegal conf-req in state initial > > ... > > sr1: lcp illegal conf-req in state initial > > sr1: lcp illegal conf-req in state initial > > This is a bug in the state machine of sppp. I have fixed it in -current, > but haven't merged it into stable yet. Is this may disturb the communication between the cisco and the RISCom card ? > You can also enable the debug flag in ifconfig, then you will see the > ppp packets, that should also help debuging the problem. From this debug information, I think that we can see that the card does not receive the clock signal from the cisco. When we see that "magic 0x54ef40a0", does it correspond to what we call magic number ? sr0: lcp close(initial) sr0: lcp open(initial) sr0: phase establish sr0: lcp up(starting) sr0: lcp output sr0: lcp TO(req-sent) rst_counter = 10 sr0: lcp output sr0: lcp TO(req-sent) rst_counter = 9 sr0: lcp output sr0: lcp TO(req-sent) rst_counter = 8 sr0: lcp output sr0: lcp TO(req-sent) rst_counter = 7 sr0: lcp output sr0: lcp TO(req-sent) rst_counter = 6 sr0: lcp output sr0: lcp TO(req-sent) rst_counter = 5 sr0: lcp output sr0: lcp input(req-sent): sr0: lcp parse opts: magic sr0: lcp parse opt values: magic 0x54ef40a0 send conf-ack sr0: lcp output sr0: lcp input(ack-sent): sr0: lcp parse opts: magic sr0: lcp parse opt values: magic 0x54ef40a0 send conf-ack sr0: lcp output sr0: lcp input(ack-sent): sr0: lcp parse opts: magic sr0: lcp parse opt values: magic 0x54ef40a0 send conf-ack sr0: lcp output sr0: lcp input(ack-sent): sr0: lcp parse opts: magic sr0: lcp parse opt values: magic 0x54ef40a0 send conf-ack sr0: lcp output sr0: lcp input(ack-sent): sr0: lcp parse opts: magic sr0: lcp parse opt values: magic 0x54ef40a0 send conf-ack sr0: lcp output sr0: lcp input(ack-sent): sr0: lcp parse opts: magic sr0: lcp parse opt values: magic 0x54ef40a0 send conf-ack sr0: lcp output sr0: lcp input(ack-sent): sr0: lcp parse opts: magic sr0: lcp parse opt values: magic 0x54ef40a0 send conf-ack sr0: lcp output sr0: lcp input(ack-sent): sr0: lcp parse opts: magic sr0: lcp parse opt values: magic 0x54ef40a0 send conf-ack sr0: lcp output sr0: lcp input(ack-sent): sr0: lcp parse opts: magic sr0: lcp parse opt values: magic 0x54ef40a0 send conf-ack sr0: lcp output sr0: lcp input(ack-sent): sr0: lcp parse opts: magic sr0: lcp parse opt values: magic 0x54ef40a0 send conf-ack sr0: lcp output sr0: lcp input(ack-sent): sr0: lcp parse opts: magic sr0: lcp parse opt values: magic 0x54ef40a0 send conf-ack sr0: lcp output sr0: lcp TO(ack-sent) rst_counter = 4 sr0: lcp output sr0: lcp TO(ack-sent) rst_counter = 3 sr0: lcp output sr0: lcp TO(ack-sent) rst_counter = 2 sr0: lcp output sr0: lcp TO(ack-sent) rst_counter = 1 sr0: lcp output sr0: lcp TO(ack-sent) rst_counter = 0 sr0: phase dead sr0: lcp down(stopped) sr0: phase establish sr0: lcp up(starting) sr0: lcp output sr0: Down event, taking interface down. sr0: lcp close(req-sent) sr0: lcp output sr0: lcp TO(closing) rst_counter = 2 sr0: lcp output sr0: lcp TO(closing) rst_counter = 1 sr0: lcp output sr0: lcp TO(closing) rst_counter = 0 sr0: phase dead sr0: lcp down(closed) sr0: Down event, taking interface down. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 21 3:28:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailhub.nk.ukrtel.net (mailhub.nk.ukrtel.net [195.5.9.2]) by hub.freebsd.org (Postfix) with ESMTP id 0C26637B65D for ; Wed, 21 Feb 2001 03:28:28 -0800 (PST) (envelope-from gvf@nk.ukrtel.net) Received: by mailhub.nk.ukrtel.net (Postfix, from userid 1002) id E5BA810781; Wed, 21 Feb 2001 13:26:38 +0200 (EET) Date: Wed, 21 Feb 2001 13:26:38 +0200 From: George Fedorenko To: freebsd-net@freebsd.org Subject: user PPP HDLC errors Message-ID: <20010221132638.A12216@mailhub.nk.ukrtel.net> Reply-To: gvf@nk.ukrtel.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.1-RELEASE Organization: ND Ukrtelekom Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, all I have a lot of such messages in my log file. What do they mean? Is it a harware problem? ( PPP is in MP mode. FreeBSD 4.0R) Feb 18 16:54:51 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 2, ADDR: 0, COMD: 0, PROTO: 0 Feb 18 16:55:52 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 3, ADDR: 0, COMD: 0, PROTO: 0 Feb 18 16:56:53 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 2, ADDR: 0, COMD: 0, PROTO: 0 Feb 18 16:58:55 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 3, ADDR: 0, COMD: 0, PROTO: 0 Feb 18 16:59:57 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 3, ADDR: 0, COMD: 0, PROTO: 0 Feb 18 17:00:58 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 7, ADDR: 0, COMD: 0, PROTO: 0 -- George Fedorenko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 21 4:58:28 2001 Delivered-To: freebsd-net@freebsd.org Received: from avengers.ivision.co.uk (avengers.ivision.co.uk [212.25.224.7]) by hub.freebsd.org (Postfix) with ESMTP id 1FA0137B491 for ; Wed, 21 Feb 2001 04:58:25 -0800 (PST) (envelope-from jasper@ivision.co.uk) Received: from [212.25.224.7] (helo=avengers) by avengers.ivision.co.uk with esmtp (Exim 2.04 #1) id 14VYqM-0001q5-00; Wed, 21 Feb 2001 12:58:06 +0000 Date: Wed, 21 Feb 2001 12:58:06 +0000 (GMT) From: Jasper Wallace X-Sender: To: Ingo Flaschberger Cc: Subject: Re: maximum number of routes? In-Reply-To: Message-ID: X-NCC-RegID: uk.instant-web MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 20 Feb 2001, Ingo Flaschberger wrote: > Hi > > how could i modify the amount of the maximum routes that freebsd allow? > > i have seen, that with more memory i could use more routes. > some results from me: > ram routes > 128mb 75k > 196mb 110k > 256mb 150k > > is it possible to modify the maximum ammount and does it make sense? > i would need that for some routers speaking bgp. > 120k routes with 128mb ram would be nice, if possible. > > currently, adding more routes than supportet ends with: > extern# route add 20.0.0.0/24 10.0.0.1 > route: writing to routing socket: No buffer space available > add net 20.0.0.0: gateway 10.0.0.1: routing table overflow Add this to your kernel config. file: # 1/2 RAM for the kernel - lets us have full routes. options VM_KMEM_SIZE_SCALE="(2)" See also /usr/include/machine/vmparam.h Unfortunatly freebsd's kernel memory managment stuff dosn't dynamicly resize, i'm pretty sure NetBSD's does, so you might like to take a look at that too. -- Internet Vision Internet Consultancy Tel: 020 7589 4500 60 Albert Court & Web development Fax: 020 7589 4522 Prince Consort Road vision@ivision.co.uk London SW7 2BE http://www.ivision.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 Feb 21 7: 0:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from black.purplecat.net (ns1.purplecat.net [209.16.228.148]) by hub.freebsd.org (Postfix) with ESMTP id 943D937B491 for ; Wed, 21 Feb 2001 07:00:01 -0800 (PST) (envelope-from peter@black.purplecat.net) Received: from localhost (peter@localhost) by black.purplecat.net (8.8.8/8.8.8) with ESMTP id KAA04617 for ; Wed, 21 Feb 2001 10:02:22 -0500 (EST) (envelope-from peter@black.purplecat.net) Date: Wed, 21 Feb 2001 10:02:22 -0500 (EST) From: Peter Brezny To: freebsd-net@freebsd.org Subject: sysctl -w net.link.ether.inet.log_arp_wrong_iface=0 not working Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I updated the source and rebuilt a 4.2-stable machine this past weekend. sysctl -w net.link.ether.inet.log_arp_wrong_iface=0 is located in rc.conf and running that on the command line shows it's value to be 0 however, i still receive messages like this. Anyone know why this sysctl variable stoped working? Feb 21 09:48:22 bsd1 /kernel: arp: 209.16.228.140 is on fxp0 but got reply from 00:10:4b:99:7f: 6e on rl0 TIA Peter Brezny SysAdmin Services Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 21 7:16:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id EEFE737B401 for ; Wed, 21 Feb 2001 07:16:09 -0800 (PST) (envelope-from rizzo@iguana.aciri.org) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f1LFG7j76215; Wed, 21 Feb 2001 07:16:07 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102211516.f1LFG7j76215@iguana.aciri.org> Subject: Re: sysctl -w net.link.ether.inet.log_arp_wrong_iface=0 not working In-Reply-To: from Peter Brezny at "Feb 21, 2001 10: 2:22 am" To: peter@black.purplecat.net (Peter Brezny) Date: Wed, 21 Feb 2001 07:16:07 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 updated the source and rebuilt a 4.2-stable machine this past weekend. > > sysctl -w net.link.ether.inet.log_arp_wrong_iface=0 is located in rc.conf > > and running that on the command line shows it's value to be 0 however, i > still receive messages like this. > > Anyone know why this sysctl variable stoped working? it seems that i nuked it by mistake in a previous commit. Just committed a fix -- thanks for the report luigi > Feb 21 09:48:22 bsd1 /kernel: arp: 209.16.228.140 is on fxp0 but got reply > from 00:10:4b:99:7f: > 6e on rl0 > > TIA > > Peter Brezny > SysAdmin Services Inc. > > > > 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 Feb 21 10: 3:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from secure.webhotel.net (secure.webhotel.net [195.41.202.80]) by hub.freebsd.org (Postfix) with SMTP id 6AFCA37B401 for ; Wed, 21 Feb 2001 10:03:30 -0800 (PST) (envelope-from hroi@chewbacca.netgroup.dk) Received: (qmail 86222932 invoked from network); 21 Feb 2001 18:06:07 -0000 Received: from mail-gateway.webhotel.net (195.41.202.215) by mail.webhotel.net with SMTP; 21 Feb 2001 18:06:07 -0000 X-Authenticated-Timestamp: 19:06:07(CET) on February 21, 2001 Received: (from hroi@localhost) by chewbacca.netgroup.dk (8.11.2/8.9.3) id f1LI3ZV25256 for freebsd-net@freebsd.org; Wed, 21 Feb 2001 19:03:35 +0100 (CET) (envelope-from hroi) Date: Wed, 21 Feb 2001 19:03:35 +0100 From: Hroi Sigurdsson To: freebsd-net@freebsd.org Subject: pptp, mpd and chap msoftv2 Message-ID: <20010221190335.A97793@chewbacca.netgroup.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to establish a pptp tunnel to a Watchguard Firebox II with mpd-netgraph. I'm getting LCP rejects and the Firebox II is complaining about out-of-order GRE packets but not sure if that is the cause of problems :-( Also I think there is a problem negotiating an auth protocol. CHAP MSOFT vs MSOFTv2? Any ideas what is actually going wrong? (fictitious ips) FreeBSD 4.2 box: 195.41.555.555 Watchguard box: 194.203.444.444 (I have no console access to this one) Private net behind watchguard: 192.168.199.0/24 mpd.conf: othernet: new -i ng0 othernet othernet set iface disable on-demand set iface addrs 192.168.1.1 192.168.2.1 set iface idle 0 set iface route 192.168.199.0/24 set bundle disable multilink set bundle authname "netgroup" set bundle password "request" set link yes acfcomp protocomp set link yes chap set link keep-alive 10 75 set ipcp yes vjcomp set ipcp ranges 195.41.555.555/24 192.168.199.0/24 set bundle enable compression set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set bundle enable crypt-reqd set ccp yes mpp-stateless open mpd.links: othernet: set link type pptp set pptp self 195.41.555.555 set pptp peer 194.203.444.444 set pptp enable originate incoming Watchguard log: pptpd[134]: Watchguard pptpd 2.2.0 started pptpd[134]: Using interface pptp0 kernel: pptp0: daemon attached. pptpd[134]: Connect: pptp0 [0] <--> 195.41.555.555 kernel: GRE: out of order: as:0 seq:0 from:0xfdcaXXXX pptpd[134]: Terminating on signal 2. tunneld[100]: process_rfds: received bad packet from 195.41.555.555 pptpd[134]: Connection terminated. FreeBSD mpd log: [nisaba] LCP: SendConfigReq #1 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM fc621317 AUTHPROTO CHAP MSOFT MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 60 f5 06 XX XX [nisaba] LCP: SendConfigReq #2 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM fc621317 AUTHPROTO CHAP MSOFT MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 60 f5 06 XX XX [nisaba] LCP: rec'd Configure Request #1 link 0 (Req-Sent) MRU 338 AUTHPROTO CHAP MSOFTv2 MAGICNUM 78290436 PROTOCOMP ACFCOMP [nisaba] LCP: SendConfigNak #1 AUTHPROTO CHAP MSOFT [nisaba] LCP: rec'd Configure Reject #2 link 0 (Req-Sent) MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 60 f5 06 XX XX [nisaba] LCP: SendConfigReq #3 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM fc621317 AUTHPROTO CHAP MSOFT [nisaba] LCP: rec'd Configure Nak #3 link 0 (Req-Sent) AUTHPROTO CHAP MSOFTv2 [nisaba] LCP: SendConfigReq #4 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM fc621317 AUTHPROTO CHAP MSOFT [nisaba] LCP: rec'd Configure Nak #4 link 0 (Req-Sent) AUTHPROTO CHAP MSOFTv2 [nisaba] LCP: SendConfigReq #5 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM fc621317 AUTHPROTO CHAP MSOFT [nisaba] LCP: rec'd Configure Nak #5 link 0 (Req-Sent) AUTHPROTO CHAP MSOFTv2 [nisaba] LCP: SendConfigReq #6 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM fc621317 AUTHPROTO CHAP MSOFT [nisaba] LCP: rec'd Configure Nak #6 link 0 (Req-Sent) AUTHPROTO CHAP MSOFTv2 [nisaba] LCP: SendConfigReq #7 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM fc621317 AUTHPROTO CHAP MSOFT [nisaba] LCP: rec'd Configure Nak #7 link 0 (Req-Sent) AUTHPROTO CHAP MSOFTv2 [nisaba] LCP: SendConfigReq #8 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM fc621317 AUTHPROTO CHAP MSOFT [nisaba] LCP: rec'd Configure Reject #8 link 0 (Req-Sent) AUTHPROTO CHAP MSOFT [nisaba] LCP: SendConfigReq #9 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM fc621317 AUTHPROTO CHAP MSOFT -- Hroi Sigurdsson hroi@netgroup.dk Netgroup A/S http://www.netgroup.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 21 10:13:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id B87D537B401; Wed, 21 Feb 2001 10:13:37 -0800 (PST) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.11.2/8.11.2) id f1LIGog13017; Wed, 21 Feb 2001 12:16:50 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 21 Feb 2001 12:16:48 -0600 (CST) Organization: @Home Network From: Conrad Sabatier To: freebsd-questions@freebsd.org Subject: Implementing pseudo-ethernet interface for Basilisk II Cc: freebsd-net@freebsd.org Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm wondering (before delving into this and possibly wasting many hours) if it would be possible to use, say, netgraph to implement a pseudo-interface for Basilisk II's ethernet device? Been having no luck whatsoever getting B2 to network in any way, shape or form, and thought this might be a likely possibility. Opinions, anyone? -- Conrad Sabatier cjsabatier@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 21 14:17:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from org.chem.msu.su (org.chem.msu.su [158.250.32.94]) by hub.freebsd.org (Postfix) with ESMTP id ADACD37B401 for ; Wed, 21 Feb 2001 14:17:22 -0800 (PST) (envelope-from genie@qsar.chem.msu.su) Received: from genie (d33-15.ropnet.ru [212.42.33.15]) by org.chem.msu.su (8.9.3/8.9.3) with SMTP id BAA88500 for ; Thu, 22 Feb 2001 01:17:17 +0300 (MSK) Message-ID: <00b601c09c53$febaaf80$0f212ad4@genie> From: "Eugene Radchenko" To: References: Subject: PPP from Win2K to FreeBSD Date: Thu, 22 Feb 2001 00:42:16 +0300 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.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi people! I cannot get FreeBSD's PPP to work with Win2K dialout network connection. It connects and configures OK (as far as I can say from logs and ipconfig) but (almost) no packets manage to get across the link. From Win95/Win98/WinME/FreeBSD all work fine. I wonder if somebody has encountered this problem and would be able to offer some advice? Thank you in advance Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 21 21:19:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 5F39837B491; Wed, 21 Feb 2001 21:19:46 -0800 (PST) (envelope-from julian@elischer.org) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id NAA19373; Thu, 22 Feb 2001 13:19:41 +0800 Received: from elischer.org (i076-061.nv.iinet.net.au [203.59.76.61]) by muzak.iinet.net.au (8.8.5/8.8.5) with ESMTP id NAA12677; Thu, 22 Feb 2001 13:16:49 +0800 Message-ID: <3A94A14C.D4D66EF8@elischer.org> Date: Wed, 21 Feb 2001 21:19:08 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Jean-Christophe Varaillon Cc: "Andy [TECC NOPS]" , freebsd-net@FreeBSD.ORG, jhay@FreeBSD.ORG Subject: Re: - RISCom card: lcp illegal conf-req in state initial - References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jean-Christophe Varaillon wrote: > > Thanks for your prompt repply. > > > > This is what dmesg | grep sr1 shows: > > > -------- > > > sr1: Adapter 0, port 1. > > > sr1 XXX: driver didn't set ifq_maxlen > > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > > ... > > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. I have seen this problem before with one model of sr card. the driver seemed unable to be able to drive that model of card.. john hay (jhay@freebsd.org) may be you best bet. (CC'd) -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 21 22:15:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26]) by hub.freebsd.org (Postfix) with ESMTP id 4EE5837B491 for ; Wed, 21 Feb 2001 22:15:12 -0800 (PST) (envelope-from chunan.li@nokia.com) Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35]) by mgw-x3.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1M6Feu22179 for ; Thu, 22 Feb 2001 08:15:40 +0200 (EET) Received: from esebh11nok.ntc.nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.1) with ESMTP id for ; Thu, 22 Feb 2001 08:15:10 +0200 Received: by esebh11nok with Internet Mail Service (5.5.2652.78) id <18L2PANC>; Thu, 22 Feb 2001 08:15:10 +0200 Message-ID: From: chunan.li@nokia.com To: freebsd-net@freebsd.org Subject: Would you tell me how to write a timer in FreeBSD user space ? Date: Thu, 22 Feb 2001 08:09:52 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.78) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I am newbie. Would you tell me how to write a timer in FreeBSD user space ? Br. Li ChunAn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 21 22:38:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id A791537B4EC for ; Wed, 21 Feb 2001 22:38:48 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1M6cj625005; Wed, 21 Feb 2001 22:38:45 -0800 (PST) Date: Wed, 21 Feb 2001 22:38:45 -0800 From: Alfred Perlstein To: chunan.li@nokia.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: Would you tell me how to write a timer in FreeBSD user space ? Message-ID: <20010221223845.K6641@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from chunan.li@nokia.com on Thu, Feb 22, 2001 at 08:09:52AM +0200 X-all-your-base: are belong to us. Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * chunan.li@nokia.com [010221 22:15] wrote: > Hi > > I am newbie. Would you tell me how to write a timer in FreeBSD user space ? see the manpages for: sleep(3), nanosleep(2), getitimer(2), and alarm(3). -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 21 22:54: 3 2001 Delivered-To: freebsd-net@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-53.dsl.lsan03.pacbell.net [64.165.226.53]) by hub.freebsd.org (Postfix) with ESMTP id A2B7937B401 for ; Wed, 21 Feb 2001 22:54:00 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 83A9866F2F; Wed, 21 Feb 2001 22:53:56 -0800 (PST) Date: Wed, 21 Feb 2001 22:53:55 -0800 From: Kris Kennaway To: Stephen Cimarelli Cc: freebsd-net@freebsd.org Subject: Re: Help with IPSEC Message-ID: <20010221225355.A68921@mollari.cthul.hu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from stephen@clari.net.au on Wed, Feb 21, 2001 at 10:00:09AM +1100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Feb 21, 2001 at 10:00:09AM +1100, Stephen Cimarelli wrote: > * Most users seem to use gif devices to setup the tunnels instead of IPsec > tunnels, Why? gif is the name of the device used to implement tunneling. > What ports/protocols do I need to allow through a firewall to allow gif and > IPsec to work? gif isn't a protocol, it's an interface name. Check /etc/protocols for the protocol number of the AH and ESP protocols, which IPSEC uses depending on which mode you run it in. Kris --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6lLeDWry0BWjoQKURAqK5AKCDCNbmd1x5EdpnddRqx78/8hOhMgCfQvYO P/5SrFdRSEhVzKZAVwG0yuk= =fJDV -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 21 23: 9: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 6529D37B401 for ; Wed, 21 Feb 2001 23:09:04 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id QAA23478; Thu, 22 Feb 2001 16:08:44 +0900 (JST) To: Kris Kennaway Cc: Stephen Cimarelli , freebsd-net@freebsd.org In-reply-to: kris's message of Wed, 21 Feb 2001 22:53:55 PST. <20010221225355.A68921@mollari.cthul.hu> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: Help with IPSEC From: itojun@iijlab.net Date: Thu, 22 Feb 2001 16:08:44 +0900 Message-ID: <23476.982825724@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> * Most users seem to use gif devices to setup the tunnels instead of IPsec >> tunnels, Why? >gif is the name of the device used to implement tunneling. >> What ports/protocols do I need to allow through a firewall to allow gif and >> IPsec to work? >gif isn't a protocol, it's an interface name. Check /etc/protocols >for the protocol number of the AH and ESP protocols, which IPSEC uses >depending on which mode you run it in. summary: if you would like to interoperate with other devices, use IPsec tunnel mode policy, not gif. IPsec tunnel is specified in RFC2401. gif works as specified in RFC1993. if you configure an IPsec tunnel by using IPsec policy (like "spdadd foo baa tunnel"), the encapsulation will strictly conform to RFC2401. you can create a similar packet by using IPsec transport mode against gif-encapsulated packet, however, it does not look exactly the same. if the other end is picky about packet format, they may drop it because it does not conform to RFC2401. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 1:10:15 2001 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 287F937B503; Thu, 22 Feb 2001 01:10:13 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1M9ACM28588; Thu, 22 Feb 2001 01:10:12 -0800 (PST) Date: Thu, 22 Feb 2001 01:10:12 -0800 From: Alfred Perlstein To: net@freebsd.org Cc: dec@freebsd.org Subject: HEADS UP: Major RPC subsystem patch. (ti-rpc, lockd, nfs over ipv6) Message-ID: <20010222011012.N6641@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-all-your-base: are belong to us. Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin Blapp has been working with me and Daniel Eischen to port the NetBSD port of ti-rpc to FreeBSD. For more information (patches, description and scripts) please go to: http://www.attic.ch/tirpc.html Since this delta is _huge_ and starting to become difficult to maintain I would like to shoot for committing within a couple of days. David, the reason I'm cc'ing you is because of your lockd work, I've heard rumors that you have both client and server nearly complete. When it is complete it would be ok with me if you replaced the netbsd lockd with your own implementation, the main gist of these patches is to bring us the benifit of a more modern RPC subsystem. I just wanted to make sure you weren't shooting for a commit within the next week or so, otherwise I'd like to see the delta applied. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 5:35: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id 5B2A737B491 for ; Thu, 22 Feb 2001 05:35:03 -0800 (PST) (envelope-from jcv@vbc.net) Received: from localhost (jcv@localhost) by brunel.uk1.vbc.net (8.11.0/8.11.0) with ESMTP id f1MDYOi71551; Thu, 22 Feb 2001 13:34:30 GMT X-Authentication-Warning: brunel.uk1.vbc.net: jcv owned process doing -bs Date: Thu, 22 Feb 2001 13:34:24 +0000 (GMT) From: Jean-Christophe Varaillon X-Sender: jcv@brunel.uk1.vbc.net To: John Hay Cc: freebsd-net@FreeBSD.ORG Subject: - N2d PCI & Driver option _ In-Reply-To: <200102201936.f1KJaJj91966@zibbi.icomtek.csir.co.za> 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 John, +-------+ Serial Interface +-------------+ | cisco | | FreeBSD 4.1 | | 3600 }----------{}-----------{ | | | N2d | | +-------+ card +-------------+ x.x.x.145 x.x.x.146 I need help to establish the communication between the router and the N2d card (sr interface). The reason why it is not working is almost certainly in the driver. There are two kinds of cables used with these cards. SDL Communications, the manufacturer, supplies x.21 cables that have the input clock pin tied to the output clock pin. Normaly I should be able to use a driver option to tell the HDLC chip to pass the signal through to the output clock pin. If this isn't configured, there is no data out clock, so the card doesn't work. Could you, please, tell me how to configure it ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 6:26:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 47A0A37B401 for ; Thu, 22 Feb 2001 06:26:18 -0800 (PST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.1/8.11.1) id f1MEPR352690; Thu, 22 Feb 2001 16:25:27 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200102221425.f1MEPR352690@zibbi.icomtek.csir.co.za> Subject: Re: - N2d PCI & Driver option _ In-Reply-To: from Jean-Christophe Varaillon at "Feb 22, 2001 01:34:24 pm" To: jcv@vbc.net (Jean-Christophe Varaillon) Date: Thu, 22 Feb 2001 16:25:27 +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 > > +-------+ Serial Interface +-------------+ > | cisco | | FreeBSD 4.1 | > | 3600 }----------{}-----------{ | > | | N2d | | > +-------+ card +-------------+ > x.x.x.145 x.x.x.146 > > > I need help to establish the communication between the router and the N2d > card (sr interface). > > The reason why it is not working is almost certainly in the driver. > > There are two kinds of cables used with these cards. > SDL Communications, the manufacturer, supplies x.21 cables > that have the input clock pin tied to the output clock pin. > > Normaly I should be able to use a driver option to tell the > HDLC chip to pass the signal through to the output clock pin. > > If this isn't configured, there is no data out clock, so the card > doesn't work. > > Could you, please, tell me how to configure it ? You are a little bit out of luck. On the ISA cards you can configure the clock settings with the flags option in the kernel config file. You can't do it with the PCI cards though, because none of that config line is used. The reason is that on the ISA cards there were no way for the driver to figure out what kind of cable was attached. On the PCI cards there are some registers that you can read to get that info. The driver will use 2 seperate clocks for V.35 cables and a combined clock for X.21 cables. If you want to play with it, look in /usr/src/sys/i386/isa/if_sr.c almost at the end of srattach_pci(). You will see either SR_FLAGS_EXT_SEP_CLK or SR_FLAGS_EXT_CLK gets assigned to sc->clk_cfg. If you search further into the file for SR_FLAGS_EXT_CLK, you will find the place where the actual magic is done to select the clocks. John -- John Hay -- John.Hay@icomtek.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 Thu Feb 22 6:42: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from relay.tecc.co.uk (luggage.tecc.co.uk [193.128.6.129]) by hub.freebsd.org (Postfix) with SMTP id 1056637B503 for ; Thu, 22 Feb 2001 06:41:31 -0800 (PST) (envelope-from andy@tecc.co.uk) Received: from fw-smtp.tecc.co.uk [195.217.37.39] by relay.tecc.co.uk with esmtp (Exim 1.70 #1) id 14Vvyi-0005UT-00; Thu, 22 Feb 2001 13:40:16 +0000 Received: from [195.217.37.155] (helo=southampton) by fw-smtp.tecc.co.uk with smtp (Exim 2.12 #3) id 14Vvwo-0001JA-00; Thu, 22 Feb 2001 13:38:18 +0000 From: "Andy [TECC NOPS]" To: "Jean-Christophe Varaillon" , "John Hay" Cc: Subject: RE: - N2d PCI & Driver option _ Date: Thu, 22 Feb 2001 13:43:50 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Guy's, don't forget that the Cisco needs a special cable also and infact as far as know don't make them as standard! I had to get mine specially made up for me. If the pinning is not correct at the cisco end it will not produce a clock even if the config says to do so. Cisco's rely on certain pins being joined together to identify the port type. The hardware will override any software config settings. Ak > -----Original Message----- > From: owner-freebsd-net@FreeBSD.ORG > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Jean-Christophe > Varaillon > Sent: 22 February 2001 13:34 > To: John Hay > Cc: freebsd-net@FreeBSD.ORG > Subject: - N2d PCI & Driver option _ > > > John, > > > +-------+ Serial Interface +-------------+ > | cisco | | FreeBSD 4.1 | > | 3600 }----------{}-----------{ | > | | N2d | | > +-------+ card +-------------+ > x.x.x.145 x.x.x.146 > > > I need help to establish the communication between the router and the N2d > card (sr interface). > > The reason why it is not working is almost certainly in the driver. > > There are two kinds of cables used with these cards. > SDL Communications, the manufacturer, supplies x.21 cables > that have the input clock pin tied to the output clock pin. > > Normaly I should be able to use a driver option to tell the > HDLC chip to pass the signal through to the output clock pin. > > If this isn't configured, there is no data out clock, so the card > doesn't work. > > Could you, please, tell me how to configure it ? > > > 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 Thu Feb 22 7:12: 1 2001 Delivered-To: freebsd-net@freebsd.org Received: from cgaylord.async.vt.edu (e028121.vtacs.vt.edu [63.164.28.121]) by hub.freebsd.org (Postfix) with ESMTP id 7E73337B491 for ; Thu, 22 Feb 2001 07:11:55 -0800 (PST) (envelope-from cgaylord@vt.edu) Received: from penderecki (dyn-1-101 [10.0.1.101]) by cgaylord.async.vt.edu (Postfix) with SMTP id 16972103; Thu, 22 Feb 2001 10:11:53 -0500 (EST) Message-ID: <009101c09ce1$c8bba810$6501000a@cns.vt.edu> From: "Clark Gaylord" To: Cc: References: <20010221132638.A12216@mailhub.nk.ukrtel.net> Subject: Re: user PPP HDLC errors Date: Thu, 22 Feb 2001 10:11:50 -0500 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I noticed similar errors upon starting PPP sessions ... are you bringing up the second line every couple minutes? What this seemed to be was some ASCII overlap at the beginning of the PPP session. I was using ASCII (i.e. scripted) login at the time and the message the access server sent ("your address is x.x.x.x, etc") was being interpreted by PPP as invalid frames. Check that your access server isn't trying to send you some text garbage. My solution was to go to strictly PAP authentication, and in our case this meant the access server did not spew garbage after the authentication completed. Let me know if this sounds consistent with your situation. Clark Gaylord Blacksburg, VA cgaylord@vt.edu ----- Original Message ----- From: George Fedorenko To: Sent: Wednesday, 21 February, 2001 06:26 Subject: user PPP HDLC errors > Hi, all > > I have a lot of such messages in my log file. > What do they mean? Is it a harware problem? > > ( PPP is in MP mode. FreeBSD 4.0R) > > Feb 18 16:54:51 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 2, ADDR: 0, COMD: 0, PROTO: 0 > Feb 18 16:55:52 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 3, ADDR: 0, COMD: 0, PROTO: 0 > Feb 18 16:56:53 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 2, ADDR: 0, COMD: 0, PROTO: 0 > Feb 18 16:58:55 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 3, ADDR: 0, COMD: 0, PROTO: 0 > Feb 18 16:59:57 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 3, ADDR: 0, COMD: 0, PROTO: 0 > Feb 18 17:00:58 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 7, ADDR: 0, COMD: 0, PROTO: 0 > > -- > George Fedorenko > > 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 Thu Feb 22 9:18: 2 2001 Delivered-To: freebsd-net@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id 7C3BC37B491; Thu, 22 Feb 2001 09:17:53 -0800 (PST) (envelope-from jcv@vbc.net) Received: from localhost (jcv@localhost) by brunel.uk1.vbc.net (8.11.0/8.11.0) with ESMTP id f1MHHqn73381; Thu, 22 Feb 2001 17:17:52 GMT X-Authentication-Warning: brunel.uk1.vbc.net: jcv owned process doing -bs Date: Thu, 22 Feb 2001 17:17:52 +0000 (GMT) From: Jean-Christophe Varaillon X-Sender: jcv@brunel.uk1.vbc.net To: jhay@FreeBSD.ORG Cc: julian@elischer.org, andy@tecc.co.uk, freebsd-net@FreeBSD.ORG Subject: Re: - N2d PCI & Driver Option - 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 Thu, 22 Feb 2001, John Hay wrote: > > >On Thu, 22 Feb 2001,Jean-Christophe Varaillon wrote: > > > > +-------+ Serial Interface +-------------+ > > | cisco | | FreeBSD 4.1 | > > | 3600 }----------{}-----------{ | > > | | N2d | | > > +-------+ card +-------------+ > > x.x.x.145 x.x.x.146 > > > > > > I need help to establish the communication between the router and the > N2d > > card (sr interface). > > > > The reason why it is not working is almost certainly in the driver. > > > > There are two kinds of cables used with these cards. > > SDL Communications, the manufacturer, supplies x.21 cables > > that have the input clock pin tied to the output clock pin. > > > > Normaly I should be able to use a driver option to tell the > > HDLC chip to pass the signal through to the output clock pin. > > > > If this isn't configured, there is no data out clock, so the card > > doesn't work. > > > > Could you, please, tell me how to configure it ? > > You are a little bit out of luck. On the ISA cards you can configure > the clock settings with the flags option in the kernel config file. > You can't do it with the PCI cards though, because none of that > config line is used. The reason is that on the ISA cards there were > no way for the driver to figure out what kind of cable was attached. > On the PCI cards there are some registers that you can read to get > that info. The driver will use 2 seperate clocks for V.35 cables > and a combined clock for X.21 cables. If you want to play with it, > look in /usr/src/sys/i386/isa/if_sr.c almost at the end of > srattach_pci(). You will see either SR_FLAGS_EXT_SEP_CLK or > SR_FLAGS_EXT_CLK gets assigned to sc->clk_cfg. If you search > further into the file for SR_FLAGS_EXT_CLK, you will find the > place where the actual magic is done to select the clocks. > > John This is now working properly, to adapt the driver if_sr.c to my case, a global variable (My_Case) has to be added in sr_init_msci(structsr_softc *sc): --------------------------------------------------------- sr_init_msci(struct sr_softc *sc) { int portndx; /* on-board port number */ u_int mcr_v; /* contents of modem control */ u_int *fecrp; /* pointer for PCI's MCR i/o */ struct sr_hardc *hc = sc->hc; msci_channel *msci = &hc->sca->msci[sc->scachan]; #ifdef N2_TEST_SPEED int br_v; /* contents for BR divisor */ int etcndx; /* index into ETC table */ int fifo_v, gotspeed; /* final tabled speed found */ int tmc_v; /* timer control register */ int wanted; /* speed (bitrate) wanted... */ struct rate_line *rtp; #endif portndx = sc->scachan; #if BUGGY > 0 printf("sr: sr_init_msci( sc=%08x)\n", sc); #endif SRC_PUT8(hc->sca_base, msci->cmd, SCA_CMD_RESET); SRC_PUT8(hc->sca_base, msci->md0, SCA_MD0_CRC_1 | SCA_MD0_CRC_CCITT | SCA_MD0_CRC_ENABLE | SCA_MD0_MODE_HDLC); SRC_PUT8(hc->sca_base, msci->md1, SCA_MD1_NOADDRCHK); SRC_PUT8(hc->sca_base, msci->md2, SCA_MD2_DUPLEX | SCA_MD2_NRZ); /* * According to the manual I should give a reset after changing the * mode registers. */ SRC_PUT8(hc->sca_base, msci->cmd, SCA_CMD_RXRESET); SRC_PUT8(hc->sca_base, msci->ctl, SCA_CTL_IDLPAT | SCA_CTL_UDRNC | SCA_CTL_RTS); /* * XXX Later we will have to support different clock settings. */ #ifdef My_Case printf ("vbcnet hack writing 0x%x\n", SCA_TXS_CLK_RX) ; SRC_PUT8(hc->sca_base, msci->rxs, 0); SRC_PUT8(hc->sca_base, msci->txs, SCA_TXS_CLK_RX); #else switch (sc->clk_cfg) { default: #if BUGGY > 0 . . . ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 9:53:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailhub.nk.ukrtel.net (mailhub.nk.ukrtel.net [195.5.9.2]) by hub.freebsd.org (Postfix) with ESMTP id BD1FB37B401 for ; Thu, 22 Feb 2001 09:53:23 -0800 (PST) (envelope-from gvf@nk.ukrtel.net) Received: by mailhub.nk.ukrtel.net (Postfix, from userid 1002) id 3A2F610781; Thu, 22 Feb 2001 19:51:29 +0200 (EET) Date: Thu, 22 Feb 2001 19:51:29 +0200 From: George Fedorenko To: Clark Gaylord Cc: freebsd-net@freebsd.org Subject: Re: user PPP HDLC errors Message-ID: <20010222195128.A27865@mailhub.nk.ukrtel.net> Reply-To: gvf@nk.ukrtel.net References: <20010221132638.A12216@mailhub.nk.ukrtel.net> <009101c09ce1$c8bba810$6501000a@cns.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <009101c09ce1$c8bba810$6501000a@cns.vt.edu>; from cgaylord@vt.edu on Thu, Feb 22, 2001 at 10:11:50AM -0500 X-Operating-System: FreeBSD 4.1-RELEASE Organization: ND Ukrtelekom Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Clark! On Thu, 22 Feb 2001, Clark Gaylord wrote: > I noticed similar errors upon starting PPP sessions ... are you bringing up > the second line every couple minutes? You mean second line in MP bundle? two leased lines with equal parameters, don't think so... or some another ppp links on the same box? than yes, this is my remote dial-up server (pppd+mgetty+login athentic) > What this seemed to be was some ASCII > overlap at the beginning of the PPP session. I was using ASCII (i.e. > scripted) login at the time and the message the access server sent ("your > address is x.x.x.x, etc") was being interpreted by PPP as invalid frames. > Check that your access server isn't trying to send you some text garbage. Hmmm, two leased lines via two Zyxels U-336s in dumb mode with command echo turned off and no authorization at all (just only enddisc defined in config, since ppp is in multi link mode and I have several such links on my central server) besides, another similarly configured box working well, say a couple of errors in logfile sometimes and then everything is OK, in opposite to the first one where only reboot can help (sorry, cant do any analysis - 120 miles from me and no qualified admin there) > My solution was to go to strictly PAP authentication, and in our case this > meant the access server did not spew garbage after the authentication > completed. Let me know if this sounds consistent with your situation. > > > ----- Original Message ----- > From: George Fedorenko > To: > Sent: Wednesday, 21 February, 2001 06:26 > Subject: user PPP HDLC errors > > > > Hi, all > > > > I have a lot of such messages in my log file. > > What do they mean? Is it a harware problem? > > > > ( PPP is in MP mode. FreeBSD 4.0R) > > > > Feb 18 16:54:51 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 2, ADDR: > 0, COMD: 0, PROTO: 0 > > Feb 18 16:55:52 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 3, ADDR: > 0, COMD: 0, PROTO: 0 > > Feb 18 16:56:53 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 2, ADDR: > 0, COMD: 0, PROTO: 0 > > Feb 18 16:58:55 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 3, ADDR: > 0, COMD: 0, PROTO: 0 > > Feb 18 16:59:57 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 3, ADDR: > 0, COMD: 0, PROTO: 0 > > Feb 18 17:00:58 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 7, ADDR: > 0, COMD: 0, PROTO: 0 > > -- George Fedorenko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 10: 6:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 5F5EA37B491 for ; Thu, 22 Feb 2001 10:06:07 -0800 (PST) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f1MI5VH01376; Thu, 22 Feb 2001 10:05:31 -0800 (PST) Message-ID: <3A9554E8.D2F6FE2E@isi.edu> Date: Thu, 22 Feb 2001 10:05:28 -0800 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: itojun@iijlab.net Cc: Kris Kennaway , Stephen Cimarelli , freebsd-net@freebsd.org Subject: Re: Help with IPSEC References: <23476.982825724@coconut.itojun.org> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msC5A16CDA791C619EBEB21F9A" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a cryptographically signed message in MIME format. --------------msC5A16CDA791C619EBEB21F9A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit itojun@iijlab.net wrote: > you can create a similar packet by using IPsec transport mode against > gif-encapsulated packet, however, it does not look exactly the same. > if the other end is picky about packet format, they may drop it > because it does not conform to RFC2401. Our ID "Use of IPSEC Transport Mode for Virtual Networks" has more information on this: ftp://ftp.isi.edu/internet-drafts/draft-touch-ipsec-vpn-01.txt -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------msC5A16CDA791C619EBEB21F9A Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAxMDIyMjE4MDUzMVowIwYJKoZIhvcNAQkEMRYE FORamkOY+piOgQDkTPEfJ3TTfJLsMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGAfi/NiUUefuHluuDfAWeHGXGBhBoFYRTJRUJQUGqpHjuBeXS5N9Lk ohSW7ncheTWePhHi8X9kByaHIMlfWWKpOrEE1gs6w5vfz1e2JQrZ6B5/R7dlWA7OM/Qctt57 pev/KL75Cyy42mZyNY4H7NsXPn0P18ufc1BtBpFkh1UOpT0= --------------msC5A16CDA791C619EBEB21F9A-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 10:27:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 181E837B4EC for ; Thu, 22 Feb 2001 10:27:41 -0800 (PST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.1/8.11.1) id f1MIRGm58347; Thu, 22 Feb 2001 20:27:16 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200102221827.f1MIRGm58347@zibbi.icomtek.csir.co.za> Subject: Re: - N2d PCI & Driver Option - In-Reply-To: from Jean-Christophe Varaillon at "Feb 22, 2001 05:17:52 pm" To: jcv@vbc.net (Jean-Christophe Varaillon) Date: Thu, 22 Feb 2001 20:27:16 +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 > > > > > > The reason why it is not working is almost certainly in the driver. > > > > > > There are two kinds of cables used with these cards. > > > SDL Communications, the manufacturer, supplies x.21 cables > > > that have the input clock pin tied to the output clock pin. > > > > > > Normaly I should be able to use a driver option to tell the > > > HDLC chip to pass the signal through to the output clock pin. > > This is now working properly, to adapt the driver if_sr.c to my case, > a global variable (My_Case) has to be added in > sr_init_msci(structsr_softc *sc): Oops! It looks like you found the bug. It is amazing that the driver have lived so long with this. My test setup is much too forgiving. :-/ Can you try this (untested) patch and see if it still works, please? This is basically the same I as have it in the ar(4) driver. Thanks. John -- John Hay -- John.Hay@icomtek.csir.co.za --- if_sr.c.org Tue May 16 12:48:41 2000 +++ if_sr.c Thu Feb 22 20:04:23 2001 @@ -1815,8 +1815,10 @@ printf("sr%d: External Clock Selected.\n", portndx); #endif - SRC_PUT8(hc->sca_base, msci->rxs, 0); - SRC_PUT8(hc->sca_base, msci->txs, 0); + SRC_PUT8(hc->sca_base, msci->rxs, + SCA_RXS_CLK_RXC0 | SCA_RXS_DIV1); + SRC_PUT8(hc->sca_base, msci->txs, + SCA_TXS_CLK_RX | SCA_TXS_DIV1); break; case SR_FLAGS_EXT_SEP_CLK: @@ -1824,20 +1826,10 @@ printf("sr%d: Split Clocking Selected.\n", portndx); #endif -#if 1 - SRC_PUT8(hc->sca_base, msci->rxs, 0); - SRC_PUT8(hc->sca_base, msci->txs, 0); -#else SRC_PUT8(hc->sca_base, msci->rxs, SCA_RXS_CLK_RXC0 | SCA_RXS_DIV1); - - /* - * We need to configure the internal bit clock for the - * transmitter's channel... - */ SRC_PUT8(hc->sca_base, msci->txs, - SCA_TXS_CLK_RX | SCA_TXS_DIV1); -#endif + SCA_TXS_CLK_TXC | SCA_TXS_DIV1); break; case SR_FLAGS_INT_CLK: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 15: 4:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from black.purplecat.net (ns1.purplecat.net [209.16.228.148]) by hub.freebsd.org (Postfix) with ESMTP id 4F13437B491 for ; Thu, 22 Feb 2001 15:04:54 -0800 (PST) (envelope-from peter@black.purplecat.net) Received: from localhost (peter@localhost) by black.purplecat.net (8.8.8/8.8.8) with ESMTP id SAA08581 for ; Thu, 22 Feb 2001 18:07:14 -0500 (EST) (envelope-from peter@black.purplecat.net) Date: Thu, 22 Feb 2001 18:07:14 -0500 (EST) From: Peter Brezny To: freebsd-net@freebsd.org Subject: ipfw simple quesiton Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I've just added a second external interface to a machine. I'd like to not have to duplicate all the rules that involve outside interfaces. I've got rules like $fwcmd add deny all from 0.0.0.0/8 to any in via $oif is it possible to specify multiple interfaces for one rule by letting oif= ed0,ed1 ? Similarly, would that work for the ip's of the outside if's? $fwcmd add allow ip from $oip to any keep-state out via $oif oip= 10.10.1.1,10.10.1.2 ? And finally, my rc.conf defines the interface for natd like this: natd_interface="xl0" is it possible to have natd run on both external interfaces without causing problems? how would i configure that? TIA pb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 16:55: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 58BEA37B401 for ; Thu, 22 Feb 2001 16:54:52 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1N0sCR53509 for net@freebsd.org; Thu, 22 Feb 2001 18:54:12 -0600 (CST) (envelope-from jlemon) Date: Thu, 22 Feb 2001 18:54:12 -0600 From: Jonathan Lemon To: net@freebsd.org Subject: ICMP unreachables, take II. Message-ID: <20010222185412.E5714@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I recently had a bug report regarding kqueue, where the kevent() call for a TCP socket would return because so_error was set, but the connection was still valid. The cause of this was because a non-blocking connect() call was made, and then the socket was monitored for writability. However, an ICMP error was returned, which eventually (after several retransmits) caused so_error to be set in tcp_notify() without changing the connection state. However, it doesn't really seem reasonable to leave the connection pending in a SYN_SENT state at this point. From the user's perspective, the select/kevent call returns, indicating writability, but the next operation (probably write) would fail, returning the contents of so_error. I would propose that instead of this behavior, the connection should be dropped instead. Also, RFC 1122 indicates that the application layer SHOULD report soft errors, and it seems that a half-hearted attempt is made in tcp_notify(), by calling so{rw}wakeup. However, this also seems to be incorrect, since select will not return and any tests performed on the socket state will show no change, so it seems that the wakeup calls should be removed. Also, (still reading?) while I'm in this bit of code, we currently react to all ICMP unreachable errors during setup of a connection; this is incorrect, only port/protocol and administrative icmp subtypes should be valid, so fix this as well. In this case, return ENETRESET as the error code to the user layer. Finally, ICMP errors should never be allowed to kill an existing TCP connection; if an administrative filter is installed across some existing flows, then those flows should be allowed to time out per the TCP protocol. Patch attached, please review. -- Jonathan Index: ip_icmp.c =================================================================== RCS file: /ncvs/src/sys/netinet/ip_icmp.c,v retrieving revision 1.52 diff -u -r1.52 ip_icmp.c --- ip_icmp.c 2001/02/18 09:34:51 1.52 +++ ip_icmp.c 2001/02/22 23:48:25 @@ -315,67 +315,35 @@ case ICMP_UNREACH: switch (code) { case ICMP_UNREACH_NET: - code = PRC_UNREACH_HOST; - break; - case ICMP_UNREACH_HOST: - code = PRC_UNREACH_HOST; - break; - - case ICMP_UNREACH_PROTOCOL: - code = PRC_UNREACH_HOST; - break; - - case ICMP_UNREACH_PORT: - code = PRC_UNREACH_HOST; - break; - case ICMP_UNREACH_SRCFAIL: - code = PRC_UNREACH_HOST; + case ICMP_UNREACH_NET_UNKNOWN: + case ICMP_UNREACH_HOST_UNKNOWN: + case ICMP_UNREACH_ISOLATED: + case ICMP_UNREACH_TOSNET: + case ICMP_UNREACH_TOSHOST: + case ICMP_UNREACH_HOST_PRECEDENCE: + case ICMP_UNREACH_PRECEDENCE_CUTOFF: + code = PRC_UNREACH_NET; break; case ICMP_UNREACH_NEEDFRAG: code = PRC_MSGSIZE; break; - case ICMP_UNREACH_NET_UNKNOWN: - code = PRC_UNREACH_HOST; - break; - - case ICMP_UNREACH_NET_PROHIB: + /* + * RFC 1122, Sections 3.2.2.1 and 4.2.3.9. + * Treat subcodes 2,3 as immediate RST + */ + case ICMP_UNREACH_PROTOCOL: + case ICMP_UNREACH_PORT: code = PRC_UNREACH_ADMIN_PROHIB; break; - case ICMP_UNREACH_TOSNET: - code = PRC_UNREACH_HOST; - break; - - case ICMP_UNREACH_HOST_UNKNOWN: - code = PRC_UNREACH_HOST; - break; - - case ICMP_UNREACH_ISOLATED: - code = PRC_UNREACH_HOST; - break; - + case ICMP_UNREACH_NET_PROHIB: case ICMP_UNREACH_HOST_PROHIB: - code = PRC_UNREACH_ADMIN_PROHIB; - break; - - case ICMP_UNREACH_TOSHOST: - code = PRC_UNREACH_HOST; - break; - case ICMP_UNREACH_FILTER_PROHIB: code = PRC_UNREACH_ADMIN_PROHIB; - break; - - case ICMP_UNREACH_HOST_PRECEDENCE: - code = PRC_UNREACH_HOST; - break; - - case ICMP_UNREACH_PRECEDENCE_CUTOFF: - code = PRC_UNREACH_HOST; break; default: Index: ip_input.c =================================================================== RCS file: /ncvs/src/sys/netinet/ip_input.c,v retrieving revision 1.154 diff -u -r1.154 ip_input.c --- ip_input.c 2001/02/21 16:59:47 1.154 +++ ip_input.c 2001/02/23 00:14:39 @@ -1429,7 +1429,7 @@ EHOSTUNREACH, EHOSTUNREACH, ECONNREFUSED, ECONNREFUSED, EMSGSIZE, EHOSTUNREACH, 0, 0, 0, 0, 0, 0, - ENOPROTOOPT + ENOPROTOOPT, ENETRESET }; /* Index: tcp_subr.c =================================================================== RCS file: /ncvs/src/sys/netinet/tcp_subr.c,v retrieving revision 1.91 diff -u -r1.91 tcp_subr.c --- tcp_subr.c 2001/02/22 21:23:45 1.91 +++ tcp_subr.c 2001/02/22 23:43:33 @@ -134,32 +134,9 @@ SYSCTL_INT(_net_inet_tcp, OID_AUTO, pcbcount, CTLFLAG_RD, &tcbinfo.ipi_count, 0, "Number of active PCBs"); -/* - * Treat ICMP unreachables like a TCP RST as required by rfc1122 section 3.2.2.1 - * - * Administatively prohibited kill's sessions regardless of - * their current state, other unreachable by default only kill - * sessions if they are in SYN-SENT state, this ensure temporary - * routing problems doesn't kill existing TCP sessions. - * This can be overridden by icmp_like_rst_syn_sent_only. - */ - -static int icmp_unreach_like_rst = 1; -SYSCTL_INT(_net_inet_tcp, OID_AUTO, icmp_unreach_like_rst, CTLFLAG_RW, - &icmp_unreach_like_rst, 0, - "Treat ICMP unreachable messages like TCP RST, rfc1122 section 3.2.2.1"); - -/* - * Control if ICMP unreachable messages other that administratively prohibited - * ones will kill sessions not in SYN-SENT state. - * - * Has no effect unless icmp_unreach_like_rst is enabled. - */ - -static int icmp_like_rst_syn_sent_only = 1; -SYSCTL_INT(_net_inet_tcp, OID_AUTO, icmp_like_rst_syn_sent_only, CTLFLAG_RW, - &icmp_like_rst_syn_sent_only, 0, - "When icmp_unreach_like_rst is enabled, only act on sessions in SYN-SENT state"); +static int icmp_may_rst = 1; +SYSCTL_INT(_net_inet_tcp, OID_AUTO, icmp_may_rst, CTLFLAG_RW, &icmp_may_rst, 0, + "Certain ICMP unreachable messages may abort connections in SYN_SENT"); static void tcp_cleartaocache __P((void)); static void tcp_notify __P((struct inpcb *, int)); @@ -775,14 +752,16 @@ * Notify a tcp user of an asynchronous error; * store error as soft error, but wake up user * (for now, won't do anything until can select for soft error). + * + * Do not wake up user since there currently is no mechanism for + * reporting soft errors. */ static void tcp_notify(inp, error) struct inpcb *inp; int error; { - register struct tcpcb *tp = (struct tcpcb *)inp->inp_ppcb; - register struct socket *so = inp->inp_socket; + struct tcpcb *tp = (struct tcpcb *)inp->inp_ppcb; /* * Ignore some errors if we are hooked up. @@ -797,12 +776,14 @@ return; } else if (tp->t_state < TCPS_ESTABLISHED && tp->t_rxtshift > 3 && tp->t_softerror) - so->so_error = error; + tcp_drop(tp, error); else tp->t_softerror = error; +#if 0 wakeup((caddr_t) &so->so_timeo); sorwakeup(so); sowwakeup(so); +#endif } static int @@ -993,35 +974,17 @@ struct sockaddr *sa; void *vip; { - register struct ip *ip = vip; - register struct tcphdr *th; + struct ip *ip = vip; + struct tcphdr *th; void (*notify) __P((struct inpcb *, int)) = tcp_notify; tcp_seq tcp_sequence = 0; int tcp_seq_check = 0; if (cmd == PRC_QUENCH) notify = tcp_quench; - else if ((icmp_unreach_like_rst == 1) && ((cmd == PRC_UNREACH_HOST) || - (cmd == PRC_UNREACH_ADMIN_PROHIB)) && (ip) && - ((IP_VHL_HL(ip->ip_vhl) << 2) == sizeof(struct ip))) { - /* - * Only go here if the length of the IP header in the ICMP packet - * is 20 bytes, that is it doesn't have options, if it does have - * options, we will not have the first 8 bytes of the TCP header, - * and thus we cannot match against TCP source/destination port - * numbers and TCP sequence number. - * - * If PRC_UNREACH_ADMIN_PROHIB drop session regardsless of current - * state, else we check the sysctl icmp_like_rst_syn_sent_only to - * see if we should drop the session only in SYN-SENT state, or - * in all states. - */ + else if (icmp_may_rst && cmd == PRC_UNREACH_ADMIN_PROHIB && ip) { tcp_seq_check = 1; - if (cmd == PRC_UNREACH_ADMIN_PROHIB) { - notify = tcp_drop_all_states; - } else { - notify = tcp_drop_syn_sent; - } + notify = tcp_drop_syn_sent; } else if (cmd == PRC_MSGSIZE) notify = tcp_mtudisc; else if (PRC_IS_REDIRECT(cmd)) { @@ -1173,10 +1136,9 @@ } /* - * When a ICMP unreachable is recieved, drop the - * TCP connection, depending on the sysctl - * icmp_like_rst_syn_sent_only, it only drops - * the session if it's in SYN-SENT state + * When a specific ICMP unreachable message is received and the + * connection state is SYN-SENT, drop the connection. This behavior + * is controlled by the icmp_may_rst sysctl. */ void tcp_drop_syn_sent(inp, errno) @@ -1184,22 +1146,8 @@ int errno; { struct tcpcb *tp = intotcpcb(inp); - if((tp) && ((icmp_like_rst_syn_sent_only == 0) || - (tp->t_state == TCPS_SYN_SENT))) - tcp_drop(tp, errno); -} -/* - * When a ICMP unreachable is recieved, drop the - * TCP connection, regardless of the state. - */ -void -tcp_drop_all_states(inp, errno) - struct inpcb *inp; - int errno; -{ - struct tcpcb *tp = intotcpcb(inp); - if(tp) + if (tp && tp->t_state == TCPS_SYN_SENT) tcp_drop(tp, errno); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 17: 4:53 2001 Delivered-To: freebsd-net@freebsd.org Received: from black.purplecat.net (ns1.purplecat.net [209.16.228.148]) by hub.freebsd.org (Postfix) with ESMTP id 6711037B503 for ; Thu, 22 Feb 2001 17:04:49 -0800 (PST) (envelope-from peter@black.purplecat.net) Received: from localhost (peter@localhost) by black.purplecat.net (8.8.8/8.8.8) with ESMTP id UAA08870 for ; Thu, 22 Feb 2001 20:07:09 -0500 (EST) (envelope-from peter@black.purplecat.net) Date: Thu, 22 Feb 2001 20:07:09 -0500 (EST) From: Peter Brezny To: freebsd-net@freebsd.org Subject: nat forwarding 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 After reading through the natd man page, I think I understand what I need to do to redirect requests to one specified ip to another, however, I don't understand where I put this config info. i currently start natd with rc.conf with the following lines: natd_enable="YES" #natd_config="/etc/rc.natd" natd_interface="fpx1" natd_flags="-dynamic" as you can see, i've attempted creating a file with natd config options in it, but things don't seem to jive when i use it and comment out the last two lines in the example above (specifying them inside rc.natd) Also, i'd like to have multiple external interfaces with natd aliasing each one respectively. is this possible? how would i configure that? TIA pb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 18:13:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D9CE837B491; Thu, 22 Feb 2001 18:13:46 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1N2DkA03315; Thu, 22 Feb 2001 18:13:46 -0800 (PST) Date: Thu, 22 Feb 2001 18:13:46 -0800 From: Alfred Perlstein To: net@freebsd.org Cc: dec@freebsd.org, peter@freebsd.org Subject: Re: HEADS UP: Major RPC subsystem patch. (ti-rpc, lockd, nfs over ipv6) Message-ID: <20010222181346.R29126@fw.wintelcom.net> References: <20010222011012.N6641@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010222011012.N6641@fw.wintelcom.net>; from bright@wintelcom.net on Thu, Feb 22, 2001 at 01:10:12AM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org An updated patch is available here: http://people.freebsd.org/~alfred/tirpc.diff.gz please see the homepage at: http://www.attic.ch/tirpc.html Martin has a script that you need to run to create the directories otherwise patch(1) gets confused. * Alfred Perlstein [010222 01:10] wrote: > Martin Blapp has been working with me and Daniel Eischen to > port the NetBSD port of ti-rpc to FreeBSD. > > For more information (patches, description and scripts) please go > to: http://www.attic.ch/tirpc.html > > Since this delta is _huge_ and starting to become difficult to > maintain I would like to shoot for committing within a couple of > days. > > David, the reason I'm cc'ing you is because of your lockd work, > I've heard rumors that you have both client and server nearly > complete. When it is complete it would be ok with me if you replaced > the netbsd lockd with your own implementation, the main gist of > these patches is to bring us the benifit of a more modern RPC > subsystem. I just wanted to make sure you weren't shooting for a > commit within the next week or so, otherwise I'd like to see the > delta applied. > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 18:49:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 88FB337B491 for ; Thu, 22 Feb 2001 18:49:53 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id CA9163E69; Fri, 23 Feb 2001 03:49:52 +0100 (CET) Date: Fri, 23 Feb 2001 03:49:52 +0100 From: Jesper Skriver To: Jonathan Lemon Cc: net@freebsd.org Subject: Re: ICMP unreachables, take II. Message-ID: <20010223034952.A6694@skriver.dk> References: <20010222185412.E5714@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010222185412.E5714@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Thu, Feb 22, 2001 at 06:54:12PM -0600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Feb 22, 2001 at 06:54:12PM -0600, Jonathan Lemon wrote: I was just about to send a MFC of the current code out for review, will ditch that ... > I recently had a bug report regarding kqueue, where the kevent() call > for a TCP socket would return because so_error was set, but the > connection was still valid. > > The cause of this was because a non-blocking connect() call was made, > and then the socket was monitored for writability. However, an ICMP > error was returned, which eventually (after several retransmits) caused > so_error to be set in tcp_notify() without changing the connection state. > > However, it doesn't really seem reasonable to leave the connection > pending in a SYN_SENT state at this point. From the user's perspective, > the select/kevent call returns, indicating writability, but the next > operation (probably write) would fail, returning the contents of so_error. > > I would propose that instead of this behavior, the connection should > be dropped instead. Makes sense. > Also, RFC 1122 indicates that the application layer SHOULD report > soft errors, and it seems that a half-hearted attempt is made in > tcp_notify(), by calling so{rw}wakeup. > > However, this also seems to be incorrect, since select will not return > and any tests performed on the socket state will show no change, so it > seems that the wakeup calls should be removed. > > Also, (still reading?) while I'm in this bit of code, we currently > react to all ICMP unreachable errors during setup of a connection; > this is incorrect, only port/protocol and administrative icmp subtypes > should be valid, so fix this as well. In this case, return ENETRESET > as the error code to the user layer. Agree, it should be a different from ECONNREFUSED I still think we should react to the following as a minimum - type 3 code 0 net unreachable - type 3 code 1 host unreachable - type 3 code 9 net administrative prohibited - type 3 code 10 host administrative prohibited in addition to - type 3 code 2 protocol unreachable - type 3 code 3 port unreachable The first too, so connections won't wait for timeout if the routers tell you that the net/host is unreachable. > Finally, ICMP errors should never be allowed to kill an existing TCP > connection; if an administrative filter is installed across some existing > flows, then those flows should be allowed to time out per the TCP protocol. What I submitted was what we agreed upon earlier, but the above is fine by me. > Patch attached, please review. See comments inline, I havn't build a kernel with it to verify functionality. > Index: ip_icmp.c > =================================================================== > RCS file: /ncvs/src/sys/netinet/ip_icmp.c,v > retrieving revision 1.52 > diff -u -r1.52 ip_icmp.c > --- ip_icmp.c 2001/02/18 09:34:51 1.52 > +++ ip_icmp.c 2001/02/22 23:48:25 > @@ -315,67 +315,35 @@ > case ICMP_UNREACH: > switch (code) { > case ICMP_UNREACH_NET: > - code = PRC_UNREACH_HOST; > - break; > - > case ICMP_UNREACH_HOST: > - code = PRC_UNREACH_HOST; > - break; These 2 I don't agree upon, see above. > Index: tcp_subr.c > =================================================================== > RCS file: /ncvs/src/sys/netinet/tcp_subr.c,v > retrieving revision 1.91 > diff -u -r1.91 tcp_subr.c > --- tcp_subr.c 2001/02/22 21:23:45 1.91 > +++ tcp_subr.c 2001/02/22 23:43:33 > @@ -134,32 +134,9 @@ > SYSCTL_INT(_net_inet_tcp, OID_AUTO, pcbcount, CTLFLAG_RD, > &tcbinfo.ipi_count, 0, "Number of active PCBs"); > > -/* > - * Treat ICMP unreachables like a TCP RST as required by rfc1122 section 3.2.2.1 > - * > - * Administatively prohibited kill's sessions regardless of > - * their current state, other unreachable by default only kill > - * sessions if they are in SYN-SENT state, this ensure temporary > - * routing problems doesn't kill existing TCP sessions. > - * This can be overridden by icmp_like_rst_syn_sent_only. > - */ > - > -static int icmp_unreach_like_rst = 1; > -SYSCTL_INT(_net_inet_tcp, OID_AUTO, icmp_unreach_like_rst, CTLFLAG_RW, > - &icmp_unreach_like_rst, 0, > - "Treat ICMP unreachable messages like TCP RST, rfc1122 section 3.2.2.1"); > - > -/* > - * Control if ICMP unreachable messages other that administratively prohibited > - * ones will kill sessions not in SYN-SENT state. > - * > - * Has no effect unless icmp_unreach_like_rst is enabled. > - */ > - > -static int icmp_like_rst_syn_sent_only = 1; > -SYSCTL_INT(_net_inet_tcp, OID_AUTO, icmp_like_rst_syn_sent_only, CTLFLAG_RW, > - &icmp_like_rst_syn_sent_only, 0, > - "When icmp_unreach_like_rst is enabled, only act on sessions in SYN-SENT state"); Perhaps you could keep some of the comment ... /* * Treat some ICMP unreachables like a TCP RST as required by * rfc1122 section 3.2.2.1 */ > if (cmd == PRC_QUENCH) > notify = tcp_quench; > - else if ((icmp_unreach_like_rst == 1) && ((cmd == PRC_UNREACH_HOST) || > - (cmd == PRC_UNREACH_ADMIN_PROHIB)) && (ip) && > - ((IP_VHL_HL(ip->ip_vhl) << 2) == sizeof(struct ip))) { Sure we'll not try to read off the end of the recieved packet, when we remove the check for the header length. I put it there as a extra check against "attackers" sending us malformed ICMP messages with only part of the attached IP header, or even without it. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 19:15:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 25AB837B401; Thu, 22 Feb 2001 19:15:39 -0800 (PST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.2/8.11.2) with ESMTP id f1N3DLg08996; Thu, 22 Feb 2001 22:13:22 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010222215259.03d78d60@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 22 Feb 2001 22:13:20 -0500 To: stable@freebsd.org From: Mike Tancsa Subject: 802.1q vlans and STABLE Cc: freebsd-net@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, are vlans and the fxp driver ready for prime time ? I have a situation where I would like to deploy a simple network which looks like [network vlan #1]-----[cat5500]-----[network vlan #2] | | | [freebsd fxp0] The two remote networks would be trunked back to me using 802.1q encaps off a cat 5500 switch. I am using the patch at http://www.euitt.upm.es/~pjlobo/fbsdvlan.html to account for larger frame sizes. Whats not clear to me is that when configuring fxp0, do I just assign it IPs via the vlan interface, or should I also give fxp0 a normal IP. Will it break things if fxp0 has an IP associated with it ? Also, does aliasing of vlan interfaces work as expected ? if network #1 was 10.20.30.1/24 and 10.30.40.1/24 on vlan #123 and network #2 was 172.16.1.1/24 and 192.168.1.1/24 on vlan #456 do I just do ifconfig fxp0 up ifconfig vlan0 inet 10.20.30.1 netmask 255.255.255.0 vlan 123 vlandev fxp0 mtu 1500 ifconfig vlan0 inet 10.30.40.1 netmask 255.255.255.0 alias ifconfig vlan1 .... Is there a limit as to the # of vlan interfaces ? Also, do I have any performance hits if I have too many vlans ? If I recall correctly, in LINUX, there used to be a performance hit if you had too many interfaces. -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 19:21:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 0E5AB37B401 for ; Thu, 22 Feb 2001 19:21:28 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1N3Kiq58098; Thu, 22 Feb 2001 21:20:44 -0600 (CST) (envelope-from jlemon) Date: Thu, 22 Feb 2001 21:20:44 -0600 From: Jonathan Lemon To: Jesper Skriver Cc: Jonathan Lemon , net@freebsd.org Subject: Re: ICMP unreachables, take II. Message-ID: <20010222212044.H5714@prism.flugsvamp.com> References: <20010222185412.E5714@prism.flugsvamp.com> <20010223034952.A6694@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20010223034952.A6694@skriver.dk> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Feb 23, 2001 at 03:49:52AM +0100, Jesper Skriver wrote: > > I still think we should react to the following as a minimum > - type 3 code 0 net unreachable > - type 3 code 1 host unreachable RFC 1122, Section 4.2.3.9 says: o Destination Unreachable -- codes 0, 1, 5 Since these Unreachable messages indicate soft error conditions, TCP MUST NOT abort the connection, and it SHOULD make the information available to the application. I think that these should be transients. > Perhaps you could keep some of the comment ... Hmm, yeah, I was probably a little too overzealous with the axe there > > if (cmd == PRC_QUENCH) > > notify = tcp_quench; > > - else if ((icmp_unreach_like_rst == 1) && ((cmd == PRC_UNREACH_HOST) || > > - (cmd == PRC_UNREACH_ADMIN_PROHIB)) && (ip) && > > - ((IP_VHL_HL(ip->ip_vhl) << 2) == sizeof(struct ip))) { > > Sure we'll not try to read off the end of the recieved packet, when we > remove the check for the header length. > > I put it there as a extra check against "attackers" sending us malformed > ICMP messages with only part of the attached IP header, or even without > it. Yup, but if you exmaine icmp_input, which calls this code, it has already verified that there are a full 8 bytes of the TCP packet in existence; if this is not the case, icmp_input will drop the packet. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 19:34:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id DB6CD37B491 for ; Thu, 22 Feb 2001 19:34:06 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id C9F663E6C; Fri, 23 Feb 2001 04:34:05 +0100 (CET) Date: Fri, 23 Feb 2001 04:34:05 +0100 From: Jesper Skriver To: Jonathan Lemon Cc: net@freebsd.org Subject: Re: ICMP unreachables, take II. Message-ID: <20010223043405.B6694@skriver.dk> References: <20010222185412.E5714@prism.flugsvamp.com> <20010223034952.A6694@skriver.dk> <20010222212044.H5714@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010222212044.H5714@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Thu, Feb 22, 2001 at 09:20:44PM -0600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Feb 22, 2001 at 09:20:44PM -0600, Jonathan Lemon wrote: > On Fri, Feb 23, 2001 at 03:49:52AM +0100, Jesper Skriver wrote: > > > > I still think we should react to the following as a minimum > > - type 3 code 0 net unreachable > > - type 3 code 1 host unreachable > > RFC 1122, Section 4.2.3.9 says: > > o Destination Unreachable -- codes 0, 1, 5 > Since these Unreachable messages indicate soft error > conditions, TCP MUST NOT abort the connection, and it > SHOULD make the information available to the > application. > > I think that these should be transients. As discussed on IRC I suggest adding the ability (under control of a sysctl, disabled by default) to treat 0/1 (perhaps even 5) like 2,3,9 & 10. This would be of benifit to server whose application will retry itself, a example of such a server would be a mailserver ... Routers sending host/net unreachables would enable the mailserver to immediate delay delivery of that email instead of waiting for the long TCP timeout, thus freeing delivery processes. And for transients it doesn't matter as the mailserver will just retry shortly after. > > Perhaps you could keep some of the comment ... > > Hmm, yeah, I was probably a little too overzealous with the axe there > > > > > if (cmd == PRC_QUENCH) > > > notify = tcp_quench; > > > - else if ((icmp_unreach_like_rst == 1) && ((cmd == PRC_UNREACH_HOST) || > > > - (cmd == PRC_UNREACH_ADMIN_PROHIB)) && (ip) && > > > - ((IP_VHL_HL(ip->ip_vhl) << 2) == sizeof(struct ip))) { > > > > Sure we'll not try to read off the end of the recieved packet, when we > > remove the check for the header length. > > > > I put it there as a extra check against "attackers" sending us malformed > > ICMP messages with only part of the attached IP header, or even without > > it. > > Yup, but if you exmaine icmp_input, which calls this code, it has > already verified that there are a full 8 bytes of the TCP packet > in existence; if this is not the case, icmp_input will drop the packet. Ok - thanks, still havn't got a full overview of the networking code, but getting closer ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 20:20:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id A0AB737B401 for ; Thu, 22 Feb 2001 20:20:14 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 336F03E66; Fri, 23 Feb 2001 05:20:13 +0100 (CET) Date: Fri, 23 Feb 2001 05:20:13 +0100 From: Jesper Skriver To: Jonathan Lemon Cc: net@freebsd.org Subject: Re: ICMP unreachables, take II. Message-ID: <20010223052012.A39613@skriver.dk> References: <20010222185412.E5714@prism.flugsvamp.com> <20010223034952.A6694@skriver.dk> <20010222212044.H5714@prism.flugsvamp.com> <20010223043405.B6694@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010223043405.B6694@skriver.dk>; from jesper@skriver.dk on Fri, Feb 23, 2001 at 04:34:05AM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Feb 23, 2001 at 04:34:05AM +0100, Jesper Skriver wrote: > On Thu, Feb 22, 2001 at 09:20:44PM -0600, Jonathan Lemon wrote: > > On Fri, Feb 23, 2001 at 03:49:52AM +0100, Jesper Skriver wrote: > > > > > > I still think we should react to the following as a minimum > > > - type 3 code 0 net unreachable > > > - type 3 code 1 host unreachable > > > > RFC 1122, Section 4.2.3.9 says: > > > > o Destination Unreachable -- codes 0, 1, 5 > > Since these Unreachable messages indicate soft error > > conditions, TCP MUST NOT abort the connection, and it > > SHOULD make the information available to the > > application. > > > > I think that these should be transients. > > As discussed on IRC I suggest adding the ability (under control of a > sysctl, disabled by default) to treat 0/1 (perhaps even 5) like 2,3,9 & > 10. Forget this, as discussed on IRC, it would be better to have a code 0/1 trigger a immediate retransmit of the SYN, this would also give us timeouts < 10 secs ... If jlemon doesn't beat me to it, I'll try to look at this in the weekend ... as a possible "take III" /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 20:23:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 6EC5D37B503; Thu, 22 Feb 2001 20:23:10 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id PAA24812; Fri, 23 Feb 2001 15:23:02 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01K0GD7VKCGGO2K116@cim.alcatel.com.au>; Fri, 23 Feb 2001 15:22:49 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f1N4Mwn39837; Fri, 23 Feb 2001 15:22:58 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Fri, 23 Feb 2001 15:22:57 +1100 From: Peter Jeremy Subject: Re: 802.1q vlans and STABLE In-reply-to: <4.2.2.20010222215259.03d78d60@marble.sentex.net>; from mike@sentex.net on Thu, Feb 22, 2001 at 10:13:20PM -0500 To: Mike Tancsa Cc: stable@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Mail-Followup-To: Mike Tancsa , stable@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Message-id: <20010223152257.K36182@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <4.2.2.20010222215259.03d78d60@marble.sentex.net> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 2001-Feb-22 22:13:20 -0500, Mike Tancsa wrote: >are vlans and the fxp driver ready for prime time ? I've been running a system with 6 VLANs on an fxp for about 6 months now without problems. The system has currently been up nearly 3 weeks (following a blackout) and had been up for 2 1/2 months before that. netstat -I gives: aalp02# netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll dc0* 1500 08:00:2b:c3:6b:b9 0 0 0 0 0 fxp0 1500 00:d0:b7:20:8f:ee 252636245 0 252026018 0 0 fxp0 1500 none none 252636245 0 252026018 0 0 fxp1* 1500 00:d0:b7:20:bd:ab 0 0 0 0 0 xl0* 1500 00:c0:4f:ba:32:2b 0 0 0 0 0 vlan0 1500 00:d0:b7:20:8f:ee 51854151 0 24998001 0 0 vlan0 1500 net91/24 aalp02-a0 51854151 0 24998001 0 0 vlan1 1500 00:d0:b7:20:8f:ee 0 0 2 0 0 vlan1 1500 net155 aalp02-a1 0 0 2 0 0 vlan2 1500 00:d0:b7:20:8f:ee 90580612 0 128663939 0 0 vlan2 1500 net156 aalp02-l0 90580612 0 128663939 0 0 vlan3 1500 00:d0:b7:20:8f:ee 9104283 0 9104999 0 0 vlan3 1500 net157 aalp02-l1 9104283 0 9104999 0 0 vlan4 1500 00:d0:b7:20:8f:ee 93593008 0 81969794 0 0 vlan4 1500 net158 aalp02-r0 93593008 0 81969794 0 0 vlan5 1500 00:d0:b7:20:8f:ee 7504326 0 7289701 0 0 vlan5 1500 net159 aalp02-r1 7504326 0 7289701 0 0 lo0 16384 8 0 8 0 0 lo0 16384 127 localhost 8 0 8 0 0 ds0* 65532 0 0 0 0 0 aalp02# >http://www.euitt.upm.es/~pjlobo/fbsdvlan.html That's where I got my code last August. I haven't looked to see what has changed since then. I know I have patches for: - set the "Long Receive OK" bit in the i82559 (fxp) [rather than rummage through "error packets"] - support VLANs on the TI ThunderLan (tl driver) - support VLANs on the SMC 9432TX (tx driver) - VLAN support in driver modules for the above drivers - fix VLAN handling in arp(8) - support VLANs in tcpdump(8) [this may be in the generic tree by now] >configuring fxp0, do I just assign it IPs via the vlan interface, or should >I also give fxp0 a normal IP. The fxp0 interface doesn't need an IP address, but you will need to explicitly `up' it with a line in /etc/rc.conf like: ifconfig_fxp0="up media 100baseTX mediaopt full-duplex" > Will it break things if fxp0 has an IP associated with it ? No, but at least the Alcatel (Xylan) switch I'm using won't send `normal' ethernet packets once the port has been designated as a VLAN trunk. >Also, does aliasing of vlan interfaces work as expected ? I don't know any reason why it wouldn't, but haven't tried. I _am_ using proxy ARP on one of the VLAN interfaces. >Is there a limit as to the # of vlan interfaces ? There used to be some hard limits on total interfaces (16 or 32, I can't remember which) - I'm not sure when the fix was MFC'd. I don't believe there is any hard limit on the number of VLANs, but I've never tried more than 6. > Also, do I have any >performance hits if I have too many vlans ? On incoming 802.1Q packets, there's a linear search through a list of known VLAN numbers to determine the destination vlan device. Unless you're planning on lots of VLAN's, this probably isn't an issue. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 22 23:55:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id 7DC4D37B65D; Thu, 22 Feb 2001 23:55:43 -0800 (PST) (envelope-from Peter.Blok@inter.NL.net) Received: from ntpc by altrade.nijmegen.inter.nl.net via 1Cust143.tnt34.rtm1.nl.uu.net [213.116.162.143] with SMTP id IAA21577 (8.8.8/1.3); Fri, 23 Feb 2001 08:55:38 +0100 (MET) Reply-To: From: "Peter Blok" To: "'Mike Tancsa'" , Cc: Subject: RE: 802.1q vlans and STABLE Date: Fri, 23 Feb 2001 08:53:51 +0100 Message-ID: <000001c09d6d$c3b3caf0$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-reply-to: <4.2.2.20010222215259.03d78d60@marble.sentex.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am working with VLANs and a BayStack 450-T without stability problems, except when you configure NETGRAPH at the same time. The kernel crashes during boot-up. -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Mike Tancsa Sent: Friday, February 23, 2001 04:13 To: stable@freebsd.org Cc: freebsd-net@freebsd.org Subject: 802.1q vlans and STABLE Hi, are vlans and the fxp driver ready for prime time ? I have a situation where I would like to deploy a simple network which looks like [network vlan #1]-----[cat5500]-----[network vlan #2] | | | [freebsd fxp0] The two remote networks would be trunked back to me using 802.1q encaps off a cat 5500 switch. I am using the patch at http://www.euitt.upm.es/~pjlobo/fbsdvlan.html to account for larger frame sizes. Whats not clear to me is that when configuring fxp0, do I just assign it IPs via the vlan interface, or should I also give fxp0 a normal IP. Will it break things if fxp0 has an IP associated with it ? Also, does aliasing of vlan interfaces work as expected ? if network #1 was 10.20.30.1/24 and 10.30.40.1/24 on vlan #123 and network #2 was 172.16.1.1/24 and 192.168.1.1/24 on vlan #456 do I just do ifconfig fxp0 up ifconfig vlan0 inet 10.20.30.1 netmask 255.255.255.0 vlan 123 vlandev fxp0 mtu 1500 ifconfig vlan0 inet 10.30.40.1 netmask 255.255.255.0 alias ifconfig vlan1 .... Is there a limit as to the # of vlan interfaces ? Also, do I have any performance hits if I have too many vlans ? If I recall correctly, in LINUX, there used to be a performance hit if you had too many interfaces. -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 23 1:43:15 2001 Delivered-To: freebsd-net@freebsd.org Received: from euitt.upm.es (haddock.euitt.upm.es [138.100.52.102]) by hub.freebsd.org (Postfix) with ESMTP id C291537B401 for ; Fri, 23 Feb 2001 01:43:09 -0800 (PST) (envelope-from pjlobo@euitt.upm.es) Received: from odin.euitt.upm.es (odin.euitt.upm.es [138.100.52.111]) by euitt.upm.es (8.9.3/8.9.3) with ESMTP id KAA01286; Fri, 23 Feb 2001 10:42:42 +0100 (MET) Date: Fri, 23 Feb 2001 10:42:42 +0100 (CET) From: "Pedro J. Lobo" To: Mike Tancsa Cc: Subject: Re: 802.1q vlans and STABLE In-Reply-To: <4.2.2.20010222215259.03d78d60@marble.sentex.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 22 Feb 2001, Mike Tancsa wrote: > Hi, > are vlans and the fxp driver ready for prime time ? To be honest, there is still a minor problem (see the end of the message). > I have a situation where I would like to deploy a simple network which > looks like > > > [network vlan #1]-----[cat5500]-----[network vlan #2] > | > | > | > [freebsd fxp0] > > The two remote networks would be trunked back to me using 802.1q encaps off > a cat 5500 switch. I am using the patch at > http://www.euitt.upm.es/~pjlobo/fbsdvlan.html > to account for larger frame sizes. Whats not clear to me is that when > configuring fxp0, do I just assign it IPs via the vlan interface, or should > I also give fxp0 a normal IP. The usual situation is to only assign IP addresses to the VLAN interfaces, so you would have in rc.conf: network_interfaces="fxp0 vlan0 vlan1" ifconfig_fxp0="up" ifconfig_vlan0="inet xx.xx.xx.xx netmask yy.yy.yy.yy vlan #1 vlandev fxp0" ifconfig_vlan1="inet zz.zz.zz.zz netmask aa.aa.aa.aa vlan #2 vlandev fxp0" > Will it break things if fxp0 has an IP associated with it ? No, it won't. Just be aware that not all switches will allow you to use tagged and non-tagged frames on the same port. > Also, does aliasing of vlan interfaces work as expected ? Yes. > Is there a limit as to the # of vlan interfaces ? Also, do I have any > performance hits if I have too many vlans ? If I recall correctly, in > LINUX, there used to be a performance hit if you had too many interfaces. Don't know for sure. I have a router with 3 cards and 12 vlans, and that's what uptime says right now: caronte:pjlobo> uptime 10:21AM up 150 days, 2:32, 1 user, load averages: 0.00, 0.00, 0.00 The machine is a PII-400 with 32 MB of RAM, and its performance is quite decent. I haven't done any torture tests, but it doesn't appear to be very busy looking at the cpu times: CPU states: 0.0% user, 0.0% nice, 0.4% system, 4.7% interrupt, 95.0% idle As for the problem I spoke of, this is it: caronte:pjlobo> netstat -ib Name Mtu Network Address Ipkts Ierrs Ibytes Opkts Oerrs Obytes Coll fxp0 1500 00:90:27:8c:f9:f4 464689332 0 66292389 727275472 0 0 0 fxp0 1500 none none 464689332 0 66292389 727275472 0 0 0 fxp1 1500 00:90:27:8c:fa:92 250841282 0 3715740027 294179467 0 0 0 fxp1 1500 none none 250841282 0 3715740027 294179467 0 0 0 fxp2 1500 00:d0:b7:09:cc:e8 895025963 0 3489296215 670473207 0 994515613 0 fxp2 1500 138.100.87.16 138.100.87.18 895025963 0 3489296215 670473207 0 994515613 0 vlan0 1500 00:90:27:8c:f9:f4 503740779 0 969833213 700887254 0 2896942987 0 vlan0 1500 138.100.52/25 caronte 503740779 0 969833213 700887254 0 2896942987 0 [...] fxp0/1 are vlan-only devices, and fxp2 is a "normal" device with no vlans defined. As you may see, the vlan-enabled devices doesn't count the output bytes. This is true only for the physical devices (fxp0 and fxp1), as the virtual devices (vlanXX) do it right. I haven't found the time to investigate this, because I can live with it and (like most of us) am loaded with tons of work. Cheers, Pedro. -- Pedro José Lobo Perea Tel: +34 913367819 / Fax: +34 913319229 Centro de Cálculo e-mail: pjlobo@euitt.upm.es E.U.I.T. Telecomunicación Universidad Politécnica de Madrid Ctra. de Valencia, Km. 7 E-28031 Madrid - España / Spain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 23 1:48:26 2001 Delivered-To: freebsd-net@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id 5402437B4EC for ; Fri, 23 Feb 2001 01:48:20 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 28879 invoked by uid 666); 23 Feb 2001 09:59:48 -0000 Received: from i078-087.nv.iinet.net.au (HELO elischer.org) (203.59.78.87) by mail.m.iinet.net.au with SMTP; 23 Feb 2001 09:59:48 -0000 Message-ID: <3A9631C0.C3A7C351@elischer.org> Date: Fri, 23 Feb 2001 01:47:44 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Peter.Blok@inter.NL.net Cc: 'Mike Tancsa' , stable@freebsd.org, freebsd-net@freebsd.org Subject: Re: 802.1q vlans and STABLE References: <000001c09d6d$c3b3caf0$8a02a8c0@ntpc> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Blok wrote: > > I am working with VLANs and a BayStack 450-T without stability problems, > except when you configure NETGRAPH at the same time. The kernel crashes > during boot-up. > huh? can you give me more on this? -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 23 1:52:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from euitt.upm.es (haddock.euitt.upm.es [138.100.52.102]) by hub.freebsd.org (Postfix) with ESMTP id 2D97537B491 for ; Fri, 23 Feb 2001 01:52:28 -0800 (PST) (envelope-from pjlobo@euitt.upm.es) Received: from odin.euitt.upm.es (odin.euitt.upm.es [138.100.52.111]) by euitt.upm.es (8.9.3/8.9.3) with ESMTP id KAA00791; Fri, 23 Feb 2001 10:52:17 +0100 (MET) Date: Fri, 23 Feb 2001 10:52:17 +0100 (CET) From: "Pedro J. Lobo" To: Peter Jeremy Cc: Subject: Re: 802.1q vlans and STABLE In-Reply-To: <20010223152257.K36182@gsmx07.alcatel.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 23 Feb 2001, Peter Jeremy wrote: > >http://www.euitt.upm.es/~pjlobo/fbsdvlan.html > > That's where I got my code last August. I haven't looked to see what > has changed since then. I know I have patches for: > - set the "Long Receive OK" bit in the i82559 (fxp) [rather than > rummage through "error packets"] This is now in the vlan patches. > - VLAN support in driver modules for the above drivers Including fxp? My code only supports vlan in modules for the 558 and 559 controllers, not for the old 557. > - fix VLAN handling in arp(8) Can you ellaborate a bit more on this one? > - support VLANs in tcpdump(8) [this may be in the generic tree by now] It's been for quite some time. I used it when doing my first version of the patches on a 3.2-stable system. > > Also, do I have any > >performance hits if I have too many vlans ? > > On incoming 802.1Q packets, there's a linear search through a list of > known VLAN numbers to determine the destination vlan device. Unless > you're planning on lots of VLAN's, this probably isn't an issue. That makes sense. A linear search through 10 or 20 elements doesn't seem like a performance killer. And, provided that most switches won't support more than 16 or 32 vlans, it is very unusual to have more than that. -- Pedro José Lobo Perea Tel: +34 913367819 / Fax: +34 913319229 Centro de Cálculo e-mail: pjlobo@euitt.upm.es E.U.I.T. Telecomunicación Universidad Politécnica de Madrid Ctra. de Valencia, Km. 7 E-28031 Madrid - España / Spain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 23 4:21: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id 5801637B4EC for ; Fri, 23 Feb 2001 04:21:02 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id f1NCKxf14470; Fri, 23 Feb 2001 13:20:59 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.2/8.11.0) id f1NCHCM35884; Fri, 23 Feb 2001 13:17:12 +0100 (CET) (envelope-from asmodai) Date: Fri, 23 Feb 2001 13:17:12 +0100 From: Jeroen Ruigrok/Asmodai To: Andrea Venturoli Cc: freebsd-net@freebsd.org Subject: Re: Meditation on rl driver Message-ID: <20010223131712.B35087@daemon.ninth-circle.org> References: <200102091039.f19AdGl25740@relay.flashnet.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200102091039.f19AdGl25740@relay.flashnet.it>; from ml.ventu@flashnet.it on Fri, Feb 09, 2001 at 11:39:14AM -0500 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20010209 12:00], Andrea Venturoli (ml.ventu@flashnet.it) wrote: >** Reply to note from Clark Gaylord Thu, 8 Feb 2001 12:46:06 -0500 > >> It used to be the case that mediaopt half-duplex worked. It stopped >> working at some point (I don't recall exactly when ... somewhere >> between 4.0 and 4.2 I think), > >So this IS a bug. Not in the RL driver source at least. Must be a problem in ifconfig or somewhere else. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 23 4:23: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id 53A2737B65D for ; Fri, 23 Feb 2001 04:23:05 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id f1NCN2U51965; Fri, 23 Feb 2001 13:23:02 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.2/8.11.0) id f1NCLmE35921; Fri, 23 Feb 2001 13:21:48 +0100 (CET) (envelope-from asmodai) Date: Fri, 23 Feb 2001 13:21:48 +0100 From: Jeroen Ruigrok/Asmodai To: "Rogier R. Mulhuijzen" Cc: freebsd-net@FreeBSD.ORG Subject: Re: call for testers: port aggregation netgraph module Message-ID: <20010223132148.C35087@daemon.ninth-circle.org> References: <4.3.2.7.0.20010212000150.00adec60@mail.bsdchicks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4.3.2.7.0.20010212000150.00adec60@mail.bsdchicks.com>; from drwilco@drwilco.nl on Mon, Feb 12, 2001 at 12:01:58AM +0100 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20010212 00:30], Rogier R. Mulhuijzen (drwilco@drwilco.nl) wrote: >There's a IEEE standard these days for link aggregation. 802.3AD if I'm not >mistaken. When my workload at work lightens up I'll be spending time on this. You are correct. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 23 8:18:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from org.chem.msu.su (org.chem.msu.su [158.250.32.94]) by hub.freebsd.org (Postfix) with ESMTP id 0584537B491 for ; Fri, 23 Feb 2001 08:18:34 -0800 (PST) (envelope-from genie@qsar.chem.msu.su) Received: from qsar2 (org-qsar2.chem.msu.su [158.250.48.99]) by org.chem.msu.su (8.9.3/8.9.3) with SMTP id TAA01262 for ; Fri, 23 Feb 2001 19:18:25 +0300 (MSK) Message-ID: <001701c09db4$282102a0$6330fa9e@qsar2> From: "Eugene Radchenko" To: References: <00b601c09c53$febaaf80$0f212ad4@genie> Subject: PPP from Win2K to FreeBSD Date: Fri, 23 Feb 2001 19:17:44 +0300 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.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi people! I cannot get FreeBSD's PPP to work with Win2K dialout network connection. It connects and configures OK (as far as I can say from logs and ipconfig) but (almost) no packets manage to get across the link. From Win95/Win98/WinME/FreeBSD all work fine. I wonder if somebody has encountered this problem and would be able to offer some advice? Thank you in advance Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 23 9:11:35 2001 Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 0A08737B401 for ; Fri, 23 Feb 2001 09:11:31 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14WLtz-0000pW-00; Fri, 23 Feb 2001 10:21:07 -0700 Message-ID: <3A969C03.A1B61ACB@softweyr.com> Date: Fri, 23 Feb 2001 10:21:07 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Pedro J. Lobo" Cc: Peter Jeremy , freebsd-net@FreeBSD.ORG Subject: Re: 802.1q vlans and STABLE References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Pedro J. Lobo" wrote: > > On Fri, 23 Feb 2001, Peter Jeremy wrote: > > > - fix VLAN handling in arp(8) > > Can you ellaborate a bit more on this one? For instance, do your fixes create an ARP table per VLAN? If so, I know some Alcatel people who might be interested. ;^) -- "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 Feb 23 9:40:45 2001 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 C9B7B37B401 for ; Fri, 23 Feb 2001 09:40:43 -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 MAA33788; Fri, 23 Feb 2001 12:40:06 -0500 (EST) (envelope-from wollman) Date: Fri, 23 Feb 2001 12:40:06 -0500 (EST) From: Garrett Wollman Message-Id: <200102231740.MAA33788@khavrinen.lcs.mit.edu> To: Jesper Skriver Cc: net@FreeBSD.ORG Subject: Re: ICMP unreachables, take II. In-Reply-To: <20010223034952.A6694@skriver.dk> References: <20010222185412.E5714@prism.flugsvamp.com> <20010223034952.A6694@skriver.dk> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > The first too, so connections won't wait for timeout if the routers tell > you that the net/host is unreachable. They're supposed to -- that's intentional. Unreachables are *transient* events. Getting just one doesn't imply anything. -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 Fri Feb 23 13:28: 3 2001 Delivered-To: freebsd-net@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id 26D4737B4EC; Fri, 23 Feb 2001 13:27:58 -0800 (PST) (envelope-from Peter.Blok@inter.NL.net) Received: from ntpc by altrade.nijmegen.inter.nl.net via 1Cust204.tnt29.rtm1.nl.uu.net [213.116.152.204] with SMTP id WAA02591 (8.8.8/1.3); Fri, 23 Feb 2001 22:27:33 +0100 (MET) Reply-To: From: "Peter Blok" To: "'Julian Elischer'" Cc: "'Mike Tancsa'" , , Subject: RE: 802.1q vlans and STABLE Date: Fri, 23 Feb 2001 22:25:35 +0100 Message-ID: <000f01c09ddf$2987b000$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3A9631C0.C3A7C351@elischer.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian, The moment I compiled NETGRAPH in and rebootted the system crashed in vlanioctl. For a strange reason my system doesn't saves the dump, so I still don't know where exactly. Since it is my "production/clean" machine I haven't done any testing yet. On another machine I have VLAN and NETGRAPH compiled in, but haven't used the vlan interfaces yet. Maybe I'll do so this weekend to get to the bottom of this. Peter -----Original Message----- From: julian@inter.nl.net [mailto:julian@inter.nl.net]On Behalf Of Julian Elischer Sent: Friday, February 23, 2001 10:48 To: Peter.Blok@inter.NL.net Cc: 'Mike Tancsa'; stable@freebsd.org; freebsd-net@freebsd.org Subject: Re: 802.1q vlans and STABLE Peter Blok wrote: > > I am working with VLANs and a BayStack 450-T without stability problems, > except when you configure NETGRAPH at the same time. The kernel crashes > during boot-up. > huh? can you give me more on this? -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 23 13:45: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id 6718D37B4EC for ; Fri, 23 Feb 2001 13:44:58 -0800 (PST) (envelope-from petro@She.wertep.com) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id XAA71016 for ; Fri, 23 Feb 2001 23:44:54 +0200 (EET) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id XAA28773 for ; Fri, 23 Feb 2001 23:46:51 +0200 (EET) (envelope-from petro@She.wertep.com) Date: Fri, 23 Feb 2001 23:46:41 +0200 (EET) From: petro To: freebsd-net@FreeBSD.ORG Subject: ISDN question. 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 Hello. I would like to find or may be somebody can give me some additional instruction how to run ISDN line. I installed in kernel Fritz!Card and read in /etc/isdn examples but can't understand how to begin this run. Thank you very much for any help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 23 15:54: 8 2001 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id E147837B401 for ; Fri, 23 Feb 2001 15:54:05 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.2/8.11.2) with ESMTP id f1NNrm405877; Fri, 23 Feb 2001 23:53:48 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.2/8.11.2) with ESMTP id f1NNtfo05913; Fri, 23 Feb 2001 23:55:41 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200102232355.f1NNtfo05913@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: petro Cc: freebsd-net@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: ISDN question. In-Reply-To: Message from petro of "Fri, 23 Feb 2001 23:46:41 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Feb 2001 23:55:41 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello. > I would like to find or may be somebody can give me some additional > instruction how to run ISDN line. I installed in kernel Fritz!Card and > read in /etc/isdn examples but can't understand how to begin this run. > Thank you very much for any help. Have you looked at /usr/share/examples/ppp/*isdn* ? -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 24 4:36: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id D0EAA37B401 for ; Sat, 24 Feb 2001 04:36:03 -0800 (PST) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from localhost ([3ffe:501:100f:13ff::e]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id VAA24535; Sat, 24 Feb 2001 21:20:51 +0900 (JST) Date: Sat, 24 Feb 2001 19:33:51 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: skodati@in.ibm.com, freebsd-net@FreeBSD.ORG Subject: Re: Query: SIOCGIFAFLAGS_IN6 In-Reply-To: In your message of "Tue, 20 Feb 2001 19:57:22 +0900" <17792.982666642@coconut.itojun.org> References: <17792.982666642@coconut.itojun.org> User-Agent: Wanderlust/2.3.0 (Roam) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 20000414(IM141) Lines: 23 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> On Tue, 20 Feb 2001 19:57:22 +0900, >>>>> itojun@iijlab.net said: >> Iam a newbie to FreeBSD and iam working on DHCPv6. i would like to know the >> importance of SIOCGIFAFLAGS_IN6 defined in in6_var.h >> The definition of structure in6_ifreq differs from the definition of >> in6_ifreq defined in Linux 2.4.0, and creates woes to port it. >> Do i have any alternatives for the above for Linux . > interface management ioctls are not standardized in any place > (as far as I know of). if you would like to support both *BSD and > linux, you definitely need some #ifdef in your code, or use > /sbin/ifconfig. BTW, what if your goal is to just grab all interface addresses, you can use the getifaddrs(3) library, which can be used for all *BSD. And, if I remember correctly, the USAGI project has ported the function to Linux. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 24 6: 9:30 2001 Delivered-To: freebsd-net@freebsd.org Received: from hera.drwilco.net (isis.drwilco.net [194.109.63.159]) by hub.freebsd.org (Postfix) with ESMTP id AB04637B491 for ; Sat, 24 Feb 2001 06:09:26 -0800 (PST) (envelope-from drwilco@drwilco.nl) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.2/8.11.1) with ESMTP id f1OEMMo66732; Sat, 24 Feb 2001 15:22:23 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010224144707.00df4100@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 24 Feb 2001 14:58:52 +0100 To: Peter Brezny , freebsd-net@FreeBSD.ORG From: "Rogier R. Mulhuijzen" Subject: Re: ipfw simple quesiton In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 18:07 22-2-01 -0500, Peter Brezny wrote: >Hello, > >I've just added a second external interface to a machine. I'd like to not >have to duplicate all the rules that involve outside interfaces. > > >I've got rules like > > $fwcmd add deny all from 0.0.0.0/8 to any in via $oif > >is it possible to specify multiple interfaces for one rule by letting > >oif= ed0,ed1 > >? No, rc.firewall is just a shell script, $oif would be replaced with ed0,ed1 and if you read the ipfw manpage you'll see that ipfw doesn't like that. You could however use ed* which would match every ed interface in the box. >Similarly, would that work for the ip's of the outside if's? > > $fwcmd add allow ip from $oip to any keep-state out via $oif > >oip= 10.10.1.1,10.10.1.2 > >? Again, no. But you can use netmasks. 10.10.1.1/24 and 10.10.1.1:255.255.255.0 would both match 10.10.1.* IPs, or you could try 10.10.1.1/30 which would match 10.10.1.0, 10.10.1.1, 10.10.1.2 and 10.10.1.3 if I'm not mistaken. >And finally, my rc.conf defines the interface for natd like this: > > >natd_interface="xl0" > > >is it possible to have natd run on both external interfaces without >causing problems? how would i configure that? Why would you want to run natd on external 2 interfaces at the same time? DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 24 6: 9:53 2001 Delivered-To: freebsd-net@freebsd.org Received: from hera.drwilco.net (isis.drwilco.net [194.109.63.159]) by hub.freebsd.org (Postfix) with ESMTP id 284DB37B65D for ; Sat, 24 Feb 2001 06:09:49 -0800 (PST) (envelope-from drwilco@drwilco.nl) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.2/8.11.1) with ESMTP id f1ODwCo66656; Sat, 24 Feb 2001 14:58:13 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010224143232.00bff2d0@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 24 Feb 2001 14:34:42 +0100 To: Julian Elischer , Satyajeet Seth From: "Rogier R. Mulhuijzen" Subject: Re: Using netgraph to implement pseudo interfaces Cc: net@FreeBSD.ORG In-Reply-To: <3A910856.CE68FEAC@elischer.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I plan to design a netgraph as follows: > > > > iface1 > > / > > fxp0 <-> bpf > > \ > > iface2 > >I forgot to add in my previous response that you'd have to do this like: > >fxp0: <--> bpf <--> bpf <--> interface0 > \ \ > \ ------>interface1 > \ > \------------>interface2 > >as each bpfnode hook only selects between a >"match" and "no match" hook. > >you could do it with one node as follows: > > > +----------------------------+ > | | > +->(hook2)[ ] | >fxp0:(lower)<->(hook1)[bpf](nomatch1)----+ > [ ](match1)<-------->(upper)fxp0: > [ ](nomatch2)<------>(hook)iface1: > [ ](match2)<-------->(hook)iface2: > >i.e. loop the data back through the same node twice to effect two rules on >the same data. Or you could use the ALL mode in the one2many node. That way all incoming traffic would reach all interfaces. Interfaces should still only accept packets meant for themselves. Or you the bridge node. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 24 6:16: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id AE79037B4EC for ; Sat, 24 Feb 2001 06:16:07 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.9.3) with SMTP id f1OEEEi05536; Sat, 24 Feb 2001 09:14:15 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <005201c09e6c$46511770$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Peter Brezny" , , "Rogier R. Mulhuijzen" References: <4.3.2.7.0.20010224144707.00df4100@mail.bsdchicks.com> Subject: Re: ipfw simple quesiton Date: Sat, 24 Feb 2001 09:15:43 -0500 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.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >is it possible to have natd run on both external interfaces without > >causing problems? how would i configure that? > > Why would you want to run natd on external 2 interfaces at the same time? I'm not sure if this is the case, but if the box was multihomed (for example, DHCP-based DSL and Cable), then you would want NATD running on both external interfaces. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 24 8:22:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from keyser.soze.com (keyser.soze.com [194.165.93.196]) by hub.freebsd.org (Postfix) with ESMTP id 95EE337B401 for ; Sat, 24 Feb 2001 08:22:34 -0800 (PST) (envelope-from stefan@keyser.soze.com) Received: (from stefan@localhost) by keyser.soze.com (8.9.1/8.9.1) id RAA17998 for freebsd-net@FreeBSD.ORG; Sat, 24 Feb 2001 17:22:32 +0100 (CET) Date: Sat, 24 Feb 2001 17:22:32 +0100 From: Stefan Arentz To: freebsd-net@FreeBSD.ORG Subject: netgraph pptp and alcatel adsl modems Message-ID: <20010224172232.A17840@keyser.soze.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to connect a FreeBSD 4.1.1 box with mpd-netgraph 3.2 to an Alcatel Speed Touch Pro (Home) modem. On Windows 2000 this is the setup: Ethernet: Address: 10.0.0.150/255.0.0.0 VPN: Server: 10.0.0.138 pc1 PPTP Only PAP No Encryption That's all I have to configure. My problem is that I don't know how to map this to the mpd configuration. To start I added an extra network card to the freebsd machine and gave it the following config: ed2: flags=8843 mtu 1500 inet 10.0.0.150 netmask 0xff000000 broadcast 10.255.255.255 ether 00:00:b4:b7:a2:ff The network is working, I can ping the Alcatel router, which is on 10.0.0.138. Then I created a mpd.links: adslclient: set link type pptp set pptp peer 10.0.0.138 set pptp enable originate outcall And an mpd.conf: adslclient: new -i ng0 adslclient adslclient set iface disable on-demand set iface idle 0 set bundle disable multilink set bundle authname "USERNAME" set bundle password "PASSWORD" set link max-redial 1 set link yes pap set link no chap set ccp no mppc set link disable no-orig-auth set ipcp ranges 0.0.0.0/0 0.0.0.0/0 However, I have no idea how to map the 'pc1' to the mpd.conf file. In the Win2000 client this is added after the PPTP server address. This is not a port number, what is it called in the PPTP protocol? I configured a 'phonebook' with four entries, pc1/pc4 in the Alcatel router, these allow four pptp sessions to be created to the modem. Oh, the connection ends with these errors: ... [adslclient] LCP: state change Ack-Rcvd --> Opened [adslclient] LCP: phase shift ESTABLISH --> AUTHENTICATE [adslclient] LCP: auth: peer wants PAP, I want PAP [adslclient] PAP: using authname "F100035382" [adslclient] PAP: sending REQUEST [adslclient] LCP: LayerUp [adslclient] PAP: rec'd ACK #1 [adslclient] LCP: authorization timer expired [adslclient] LCP: authorization failed [adslclient] device: CLOSE event in state UP It' must be something with the 'pc1' thing, but I have no idea what it is. Reading the RFC now, but I hope someone on the list knows more about this. Thanks! Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 24 9:16:52 2001 Delivered-To: freebsd-net@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id B5E1537B503 for ; Sat, 24 Feb 2001 09:16:50 -0800 (PST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.2/8.11.2) with ESMTP id f1OHGog14699 for ; Sat, 24 Feb 2001 12:16:50 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010224121627.02c67f00@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 24 Feb 2001 12:16:49 -0500 To: freebsd-net@freebsd.org From: Mike Tancsa Subject: Re: 802.1q vlans and STABLE Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:17 AM 2/24/2001 -0500, C. Stephen Gunn wrote: >2/3 of our traffic started showing up on the wrong logical network. How did you work around it ? Or were you able to ? ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 24 11:20:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id 7242837B4EC for ; Sat, 24 Feb 2001 11:20:46 -0800 (PST) (envelope-from mark@whistle.com) Received: from [10.1.10.113] ([10.1.10.113]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id LAA65820; Sat, 24 Feb 2001 11:19:08 -0800 (PST) Mime-Version: 1.0 X-Sender: mark@207.76.206.1 Message-Id: In-Reply-To: References: Date: Sat, 24 Feb 2001 11:19:02 -0800 To: Paul Herman , Garrett Wollman From: Mark Peek Subject: Re: I have delayed ACK problems Cc: Jonathan Lemon , Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:19 PM +0100 1/25/01, Paul Herman wrote: >On Thu, 25 Jan 2001, Garrett Wollman wrote: > >> <> said: >> >> The important part was the >> if (callout_pending(tp->tt_delack)) { >> ... >> tp->t_flags |= TF_ACKNOW; >> } >> >> bit. This causes us to ack immediately where previously we would just >> delay an already-schedule delayed ack. > >Yep, that does it. Simple. Elegant. I see now why my (bloated >unintelligible) patch worked, it also didn't reset the timer when a >delayed ack might have already been pending. > >OK, there are other parts of the code that do the same thing >(TCP_REASS, SYN was ACKed, et. al.) but if no one objects, I'll >send-pr the patch to be commited. Was there ever a final resolution to this problem? I checked CVS and there didn't appear to be any code changes made as a result of this discussion. If this was a real problem, I'm wondering whether it should be checked into -current and considered for MFC into 4.3. Thanks, Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 24 12:28:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id C7B7437B401 for ; Sat, 24 Feb 2001 12:28:46 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1OKRgP36070; Sat, 24 Feb 2001 14:27:42 -0600 (CST) (envelope-from jlemon) Date: Sat, 24 Feb 2001 14:27:42 -0600 From: Jonathan Lemon To: Mark Peek Cc: Paul Herman , Garrett Wollman , Jonathan Lemon , net@FreeBSD.ORG Subject: Re: I have delayed ACK problems Message-ID: <20010224142742.T5714@prism.flugsvamp.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Feb 24, 2001 at 11:19:02AM -0800, Mark Peek wrote: > At 11:19 PM +0100 1/25/01, Paul Herman wrote: > >On Thu, 25 Jan 2001, Garrett Wollman wrote: > > > >> < >> said: > >> > >> The important part was the > >> if (callout_pending(tp->tt_delack)) { > >> ... > >> tp->t_flags |= TF_ACKNOW; > >> } > >> > >> bit. This causes us to ack immediately where previously we would just > >> delay an already-schedule delayed ack. > > > >Yep, that does it. Simple. Elegant. I see now why my (bloated > >unintelligible) patch worked, it also didn't reset the timer when a > >delayed ack might have already been pending. > > > >OK, there are other parts of the code that do the same thing > >(TCP_REASS, SYN was ACKed, et. al.) but if no one objects, I'll > >send-pr the patch to be commited. > > Was there ever a final resolution to this problem? I checked CVS and > there didn't appear to be any code changes made as a result of this > discussion. If this was a real problem, I'm wondering whether it > should be checked into -current and considered for MFC into 4.3. The patches are still sitting in my tree, as I've been unable to come up with a test case that actually makes a difference. The "tar cf host:..." example is bogus, as the problem here is apparently the protocol doesn't stream data, but waits for an entire block to be ack'd before continuing; using a larger blocking factor results in better transfer times. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 24 13:18:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id 80B9B37B4EC for ; Sat, 24 Feb 2001 13:18:27 -0800 (PST) (envelope-from Peter.Blok@inter.NL.net) Received: from ntpc by altrade.nijmegen.inter.nl.net via 1Cust116.tnt32.rtm1.nl.uu.net [213.116.158.116] with SMTP id WAA16361 (8.8.8/1.3); Sat, 24 Feb 2001 22:18:23 +0100 (MET) Reply-To: From: "Peter Blok" To: "'Stefan Arentz'" , Subject: RE: netgraph pptp and alcatel adsl modems Date: Sat, 24 Feb 2001 22:16:34 +0100 Message-ID: <000401c09ea7$11ad7000$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0005_01C09EAF.73744900" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20010224172232.A17840@keyser.soze.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C09EAF.73744900 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Stefan, You have to patch mpd-netgraph to make it work. I have recently found out how to use mpd-netgraph in such an environment. Attached my patch and config files. I don't have a written procedure yet. If you have questions, don't hesitate to e-mail me. Peter -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Stefan Arentz Sent: Saturday, February 24, 2001 17:23 To: freebsd-net@FreeBSD.ORG Subject: netgraph pptp and alcatel adsl modems I'm trying to connect a FreeBSD 4.1.1 box with mpd-netgraph 3.2 to an Alcatel Speed Touch Pro (Home) modem. On Windows 2000 this is the setup: Ethernet: Address: 10.0.0.150/255.0.0.0 VPN: Server: 10.0.0.138 pc1 PPTP Only PAP No Encryption That's all I have to configure. My problem is that I don't know how to map this to the mpd configuration. To start I added an extra network card to the freebsd machine and gave it the following config: ed2: flags=8843 mtu 1500 inet 10.0.0.150 netmask 0xff000000 broadcast 10.255.255.255 ether 00:00:b4:b7:a2:ff The network is working, I can ping the Alcatel router, which is on 10.0.0.138. Then I created a mpd.links: adslclient: set link type pptp set pptp peer 10.0.0.138 set pptp enable originate outcall And an mpd.conf: adslclient: new -i ng0 adslclient adslclient set iface disable on-demand set iface idle 0 set bundle disable multilink set bundle authname "USERNAME" set bundle password "PASSWORD" set link max-redial 1 set link yes pap set link no chap set ccp no mppc set link disable no-orig-auth set ipcp ranges 0.0.0.0/0 0.0.0.0/0 However, I have no idea how to map the 'pc1' to the mpd.conf file. In the Win2000 client this is added after the PPTP server address. This is not a port number, what is it called in the PPTP protocol? I configured a 'phonebook' with four entries, pc1/pc4 in the Alcatel router, these allow four pptp sessions to be created to the modem. Oh, the connection ends with these errors: ... [adslclient] LCP: state change Ack-Rcvd --> Opened [adslclient] LCP: phase shift ESTABLISH --> AUTHENTICATE [adslclient] LCP: auth: peer wants PAP, I want PAP [adslclient] PAP: using authname "F100035382" [adslclient] PAP: sending REQUEST [adslclient] LCP: LayerUp [adslclient] PAP: rec'd ACK #1 [adslclient] LCP: authorization timer expired [adslclient] LCP: authorization failed [adslclient] device: CLOSE event in state UP It' must be something with the 'pc1' thing, but I have no idea what it is. Reading the RFC now, but I hope someone on the list knows more about this. Thanks! Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message ------=_NextPart_000_0005_01C09EAF.73744900 Content-Type: application/x-gzip; name="mxstream.tar.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="mxstream.tar.gz" H4sICB0ilDoAA214c3RyZWFtLnRhcgDtwQENAAAAwqD3T20ON6AAAAAAAAAAAACANwOa3h0nACgA AA== ------=_NextPart_000_0005_01C09EAF.73744900-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 24 14:56:25 2001 Delivered-To: freebsd-net@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 988BC37B491 for ; Sat, 24 Feb 2001 14:56:19 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 9002B3E53; Sat, 24 Feb 2001 23:56:18 +0100 (CET) Date: Sat, 24 Feb 2001 23:56:18 +0100 From: Jesper Skriver To: Jonathan Lemon Cc: net@freebsd.org Subject: Re: ICMP unreachables, take II. Message-ID: <20010224235618.C57625@skriver.dk> References: <20010222185412.E5714@prism.flugsvamp.com> <20010223034952.A6694@skriver.dk> <20010222212044.H5714@prism.flugsvamp.com> <20010223043405.B6694@skriver.dk> <20010223052012.A39613@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010223052012.A39613@skriver.dk>; from jesper@skriver.dk on Fri, Feb 23, 2001 at 05:20:13AM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Feb 23, 2001 at 05:20:13AM +0100, Jesper Skriver wrote: > On Fri, Feb 23, 2001 at 04:34:05AM +0100, Jesper Skriver wrote: > > On Thu, Feb 22, 2001 at 09:20:44PM -0600, Jonathan Lemon wrote: > > > On Fri, Feb 23, 2001 at 03:49:52AM +0100, Jesper Skriver wrote: > > > > > > > > I still think we should react to the following as a minimum > > > > - type 3 code 0 net unreachable > > > > - type 3 code 1 host unreachable > > > > > > RFC 1122, Section 4.2.3.9 says: > > > > > > o Destination Unreachable -- codes 0, 1, 5 > > > Since these Unreachable messages indicate soft error > > > conditions, TCP MUST NOT abort the connection, and it > > > SHOULD make the information available to the > > > application. > > > > > > I think that these should be transients. > > > > As discussed on IRC I suggest adding the ability (under control of a > > sysctl, disabled by default) to treat 0/1 (perhaps even 5) like 2,3,9 & > > 10. > > Forget this, as discussed on IRC, it would be better to have a code 0/1 > trigger a immediate retransmit of the SYN, this would also give us > timeouts < 10 secs ... > > If jlemon doesn't beat me to it, I'll try to look at this in the weekend > ... as a possible "take III" 23:53:42.440817 193.162.74.6.1059 > 193.162.153.164.53: 36307+ PTR? 1.23.41.195.in-addr.arpa. (42) 23:53:42.458868 193.162.153.164.53 > 193.162.74.6.1059: 36307 NXDomain 0/1/0 (92) 23:53:42.460135 193.162.74.6.1165 > 195.41.23.1.23: S 1847740321:1847740321(0) win 16384 (DF) [tos 0x10] 23:53:42.511069 195.249.6.93 > 193.162.74.6: icmp: host 195.41.23.1 unreachable (DF) 23:53:42.511161 193.162.74.6.1165 > 195.41.23.1.23: S 1847740321:1847740321(0) win 16384 (DF) [tos 0x10] 23:53:42.516799 195.249.6.93 > 193.162.74.6: icmp: host 195.41.23.1 unreachable (DF) 23:53:42.516836 193.162.74.6.1165 > 195.41.23.1.23: S 1847740321:1847740321(0) win 16384 (DF) [tos 0x10] 23:53:42.521763 195.249.6.93 > 193.162.74.6: icmp: host 195.41.23.1 unreachable (DF) 23:53:42.521796 193.162.74.6.1165 > 195.41.23.1.23: S 1847740321:1847740321(0) win 16384 (DF) [tos 0x10] 23:53:42.526749 195.249.6.93 > 193.162.74.6: icmp: host 195.41.23.1 unreachable (DF) 23:53:42.526793 193.162.74.6.1165 > 195.41.23.1.23: S 1847740321:1847740321(0) win 16384 (DF) [tos 0x10] 23:53:42.531753 195.249.6.93 > 193.162.74.6: icmp: host 195.41.23.1 unreachable (DF) jesper@tam% time telnet 195.41.23.1 Trying 195.41.23.1... telnet: connect to address 195.41.23.1: No route to host telnet: Unable to connect to remote host 0.000u 0.020s 0:00.70 2.8% 88+164k 0+0io 12pf+0w But that is probably too fast, what if we delay the retransmit by say 100ms efter recieving the host unreachable ? Diff below Index: tcp_subr.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_subr.c,v retrieving revision 1.93 diff -u -r1.93 tcp_subr.c --- tcp_subr.c 2001/02/23 21:07:06 1.93 +++ tcp_subr.c 2001/02/24 21:30:30 @@ -138,6 +138,11 @@ SYSCTL_INT(_net_inet_tcp, OID_AUTO, icmp_may_rst, CTLFLAG_RW, &icmp_may_rst, 0, "Certain ICMP unreachable messages may abort connections in SYN_SENT"); +static int icmp_trigger_retransmit = 1; +SYSCTL_INT(_net_inet_tcp, OID_AUTO, icmp_trigger_retransmit, CTLFLAG_RW, + &icmp_trigger_retransmit, 0, + "Certain ICMP unreachable messages trigger retransmit when in SYN_SENT"); + static void tcp_cleartaocache __P((void)); static void tcp_notify __P((struct inpcb *, int)); @@ -777,7 +782,25 @@ } else if (tp->t_state < TCPS_ESTABLISHED && tp->t_rxtshift > 3 && tp->t_softerror) tcp_drop(tp, error); - else + else if (tp->t_state == TCPS_SYN_SENT && icmp_trigger_retransmit) { + tp->t_softerror = error; + tp->t_rxtshift++; + tp->snd_nxt = tp->snd_una; + /* + * Note: We overload snd_recover to function also as the + * snd_last variable described in RFC 2582 + */ + tp->snd_recover = tp->snd_max; + /* + * Force a segment to be sent. + */ + tp->t_flags |= TF_ACKNOW; + /* + * If timing a segment in this window, stop the timer. + */ + tp->t_rtttime = 0; + (void) tcp_output(tp); + } else tp->t_softerror = error; #if 0 wakeup((caddr_t) &so->so_timeo); /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 24 22: 7:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id 8B17537B4EC for ; Sat, 24 Feb 2001 22:07:52 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 10389 invoked by uid 666); 25 Feb 2001 06:19:13 -0000 Received: from i080-119.nv.iinet.net.au (HELO elischer.org) (203.59.80.119) by mail.m.iinet.net.au with SMTP; 25 Feb 2001 06:19:13 -0000 Message-ID: <3A98A112.19BDA328@elischer.org> Date: Sat, 24 Feb 2001 22:07:14 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Peter.Blok@inter.NL.net Cc: 'Stefan Arentz' , freebsd-net@FreeBSD.ORG Subject: Re: netgraph pptp and alcatel adsl modems References: <000401c09ea7$11ad7000$8a02a8c0@ntpc> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Blok wrote: > -------------------------------------------------------------------------------- > Name: mxstream.tar.gz > mxstream.tar.gz Type: Unix Tape Archive (application/x-tar) > Encoding: base64 this file is empty -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message