From owner-freebsd-net Sun May 27 13: 0:29 2001
Delivered-To: freebsd-net@freebsd.org
Received: from e028121.vtacs.vt.edu (e028121.vtacs.vt.edu [63.164.28.121])
by hub.freebsd.org (Postfix) with ESMTP id 6CC1537B423
for <freebsd-net@freebsd.org>; Sun, 27 May 2001 13:00:26 -0700 (PDT)
(envelope-from gaylord@e028121.vtacs.vt.edu)
Received: by e028121.vtacs.vt.edu (Postfix, from userid 1000)
id 40864130; Sun, 27 May 2001 15:59:54 -0400 (EDT)
Date: Sun, 27 May 2001 15:59:53 -0400
From: Clark Gaylord <cgaylord@vt.edu>
To: freebsd-net@freebsd.org
Subject: [singh@pdx.edu: UDP - Reliable throughput mesaurement tool]
Message-ID: <20010527155953.B29042@e028121.vtacs.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
----- Forwarded message from Harkirat Singh <singh@pdx.edu> -----
> I want to measure UDP thruput of lossy channel, is there any tool
> which tests it? I looked at some of the tools but these do not take care
> of loss, I mean no retransmisson, just measure raw thruput of UDP (TTCP
> is one of these).
>
> I am looking for a measurement tool which should retransmit in case of
> loss and keep a track of packets, I mean make UDP reliable amd blocking
> calls.
----- End forwarded message -----
As many have pointed out, the reliability of UDP is accomplished
at the application layer. Hence, any test of this nature is going
to test the application implementation as much as the nature of
the protocols, per se.
Both ttcp and netperf have the ability to use either TCP or UDP.
The behavior of TCP is, I think well understood. OTOH, I don't
think you should discount the use of ttcp's/netperf's UDP method.
Rather consider the receiver's measurement as an upper bound of
what a particular retransmitting UDP implementation can acheive.
As has been pointed out, the UDP_RR method for netperf looks
interesting, but the documentation is scant. Use the source, Luke.
--
Clark K. Gaylord
Blacksburg, Virginia USA
cgaylord@vt.edu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Sun May 27 20:14: 2 2001
Delivered-To: freebsd-net@freebsd.org
Received: from fester.unkempt.net (cm623478-a.ftwrth1.tx.home.com [24.4.14.251])
by hub.freebsd.org (Postfix) with ESMTP id 94ACB37B424
for <freebsd-net@FreeBSD.ORG>; Sun, 27 May 2001 20:13:58 -0700 (PDT)
(envelope-from lagsalot@unkempt.net)
Received: from localhost (lagsalot@localhost)
by fester.unkempt.net (8.9.3/8.9.3) with ESMTP id WAA58877;
Sun, 27 May 2001 22:18:27 -0500 (CDT)
(envelope-from lagsalot@unkempt.net)
Date: Sun, 27 May 2001 22:18:27 -0500 (CDT)
From: Brandt <lagsalot@unkempt.net>
To: "Justin C.Walker" <justin@mac.com>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: natd, 2 NIC's, 2 Hubs, Something I'm missing?
In-Reply-To: <20010527050742.IAAH13163.femail1.sdc1.sfba.home.com@grinch>
Message-ID: <Pine.BSF.4.21.0105272210470.58860-100000@fester.unkempt.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Actually I flatened the box and reinstalled. Seems there
was a problem with the dc0 interface, it wouldn't reply
to pings (but would still ping other boxen) from the get go.
My bad for not testing both interfaces right off the bat.
I assumed since it was a brand new card, and BSD detected
it, that all was good. You would think that after working
with computers for 6 years, that I would know better than
to assume.
Card was a Linksys NC100, 10/100
Thanks for all the input.
-Brandt
On Sat, 26 May 2001, Justin C.Walker wrote:
>
> On Saturday, May 26, 2001, at 07:59 PM, Brandt wrote:
>
> > Well, I assumed the natd would be noticed in the subject line, and also
> > it is listed under the "rc.conf" section I listed below.
>
> I did indeed notice that you mentioned Natd, but without the
> config, it's hard to tell whether you are actually using it. It's
> also hard to diagnose a problem without all the info. I'm no
> expert in firewalls either, but your rules look a bit odd to me.
> They seem to work on my box, though, so I suppose they're OK.
>
> Another thing you haven't mentioned is whether you've enabled
> forwarding:
> sysctl -w net.inet.ip.fowarding=1
> (at least, that's the syntax on my 3.2-based Darwin system).
>
> Regards,
>
> Justin
>
> > As for the dc0, I forgot I had tried a 255.255.0.0 subnet, and played
> > with the broadcast just for giggles. Normally they are 255.255.0.0
> > and 192.168.1.255 respectively.
> >
> > And no its not the firewall rules, I don't think, but I'm no expert.
> > ## ipfw #########
> > 00050 divert 8668 ip from any to any via vr0
> > 00100 allow ip from any to any via lo0
> > 00200 deny ip from any to 127.0.0.0/8
> > 00300 deny ip from 127.0.0.0/8 to any
> > 65000 allow ip from any to any
> > 65535 deny ip from any to any
> >
> > ----- Original Message -----
> > From: "Justin C.Walker" <justin@mac.com>
> > To: <freebsd-net@FreeBSD.ORG>
> > Sent: Saturday, May 26, 2001 9:52 PM
> > Subject: Re: natd, 2 NIC's, 2 Hubs, Something I'm missing?
> >
>
> ---
> Justin C. Walker, Curmudgeon-At-Large *
> Institute for General Semantics |
> Director of Technology | It's not whether you win
> or lose...
> Nexsi Systems Corp. | It's whether *I* win or lose.
> 1959 Concourse Drive |
> San Jose, CA 95131 |
> *--------------------------------------*-------------------------------*
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-net" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Sun May 27 21:58:37 2001
Delivered-To: freebsd-net@freebsd.org
Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4])
by hub.freebsd.org (Postfix) with ESMTP id D86EC37B423
for <freebsd-net@freebsd.org>; Sun, 27 May 2001 21:58:31 -0700 (PDT)
(envelope-from netch@iv.nn.kiev.ua)
Received: (from uucp@localhost)
by segfault.kiev.ua (8) with UUCP id HWM50248
for freebsd-net@freebsd.org; Mon, 28 May 2001 07:58:28 +0300 (EEST)
(envelope-from netch@iv.nn.kiev.ua)
Received: (from netch@localhost)
by iv.nn.kiev.ua (8.11.3/8.11.3) id f4RJoer01532
for freebsd-net@freebsd.org; Sun, 27 May 2001 22:50:40 +0300 (EEST)
(envelope-from netch)
Date: Sun, 27 May 2001 22:50:40 +0300
From: Valentin Nechayev <netch@iv.nn.kiev.ua>
To: freebsd-net@freebsd.org
Subject: ssh protocol 2 interactive delays
Message-ID: <20010527225040.A1375@iv.nn.kiev.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-42: On
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
What is the difference between ssh protocol 1 and protocol 2 stream control?
I tried protocol 1 in openssh and protocol 2 in openssh and Ylonen's
SSH 2.3.0 via PSTN 56K line. With protocol 1 interactive delays are
reasonable. With protocol 2, in both openssh and Ylonen's ssh,
delays are unreasonable annoying. When going to localhost, all is OK.
My impression is those delays are similar to ones in case when TCP_NODELAY
was not turned on.
Openssh client is standard from -current date=2001.05.12.00.00.00
(`SSH-1.99-OpenSSH_2.9 green@FreeBSD.org 20010503'). All ssh servers
are openssh from 4.3-RC or 4.3-RELEASE.
/netch
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Mon May 28 1:59: 8 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 1959F37B422
for <freebsd-net@FreeBSD.ORG>; Mon, 28 May 2001 01:59:05 -0700 (PDT)
(envelope-from jinmei@isl.rdc.toshiba.co.jp)
Received: from localhost ([2001:218:1800:c051:b48d:7d30:4490:4cdb])
by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id RAA03485;
Mon, 28 May 2001 17:58:47 +0900 (JST)
Date: Mon, 28 May 2001 17:28:39 +0900
Message-ID: <y7vae3xnah4.wl@condor2.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: raviprasad20@netscape.net
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: rtmsg_input
In-Reply-To: <4BBB03E1.52C6A9EE.9513E96F@netscape.net>
References: <4BBB03E1.52C6A9EE.9513E96F@netscape.net>
User-Agent: Wanderlust/2.5.8 (Smooth) 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 980905(IM100)
Lines: 20
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
>>>>> On Thu, 24 May 2001 12:17:39 -0400,
>>>>> raviprasad20@netscape.net said:
> This is regarding the rtmsg_input() in the module rtadvd.c of the rtadvd daemon.
> I think the above function will receive message in the routing socket when a route is added or deleted. My doubt is whether this message will be generated only for addresses other than link local & multicast or it will be generated for all the addresses.
It depends on the kernel implementation, but, in any case, all routes
that users (applications) manually install to the kernel will be
announced through the routing socket, even if the routes are
link-local or multicast ones.
And, in my understanding, on FreeBSD 4.3 (and prior versions), other
routes will basically not be announced. In particular, routes
automatically installed via RA messages will not be announce through
the routing socket.
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 Mon May 28 4:28:57 2001
Delivered-To: freebsd-net@freebsd.org
Received: from shadow.otel.net (JuDiCaToR.OTEL.net [212.36.9.113])
by hub.freebsd.org (Postfix) with ESMTP id BA39437B42C
for <freebsd-net@freebsd.org>; Mon, 28 May 2001 04:28:53 -0700 (PDT)
(envelope-from tbyte@tbyte.org)
Received: from localhost (localhost [127.0.0.1])
by shadow.otel.net (8.11.3/8.11.1) with ESMTP id f4SBSp021340
for <freebsd-net@freebsd.org>; Mon, 28 May 2001 14:28:52 +0300 (EEST)
(envelope-from tbyte@tbyte.org)
Date: Mon, 28 May 2001 14:28:51 +0300 (EEST)
From: Iasen Kostoff <tbyte@tbyte.org>
X-Sender: tbyte@shadow.otel.net
To: freebsd-net@freebsd.org
Subject: routing socket and routes assignment
Message-ID: <Pine.BSF.4.21.0105281342480.21037-100000@shadow.otel.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hi,
I have a problem in assigning a default gateway from network that
my computer's interfaces don't have IP from. And even when I add a route
to this network throw any of the interfaces it still returns ENETUNREACH
message. Then I thought that I can fix that with -ifp modifer of route
command but - no luck. After many tryes I found a way to set this route
but I don't think it's the right way it should be done.
Ok, now you have an interface with IP 2.2.2.2 but your gateway is
1.1.1.1 . First you should add a default route from your interface's
network or even his own IP 2.2.2.2 , then you should change this route
gateway to point to real gateway 1.1.1.1 and you should have a route to
this host or his network 1.1.1.1/??. Here is same but displayed with route
command:
1. route add default 2.2.2.2
2. route add 1.1.1.1 -iface xl0
arp -s 1.1.1.1 lladdr_of_1.1.1.1
or
route add -net 1.1.1.1/24 -iface xl0
3. route change default 1.1.1.1
4. optionaly : route change default -ifp xl0
That did it but why can't I do it with this command:
route add default 1.1.1.1 -ifp xl0
I look in sys/net/rtsock.c and sys/net/route.c and saw that
rtrequest() can't add a route to host throw interface but
route_output() function in rtsock.c could change it that way ?!?
I've changed these tow functions and now "route add default host -ifp
ifname" works but you still need a route to the gateway.
I think that if there is set ifp or ifa (end this is set if there
is a route at all :)) the kernel should try to arpresolve gateway's
lladdr throw that interface if it can't find a route to it.
Regards.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Mon May 28 6:35: 0 2001
Delivered-To: freebsd-net@freebsd.org
Received: from spinoza.ime.usp.br (spinoza.ime.usp.br [143.107.45.30])
by hub.freebsd.org (Postfix) with SMTP id 964B437B509
for <freebsd-net@freebsd.org>; Mon, 28 May 2001 06:34:44 -0700 (PDT)
(envelope-from galmeida@linux.ime.usp.br)
Received: (qmail 18877 invoked from network); 28 May 2001 13:34:38 -0000
Received: from unknown (HELO vila.linux.ime.usp.br) (qmailr@192.168.240.9)
by 192.168.240.1 with SMTP; 28 May 2001 13:34:38 -0000
Received: (qmail 8716 invoked from network); 28 May 2001 13:34:38 -0000
Received: from epicurus.linux.ime.usp.br (galmeida@192.168.240.44)
by vila.linux.ime.usp.br with QMQP; 28 May 2001 13:34:38 -0000
Date: 28 May 2001 13:34:38 -0000
Message-ID: <20010528133438.29542.qmail@epicurus.linux.ime.usp.br>
From: galmeida@linux.ime.usp.br
To: freebsd-net@freebsd.org
Subject: IPFilter new license
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
I've recently downloaded a current ipfilter and noticed a "small" license change
mathilda$ cat LICENCE
/*
* Copyright (C) 1993-2001 by Darren Reed.
*
* The author accepts no responsibility for the use of this software and
* provides it on an ``as is'' basis without express or implied warranty.
*
* Redistribution is not permitted.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
*
* I hate legalese, don't you ?
*/
Did I missed something, or ipfilter must be removed from FreeBSD's source base?
PS.: hope I've missed something.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Mon May 28 8:21:54 2001
Delivered-To: freebsd-net@freebsd.org
Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1])
by hub.freebsd.org (Postfix) with ESMTP id 7653237B422
for <freebsd-net@FreeBSD.ORG>; Mon, 28 May 2001 08:21:52 -0700 (PDT)
(envelope-from doegi@kawoserv.kawo2.rwth-aachen.de)
Received: (from doegi@localhost) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.6.9) id RAA17203; Mon, 28 May 2001 17:21:49 +0200
Date: Mon, 28 May 2001 17:21:49 +0200
From: Alexander Langer <alex@big.endian.de>
To: galmeida@linux.ime.usp.br
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: IPFilter new license
Message-ID: <20010528172149.A17080@kawoserv.kawo2.rwth-aachen.de>
References: <20010528133438.29542.qmail@epicurus.linux.ime.usp.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3us
In-Reply-To: <20010528133438.29542.qmail@epicurus.linux.ime.usp.br>
X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F
X-PGP-at: finger alex@big.endian.de
X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung.
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Thus spake galmeida@linux.ime.usp.br (galmeida@linux.ime.usp.br):
>
> mathilda$ cat LICENCE
...
> * Redistribution is not permitted.
...
> Did I missed something, or ipfilter must be removed from FreeBSD's source base?
> PS.: hope I've missed something.
Hmm, Darren Reed also maintains ipfilter in the FreeBSD tree, so I
think I know what he's doing, if he imports a new version.
Alex
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Mon May 28 17:58: 1 2001
Delivered-To: freebsd-net@freebsd.org
Received: from mail.viasoft.com.cn (unknown [61.153.1.177])
by hub.freebsd.org (Postfix) with ESMTP id 8376D37B423
for <freebsd-net@FreeBSD.ORG>; Mon, 28 May 2001 17:57:58 -0700 (PDT)
(envelope-from bsddiy@163.net)
Received: from William ([192.168.1.98])
by mail.viasoft.com.cn (8.9.3/8.9.3) with ESMTP id IAA18830;
Tue, 29 May 2001 08:57:42 +0800
Date: Tue, 29 May 2001 09:06:11 +0800
From: David Xu <bsddiy@163.net>
X-Mailer: The Bat! (v1.48f) Personal
Reply-To: bsddiy@163.net
Organization: Viasoft
X-Priority: 3 (Normal)
Message-ID: <175774573.20010529090611@163.net>
To: Alexander Langer <alex@big.endian.de>
Cc: galmeida@linux.ime.usp.br, freebsd-net@FreeBSD.ORG
Subject: Re[2]: IPFilter new license
In-reply-To: <20010528172149.A17080@kawoserv.kawo2.rwth-aachen.de>
References: <20010528133438.29542.qmail@epicurus.linux.ime.usp.br>
<20010528172149.A17080@kawoserv.kawo2.rwth-aachen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hello Alexander,
Monday, May 28, 2001, 11:21:49 PM, you wrote:
AL> Thus spake galmeida@linux.ime.usp.br (galmeida@linux.ime.usp.br):
>>
>> mathilda$ cat LICENCE
AL> ..
>> * Redistribution is not permitted.
AL> ..
>> Did I missed something, or ipfilter must be removed from FreeBSD's source base?
>> PS.: hope I've missed something.
AL> Hmm, Darren Reed also maintains ipfilter in the FreeBSD tree, so I
AL> think I know what he's doing, if he imports a new version.
AL> Alex
Hmm, It seems FreeBSD allow a non-compatible license mixed in system.
it will possibly have trouble in future.
--
David Xu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Mon May 28 19:23: 9 2001
Delivered-To: freebsd-net@freebsd.org
Received: from molly.straylight.com (molly.straylight.com [204.69.232.69])
by hub.freebsd.org (Postfix) with ESMTP id A08CE37B423
for <freebsd-net@freebsd.org>; Mon, 28 May 2001 19:23:06 -0700 (PDT)
(envelope-from jonathan@graehl.org)
Received: from case (root@localhost [127.0.0.1])
by molly.straylight.com (8.11.0/8.10.0) with ESMTP id f4T2Mxc17538
for <freebsd-net@freebsd.org>; Mon, 28 May 2001 19:22:59 -0700
From: "Jonathan Graehl" <jonathan@graehl.org>
To: <freebsd-net@freebsd.org>
Subject: Ipfilter nat vs ipfw divert + natd performance
Date: Mon, 28 May 2001 19:24:05 -0700
Message-ID: <000001c0e7e6$6fb1ee00$6dfeac40@straylight.com>
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, Build 10.0.2605
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Importance: Normal
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
I've set up an old Pentium to NAT my little brother's cablemodem using
ipfw/natd. Would I see much better performance from ipfilter? (I
assume that in-kernel NAT would be faster and have more consistent
latency than a user process which might not be scheduled for a while?)
The family does play a game of Tribes now and then, so unpredictable
10ms delays would not be fun for them.
--
Jonathan Graehl
http://jonathan.graehl.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Tue May 29 0:58:57 2001
Delivered-To: freebsd-net@freebsd.org
Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1])
by hub.freebsd.org (Postfix) with ESMTP id 1110837B422
for <freebsd-net@FreeBSD.ORG>; Tue, 29 May 2001 00:58:55 -0700 (PDT)
(envelope-from alex@big.endian.de)
Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.6.9) with ESMTP id JAA21696; Tue, 29 May 2001 09:58:40 +0200
Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001)
id 1194C14BB0; Tue, 29 May 2001 09:58:25 +0200 (CEST)
Date: Tue, 29 May 2001 09:58:24 +0200
From: Alexander Langer <alex@big.endian.de>
To: David Xu <bsddiy@163.net>
Cc: galmeida@linux.ime.usp.br, freebsd-net@FreeBSD.ORG
Subject: Re: Re[2]: IPFilter new license
Message-ID: <20010529095824.F849@zerogravity.kawo2.rwth-aachen.d>
References: <20010528133438.29542.qmail@epicurus.linux.ime.usp.br> <20010528172149.A17080@kawoserv.kawo2.rwth-aachen.de> <175774573.20010529090611@163.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <175774573.20010529090611@163.net>; from bsddiy@163.net on Tue, May 29, 2001 at 09:06:11AM +0800
X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F
X-PGP-at: finger alex@big.endian.de
X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung.
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Thus spake David Xu (bsddiy@163.net):
> Hmm, It seems FreeBSD allow a non-compatible license mixed in system.
> it will possibly have trouble in future.
BTW, the issue has been raised on developers@ and is currently
discussed there.
Let's see what it brings.
Alex
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Tue May 29 2: 8:31 2001
Delivered-To: freebsd-net@freebsd.org
Received: from mail.chem.msu.ru (mail.chem.msu.ru [195.208.208.19])
by hub.freebsd.org (Postfix) with ESMTP id AD56B37B424
for <freebsd-net@FreeBSD.ORG>; Tue, 29 May 2001 02:08:27 -0700 (PDT)
(envelope-from yar@comp.chem.msu.su)
Received: from comp.chem.msu.su ([158.250.32.97]) by mail.chem.msu.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
id LR567R5H; Tue, 29 May 2001 12:46:10 +0400
Received: (from yar@localhost)
by comp.chem.msu.su (8.11.1/8.11.1) id f4T8n5l97267;
Tue, 29 May 2001 12:49:05 +0400 (MSD)
(envelope-from yar)
Date: Tue, 29 May 2001 12:49:04 +0400
From: Yar Tikhiy <yar@FreeBSD.ORG>
To: Jonathan Graehl <jonathan@graehl.org>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: Ipfilter nat vs ipfw divert + natd performance
Message-ID: <20010529124904.A94542@comp.chem.msu.su>
References: <000001c0e7e6$6fb1ee00$6dfeac40@straylight.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <000001c0e7e6$6fb1ee00$6dfeac40@straylight.com>; from jonathan@graehl.org on Mon, May 28, 2001 at 07:24:05PM -0700
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hi Jonathan,
On Mon, May 28, 2001 at 07:24:05PM -0700, Jonathan Graehl wrote:
> I've set up an old Pentium to NAT my little brother's cablemodem using
> ipfw/natd. Would I see much better performance from ipfilter? (I
> assume that in-kernel NAT would be faster and have more consistent
> latency than a user process which might not be scheduled for a while?)
> The family does play a game of Tribes now and then, so unpredictable
> 10ms delays would not be fun for them.
I'd suggest you measure the performance parameters (packet delay,
CPU time spent in interrupts etc) for the two cases, and send a small
report here ;-)
--
Yar
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Tue May 29 5:39:14 2001
Delivered-To: freebsd-net@freebsd.org
Received: from web5305.mail.yahoo.com (web5305.mail.yahoo.com [216.115.106.114])
by hub.freebsd.org (Postfix) with SMTP id 93E5537B423
for <freebsd-net@freebsd.org>; Tue, 29 May 2001 05:39:09 -0700 (PDT)
(envelope-from vishubp@yahoo.com)
Message-ID: <20010529123909.12618.qmail@web5305.mail.yahoo.com>
Received: from [203.200.20.3] by web5305.mail.yahoo.com; Tue, 29 May 2001 13:39:09 BST
Date: Tue, 29 May 2001 13:39:09 +0100 (BST)
From: =?iso-8859-1?q?vishwanath=20pargaonkar?= <vishubp@yahoo.com>
Subject: Router advertisement
To: freebsd-net@freebsd.org
Cc: freebsd-hackers@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hi,
i have freebsd 4.2 stable.
my doubt is how is router advertisement called?
ie i know that router advertisement is user land
program.so when ever router solicitation is received
we receive it and update the cache by calling
nd6_cache_lladdr.but how exactly RA invoked it being
user land program?
how RA responce is evoked to RS?
TIA
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Tue May 29 11: 3:46 2001
Delivered-To: freebsd-net@freebsd.org
Received: from zahn.mit.oasch.org (isohypse.org [62.116.3.50])
by hub.freebsd.org (Postfix) with SMTP id E1FC137B422
for <freebsd-net@freebsd.org>; Tue, 29 May 2001 11:03:40 -0700 (PDT)
(envelope-from chris@zahn.mit.oasch.org)
Received: (qmail 6478 invoked by uid 1003); 28 May 2001 17:02:06 -0000
Date: Mon, 28 May 2001 19:02:06 +0200
From: christian fernau <chris@fernau.ch>
To: freebsd-net@freebsd.org
Subject: problem with pcn NIC
Message-ID: <20010528190206.A19400@zahn.mit>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hi!
i am experiencing the following problem with my AMD PCnet/PCI nic:
if i connect to a 10mbit segment -> doesn't work * (explained below)
if i connect to the same 10mbit segment via a 10/100mbit dual speed hub
-> works perfectly (100hdx)
if i set the nic manually to operate at 10mbit the link goes down for a
moment and comes up again with 100mbit
if i do the same running win2k i have network connection at 10 and 100mbit
using win2k is NOT a solution :)
* what i meant with "doesn't work" is:
using tcpdump i can see my outgoing eth-frames (don't think that prooves
that they make it to the wire)
i can see broadcasts from other machines
i never get a response from the others
i'm using 4.3-RELEASE with stable kernel cvsuped on 27.5
thanks a lot for your help!
chris
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Tue May 29 13: 2:51 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 615E337B43C
for <freebsd-net@freebsd.org>; Tue, 29 May 2001 13:02:47 -0700 (PDT)
(envelope-from jesper@skriver.dk)
Received: by freesbee.wheel.dk (Postfix, from userid 1001)
id 9A2EE5D3B; Tue, 29 May 2001 22:04:38 +0200 (CEST)
Date: Tue, 29 May 2001 22:04:38 +0200
From: Jesper Skriver <jesper@skriver.dk>
To: Iasen Kostoff <tbyte@tbyte.org>
Cc: freebsd-net@freebsd.org
Subject: Re: routing socket and routes assignment
Message-ID: <20010529220438.B49875@skriver.dk>
References: <Pine.BSF.4.21.0105281342480.21037-100000@shadow.otel.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.BSF.4.21.0105281342480.21037-100000@shadow.otel.net>; from tbyte@tbyte.org on Mon, May 28, 2001 at 02:28:51PM +0300
X-PGP-Fingerprint: 6B88 9CE8 66E9 E631 C9C5 5EB4 22AB F0EC F956 1C31
X-PGP-Public-Key: http://freesbee.wheel.dk/~jesper/gpgkey.pub
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
On Mon, May 28, 2001 at 02:28:51PM +0300, Iasen Kostoff wrote:
> Hi,
> I have a problem in assigning a default gateway from network that
> my computer's interfaces don't have IP from.
All routes should have a next-hop on a directly connected
interface.
/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 Wed May 30 1:23:23 2001
Delivered-To: freebsd-net@freebsd.org
Received: from shadow.otel.net (JuDiCaToR.OTEL.net [212.36.9.113])
by hub.freebsd.org (Postfix) with ESMTP id 307CA37B42C
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 01:23:19 -0700 (PDT)
(envelope-from tbyte@tbyte.org)
Received: from localhost (localhost [127.0.0.1])
by shadow.otel.net (8.11.3/8.11.1) with ESMTP id f4U8N7033035;
Wed, 30 May 2001 11:23:09 +0300 (EEST)
(envelope-from tbyte@tbyte.org)
Date: Wed, 30 May 2001 11:23:07 +0300 (EEST)
From: Iasen Kostoff <tbyte@tbyte.org>
X-Sender: tbyte@shadow.otel.net
To: Jesper Skriver <jesper@skriver.dk>
Cc: freebsd-net@freebsd.org
Subject: Re: routing socket and routes assignment
In-Reply-To: <20010529220438.B49875@skriver.dk>
Message-ID: <Pine.BSF.4.21.0105301102510.32941-100000@shadow.otel.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
On Tue, 29 May 2001, Jesper Skriver wrote:
> On Mon, May 28, 2001 at 02:28:51PM +0300, Iasen Kostoff wrote:
> > Hi,
> > I have a problem in assigning a default gateway from network that
> > my computer's interfaces don't have IP from.
>
> All routes should have a next-hop on a directly connected
> interface.
>
> /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.
>
The gateway is directly connected and I think this is obvious and should
not even be discused. The IP address of the gateway is not from
network that the computer is. But there is a route throu interface to it
and the kernel still refuses to use that gateway with error ENETUNREACH.
And I wrote a patch which allows kernel to set that route. It's kinda
unfinished still but it works. Even now (without the patch) you can set
this route but it's not straight forward and I don't think that's the
right way to be done.
Regards.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 2:38:15 2001
Delivered-To: freebsd-net@freebsd.org
Received: from vbook.express.ru (vbook.express.ru [212.24.37.106])
by hub.freebsd.org (Postfix) with ESMTP id 4BBD537B423
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 02:38:12 -0700 (PDT)
(envelope-from vova@vbook.express.ru)
Received: (from vova@localhost)
by vbook.express.ru (8.9.3/8.9.3) id NAA19135;
Wed, 30 May 2001 13:38:17 +0400 (MSD)
(envelope-from vova)
From: "Vladimir B. Grebenschikov" <vova@express.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15124.49032.621510.427536@vbook.express.ru>
Date: Wed, 30 May 2001 13:38:16 +0400 (MSD)
To: freebsd-net@freebsd.org
Subject: Netgraph node to support 802.1q VLANs ?
X-Mailer: VM 6.72 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hi all
Does anybody manage to make netgraph node to do VLAN multiplexing ?
Yes, I know, freebsd kernel have now supporting for VLAN's
(pseudo-device vlan), but it have number of disadvantages:
- fixed number of vlan interfaces
- vlanX pseudo-interfaces don't support netgraph'ing, so I can't
bridge two VLANs using ng_bridge
- fixed vlanX interfaces numbering, so if I want use VLANs from 320
to 340, so I can use interfaces vlan0 - vlan20, but if I use VLANs
with ID's 1-20 it will be confusing. If I want interface names
vlan320-vlan340, I need to specify in kernel 340 vlan interfaces.
But contrary in netgraph scheme I can name interface connected to
802dotQ node hook vlan320 as, for example, vlan340 without any problem.
--
TSB Russian Express, Moscow
Vladimir B. Grebenschikov, vova@express.ru
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 3:32: 1 2001
Delivered-To: freebsd-net@freebsd.org
Received: from tinuviel.compendium.net.ar (usat2-00222.usateleport.com [208.248.183.222])
by hub.freebsd.org (Postfix) with ESMTP id B772837B422
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 03:31:54 -0700 (PDT)
(envelope-from horape@tinuviel.compendium.net.ar)
Received: by tinuviel.compendium.net.ar (Postfix, from userid 1000)
id 52AC0196764; Wed, 30 May 2001 07:31:50 -0300 (ART)
Date: Wed, 30 May 2001 07:31:50 -0300
From: horape@tinuviel.compendium.net.ar
To: freebsd-net@freebsd.org
Subject: why cannot bind to someipaddress:port when something else has *:port bound?
Message-ID: <20010530073150.A15247@tinuviel.compendium.net.ar>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Mutt/1.3.18i
x-attribution: HoraPe
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
=A1Hola!
The following program binds *:1000 to a socket, and then tries to bind
200.47.36.254:1000 to another socket, the error i gets is "Address
already in use". Why?
I am not asking for a "you're not allowed to do that", I know. I don't
ask for a "why are you trying to do that?", I amn't trying. But I need
to know why that's not permited. I know vaguely but i need a more sound
explanation. A pointer to a mailing list/usenet archive where the subject
was discussed in the past would be great.
Just another time, i am asking for the theory about why that shouldn't
be allowed. Not the fact that it's not allowed.
Lots of thanks,
HoraPe
The code is:
main()
{
l4();
l4esp();
select(0,NULL,NULL,NULL,NULL);
}
int l4()
{
int listenfd;
struct sockaddr_in cliaddr, servaddr;
socklen_t clilen;
listenfd =3D socket(AF_INET, SOCK_STREAM, 0);
if(listenfd < 0)
die();
memset(&servaddr, 0, sizeof(servaddr));
servaddr.sin_family =3D AF_INET;
servaddr.sin_addr.s_addr =3D htonl(INADDR_ANY);
servaddr.sin_port =3D htons(1000);
if(bind(listenfd, (struct sockaddr*) &servaddr, sizeof(servaddr)) !=3D 0)
die();
if(listen(listenfd, 10) !=3D 0)
die();
}
int l4esp()
{
int listenfd;
struct sockaddr_in cliaddr, servaddr;
socklen_t clilen;
listenfd =3D socket(AF_INET, SOCK_STREAM, 0);
if(listenfd < 0)
die();
memset(&servaddr, 0, sizeof(servaddr));
servaddr.sin_family =3D AF_INET;
servaddr.sin_addr.s_addr =3D htonl(INADDR_ANY);
servaddr.sin_port =3D htons(1000);
if(bind(listenfd, (struct sockaddr*) &servaddr, sizeof(servaddr)) !=3D 0)
die();
if(listen(listenfd, 10) !=3D 0)
die();
}
int l4esp()
{
int listenfd;
struct sockaddr_in cliaddr, servaddr;
socklen_t clilen;
listenfd =3D socket(AF_INET, SOCK_STREAM, 0);
if(listenfd < 0)
die();
memset(&servaddr, 0, sizeof(servaddr));
servaddr.sin_family =3D AF_INET;
servaddr.sin_addr.s_addr =3D htonl(0xc82f24fe);
servaddr.sin_port =3D htons(1000);
if(bind(listenfd, (struct sockaddr*) &servaddr, sizeof(servaddr)) !=3D 0)
die();
if(listen(listenfd, 10) !=3D 0)
die();
}
die()
{
printf("die %s\n", strerror(errno));
}
HoraPe
---
Horacio J. Pe=F1a
horape@compendium.com.ar
horape@uninet.edu
bofh@puntoar.net.ar
horape@hcdn.gov.ar
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 5: 3:27 2001
Delivered-To: freebsd-net@freebsd.org
Received: from alijku04.edvz.uni-linz.ac.at (alijku04.edvz.uni-linz.ac.at [140.78.182.1])
by hub.freebsd.org (Postfix) with ESMTP id B944637B422
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 05:03:23 -0700 (PDT)
(envelope-from ferdl@atommuell.oeh.uni-linz.ac.at)
Received: from sondermuell.oeh.uni-linz.ac.at (IDENT:root@sondermuell.oeh.uni-linz.ac.at [140.78.214.105])
by alijku04.edvz.uni-linz.ac.at (8.9.3/8.9.3) with ESMTP id OAA05924
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 14:03:02 +0200
Received: from atommuell.oeh.uni-linz.ac.at (root@atommuell.oeh.uni-linz.ac.at [140.78.214.101])
by sondermuell.oeh.uni-linz.ac.at (8.9.3/8.9.3) with ESMTP id OAA02890
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 14:03:16 +0200
Received: from localhost (ferdl@localhost)
by atommuell.oeh.uni-linz.ac.at (8.9.3/8.9.3) with ESMTP id OAA59023
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 14:03:33 +0200 (CEST)
(envelope-from ferdl@atommuell.oeh.uni-linz.ac.at)
Date: Wed, 30 May 2001 14:03:32 +0200 (CEST)
From: Ferdinand Goldmann <ferdl@atommuell.oeh.uni-linz.ac.at>
To: <freebsd-net@freebsd.org>
Subject: Intel Etherexpress PILA
Message-ID: <Pine.BSF.4.31.0105301402280.50343-100000@atommuell.oeh.uni-linz.ac.at>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hello!
Can anyone explain to me what that PILA stands for, and if this card is
compatible with the Intel Etherexpress PRO and thus allow VLAN tagging?
kind regards,
ferdinand
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 6:42: 4 2001
Delivered-To: freebsd-net@freebsd.org
Received: from measurement-factory.com (measurement-factory.com [206.168.0.5])
by hub.freebsd.org (Postfix) with ESMTP id ED0AF37B424
for <freebsd-net@FreeBSD.ORG>; Wed, 30 May 2001 06:42:01 -0700 (PDT)
(envelope-from rousskov@measurement-factory.com)
Received: (from rousskov@localhost)
by measurement-factory.com (8.9.3/8.9.3) id HAA68905;
Wed, 30 May 2001 07:41:42 -0600 (MDT)
(envelope-from rousskov)
Date: Wed, 30 May 2001 07:41:42 -0600 (MDT)
From: Alex Rousskov <rousskov@measurement-factory.com>
To: horape@tinuviel.compendium.net.ar
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: why cannot bind to someipaddress:port when something else has
*:port bound?
In-Reply-To: <20010530073150.A15247@tinuviel.compendium.net.ar>
Message-ID: <Pine.BSF.4.10.10105300737040.68439-100000@measurement-factory.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
On Wed, 30 May 2001 horape@tinuviel.compendium.net.ar wrote:
> The following program binds *:1000 to a socket, and then tries to
> bind 200.47.36.254:1000 to another socket, the error i gets is
> "Address already in use". Why?
*:1000 includes 200.47.36.254:1000 by definition of bind(2). Binding
two sockets to one address (200.47.36.254:1000 in your case) cannot be
allowed because it is unclear which of the two sockets should recieve
packets destined to 200.47.36.254:1000. There may be other reasons.
Alex.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 6:52:34 2001
Delivered-To: freebsd-net@freebsd.org
Received: from web13308.mail.yahoo.com (web13308.mail.yahoo.com [216.136.175.44])
by hub.freebsd.org (Postfix) with SMTP id 67FE937B43C
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 06:52:31 -0700 (PDT)
(envelope-from nuzrin@yahoo.com)
Message-ID: <20010530135231.22042.qmail@web13308.mail.yahoo.com>
Received: from [203.106.66.32] by web13308.mail.yahoo.com; Wed, 30 May 2001 06:52:31 PDT
Date: Wed, 30 May 2001 06:52:31 -0700 (PDT)
From: nuzrin <nuzrin@yahoo.com>
Reply-To: p9711422@mmu.edu.my
Subject: mpd-netgraph as pptp server
To: freebsd-net@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
hi,
i just want to know that if in mpd.conf, i have this entry:
pptp0:
new -i ng0 pptp0 pptp0
set iface route default
set iface disable on-demand
set iface enable proxy-arp
set iface idle 0
set bundle disable multilink
set link yes acfcomp protocomp
set link enable pap chap
set link enable chap
set link keep-alive 10 60
set ipcp yes vjcomp
set ipcp ranges 192.168.254.0/24 10.8.1.0/24
set ipcp dns xxx.xxx.xxx.xx
set ipcp nbns 0.0.0.0
set iface up-script /usr/local/etc/mpd/if-up.sh
set iface down-script /usr/local/etc/mpd/if-down.sh
set bundle enable compression
set ccp yes mppc
set ccp yes mpp-e40
set ccp yes mpp-e128
set ccp yes mpp-stateless
and in mpd.link i have this entry:
pptp0:
set link type pptp
set pptp self xxx.xxx.xxx.xxx
set pptp enable incoming
set pptp disable originate
and if i want to allow 100 simultaneous client connecting to my pptp server,
do i have to repeat the entry above 100 times, increasing pptp0 and ng0
values respectively? this would result in a very big mpd.conf and mpd.links
file.
is there any other simple way that will keep the mpd.conf and mpd.links files
short, simple and manageable?
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 8:33:59 2001
Delivered-To: freebsd-net@freebsd.org
Received: from tp.databus.com (p101-46.acedsl.com [160.79.101.46])
by hub.freebsd.org (Postfix) with ESMTP id CC63F37B42C
for <freebsd-net@FreeBSD.ORG>; Wed, 30 May 2001 08:33:51 -0700 (PDT)
(envelope-from barney@tp.databus.com)
Received: (from barney@localhost)
by tp.databus.com (8.11.3/8.11.3) id f4UFXIS53794;
Wed, 30 May 2001 11:33:18 -0400 (EDT)
(envelope-from barney)
Date: Wed, 30 May 2001 11:33:18 -0400
From: Barney Wolff <barney@databus.com>
To: Alex Rousskov <rousskov@measurement-factory.com>
Cc: horape@tinuviel.compendium.net.ar, freebsd-net@FreeBSD.ORG
Subject: Re: why cannot bind to someipaddress:port when something else has *:port bound?
Message-ID: <20010530113318.A53768@tp.databus.com>
References: <20010530073150.A15247@tinuviel.compendium.net.ar> <Pine.BSF.4.10.10105300737040.68439-100000@measurement-factory.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.BSF.4.10.10105300737040.68439-100000@measurement-factory.com>; from rousskov@measurement-factory.com on Wed, May 30, 2001 at 07:41:42AM -0600
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
See SO_REUSEADDR.
Barney Wolff
On Wed, May 30, 2001 at 07:41:42AM -0600, Alex Rousskov wrote:
> On Wed, 30 May 2001 horape@tinuviel.compendium.net.ar wrote:
>
> > The following program binds *:1000 to a socket, and then tries to
> > bind 200.47.36.254:1000 to another socket, the error i gets is
> > "Address already in use". Why?
>
> *:1000 includes 200.47.36.254:1000 by definition of bind(2). Binding
> two sockets to one address (200.47.36.254:1000 in your case) cannot be
> allowed because it is unclear which of the two sockets should recieve
> packets destined to 200.47.36.254:1000. There may be other reasons.
>
> Alex.
>
>
>
> 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 May 30 9:13:31 2001
Delivered-To: freebsd-net@freebsd.org
Received: from web5301.mail.yahoo.com (web5301.mail.yahoo.com [216.115.106.110])
by hub.freebsd.org (Postfix) with SMTP id 25B9437B423
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 09:13:28 -0700 (PDT)
(envelope-from vishubp@yahoo.com)
Message-ID: <20010530161327.9442.qmail@web5301.mail.yahoo.com>
Received: from [203.200.20.3] by web5301.mail.yahoo.com; Wed, 30 May 2001 17:13:27 BST
Date: Wed, 30 May 2001 17:13:27 +0100 (BST)
From: =?iso-8859-1?q?vishwanath=20pargaonkar?= <vishubp@yahoo.com>
Subject: TIP command
To: freebsd-net@freebsd.org
Cc: freebsd-hackers@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hi,
tell me how can i connect to remote system by using
tip command.
i have connected two machines by serial line.
i gave tip cuaa0c and it said connected.but how can i
make it to ask for user name.
what shd i enter in /etc/remote.shd i enter remote
system name?
pls tell me details abt connecting to remote system.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 11: 9: 5 2001
Delivered-To: freebsd-net@freebsd.org
Received: from tinuviel.compendium.net.ar (usat2-00222.usateleport.com [208.248.183.222])
by hub.freebsd.org (Postfix) with ESMTP id 0484637B423
for <freebsd-net@FreeBSD.ORG>; Wed, 30 May 2001 11:09:02 -0700 (PDT)
(envelope-from horape@tinuviel.compendium.net.ar)
Received: by tinuviel.compendium.net.ar (Postfix, from userid 1000)
id A93A0196760; Wed, 30 May 2001 15:08:55 -0300 (ART)
Date: Wed, 30 May 2001 15:08:55 -0300
From: horape@tinuviel.compendium.net.ar
To: Barney Wolff <barney@databus.com>
Cc: Alex Rousskov <rousskov@measurement-factory.com>,
freebsd-net@FreeBSD.ORG
Subject: Re: why cannot bind to someipaddress:port when something else has *:port bound?
Message-ID: <20010530150855.A9994@tinuviel.compendium.net.ar>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20010530113318.A53768@tp.databus.com>
User-Agent: Mutt/1.3.18i
x-attribution: HoraPe
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
=A1Hola!
> See SO_REUSEADDR.
Seen that. Don't believe it has something to do with that. Isn't it supposed
to allow binding on a port where there is some other socket using that sock=
et
in TIME_WAIT ?
> Barney Wolff
HoraPe
---
Horacio J. Pe=F1a
horape@compendium.com.ar
horape@uninet.edu
bofh@puntoar.net.ar
horape@hcdn.gov.ar
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 11:48:52 2001
Delivered-To: freebsd-net@freebsd.org
Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209])
by hub.freebsd.org (Postfix) with SMTP id A973037B42C
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 11:48:44 -0700 (PDT)
(envelope-from karsten@rohrbach.de)
Received: (qmail 39304 invoked by uid 1000); 30 May 2001 18:49:05 -0000
Date: Wed, 30 May 2001 20:49:05 +0200
From: "Karsten W. Rohrbach" <karsten@rohrbach.de>
To: vishwanath pargaonkar <vishubp@yahoo.com>
Cc: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org
Subject: Re: TIP command
Message-ID: <20010530204905.F29853@mail.webmonster.de>
Mail-Followup-To: "Karsten W. Rohrbach" <karsten@rohrbach.de>,
vishwanath pargaonkar <vishubp@yahoo.com>, freebsd-net@freebsd.org,
freebsd-hackers@freebsd.org
References: <20010530161327.9442.qmail@web5301.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="ZY5CS28jBCfb727c"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010530161327.9442.qmail@web5301.mail.yahoo.com>; from vishubp@yahoo.com on Wed, May 30, 2001 at 05:13:27PM +0100
X-Arbitrary-Number-Of-The-Day: 42
X-URL: http://www.webmonster.de/
X-Disclaimer: My opinions do not necessarily represent those of my employer
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
--ZY5CS28jBCfb727c
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
vishwanath pargaonkar(vishubp@yahoo.com)@2001.05.30 17:13:27 +0000:
> Hi,
> tell me how can i connect to remote system by using
> tip command.
> i have connected two machines by serial line.
> i gave tip cuaa0c and it said connected.but how can i
> make it to ask for user name.
> what shd i enter in /etc/remote.shd i enter remote
> system name?=20
> pls tell me details abt connecting to remote system.
you probably want 2 things:
1) a serial line handling utility for the initiating side.
cd /usr/ports/comms/ecu && make install clean
2) a getty sitting on the other side to let you log in
man ttys
man getty
vi /etc/ttys
kill -1 1
have fun
/k
--=20
> Sex is the poor man's opera. --G. B. Shaw
KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie
http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.n=
et/
karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- catch@spam.de
GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 B=
F46
--ZY5CS28jBCfb727c
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD4DBQE7FUChM0BPTilkv0YRAjXeAJwI1zrSPvD3Ptjm+oxMGX0SaSf3KQCY1RdS
dm0tJdO7NuQN4fY7luw4oA==
=ACpo
-----END PGP SIGNATURE-----
--ZY5CS28jBCfb727c--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 15: 9:49 2001
Delivered-To: freebsd-net@freebsd.org
Received: from cicero1.cybercity.dk (cicero1.cybercity.dk [212.242.40.4])
by hub.freebsd.org (Postfix) with ESMTP id 00FD537B424
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 15:09:46 -0700 (PDT)
(envelope-from hroi@asdf.dk)
Received: from usr00.cybercity.dk (usr00.cybercity.dk [212.242.40.34])
by cicero1.cybercity.dk (Postfix) with ESMTP
id 04C8B15FCBA; Thu, 31 May 2001 00:09:40 +0200 (CEST)
Received: from asdf.dk (port18.ds1-noe.adsl.cybercity.dk [212.242.52.19])
by usr00.cybercity.dk (8.11.2/8.11.0) with ESMTP id f4UM9Xb31984;
Thu, 31 May 2001 00:09:34 +0200 (CEST)
(envelope-from hroi@asdf.dk)
Message-ID: <3B157021.8DF52B75@asdf.dk>
Date: Thu, 31 May 2001 00:11:45 +0200
From: Hroi Sigurdsson <hroi@asdf.dk>
Organization: Expert Knob Twiddlers
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Iasen Kostoff <tbyte@tbyte.org>
Cc: freebsd-net@freebsd.org
Subject: Re: routing socket and routes assignment
References: <Pine.BSF.4.21.0105301102510.32941-100000@shadow.otel.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Iasen Kostoff wrote:
> The gateway is directly connected and I think this is obvious and should
> not even be discused. The IP address of the gateway is not from
> network that the computer is. But there is a route throu interface to it
> and the kernel still refuses to use that gateway with error ENETUNREACH.
> And I wrote a patch which allows kernel to set that route. It's kinda
> unfinished still but it works. Even now (without the patch) you can set
> this route but it's not straight forward and I don't think that's the
> right way to be done.
That is just broken IMHO. You will also need to disable any
e/ingress-filtering that may be on the gateway.
The right thing to do would be to assign an address on that net to your
interface which will allow you to point your default gateway at an
address on that net.
--
Hroi Sigurdsson
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 16:57:15 2001
Delivered-To: freebsd-net@freebsd.org
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
by hub.freebsd.org (Postfix) with ESMTP
id AAE5A37B422; Wed, 30 May 2001 16:57:09 -0700 (PDT)
(envelope-from louie@whizzo.transsys.com)
Received: (from louie@localhost)
by whizzo.transsys.com (8.11.3/8.11.3) id f4UNv8k14534;
Wed, 30 May 2001 19:57:09 -0400 (EDT)
(envelope-from louie)
Date: Wed, 30 May 2001 19:57:09 -0400 (EDT)
From: Louis Mamakos <louie@whizzo.transsys.com>
Message-Id: <200105302357.f4UNv8k14534@whizzo.transsys.com>
To: FreeBSD-gnats-submit@freebsd.org
Subject: ipf packet munging bug using "to" option in rule
Reply-To: louie@whizzo.transsys.com
Cc: freebsd-net@freebsd.org, darrenr@freebsd.org
X-send-pr-version: 3.113
X-GNATS-Notify:
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
>Submitter-Id: current-users
>Originator: Louis Mamakos
>Organization: dept of serendipity scheduling and managment
>Confidential: no
>Synopsis: ipf packet munging bug using "to" option in rule
>Severity: serious
>Priority: medium
>Category: kern
>Class: sw-bug
>Release: FreeBSD 4.3-STABLE i386
>Environment:
System: FreeBSD whizzo.transsys.com 4.3-STABLE FreeBSD 4.3-STABLE #18: Sat May 12 20:38:19 EDT 2001 louie@whizzo.transsys.com:/usr/src/sys/compile/SAYSHELL i386
>Description:
I'm using ipf on a machine to perform some stupid packet tricks, including
the dubious operation of fowarding traffic out an alternative network
interface based on the source address of the packet. The reasons why
are beyond the scope of this PR.
I have a rule that looks something like this:
pass out quick on de0 from any to any head 11
block out quick on de0 to tun0 from 144.202.0.0/16 to !144.202.0.0/16 group 11
...
The intent is that when packets from 144.202.0.0/16 arrive on this
host, that they get forcebly shoved out the tun0 network interface,
rather than taking the expect forwarding path via the de0 interface.
This works MOST OF THE TIME. However, sending packets larger than a
certain size results in the packet being mangled. It turns out this
happens when the packet is large enough that it can no longer be
contained within a single mbuf, and there's an mbuf cluster attached.
There is code in sys/netinet/ip_fil.c:ipfr_fastroute() which does
something like this (paraphrased):n
ip->ip_len = htons(ip->ip_len);
ip->ip_off = htons(ip->ip_off);
if (!ip->ip_sum)
ip->ip_sum = in_cksum(m, hlen);
error = (*ifp->if_output)(ifp, m, (struct sockaddr *)dst,
ro->ro_rt);
if (i) {
ip->ip_id = ntohs(ip->ip_id);
ip->ip_len = ntohs(ip->ip_len);
ip->ip_off = ntohs(ip->ip_off);
}
The problem is that if the outbound network interface saves a pointer
to the cluster, it will pick up up the version of the packet after
it's been modified by the ntohs() calls after the if_output routine
is called. In my case, this happens on a tunnel interface but
other network interfaces which can DMA directly from the mbufs rather
than copying the data will suffer from the same problem.
>How-To-Repeat:
as described, sorta..
>Fix:
I did a brutal hack in ipfr_fastroute() to make a copy of the
mbuf if it's not M_WRITABLE(), and then arranged for the
if (i) case in the code above to never get run to corrupt the
data in the mbuf.
I don't understand the global structure of the ipf code well
enough to know if that's a "proper" way to solve the problem
or not. After applying the workaround, traffic is now working
where previously I was getting nasty checksum errors and the
like due to some of the fields being byte-swapped. I would
imagine that big-endian systems and those with network interfaces
that require the transmit data to be copied wouldn't have
seen this problem previously.
--- /sys/netinet/ip_fil.c Sun Feb 25 10:53:34 2001
+++ /tmp/ip_fil.c Wed May 30 19:50:45 2001
@@ -1284,6 +1284,32 @@
struct route iproute;
frentry_t *fr;
+#ifdef __FreeBSD__
+ /*
+ * HOT FIX/KLUDGE:
+ *
+ * If the mbuf we're about to send is not writable (because of
+ * a cluster reference, for example) we'll need to make a copy
+ * of it since this routine modifies the contents.
+ *
+ * If you have non-crappy network hardware that can transmit data
+ * from the mbuf, rather than making a copy, this is gonna be a
+ * problem.
+ */
+
+ if (M_WRITABLE(m) == 0) {
+ if ((m0 = m_dup(m, M_DONTWAIT)) != 0) {
+ m_freem(m);
+ m = m0;
+ } else {
+ error = ENOBUFS;
+ m_freem(m);
+ ipl_frouteok[1]++;
+ return 0;
+ }
+ }
+#endif
+
hlen = fin->fin_hlen;
ip = mtod(m0, struct ip *);
@@ -1379,12 +1405,17 @@
# if BSD >= 199306
int i = 0;
+#ifdef __FreeBSD__
+ /* HOT FIX: we've already made a copy of the mbuf
+ above, so we won't need to restore it here. */
+#else /* __FreeBSD__ */
# ifdef MCLISREFERENCED
if ((m->m_flags & M_EXT) && MCLISREFERENCED(m))
# else
if (m->m_flags & M_EXT)
# endif
i = 1;
+#endif /* __FreeBSD__ */
# endif
# ifndef sparc
# ifndef __FreeBSD__
@@ -1399,7 +1430,9 @@
error = (*ifp->if_output)(ifp, m, (struct sockaddr *)dst,
ro->ro_rt);
if (i) {
+# ifndef __FreeBSD__
ip->ip_id = ntohs(ip->ip_id);
+# endif
ip->ip_len = ntohs(ip->ip_len);
ip->ip_off = ntohs(ip->ip_off);
}
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 21:46:42 2001
Delivered-To: freebsd-net@freebsd.org
Received: from imo-d09.mx.aol.com (imo-d09.mx.aol.com [205.188.157.41])
by hub.freebsd.org (Postfix) with ESMTP id 9C3FF37B422
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 21:46:37 -0700 (PDT)
(envelope-from raviprasad20@netscape.net)
Received: from raviprasad20@netscape.net
by imo-d09.mx.aol.com (mail_out_v30.22.) id n.2c.170c5c1 (16230)
for <freebsd-net@freebsd.org>; Thu, 31 May 2001 00:46:34 -0400 (EDT)
Received: from netscape.com (aimmail09.aim.aol.com [205.188.144.201]) by air-in02.mx.aol.com (v77_r1.37) with ESMTP; Thu, 31 May 2001 00:46:33 -0400
Date: Thu, 31 May 2001 00:46:33 -0400
From: raviprasad20@netscape.net
To: freebsd-net@freebsd.org
Subject: rtmsg_input function of rtadvd daemon
Mime-Version: 1.0
Message-ID: <11D7AE68.34A48F69.9513E96F@netscape.net>
X-Mailer: Franklin Webmailer 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hi,
My understanding of this function is like this.
This function will receive input only when
a)the routes are added through the route6 command.
b) When a prefix is added through the prefix command.
c) when a new address is formed from the prefix through the prefix received through router advertisement.
Kindly mail me if my understanding is correct.
If the the rtmsg_input() function receives messages through the routing socket in any other case kindly mail me.
regards
ravi prasad
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 21:56: 0 2001
Delivered-To: freebsd-net@freebsd.org
Received: from web5302.mail.yahoo.com (web5302.mail.yahoo.com [216.115.106.111])
by hub.freebsd.org (Postfix) with SMTP id C9EC837B423
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 21:55:57 -0700 (PDT)
(envelope-from vishubp@yahoo.com)
Message-ID: <20010531045557.19028.qmail@web5302.mail.yahoo.com>
Received: from [203.200.20.3] by web5302.mail.yahoo.com; Thu, 31 May 2001 05:55:57 BST
Date: Thu, 31 May 2001 05:55:57 +0100 (BST)
From: =?iso-8859-1?q?vishwanath=20pargaonkar?= <vishubp@yahoo.com>
Subject: ipv6 tools
To: freebsd-net@freebsd.org
Cc: questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hi,
i have 4.2 stable powepack CD ie 10 CDs.
does we have anything as ipv6 testing tool in those 10
CDs.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 21:59:36 2001
Delivered-To: freebsd-net@freebsd.org
Received: from obsecurity.dyndns.org (adsl-63-207-60-66.dsl.lsan03.pacbell.net [63.207.60.66])
by hub.freebsd.org (Postfix) with ESMTP
id 65BD237B424; Wed, 30 May 2001 21:59:32 -0700 (PDT)
(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
id 0D71D675B2; Wed, 30 May 2001 21:59:31 -0700 (PDT)
Date: Wed, 30 May 2001 21:59:30 -0700
From: Kris Kennaway <kris@obsecurity.org>
To: vishwanath pargaonkar <vishubp@yahoo.com>
Cc: freebsd-net@FreeBSD.ORG, questions@FreeBSD.ORG
Subject: Re: ipv6 tools
Message-ID: <20010530215930.A49755@xor.obsecurity.org>
References: <20010531045557.19028.qmail@web5302.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010531045557.19028.qmail@web5302.mail.yahoo.com>; from vishubp@yahoo.com on Thu, May 31, 2001 at 05:55:57AM +0100
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
--IS0zKkzwUGydFO0o
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Thu, May 31, 2001 at 05:55:57AM +0100, vishwanath pargaonkar wrote:
> Hi,
> i have 4.2 stable powepack CD ie 10 CDs.
> does we have anything as ipv6 testing tool in those 10
> CDs.
Only what's in the FreeBSD base system and ports collection anyway.
Kris
--IS0zKkzwUGydFO0o
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD8DBQE7Fc+yWry0BWjoQKURApmtAJ9fP6fHVhubaCieScnoK3jEjlPDxQCfWkAa
neJTaHLTvC1BCAW4J0aimIg=
=bHDh
-----END PGP SIGNATURE-----
--IS0zKkzwUGydFO0o--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Wed May 30 22:29:40 2001
Delivered-To: freebsd-net@freebsd.org
Received: from mail.datausa.com (mail.datausa.com [207.174.131.1])
by hub.freebsd.org (Postfix) with ESMTP id 1101A37B424
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 22:29:37 -0700 (PDT)
(envelope-from brad@wcubed.net)
Received: from localhost (brad@localhost)
by mail.datausa.com (8.9.3/8.9.1) with ESMTP id XAA92806
for <freebsd-net@freebsd.org>; Wed, 30 May 2001 23:23:06 -0600 (MDT)
Date: Wed, 30 May 2001 23:23:06 -0600 (MDT)
From: Brad Waite <brad@wcubed.net>
X-Sender: brad@mail.datausa.com
To: freebsd-net@freebsd.org
Subject: IPSec/NAT single gateway?
Message-ID: <Pine.BSF.4.21.0105301847220.79384-100000@mail.datausa.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hey there, all you network gurus,
I'm attempting to connect two office LANs over the Net with a VPN. I was
originally looking at vpnd, but it appears that everything I need is available
in the 4.3 kernel via IPsec.
The two offices are running Windows (95, 98, & NT4) on the desktop and are
connected to the net via DSL. While I will have static external IPs to work
with, it's likely that the DSL router is set up in PPP mode with NAT enabled.
Assuming DSL router's inside address is 10.0.0.1, would I want to set my
gateway's outside IF to 10.0.0.2 and the inside to 10.0.1.1, with all the
desktops on the 10.0.1 network?
Here's what I'm thinking:
< PC net on 10.0.3.0 >
|
|
|---- 10.0.3.1 ----|
| FBSD |
|---- 10.0.2.2 ----|
|
|
|---- 10.0.2.1 ----|
| DSL Router |
|---- Inet addr ---|
|
|
(~~~~~~~~~)
( )
( The Big I )
( )
(_________)
|
|
|---- Inet addr ---|
| DSL Router |
|---- 10.0.0.1 ----|
|
|
|---- 10.0.0.2 ----|
| FBSD |
|---- 10.0.1.1 ----|
|
|
< PC net on 10.0.1.0 >
Will this work, or will the DSL router's NAT break IPsec? Also, are there
problems with traffic to/from the Internet? Should I NAT that, or just use a
255.255.0.0 mask?
Thanks much in advance,
Brad Waite
brad@wcubed.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Thu May 31 0:51: 7 2001
Delivered-To: freebsd-net@freebsd.org
Received: from shadow.otel.net (JuDiCaToR.OTEL.net [212.36.9.113])
by hub.freebsd.org (Postfix) with ESMTP id 7D8BF37B422
for <freebsd-net@FreeBSD.ORG>; Thu, 31 May 2001 00:51:03 -0700 (PDT)
(envelope-from tbyte@tbyte.org)
Received: from localhost (localhost [127.0.0.1])
by shadow.otel.net (8.11.3/8.11.1) with ESMTP id f4V7on036862;
Thu, 31 May 2001 10:50:56 +0300 (EEST)
(envelope-from tbyte@tbyte.org)
Date: Thu, 31 May 2001 10:50:49 +0300 (EEST)
From: Iasen Kostoff <tbyte@tbyte.org>
X-Sender: tbyte@shadow.otel.net
To: Hroi Sigurdsson <hroi@asdf.dk>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: routing socket and routes assignment
In-Reply-To: <3B157021.8DF52B75@asdf.dk>
Message-ID: <Pine.BSF.4.21.0105311050440.36850-100000@shadow.otel.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: 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 May 31 0:54:22 2001
Delivered-To: freebsd-net@freebsd.org
Received: from shadow.otel.net (JuDiCaToR.OTEL.net [212.36.9.113])
by hub.freebsd.org (Postfix) with ESMTP id DB6E437B424
for <freebsd-net@FreeBSD.ORG>; Thu, 31 May 2001 00:54:17 -0700 (PDT)
(envelope-from tbyte@tbyte.org)
Received: from localhost (localhost [127.0.0.1])
by shadow.otel.net (8.11.3/8.11.1) with ESMTP id f4V7sF036877;
Thu, 31 May 2001 10:54:15 +0300 (EEST)
(envelope-from tbyte@tbyte.org)
Date: Thu, 31 May 2001 10:54:15 +0300 (EEST)
From: Iasen Kostoff <tbyte@tbyte.org>
X-Sender: tbyte@shadow.otel.net
To: Hroi Sigurdsson <hroi@asdf.dk>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: routing socket and routes assignment
In-Reply-To: <3B157021.8DF52B75@asdf.dk>
Message-ID: <Pine.BSF.4.21.0105311051060.36850-100000@shadow.otel.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
On Thu, 31 May 2001, Hroi Sigurdsson wrote:
> Iasen Kostoff wrote:
>
> > The gateway is directly connected and I think this is obvious and should
> > not even be discused. The IP address of the gateway is not from
> > network that the computer is. But there is a route throu interface to it
> > and the kernel still refuses to use that gateway with error ENETUNREACH.
> > And I wrote a patch which allows kernel to set that route. It's kinda
> > unfinished still but it works. Even now (without the patch) you can set
> > this route but it's not straight forward and I don't think that's the
> > right way to be done.
>
> That is just broken IMHO. You will also need to disable any
> e/ingress-filtering that may be on the gateway.
> The right thing to do would be to assign an address on that net to your
> interface which will allow you to point your default gateway at an
> address on that net.
>
> --
> Hroi Sigurdsson
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-net" in the body of the message
>
I don't think that assigning an address from net of the gateway is the
right way and none of the cisco's routers need that, why should FreeBSD
need it ? And no there is not any e/ingress-filtering for the FreeBSD
computer.
Regards.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Thu May 31 11:22:59 2001
Delivered-To: freebsd-net@freebsd.org
Received: from ns2.sysadmin-inc.com (ns2.sysadmin-inc.com [209.16.228.145])
by hub.freebsd.org (Postfix) with SMTP id 961E437B423
for <freebsd-net@freebsd.org>; Thu, 31 May 2001 11:22:54 -0700 (PDT)
(envelope-from peter@sysadmin-inc.com)
Received: (qmail 80060 invoked by alias); 31 May 2001 18:22:53 -0000
Received: from unknown (HELO w2kstest) (10.10.1.70)
by ns2.sysadmin-inc.com with SMTP; 31 May 2001 18:22:53 -0000
From: "Peter Brezny" <peter@sysadmin-inc.com>
To: <freebsd-net@freebsd.org>
Subject: mpdnetgraph connection refused
Date: Thu, 31 May 2001 14:21:55 -0400
Message-ID: <MFEFLELMIJGKDKPCJHAFAEKNCCAA.peter@sysadmin-inc.com>
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.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
I'm having difficulty with some ms PPTP connections over dsl connections.
The mpd server works fine for some clients, but not all. Comparing the logs
of connections that work and those that don't, I find this as the first
difference.
May 25 16:43:24 gkgw mpd: pptp0-0: call cleared by peer
Which peer is the log refering to?
ideas?
I've attached the complete log of the connection that failed below.
TIA.
Peter Brezny
SysAdmin Services Inc.
May 25 16:43:23 gkgw mpd: mpd: PPTP connection from 208.63.181.154:1123
May 25 16:43:23 gkgw mpd: pptp0: attached to connection with
208.63.181.154:1123
May 25 16:43:24 gkgw mpd: [pptp] IFACE: Open event
May 25 16:43:24 gkgw mpd: [pptp] IPCP: Open event
May 25 16:43:24 gkgw mpd: [pptp] IPCP: state change Initial --> Starting
May 25 16:43:24 gkgw mpd: [pptp] IPCP: LayerStart
May 25 16:43:24 gkgw mpd: [pptp] IPCP: Open event
May 25 16:43:24 gkgw mpd: [pptp] bundle: OPEN event in state CLOSED
May 25 16:43:24 gkgw mpd: [pptp] opening link "pptp"...
May 25 16:43:24 gkgw mpd: [pptp] link: OPEN event
May 25 16:43:24 gkgw mpd: [pptp] LCP: Open event
May 25 16:43:24 gkgw mpd: [pptp] LCP: state change Initial --> Starting
May 25 16:43:24 gkgw mpd: [pptp] LCP: LayerStart
May 25 16:43:24 gkgw mpd: [pptp] device: OPEN event in state DOWN
May 25 16:43:24 gkgw mpd: [pptp] attaching to peer's outgoing call
May 25 16:43:24 gkgw mpd: [pptp] device is now in state OPENING
May 25 16:43:24 gkgw mpd: [pptp] device: UP event in state OPENING
May 25 16:43:24 gkgw mpd: [pptp] device is now in state UP
May 25 16:43:24 gkgw mpd: [pptp] link: UP event
May 25 16:43:24 gkgw mpd: [pptp] link: origination is remote
May 25 16:43:24 gkgw mpd: [pptp] LCP: Up event
May 25 16:43:24 gkgw mpd: [pptp] LCP: state change Starting --> Req-Sent
May 25 16:43:24 gkgw mpd: [pptp] LCP: phase shift DEAD --> ESTABLISH
May 25 16:43:24 gkgw mpd: [pptp] LCP: SendConfigReq #53
May 25 16:43:24 gkgw mpd: ACFCOMP
May 25 16:43:24 gkgw mpd: PROTOCOMP
May 25 16:43:24 gkgw mpd: MRU 1500
May 25 16:43:24 gkgw mpd: MAGICNUM 07a1c760
May 25 16:43:24 gkgw mpd: AUTHPROTO CHAP MSOFT
May 25 16:43:24 gkgw mpd: pptp0-0: call cleared by peer
May 25 16:43:24 gkgw mpd: pptp0-0: killing channel
May 25 16:43:24 gkgw mpd: [pptp] PPTP call terminated
May 25 16:43:24 gkgw mpd: [pptp] IFACE: Close event
May 25 16:43:24 gkgw mpd: [pptp] IPCP: Close event
May 25 16:43:24 gkgw mpd: [pptp] IPCP: state change Starting --> Initial
May 25 16:43:24 gkgw mpd: [pptp] IPCP: LayerFinish
May 25 16:43:24 gkgw mpd: [pptp] IFACE: Close event
May 25 16:43:24 gkgw mpd: pptp0: closing connection with 208.63.181.154:1123
May 25 16:43:24 gkgw mpd: [pptp] bundle: CLOSE event in state OPENED
May 25 16:43:24 gkgw mpd: [pptp] closing link "pptp"...
May 25 16:43:24 gkgw mpd: [pptp] device: DOWN event in state UP
May 25 16:43:24 gkgw mpd: [pptp] device is now in state DOWN
May 25 16:43:24 gkgw mpd: [pptp] link: CLOSE event
May 25 16:43:24 gkgw mpd: [pptp] LCP: Close event
May 25 16:43:24 gkgw mpd: [pptp] LCP: state change Req-Sent --> Closing
May 25 16:43:24 gkgw mpd: [pptp] LCP: phase shift ESTABLISH --> TERMINATE
May 25 16:43:24 gkgw mpd: [pptp] LCP: SendTerminateReq #54
May 25 16:43:24 gkgw mpd: [pptp] error writing len 8 frame to bypass:Network
is down
May 25 16:43:24 gkgw mpd: [pptp] link: DOWN event
May 25 16:43:24 gkgw mpd: [pptp] LCP: Down event
May 25 16:43:24 gkgw mpd: [pptp] LCP: LayerFinish
May 25 16:43:24 gkgw mpd: [pptp] LCP: state change Closing --> Initial
May 25 16:43:24 gkgw mpd: [pptp] LCP: phase shift TERMINATE --> DEAD
May 25 16:43:24 gkgw mpd: [pptp] device: CLOSE event in state DOWN
May 25 16:43:24 gkgw mpd: [pptp] device is now in state DOWN
May 25 16:43:27 gkgw mpd: pptp0: no reply to StopCtrlConnRequest after 3 sec
May 25 16:43:27 gkgw mpd: pptp0: killing connection with 208.63.181.154:1123
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Thu May 31 16:23:28 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 AF94A37B422
for <net@FreeBSD.ORG>; Thu, 31 May 2001 16:23:25 -0700 (PDT)
(envelope-from jesper@skriver.dk)
Received: by freesbee.wheel.dk (Postfix, from userid 1001)
id 61DA05D82; Fri, 1 Jun 2001 01:25:29 +0200 (CEST)
Date: Fri, 1 Jun 2001 01:25:29 +0200
From: Jesper Skriver <jesper@skriver.dk>
To: Kris Kennaway <kris@obsecurity.org>
Cc: net@FreeBSD.ORG
Subject: Re: Randomized IP ID patch
Message-ID: <20010601012529.C19030@skriver.dk>
References: <20010525233811.A44455@xor.obsecurity.org> <20010526003815.A17669@xor.obsecurity.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010526003815.A17669@xor.obsecurity.org>; from kris@obsecurity.org on Sat, May 26, 2001 at 12:38:15AM -0700
X-PGP-Fingerprint: 6B88 9CE8 66E9 E631 C9C5 5EB4 22AB F0EC F956 1C31
X-PGP-Public-Key: http://freesbee.wheel.dk/~jesper/gpgkey.pub
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
On Sat, May 26, 2001 at 12:38:15AM -0700, Kris Kennaway wrote:
> Actually, this patch was broken; the updated one is at:
>
> http://www.freebsd.org/~kris/randomized-ipid.diff
Looks good to me, will you commit before your vacation ?
/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 May 31 22: 4:45 2001
Delivered-To: freebsd-net@freebsd.org
Received: from obsecurity.dyndns.org (adsl-63-207-60-66.dsl.lsan03.pacbell.net [63.207.60.66])
by hub.freebsd.org (Postfix) with ESMTP id 3CC4137B42C
for <net@FreeBSD.ORG>; Thu, 31 May 2001 22:04:40 -0700 (PDT)
(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
id 90610678A6; Thu, 31 May 2001 22:04:39 -0700 (PDT)
Date: Thu, 31 May 2001 22:04:39 -0700
From: Kris Kennaway <kris@obsecurity.org>
To: Jesper Skriver <jesper@skriver.dk>
Cc: Kris Kennaway <kris@obsecurity.org>, net@FreeBSD.ORG
Subject: Re: Randomized IP ID patch
Message-ID: <20010531220439.A15207@xor.obsecurity.org>
References: <20010525233811.A44455@xor.obsecurity.org> <20010526003815.A17669@xor.obsecurity.org> <20010601012529.C19030@skriver.dk>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010601012529.C19030@skriver.dk>; from jesper@skriver.dk on Fri, Jun 01, 2001 at 01:25:29AM +0200
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
--2oS5YaxWCcQjTEyO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Jun 01, 2001 at 01:25:29AM +0200, Jesper Skriver wrote:
> On Sat, May 26, 2001 at 12:38:15AM -0700, Kris Kennaway wrote:
> > Actually, this patch was broken; the updated one is at:
> >=20
> > http://www.freebsd.org/~kris/randomized-ipid.diff
>=20
> Looks good to me, will you commit before your vacation ?
Will try.
Kris
--2oS5YaxWCcQjTEyO
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD8DBQE7FyJmWry0BWjoQKURAo8rAJ4hHgPsOv7y4YEPFPQM2RM4x+xSrgCgpOvP
nk3x8ruQ7ap2ray3Lzm1sn8=
=RP/P
-----END PGP SIGNATURE-----
--2oS5YaxWCcQjTEyO--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Fri Jun 1 6:47:59 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 051E737B423
for <freebsd-net@FreeBSD.ORG>; Fri, 1 Jun 2001 06:47:56 -0700 (PDT)
(envelope-from jcv@vbc.net)
Received: from localhost (jcv@localhost)
by brunel.uk1.vbc.net (8.11.0/8.11.0) with ESMTP id f51DlsE13947
for <freebsd-net@FreeBSD.ORG>; Fri, 1 Jun 2001 14:47:54 +0100 (BST)
X-Authentication-Warning: brunel.uk1.vbc.net: jcv owned process doing -bs
Date: Fri, 1 Jun 2001 14:47:53 +0100 (BST)
From: Jean-Christophe Varaillon <jcv@vbc.net>
X-Sender: jcv@brunel.uk1.vbc.net
To: freebsd-net@FreeBSD.ORG
Subject: Expire value
In-Reply-To: <20010530204905.F29853@mail.webmonster.de>
Message-ID: <Pine.BSF.4.10.10106011442480.9645-100000@brunel.uk1.vbc.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hi,
By doing a netstat -nr I can see that:
----
Destination Gateway Flags Netif Expire
x.x.x.x 0:50:73:28:70:40 UHLW fxp0 914
----
I my case when the Expire value reach 0, it does not restart as it
should.
I would like to know what could stop the timer to restart?
Thanks,
Christophe.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Fri Jun 1 6:51: 0 2001
Delivered-To: freebsd-net@freebsd.org
Received: from ctron-dnm.ctron.com (ctron-dnm.cabletron.com [12.25.1.120])
by hub.freebsd.org (Postfix) with ESMTP id 5980537B43E
for <freebsd-net@freebsd.org>; Fri, 1 Jun 2001 06:50:55 -0700 (PDT)
(envelope-from bdoehner@cabletron.com)
Received: (from uucp@localhost)
by ctron-dnm.ctron.com (8.8.7/8.8.7) id JAA12742;
Fri, 1 Jun 2001 09:57:43 -0400 (EDT)
Received: from olympus.ctron.com(134.141.72.253) by ctron-dnm.ctron.com via smap (4.1)
id xma012702; Fri, 1 Jun 01 09:56:41 -0400
Received: from roam.ctron.com (roam [134.141.190.162])
by olympus.ctron.com (8.8.7/8.8.7) with ESMTP id JAA05874;
Fri, 1 Jun 2001 09:47:33 -0400 (EDT)
Date: Fri, 1 Jun 2001 09:49:33 -0400 (EDT)
From: Bernie Doehner <bdoehner@cabletron.com>
X-X-Sender: <bdoehner@roam.ctron.com>
To: Jean-Christophe Varaillon <jcv@vbc.net>
Cc: <freebsd-net@freebsd.org>
Subject: Re: Expire value
In-Reply-To: <Pine.BSF.4.10.10106011442480.9645-100000@brunel.uk1.vbc.net>
Message-ID: <Pine.BSF.4.32.0106010949120.11208-100000@roam.ctron.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
How about the entry aging out due to no more traffic to/from this
MAC address?
Bernie
On Fri, 1 Jun 2001, Jean-Christophe Varaillon wrote:
> Date: Fri, 1 Jun 2001 14:47:53 +0100 (BST)
> From: Jean-Christophe Varaillon <jcv@vbc.net>
> To: freebsd-net@FreeBSD.ORG
> Subject: Expire value
>
> Hi,
>
> By doing a netstat -nr I can see that:
> ----
> Destination Gateway Flags Netif Expire
>
> x.x.x.x 0:50:73:28:70:40 UHLW fxp0 914
> ----
>
> I my case when the Expire value reach 0, it does not restart as it
> should.
>
> I would like to know what could stop the timer to restart?
>
>
> Thanks,
> Christophe.
>
>
> 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 Jun 1 6:56:49 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 BAA8437B424
for <freebsd-net@FreeBSD.ORG>; Fri, 1 Jun 2001 06:56:46 -0700 (PDT)
(envelope-from jcv@vbc.net)
Received: from localhost (jcv@localhost)
by brunel.uk1.vbc.net (8.11.0/8.11.0) with ESMTP id f51Duak14087;
Fri, 1 Jun 2001 14:56:36 +0100 (BST)
X-Authentication-Warning: brunel.uk1.vbc.net: jcv owned process doing -bs
Date: Fri, 1 Jun 2001 14:56:35 +0100 (BST)
From: Jean-Christophe Varaillon <jcv@vbc.net>
X-Sender: jcv@brunel.uk1.vbc.net
To: Bernie Doehner <bdoehner@cabletron.com>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: Expire value
In-Reply-To: <Pine.BSF.4.32.0106010949120.11208-100000@roam.ctron.com>
Message-ID: <Pine.BSF.4.10.10106011454070.9645-100000@brunel.uk1.vbc.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
On Fri, 1 Jun 2001, Bernie Doehner wrote:
> How about the entry aging out due to no more traffic to/from this
> MAC address?
>
The thing is that I am loosing connectivity between 2 machines on a same
LAN !
I suppose that traffic or not, the MAC address of machines in a same LAN
should appears in their routing table, no ?
> >
> > Hi,
> >
> > By doing a netstat -nr I can see that:
> > ----
> > Destination Gateway Flags Netif Expire
> >
> > x.x.x.x 0:50:73:28:70:40 UHLW fxp0 914
> > ----
> >
> > I my case when the Expire value reach 0, it does not restart as it
> > should.
> >
> > I would like to know what could stop the timer to restart?
> >
> >
> > Thanks,
> > Christophe.
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-net" in the body of the message
> >
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-net" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Fri Jun 1 7: 8:40 2001
Delivered-To: freebsd-net@freebsd.org
Received: from ctron-dnm.ctron.com (ctron-dnm.cabletron.com [12.25.1.120])
by hub.freebsd.org (Postfix) with ESMTP id ED57537B422
for <freebsd-net@freebsd.org>; Fri, 1 Jun 2001 07:08:35 -0700 (PDT)
(envelope-from bdoehner@cabletron.com)
Received: (from uucp@localhost)
by ctron-dnm.ctron.com (8.8.7/8.8.7) id KAA13653;
Fri, 1 Jun 2001 10:15:26 -0400 (EDT)
Received: from olympus.ctron.com(134.141.72.253) by ctron-dnm.ctron.com via smap (4.1)
id xma013644; Fri, 1 Jun 01 10:14:45 -0400
Received: from roam.ctron.com (roam [134.141.190.162])
by olympus.ctron.com (8.8.7/8.8.7) with ESMTP id KAA06671;
Fri, 1 Jun 2001 10:05:36 -0400 (EDT)
Date: Fri, 1 Jun 2001 10:07:37 -0400 (EDT)
From: Bernie Doehner <bdoehner@cabletron.com>
X-X-Sender: <bdoehner@roam.ctron.com>
Reply-To: <bad@uhf.wireless.net>
To: Jean-Christophe Varaillon <jcv@vbc.net>
Cc: <freebsd-net@freebsd.org>
Subject: Re: Expire value
In-Reply-To: <Pine.BSF.4.10.10106011454070.9645-100000@brunel.uk1.vbc.net>
Message-ID: <Pine.BSF.4.32.0106011003070.11231-100000@roam.ctron.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Unless you have an usual setup, I think the reason the entry is aging
out of your arp table (not routing table) is that either one of the machines
or your hub or your cabling have an intermittent connection.
Whenever an entry ages out of your arp table, and if the machines decide to
talk again thereafter, an ARP request will be issued to resolve the MAC address
which will subsequently be cached in your ARP table and aged out over time.
The ARPs apparently aren't making it across.. Something to check, is are
both machines using the listening to the same broadcast address? Are you running
some kind of broadcast suppression on your LAN, any kind of firewall filtering?
Bernie
On Fri, 1 Jun 2001, Jean-Christophe Varaillon wrote:
> Date: Fri, 1 Jun 2001 14:56:35 +0100 (BST)
> From: Jean-Christophe Varaillon <jcv@vbc.net>
> To: Bernie Doehner <bdoehner@cabletron.com>
> Cc: freebsd-net@FreeBSD.ORG
> Subject: Re: Expire value
>
> On Fri, 1 Jun 2001, Bernie Doehner wrote:
>
> > How about the entry aging out due to no more traffic to/from this
> > MAC address?
> >
>
> The thing is that I am loosing connectivity between 2 machines on a same
> LAN !
>
> I suppose that traffic or not, the MAC address of machines in a same LAN
> should appears in their routing table, no ?
>
>
>
> > >
> > > Hi,
> > >
> > > By doing a netstat -nr I can see that:
> > > ----
> > > Destination Gateway Flags Netif Expire
> > >
> > > x.x.x.x 0:50:73:28:70:40 UHLW fxp0 914
> > > ----
> > >
> > > I my case when the Expire value reach 0, it does not restart as it
> > > should.
> > >
> > > I would like to know what could stop the timer to restart?
> > >
> > >
> > > Thanks,
> > > Christophe.
> > >
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-net" in the body of the message
> > >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-net" in the body of the message
> >
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-net" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Fri Jun 1 12:54:55 2001
Delivered-To: freebsd-net@freebsd.org
Received: from david.siemens.de (david.siemens.de [192.35.17.14])
by hub.freebsd.org (Postfix) with ESMTP id 2D84537B422
for <freebsd-net@FreeBSD.ORG>; Fri, 1 Jun 2001 12:54:51 -0700 (PDT)
(envelope-from andre.albsmeier@mchp.siemens.de)
X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de)
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
by david.siemens.de (8.11.0/8.11.0) with ESMTP id f51Jso502251
for <freebsd-net@FreeBSD.ORG>; Fri, 1 Jun 2001 21:54:50 +0200 (MET DST)
Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7])
by mail3.siemens.de (8.11.1/8.11.1) with ESMTP id f51JsnV10032855
for <freebsd-net@FreeBSD.ORG>; Fri, 1 Jun 2001 21:54:49 +0200 (MEST)
Received: (from localhost)
by curry.mchp.siemens.de (8.11.3/8.11.3) id f51Jsnu02097;
Date: Fri, 1 Jun 2001 21:54:49 +0200
From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
To: freebsd-net@FreeBSD.ORG
Cc: Andre.Albsmeier@mchp.siemens.de
Subject: Routing problem: Is the bug in my brain or in FreeBSD?
Message-ID: <20010601215449.A3609@curry.mchp.siemens.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
I don't know where the bug is...
Simple network:
- two routers (1 and 2)
- host C with IP 192.168.1.3
- host S with IP 192.168.2.1
All machines are FreeBSD 4.3-STABLE.
Router 1 routes pkts between the Internet and 192.168.1.0
Router 2 routes pkts between 192.168.1.0 and 192.168.2.0
+-----+ +-----+
default | | 192.168.1.0 | | 192.168.2.0
-----------| 1 |--------+--------| 2 |--------+-------- more hosts
| | | | | |
+-----+ | +-----+ |
| |
+-----+ +-----+
| | | |
192.168.1.3 | C | | S | 192.168.2.1
| | | |
+-----+ +-----+
Relevant parts of netstat -rn on C during normal operation:
-------------------------------------------------------------
Destination Gateway Flags Netif Expire
default 192.168.1.1 UGSc fxp0
127.0.0.1 127.0.0.1 UH lo0
192.168.1 link#1 UC fxp0 =>
192.168.1.1 0:e0:18:90:91:bb UHLW fxp0 1182
192.168.1.2 0:e0:18:90:94:c8 UHLW fxp0 1058
192.168.1.3 0:e0:18:90:45:dc UHLW lo0
192.168.1.255 ff:ff:ff:ff:ff:ff UHLWb fxp0
192.168.2 192.168.1.2 UGc fxp0
The syslogd on host C is configured to log messages
to syslogd running on host S. This works perfectly,
all messages appear on host S.
Now we delete the route to net 192.168.2.0 on host C.
When syslogd wants to send another message to S, the
kernel uses the default route which is obvious because
the route to net 192.168.2.0 is gone. We can see the
packets going into router 1. This is OK as well.
Now we bring back the route to net 192.168.2.0 again
on host C exactly as it was before. We can verify
this with netstat -rn on C. We can also ping host S
or telnet to it or do other stuff which all work
perfectly.
The problem is that each time when syslogd on C wants
to send a packet to S, the kernel still uses 1 as router
even though it should send them through 2. After HUPing
or restarting syslogd on C (which means that the UDP socket
is closed and opened again) things are back to normal.
Is this a know "feature"? It seems that as long as the
socket can send the packets somewhere it doesn't bother
if there is a better route to the destination until it
is closed and opened again.
Any hints?
-Andre
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Fri Jun 1 14:42:17 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 B82C237B422
for <freebsd-net@FreeBSD.ORG>; Fri, 1 Jun 2001 14:42:13 -0700 (PDT)
(envelope-from jinmei@isl.rdc.toshiba.co.jp)
Received: from localhost ([131.107.37.32])
by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id GAA11504;
Sat, 2 Jun 2001 06:42:04 +0900 (JST)
Date: Sat, 02 Jun 2001 06:39:19 +0900
Message-ID: <y7v8zjbx4l4.wl@condor2.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: vishwanath pargaonkar <vishubp@yahoo.com>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: Router advertisement
In-Reply-To: <20010529123909.12618.qmail@web5305.mail.yahoo.com>
References: <20010529123909.12618.qmail@web5305.mail.yahoo.com>
User-Agent: Wanderlust/2.5.8 (Smooth) 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 980905(IM100)
Lines: 19
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
>>>>> On Tue, 29 May 2001 13:39:09 +0100 (BST),
>>>>> vishwanath pargaonkar <vishubp@yahoo.com> said:
> i have freebsd 4.2 stable.
> my doubt is how is router advertisement called?
> ie i know that router advertisement is user land
> program.so when ever router solicitation is received
> we receive it and update the cache by calling
> nd6_cache_lladdr.but how exactly RA invoked it being
> user land program?
> how RA responce is evoked to RS?
Incoming RSes are passed to the userland daemon after processing the
link-layer address option in the kernel.
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 Fri Jun 1 23:45:59 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 A021037B62E
for <freebsd-net@FreeBSD.ORG>; Fri, 1 Jun 2001 23:45:52 -0700 (PDT)
(envelope-from jinmei@isl.rdc.toshiba.co.jp)
Received: from localhost ([3ffe:501:100f:13ff::a])
by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id PAA13567;
Sat, 2 Jun 2001 15:45:50 +0900 (JST)
Date: Sat, 02 Jun 2001 08:28:51 +0900
Message-ID: <y7v66efwzik.wl@condor2.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: raviprasad20@netscape.net
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: rtmsg_input function of rtadvd daemon
In-Reply-To: <11D7AE68.34A48F69.9513E96F@netscape.net>
References: <11D7AE68.34A48F69.9513E96F@netscape.net>
User-Agent: Wanderlust/2.5.8 (Smooth) 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 980905(IM100)
Lines: 22
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
>>>>> On Thu, 31 May 2001 00:46:33 -0400,
>>>>> raviprasad20@netscape.net said:
> My understanding of this function is like this.
> This function will receive input only when
> c) when a new address is formed from the prefix through the prefix received through router advertisement.
On FreeBSD 4.x, these kind of routes are not passed to the user space.
> Kindly mail me if my understanding is correct.
> If the the rtmsg_input() function receives messages through the routing socket in any other case kindly mail me.
d) interface routes corresponding to an interface address installed
via the ifconfig(8) command.
e) redirected route generated via a Neighbor Discovery Redirect
message.
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 Jun 2 6:15: 4 2001
Delivered-To: freebsd-net@freebsd.org
Received: from imo-d09.mx.aol.com (imo-d09.mx.aol.com [205.188.157.41])
by hub.freebsd.org (Postfix) with ESMTP id 0024837B424
for <freebsd-net@freebsd.org>; Sat, 2 Jun 2001 06:15:02 -0700 (PDT)
(envelope-from raviprasad20@netscape.net)
Received: from raviprasad20@netscape.net
by imo-d09.mx.aol.com (mail_out_v30.22.) id n.5d.49cdb8 (16213)
for <freebsd-net@freebsd.org>; Sat, 2 Jun 2001 09:15:00 -0400 (EDT)
Received: from netscape.com (aimmail09.aim.aol.com [205.188.144.201]) by air-in01.mx.aol.com (v77_r1.37) with ESMTP; Sat, 02 Jun 2001 09:15:00 -0400
Date: Sat, 02 Jun 2001 09:15:00 -0400
From: raviprasad20@netscape.net
To: freebsd-net@freebsd.org
Subject: routing advertisement daemon
Mime-Version: 1.0
Message-ID: <2C141190.4ADA443A.9513E96F@netscape.net>
X-Mailer: Franklin Webmailer 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hi,
Can any body mail me the how a prefix entered through the prefix command is known by the routing advertisement daemon?
regards
ravi prasad
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Sat Jun 2 6:27:38 2001
Delivered-To: freebsd-net@freebsd.org
Received: from imo-m08.mx.aol.com (imo-m08.mx.aol.com [64.12.136.163])
by hub.freebsd.org (Postfix) with ESMTP id 3D8F537B43C
for <freebsd-net@freebsd.org>; Sat, 2 Jun 2001 06:27:36 -0700 (PDT)
(envelope-from raviprasad20@netscape.net)
Received: from raviprasad20@netscape.net
by imo-m08.mx.aol.com (mail_out_v30.22.) id n.2e.1735461 (16241)
for <freebsd-net@freebsd.org>; Sat, 2 Jun 2001 09:27:31 -0400 (EDT)
Received: from netscape.com (aimmail09.aim.aol.com [205.188.144.201]) by air-in03.mx.aol.com (v77_r1.37) with ESMTP; Sat, 02 Jun 2001 09:27:30 -0400
Date: Sat, 02 Jun 2001 09:27:30 -0400
From: raviprasad20@netscape.net
To: freebsd-net@freebsd.org
Subject: Display of prefixes in aperticular ifnet structure.
Mime-Version: 1.0
Message-ID: <39199B3B.03898409.9513E96F@netscape.net>
X-Mailer: Franklin Webmailer 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hi,
I configured some prefixes through the "prefix" command. I then tried to display them as itis by reading the "ifnet" structure's "if_prefixhead" member. The result is like this.
Prefix was set as
#prefix wb0 fec0:11::1
the prefix displayed later by reading the ifnet structure is as follows.
The data is in 8bits. (Displayed by using the
printf(" %x\t",ifp->if_prefixhead.next->prefix.s6_addr8[0]); & etc till 15)
The output is like this.
00 00 00 00 00 00 fe c0 00 11 00 00
00 00 00 00
Can any body mail me if I had done some mistake & that's why iam getting the above result?
Or there is some other place where prefixes are stored & from that place we can get prefixes correctly?
Are prefixes stored in this way itself?
Kindly reply.
regards
ravi prasad
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Sat Jun 2 8:16:25 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 DE05637B422
for <freebsd-net@FreeBSD.ORG>; Sat, 2 Jun 2001 08:16:22 -0700 (PDT)
(envelope-from jinmei@isl.rdc.toshiba.co.jp)
Received: from localhost ([3ffe:501:100f:13ff::a])
by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id AAA15374;
Sun, 3 Jun 2001 00:16:21 +0900 (JST)
Date: Sun, 03 Jun 2001 00:13:37 +0900
Message-ID: <y7vy9ravrry.wl@condor2.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: raviprasad20@netscape.net
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: routing advertisement daemon
In-Reply-To: <2C141190.4ADA443A.9513E96F@netscape.net>
References: <2C141190.4ADA443A.9513E96F@netscape.net>
User-Agent: Wanderlust/2.5.8 (Smooth) 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 980905(IM100)
Lines: 11
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
>>>>> On Sat, 02 Jun 2001 09:15:00 -0400,
>>>>> raviprasad20@netscape.net said:
> Can any body mail me the how a prefix entered through the prefix command is known by the routing advertisement daemon?
through the routing socket.
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 Jun 2 11:24:59 2001
Delivered-To: freebsd-net@freebsd.org
Received: from prime.gushi.org (prime.gushi.org [208.23.118.172])
by hub.freebsd.org (Postfix) with ESMTP
id 47EDE37B422; Sat, 2 Jun 2001 11:24:56 -0700 (PDT)
(envelope-from danm@prime.gushi.org)
Received: from localhost (danm@localhost)
by prime.gushi.org (8.11.3/8.11.3) with ESMTP id f52IQMd07087;
Sat, 2 Jun 2001 14:26:22 -0400 (EDT)
Date: Sat, 2 Jun 2001 14:26:21 -0400 (EDT)
From: "Dan Mahoney, System Admin" <danm@prime.gushi.org>
To: freebsd-net@freebsd.org, question@freebsd.org
Subject: PCAnywhere
Message-ID: <Pine.BSF.4.21.0106021420530.94976-100000@prime.gushi.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Hey all, I have sort of an odd problem. I'm trying to use pcanywhere to
get to an external host, and while I see a lot of info about natd, I am
using ppp (yes its painful) with nat.
Here's the thing:I don't care about running a HOST behind NAT, just remote
(work-from-home), and for some reason I can connect to hosts at my ISP,
and if I have a pcanywhere connection open to hosts at my isp, I can also
connect to my job (which is not my isp), but unless I have the pcanywhere
connection open to my isp, I can't connect to any host outside the local
net.
To my knowledge (and I've examined both nets carefully) there's no
firewalls in place, I should not need to make any allowances on my nat
firewall because I'm simply running a remote, not a host. Can anyone
offer any advice?
-Dan Mahoney
--
"SOY BOMB!"
-The Chest of the nameless streaker of the 1998 Grammy Awards' Bob Dylan
Performance.
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
Web: http://prime.gushi.org
finger danm@prime.gushi.org
for pgp public key and tel#
---------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Sat Jun 2 13:15:37 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 EC38637B423
for <freebsd-net@FreeBSD.ORG>; Sat, 2 Jun 2001 13:15:33 -0700 (PDT)
(envelope-from archie@dellroad.org)
Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20])
by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id NAA21015;
Sat, 2 Jun 2001 13:03:34 -0700 (PDT)
Received: (from archie@localhost)
by arch20m.dellroad.org (8.11.3/8.11.3) id f52K3Ho51512;
Sat, 2 Jun 2001 13:03:17 -0700 (PDT)
(envelope-from archie)
From: Archie Cobbs <archie@dellroad.org>
Message-Id: <200106022003.f52K3Ho51512@arch20m.dellroad.org>
Subject: Re: mpdnetgraph connection refused
In-Reply-To: <MFEFLELMIJGKDKPCJHAFAEKNCCAA.peter@sysadmin-inc.com>
"from Peter Brezny at May 31, 2001 02:21:55 pm"
To: Peter Brezny <peter@sysadmin-inc.com>
Date: Sat, 2 Jun 2001 13:03:17 -0700 (PDT)
Cc: freebsd-net@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL82 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
Peter Brezny writes:
> I'm having difficulty with some ms PPTP connections over dsl connections.
>
> The mpd server works fine for some clients, but not all. Comparing the logs
> of connections that work and those that don't, I find this as the first
> difference.
>
> May 25 16:43:24 gkgw mpd: pptp0-0: call cleared by peer
This means that the peer sent a PPTP "Call clear request", meaning
that they want to close the connection. Mpd is just obey this request.
Not sure why they're doing that.
> Which peer is the log refering to?
The remote PPTP machine.
-Archie
__________________________________________________________________________
Archie Cobbs * Packet Design * http://www.packetdesign.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
From owner-freebsd-net Sat Jun 2 13:15:40 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 6988337B43E
for <freebsd-net@FreeBSD.ORG>; Sat, 2 Jun 2001 13:15:36 -0700 (PDT)
(envelope-from archie@dellroad.org)
Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20])
by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id NAA21013;
Sat, 2 Jun 2001 13:01:45 -0700 (PDT)
Received: (from archie@localhost)
by arch20m.dellroad.org (8.11.3/8.11.3) id f52K1SE51504;
Sat, 2 Jun 2001 13:01:28 -0700 (PDT)
(envelope-from archie)
From: Archie Cobbs <archie@dellroad.org>
Message-Id: <200106022001.f52K1SE51504@arch20m.dellroad.org>
Subject: Re: mpd-netgraph as pptp server
In-Reply-To: <20010530135231.22042.qmail@web13308.mail.yahoo.com>
"from nuzrin at May 30, 2001 06:52:31 am"
To: p9711422@mmu.edu.my
Date: Sat, 2 Jun 2001 13:01:28 -0700 (PDT)
Cc: freebsd-net@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL82 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org
nuzrin writes:
> i just want to know that if in mpd.conf, i have this entry:
>
> pptp0:
> new -i ng0 pptp0 pptp0
> ...
>
> and in mpd.link i have this entry:
>
> pptp0:
> set link type pptp
> ...
>
> and if i want to allow 100 simultaneous client connecting to my pptp server,
> do i have to repeat the entry above 100 times, increasing pptp0 and ng0
> values respectively? this would result in a very big mpd.conf and mpd.links
> file.
Unfortunately, yes..
> is there any other simple way that will keep the mpd.conf and mpd.links files
> short, simple and manageable?
Write a shell script to automatically generate them?
-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