From owner-freebsd-net  Sun Aug 22  3: 9: 6 1999
Delivered-To: freebsd-net@freebsd.org
Received: from camel.ethereal.net (camel.ethereal.net [209.228.7.140])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6EB3914D62; Sun, 22 Aug 1999 03:09:03 -0700 (PDT)
	(envelope-from mistwolf@camel.ethereal.net)
Received: (from mistwolf@localhost)
	by camel.ethereal.net (8.9.3/8.9.1) id AAA94789;
	Sun, 22 Aug 1999 00:12:22 -0700 (PDT)
Date: Sun, 22 Aug 1999 00:12:21 -0700
From: Jamie Norwood <mistwolf@ethereal.net>
To: freebsd-questions@freebsd.org, freebsd-net@freebsd.org
Subject: Rate limiting
Message-ID: <19990822001221.A94758@ethereal.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/0.96.4i
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

If I am using a FreeBSD box as a firewall, can I set up
rate-limiting? IE, can I say that news can only use X KB/s, Quake
can only use Y, and so on? I have a machine I run here that I basically
want to always have bandwidth, even when I am playing quaake or reading 
news on my other machine.

Jamie



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Sun Aug 22  5:47:29 1999
Delivered-To: freebsd-net@freebsd.org
Received: from cdc.net (server1.cdc.net [207.244.0.12])
	by hub.freebsd.org (Postfix) with SMTP id 26B9414CD5
	for <freebsd-net@freebsd.org>; Sun, 22 Aug 1999 05:47:23 -0700 (PDT)
	(envelope-from mwade@cdc.net)
Received: (qmail 15713 invoked by uid 100); 22 Aug 1999 12:46:01 -0000
Date: Sun, 22 Aug 1999 08:46:01 -0400 (EDT)
From: Mike Wade <mwade@cdc.net>
X-Sender: mwade@server1
To: Jamie Norwood <mistwolf@ethereal.net>
Cc: freebsd-questions@freebsd.org, freebsd-net@freebsd.org
Subject: Re: Rate limiting
In-Reply-To: <19990822001221.A94758@ethereal.net>
Message-ID: <Pine.GSO.4.10.9908220840460.2326-100000@server1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Sun, 22 Aug 1999, Jamie Norwood wrote:

> If I am using a FreeBSD box as a firewall, can I set up
> rate-limiting? IE, can I say that news can only use X KB/s, Quake
> can only use Y, and so on? I have a machine I run here that I basically
> want to always have bandwidth, even when I am playing quaake or reading 
> news on my other machine.

Look into dummynet (part of ipfw now, man dummynet) and the ALTQ package
(http://www.csl.sony.co.jp/person/kjc/programs.html) for FreeBSD.

Example usage of dummynet to simulate a 128k ISDN link on <your ip>: 

ipfw pipe 1 config bw 128Kbit/s
ipfw add 1000 pipe 1 ip from <your ip> to any in recv <your interface>
ipfw add 1001 pipe 1 ip from any to <your ip> out xmit <your interface>

---
Mike Wade (mwade@cdc.net)
Director of Systems Administration
CDC Internet, Inc.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Sun Aug 22  6:28:17 1999
Delivered-To: freebsd-net@freebsd.org
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
	by hub.freebsd.org (Postfix) with SMTP
	id D823814D01; Sun, 22 Aug 1999 06:28:09 -0700 (PDT)
	(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA05168; Sun, 22 Aug 1999 12:50:34 +0200
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199908221050.MAA05168@labinfo.iet.unipi.it>
Subject: Re: Rate limiting
To: mwade@cdc.net (Mike Wade)
Date: Sun, 22 Aug 1999 12:50:34 +0200 (MET DST)
Cc: mistwolf@ethereal.net, freebsd-questions@FreeBSD.ORG,
	freebsd-net@FreeBSD.ORG
In-Reply-To: <Pine.GSO.4.10.9908220840460.2326-100000@server1> from "Mike Wade" at Aug 22, 99 08:45:42 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 754       
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> Look into dummynet (part of ipfw now, man dummynet) and the ALTQ package
> (http://www.csl.sony.co.jp/person/kjc/programs.html) for FreeBSD.
> 
> Example usage of dummynet to simulate a 128k ISDN link on <your ip>: 
> 
> ipfw pipe 1 config bw 128Kbit/s
> ipfw add 1000 pipe 1 ip from <your ip> to any in recv <your interface>
> ipfw add 1001 pipe 1 ip from any to <your ip> out xmit <your interface>

nitpicking... but isn't isdn full duplex ? If so you should rather use
two pipes

    ipfw pipe 1 config bw 128Kbit/s queue 30Kbytes
    ipfw pipe 2 config bw 128Kbit/s queue 30Kbytes
    ipfw add 1000 pipe 1 ip from <your ip> to any in recv <your interface>
    ipfw add 1001 pipe 2 ip from any to <your ip> out xmit <your interface>

	cheers
	luigi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Sun Aug 22 17:53: 0 1999
Delivered-To: freebsd-net@freebsd.org
Received: from lily.ezo.net (lily.ezo.net [206.102.130.13])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7BD401545C; Sun, 22 Aug 1999 17:52:49 -0700 (PDT)
	(envelope-from jflowers@ezo.net)
Received: from lily.ezo.net (jflowers@localhost.ezo.net [127.0.0.1])
	by lily.ezo.net (8.8.7/8.8.7) with SMTP id UAA23521;
	Sun, 22 Aug 1999 20:51:15 -0400 (EDT)
Date: Sun, 22 Aug 1999 20:51:14 -0400 (EDT)
From: Jim Flowers <jflowers@ezo.net>
To: freebsd-net@freebsd.org
Cc: freebsd-questions@freebsd.org
Subject: Host Routing with GateD Questions
Message-ID: <Pine.BSI.3.91.990822192512.21079A-100000@lily.ezo.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I would like to arrange a network to provide a means of directing packets 
to one of a pair of routers, depending on the destination address.  
Packets traversing R1 endure SKIP processing, packets traversing R2 are 
subjected to NAT.  When Host B directs packets to R1 they are SKIP 
processed and placed on the private Ethernet.  The packets returning to 
Host B should be directed to R1 to be SKIP processed before being routed 
to the Internet.  The plan is to set the Gateway address for the 
Win95/8/NT hosts to the FR router which has R2 for its default 
route but which learns that the route back to host B is via R1.


  [Host B]
     |
 {Internet}
     |
  [Router]
   RIP II
     |
=================Ethernet (public)
  |      |
[R1]	[R2]
gated   gated
  |      |
=================Ethernet (private)
     |       |
  [Host A]  [FR] Cisco rip 2
   Win 95/8  |
            {Elsewhere}

So far I have not been able to get this to work, although I can verify 
that R1 is advertising routes and the other routers are listening for 
them.  A static route added to R1 just does not show up in the other 
routers.

Can this work?  Can a host route be propagated on the private network? 
What might I be doing wrong? Are the host routes being aggregated with 
the default routes?

Any tips or suggestions will be welcome.

Thanks

Jim Flowers <jflowers@ezo.net>
#4 ISP on C|NET, #1 in Ohio



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Mon Aug 23  8: 7:59 1999
Delivered-To: freebsd-net@freebsd.org
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by hub.freebsd.org (Postfix) with ESMTP id 533A71566D
	for <freebsd-net@freebsd.org>; Mon, 23 Aug 1999 08:07:53 -0700 (PDT)
	(envelope-from itojun@itojun.org)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id AAA06132;
	Tue, 24 Aug 1999 00:06:41 +0900 (JST)
To: "Ettikan Kandasamy" <ettikan@nttmsc.com.my>
Cc: freebsd-net@freebsd.org, snap-users@kame.net
In-reply-to: ettikan's message of Mon, 23 Aug 1999 17:24:12 JST.
      <C82567D6.002E294E.00@NTTMSCCJ02.nttmsc.com.my> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: Ipv6 xplot error 
From: itojun@iijlab.net
Date: Tue, 24 Aug 1999 00:06:41 +0900
Message-ID: <6130.935420801@coconut.itojun.org>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>     I tried to run the xplot fro IPv6 enabled x-windows but gave the following
>error.
> I think the function referred in the library is missing. Any patches for it !!!
>fbsd# xplot
>ld.so failed: Undefined symbol "_in6addr_loopback" in xplot:/usr/X11R6/lib/libX1
>1.so.6.1
>fbsd#

	You'll need to compile libinet6 on compilation of xplot.

itojun


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Mon Aug 23  9:51:28 1999
Delivered-To: freebsd-net@freebsd.org
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by hub.freebsd.org (Postfix) with ESMTP id D7EEF1543A
	for <freebsd-net@freebsd.org>; Mon, 23 Aug 1999 09:51:21 -0700 (PDT)
	(envelope-from kwc@world.std.com)
Received: from world.std.com (root@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id MAA14222
	for <freebsd-net@freebsd.org>; Mon, 23 Aug 1999 12:49:39 -0400 (EDT)
Received: (from kwc@localhost)
	by world.std.com (8.9.3/8.9.3) id MAA24856;
	Mon, 23 Aug 1999 12:44:42 -0400 (EDT)
Date: Mon, 23 Aug 1999 12:44:42 -0400 (EDT)
From: Kenneth W Cochran <kwc@world.std.com>
Message-Id: <199908231644.MAA24856@world.std.com>
To: freebsd-net@freebsd.org
Subject: Kernel ppp error msg in 3.2-stable (CCP)
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hello,

I'm always getting a CCP error (logging at level LOG_ERR) on FreeBSD
3.2-STABLE that I'm not getting (& have never received) with Linux.
In both instances I'm calling the same ISP from the same computer/modem
(just booting different OS).  I believe the "peer" is a 3Com/USR ENH.

Here is the debug log from Linux (Slackware 4.0, pppd-2.3.7, kernel 2.2.11):
----------------------------------------------------------------------------
Aug 14 14:43:21 darkstar pppd[2803]: rcvd [CCP ConfReq id=0x3 < 12 06 00 00 00 01> < 11 05 00 01 03> < 11 06 00 01 01 01>]
Aug 14 14:43:21 darkstar pppd[2803]: sent [CCP ConfReq id=0x1]
Aug 14 14:43:21 darkstar pppd[2803]: sent [CCP ConfRej id=0x3 < 12 06 00 00 00 01> < 11 05 00 01 03> < 11 06 00 01 01 01>]
Aug 14 14:43:21 darkstar pppd[2803]: rcvd [CCP ConfNak id=0x1 < 12 06 00 00 00 01>]
Aug 14 14:43:21 darkstar pppd[2803]: sent [CCP ConfReq id=0x2]
Aug 14 14:43:21 darkstar pppd[2803]: rcvd [CCP TermAck id=0x4]
Aug 14 14:43:21 darkstar pppd[2803]: sent [CCP TermReq id=0x3"No compression negotiated"]
Aug 14 14:43:21 darkstar pppd[2803]: rcvd [CCP TermAck id=0x3]
----------------------------------------------------------------------------

And here is the debug log from FreeBSD 3.2-STABLE (pppd-2.3.5)
(Linux pppd-2.3.5 worked & logged the same as above...)
----------------------------------------------------------------------------
Aug 21 22:54:11 myname pppd[1088]: rcvd [CCP ConfReq id=0x4 < 12 06 00 00 00 01> < 11 05 00 01 03> < 11 06 00 01 01 01>]
Aug 21 22:54:11 myname pppd[1088]: sent [CCP ConfReq id=0x1]
Aug 21 22:54:11 myname pppd[1088]: sent [CCP ConfRej id=0x4 < 12 06 00 00 00 01> < 11 05 00 01 03> < 11 06 00 01 01 01>]
Aug 21 22:54:11 myname pppd[1088]: rcvd [CCP ConfNak id=0x1 < 12 06 00 00 00 01>]
Aug 21 22:54:11 myname pppd[1088]: Received bad configure-nak/rej:  12 06 00 00 00 01
Aug 21 22:54:14 myname pppd[1088]: sent [CCP ConfReq id=0x1]
Aug 21 22:54:14 myname pppd[1088]: rcvd [CCP TermAck id=0x5]
Aug 21 22:54:14 myname pppd[1088]: sent [CCP TermReq id=0x2"No compression negotiated"]
Aug 21 22:54:14 myname pppd[1088]: rcvd [CCP TermAck id=0x2]

----------------------------------------------------------------------------

The "Received bad configure-nak/rej" is what shows up as LOG_ERR.
As far as I understand, the "requested" protocols are MSCP & LZW,
neither of which are supported by Linux or FreeBSD, so both OSes
should properly NAK those requests.  At this time I don't believe
I'm loading any compression modules in Linux.  Am I looking at a
"glitch" in Linux's pppd, FreeBSD's pppd, or in that of the "callee"
(peer)?  Any suggestions for workarounds, or maybe a Real Fix?

I suppose I could (& maybe should) put something like "noccp" in
the options, but I'm not sure if that option is designed for
this kind of glitch...  :)

Many thanks,

-kc


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Mon Aug 23  9:59:36 1999
Delivered-To: freebsd-net@freebsd.org
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by hub.freebsd.org (Postfix) with ESMTP id AAD061543A
	for <freebsd-net@freebsd.org>; Mon, 23 Aug 1999 09:59:31 -0700 (PDT)
	(envelope-from itojun@itojun.org)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id BAA08329
	for <freebsd-net@freebsd.org>; Tue, 24 Aug 1999 01:59:26 +0900 (JST)
To: freebsd-net@freebsd.org
Subject: differences in member name
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
From: itojun@iijlab.net
Date: Tue, 24 Aug 1999 01:59:26 +0900
Message-ID: <8327.935427566@coconut.itojun.org>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

	sorry I made a typo.

itojun

------- Forwarded Message

To: tech-net@netbsd.org, freebsd-net@netbsd.org
Subject: differences in member name
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
From: itojun@iijlab.net
Date: Tue, 24 Aug 1999 01:56:05 +0900
Message-ID: <8224.935427365@coconut.itojun.org>
Sender: itojun@coconut.itojun.org

	I'm working on KAME code which shares most of sys/netinet6 code
	among all *BSDs.  I find it VERY irritating (and tend to introduce
	bugs) to make #ifdef for some of very trivial differences among BSDs.
	One of very good exapmle is if_list/if_link member in struct ifnet.

	NetBSD: if_list, net/if.h
	FreeBSD: if_link, net/if_var.h (moved from net/if.h)
	OpenBSD: if_list, net/if.h (since it was inherited from NetBSD)

	Could anyone tell me why the difference is introduced?
	If either of them is more authentic than others, is there any
	chance for synchronization?

	For if_list/if_link, changes are introduced in the following version:
NetBSD:
http://www.jp.netbsd.org/cgi-bin/cvsweb.cgi/syssrc/sys/net/if.h.diff?r1=1.16&r2=1.17
FreeBSD:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/net/if.h.diff?r1=1.39&r2=1.40

	My fundamental question is, why do people work on *BSDs needs to waste
	their time on this kind of tiny (but very irritating) twists.
	Other researchers/hackers find it troublesome.

itojun
NOTE: BSDI4 is still using if_next (not queue.h) so I omitted it
from the above example.  When BSDI4 changes it in the future, I hope
them try to use common member name.

------- End of Forwarded Message



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Mon Aug 23 11:27:18 1999
Delivered-To: freebsd-net@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id 2A7F315784
	for <freebsd-net@FreeBSD.ORG>; Mon, 23 Aug 1999 11:27:11 -0700 (PDT)
	(envelope-from julian@whistle.com)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
	by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id LAA03583;
	Mon, 23 Aug 1999 11:24:27 -0700 (PDT)
Date: Mon, 23 Aug 1999 11:26:06 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
To: itojun@iijlab.net
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: differences in member name
In-Reply-To: <8327.935427566@coconut.itojun.org>
Message-ID: <Pine.BSF.3.95.990823112127.7316A-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

If you can make a patch of things you'd like to see changed 
for compatibility, I'm sure that there would be a high probability that
we would acce[t them. The names of elements (and similar things are not
set in stone if there is a good reason for a change, and
compatibility is a good reason.) The if_var.h question has been gone over
many times and reverting it to if.h is unlikely.

On Tue, 24 Aug 1999 itojun@iijlab.net wrote:

> 	sorry I made a typo.
> 
> itojun
> 
> ------- Forwarded Message
> 
> To: tech-net@netbsd.org, freebsd-net@netbsd.org
> Subject: differences in member name
> X-Template-Reply-To: itojun@itojun.org
> X-Template-Return-Receipt-To: itojun@itojun.org
> X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
> From: itojun@iijlab.net
> Date: Tue, 24 Aug 1999 01:56:05 +0900
> Message-ID: <8224.935427365@coconut.itojun.org>
> Sender: itojun@coconut.itojun.org
> 
> 	I'm working on KAME code which shares most of sys/netinet6 code
> 	among all *BSDs.  I find it VERY irritating (and tend to introduce
> 	bugs) to make #ifdef for some of very trivial differences among BSDs.
> 	One of very good exapmle is if_list/if_link member in struct ifnet.
> 
> 	NetBSD: if_list, net/if.h
> 	FreeBSD: if_link, net/if_var.h (moved from net/if.h)
> 	OpenBSD: if_list, net/if.h (since it was inherited from NetBSD)
> 
> 	Could anyone tell me why the difference is introduced?
> 	If either of them is more authentic than others, is there any
> 	chance for synchronization?
> 
> 	For if_list/if_link, changes are introduced in the following version:
> NetBSD:
> http://www.jp.netbsd.org/cgi-bin/cvsweb.cgi/syssrc/sys/net/if.h.diff?r1=1.16&r2=1.17
> FreeBSD:
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/net/if.h.diff?r1=1.39&r2=1.40
> 
> 	My fundamental question is, why do people work on *BSDs needs to waste
> 	their time on this kind of tiny (but very irritating) twists.
> 	Other researchers/hackers find it troublesome.
> 
> itojun
> NOTE: BSDI4 is still using if_next (not queue.h) so I omitted it
> from the above example.  When BSDI4 changes it in the future, I hope
> them try to use common member name.
> 
> ------- End of Forwarded Message
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-net" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Mon Aug 23 11:43:31 1999
Delivered-To: freebsd-net@freebsd.org
Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122])
	by hub.freebsd.org (Postfix) with SMTP id E58B514FB4
	for <freebsd-net@freebsd.org>; Mon, 23 Aug 1999 11:43:25 -0700 (PDT)
	(envelope-from gchung@microsoft.com)
Received: from 157.54.9.103 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 23 Aug 1999 11:42:13 -0700 (Pacific Daylight Time)
Received: by INET-IMC-04 with Internet Mail Service (5.5.2524.0)
	id <RJ5QRSQS>; Mon, 23 Aug 1999 11:42:13 -0700
Message-ID: <C35556591D34D111BB5600805F1961B910ECC138@RED-MSG-47>
From: George Chung <gchung@microsoft.com>
To: "'freebsd-net@freebsd.org'" <freebsd-net@freebsd.org>
Subject: 3 newbie Q's on routes for multicast addresses
Date: Mon, 23 Aug 1999 11:42:11 -0700
X-Mailer: Internet Mail Service (5.5.2524.0)
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Platform: FreeBSD 3.2

1. On a private network with no routers, I have to manually add a route for
multicast addresses in order to send UDP packets to that address. I don't
have to do this on a "normal" network (InterNIC assigned network address,
properly connected to Internet). What protocol is running on the latter
network that allows to FreeBSD boxes to automatically set up routes for
multicast addresses?

2. When I manually add a route for a multicast address, I use the following
command:

route add -net 225.0.0.1 -netmask 255.0.0.0 -interface 10.100.100.100

Although this works, I'm not so sure about the semantics of the netmask. It
seems that a netmask of 224.0.0.0 is also legit, but I wouldn't know how to
explain the difference between using one over the other. What does a netmask
for a class D address really mean?

3. Can someone point out the man pages for automatically adding this route
at boot up time?

Thanks very much,
George Chung



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Mon Aug 23 14:53:26 1999
Delivered-To: freebsd-net@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id DAA391575B
	for <freebsd-net@FreeBSD.ORG>; Mon, 23 Aug 1999 14:53:19 -0700 (PDT)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id RAA23164;
	Mon, 23 Aug 1999 17:52:12 -0400 (EDT)
	(envelope-from wollman)
Date: Mon, 23 Aug 1999 17:52:12 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199908232152.RAA23164@khavrinen.lcs.mit.edu>
To: George Chung <gchung@microsoft.com>
Cc: "'freebsd-net@freebsd.org'" <freebsd-net@FreeBSD.ORG>
Subject: 3 newbie Q's on routes for multicast addresses
In-Reply-To: <C35556591D34D111BB5600805F1961B910ECC138@RED-MSG-47>
References: <C35556591D34D111BB5600805F1961B910ECC138@RED-MSG-47>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

<<On Mon, 23 Aug 1999 11:42:11 -0700, George Chung <gchung@microsoft.com> said:

> route add -net 225.0.0.1 -netmask 255.0.0.0 -interface 10.100.100.100

> Although this works, I'm not so sure about the semantics of the
> netmask.

It shouldn't work, since netmasks should be contiguous and you've
created one that isn't.  However, the radix tree is a fairly flexible
data structure, so it's possible that all you've done is slow your
routing computation down a little bit.

The correct command would be:

route add -net 225.0.0.1 -netmask 255.255.255.255 -interface 10.100.100.100

(assuming you only care about this one multicast group) or:

route add -net 224.0.0.0 -netmask 0xf0000000 -interface 10.100.100.100

(if you want all muticasts in general to go out the same way).

> It seems that a netmask of 224.0.0.0 is also legit, but I wouldn't
> know how to explain the difference between using one over the
> other. What does a netmask for a class D address really mean?

The same thing a netmask for any other address means!

An address/mask pair (V, M) matches any address Vx such that
(V & M) == (Vx & M).

> 3. Can someone point out the man pages for automatically adding this route
> at boot up time?

rc.conf(5).

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA|                     - Susan Aglukark and Chad Irschick


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Mon Aug 23 17:34:26 1999
Delivered-To: freebsd-net@freebsd.org
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by hub.freebsd.org (Postfix) with ESMTP id 8E2AE14E78
	for <freebsd-net@FreeBSD.ORG>; Mon, 23 Aug 1999 17:34:16 -0700 (PDT)
	(envelope-from itojun@itojun.org)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id JAA14138;
	Tue, 24 Aug 1999 09:32:17 +0900 (JST)
To: Julian Elischer <julian@whistle.com>
Cc: freebsd-net@FreeBSD.ORG, tech-net@netbsd.org
In-reply-to: julian's message of Mon, 23 Aug 1999 11:26:06 MST.
      <Pine.BSF.3.95.990823112127.7316A-100000@current1.whistle.com> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: differences in member name 
From: itojun@iijlab.net
Date: Tue, 24 Aug 1999 09:32:17 +0900
Message-ID: <14136.935454737@coconut.itojun.org>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>If you can make a patch of things you'd like to see changed 
>for compatibility, I'm sure that there would be a high probability that
>we would acce[t them. The names of elements (and similar things are not
>set in stone if there is a good reason for a change, and
>compatibility is a good reason.)

	Sure I will.  Thanks.

>The if_var.h question has been gone over
>many times and reverting it to if.h is unlikely.

	Hmm, okay,

itojun


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Mon Aug 23 20:39: 7 1999
Delivered-To: freebsd-net@freebsd.org
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by hub.freebsd.org (Postfix) with ESMTP id 3D12D14F33
	for <freebsd-net@FreeBSD.ORG>; Mon, 23 Aug 1999 20:38:51 -0700 (PDT)
	(envelope-from itojun@itojun.org)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id MAA17181;
	Tue, 24 Aug 1999 12:37:51 +0900 (JST)
To: snap-users@kame.net
Cc: freebsd-net@FreeBSD.ORG
In-reply-to: ettikan's message of Tue, 24 Aug 1999 11:32:28 JST.
      <C82567D7.000DF5AE.00@NTTMSCCJ02.nttmsc.com.my> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (KAME-snap 1110) Problem with kame 3.1 
From: itojun@iijlab.net
Date: Tue, 24 Aug 1999 12:37:50 +0900
Message-ID: <17179.935465870@coconut.itojun.org>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>I'm using FreeBSD 3.2 with kame-19990517-fbsd31-release on my dell notebook. Had
> this problem
>when tried compiling kame.
>Any patch... or suggestions ???

	Why are you mixing versions? (KAME kit for FreeBSD31 on FreeBSD32)
	FreeBSD31 and 32 are very different and we are unable to help you.

itojun


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Mon Aug 23 23:28:37 1999
Delivered-To: freebsd-net@freebsd.org
Received: from giasbm01.vsnl.net.in (giasbm01.vsnl.net.in [202.54.1.18])
	by hub.freebsd.org (Postfix) with ESMTP
	id BEC4D14EBE; Mon, 23 Aug 1999 23:28:09 -0700 (PDT)
	(envelope-from rhtiwari@cygsoft.com)
Received: from surya.vyom.com (IDENT:root@[202.54.125.22])
	by giasbm01.vsnl.net.in (8.9.2/8.9.2) with ESMTP id LAA28872;
	Tue, 24 Aug 1999 11:57:46 +0530 (IST)
Received: from ratnakar (ratna [10.1.1.62]) by surya.vyom.com (8.8.7/8.6.12) with SMTP id RAA15599; Mon, 23 Aug 1999 17:01:22 +0300
Message-ID: <003001beed5a$dffd1fa0$3e01010a@ratnakar>
From: "Ratnakar Tiwari" <rhtiwari@cygsoft.com>
To: <freebsd-net@FreeBSD.ORG>, <freebsd-ipfw@FreeBSD.ORG>,
	<freebsd-hackers@FreeBSD.ORG>
Subject: Unable to locate function body: ip_nat_init()
Date: Mon, 23 Aug 1999 17:00:16 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002D_01BEED88.F98AA220"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

This is a multi-part message in MIME format.

------=_NextPart_000_002D_01BEED88.F98AA220
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
  I am going through the networking code for the stable release.
  In the file ip_input.c  there is a call to a function ip_nat_init() in =
the function
  ip_init(). However I have been unable to locate the code for this =
function (ip_nat_init()).

  Could somebody please tell me in which file is this function defined?


  Also in the file ip_input.c a function pointer ip_nat_ptr is =
dereferenced in the function ip_input.c
  However I could not locate where this function pointer is being =
initialized. Could somebody please
  tell me where this pointer is being initialized?

Thanks in advance.
Ratnakarprasad Tiwari

------=_NextPart_000_002D_01BEED88.F98AA220
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#d0d0c8>
<DIV><FONT color=3D#000000 size=3D2>Hi,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>&nbsp; I am going through the =
networking code=20
for the stable release.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>&nbsp; In the file ip_input.c&nbsp; =
there is a=20
call to a function ip_nat_init() in the function</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>&nbsp; ip_init(). However I have =
been unable to=20
locate the code for this function (ip_nat_init()).</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>&nbsp; Could somebody please tell me =
in which=20
file is this function defined?</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>&nbsp; Also in the file ip_input.c a =
function=20
pointer ip_nat_ptr is dereferenced in the function =
ip_input.c</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>&nbsp; However I could not locate =
where this=20
function pointer is being initialized. Could somebody =
please</FONT></DIV>
<DIV><FONT size=3D2>&nbsp; tell me where this pointer is being=20
initialized?</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Thanks in advance.</FONT></DIV>
<DIV><FONT size=3D2>Ratnakarprasad Tiwari</FONT></DIV></BODY></HTML>

------=_NextPart_000_002D_01BEED88.F98AA220--



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Mon Aug 23 23:29:48 1999
Delivered-To: freebsd-net@freebsd.org
Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2])
	by hub.freebsd.org (Postfix) with ESMTP id 9C14415967
	for <net@FreeBSD.ORG>; Mon, 23 Aug 1999 23:29:13 -0700 (PDT)
	(envelope-from ross@gilliam.users.flyingcroc.net)
Received: (from ross@localhost)
	by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04889;
	Mon, 23 Aug 1999 23:28:30 -0700 (PDT)
Date: Wed, 18 Aug 1999 13:22:00 -0700 (PDT)
Message-Id: <199908240628.XAA04889@gilliam.users.flyingcroc.net>
From: Julian Elischer <julian@whistle.com>
To: net@FreeBSD.ORG
Subject: [Fwd: Samba 2.0.5 on FreeBSD 3.1-RELEASE - very very slow writing to Samba from win98] (fwd)
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Ok, here is a problem....
Samba (the newest version) has slowed down on FreeBSD by an order of
magnitude. The cnage that was made was to replace soem read() calls from
sockets to recv() calls, and making use of the MSG_WAITALL flag.
Under alltheother Unix versions, (inc linux) this has resulted in a
smaller number of syscalls. They don't want to have a #ifdef __FreeBSD__
in the sources so they have asked for help in isolating the problem.

Here is a piece of email that details some specifics...

anyone have any ideas?

I looked at the code in soreceive() and it doesn't seem to have changed
for ages, and (to brief inspection) seems to be correct. (as regards to 
MSG_WAITALL anyhow).

julian


---------- Forwarded message ----------
Date: Wed, 18 Aug 1999 09:17:42 -0700
From: Jeremy Allison <jallison@cthulhu.engr.sgi.com>
To: Julian Elischer <julian@whistle.com>
Subject: [Fwd: Samba 2.0.5 on FreeBSD 3.1-RELEASE - very very slow writing to Samba from win98]

Julian - confirmation it's the MSG_WAITALL flag that's
causing the problem.

Jeremy.

Johan Kerckaert wrote:
> 
> Hi,
> 
> Jeremy Allison wrote:
> > Ok, thanks for the confirmation. Now I nweed to work out
> > with the FreeBSD guys why this change has such a great
> > effect. It may be that the use of the MSG_WAITALL flag in
> > the recv() call is causing problems.
> 
> Indeed, I tried replacing the MSG_WAITALL flag with 0 in the recv () calls,
> in util_sock.c, and then it's ok
> Using recv calls is also faster than using read calls:
> I got 1.3 Mb/s using read, 1.6 Mb/s using recv () with no flags, on a 100 Mbit
> crossover.
> 
>   Kind regards,
> --
>     Johan Kerckaert
>     BricsNet

-- 
--------------------------------------------------------
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
--------------------------------------------------------



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Tue Aug 24  9:30:21 1999
Delivered-To: freebsd-net@freebsd.org
Received: from maine.60north.net (maine.60north.net [198.143.201.10])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4734215939; Tue, 24 Aug 1999 09:28:00 -0700 (PDT)
	(envelope-from ankzt@maine.60north.net)
Received: from localhost (ankzt@localhost)
	by maine.60north.net (8.9.3/8.9.2) with ESMTP id LAA01403;
	Tue, 24 Aug 1999 11:05:12 -0400 (EDT)
	(envelope-from ankzt@maine.60north.net)
Date: Tue, 24 Aug 1999 11:05:12 -0400 (EDT)
From: Bill <ankzt@maine.60north.net>
To: questions@freebsd.org
Cc: freebsd-net@freebsd.org
Subject: cvsup'd to 3.2 from 3.1 arp changes? SMB changes!
Message-ID: <Pine.BSF.4.05.9908240951190.1258-100000@maine.60north.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


 after upgrading from 3.1 stable to 3.2 stable via cvs I noticed that the
output from arp -a has changed... looks like for the better as now I dont
have to permenat publish my gateway of last resort ( wich would always
drop or expire after extend periods of no use ). A bad side affect wich I
cant be sure what in this update is responcible for is, workstations on
remote networks fail to authenticate ( log on to NT domain ) via samba. 
The version of samba im using is 2.0.3. My networks look like this... 

 Inet pipe 198.143.201/24 -> FBSD multihomed two net cards ipforwarding. 
FBSD Interfaces are ed1 @ 192.168.1.10 ed2 @ 198.143.201.10. This box
is connected to 2 other networks 192.168.2/24 & 192.168.3/24 via bay
routers. All workstations on 192.168.1/24 that are configured to require
validation from network happily do so, however since the 3.1 to 3.2
upgrade the workstations on the remote networks wont validate with samba. 
Remote network connectivity is verified, routers are configured for
spanning tree bridging & netbios over tcp. 
 
 Whats particularly interesting about this is that when i reconfig the MS
workstations not to authenticate & login to NT domain, they can see &
access the FBSD box running samba using USER level security as well as
access their home directories with the correct priveledges. Im stumped. 

Heres a dump of the relevant globals from testparm:

su-2.02# ./testparm | more
Load smb config files from /usr/local/samba/lib/smb.conf
Processing section "[root]"
Processing section "[ports]"
Processing section "[homes]"
Processing section "[netlogon]"
Processing section "[printers]"
Processing section "[tmp]"
Loaded services file OK.
Load smb config files from /usr/local/samba/lib/smb.conf
Press enter to see a dump of your service definitions
# Global parameters
	workgroup = MIS
	netbios name = MAINE
	netbios aliases = 
	server string = INTERNET SERVER FIREWALL
	interfaces = 192.168.1.10 198.143.201.10
	bind interfaces only = No
	security = USER
	encrypt passwords = No
	update encrypted = No
	use rhosts = No
	min passwd length = 5
	map to guest = Never
	null passwords = No
	password server = 
	smb passwd file = /usr/local/samba/private/smbpasswd
	hosts equiv = 
	root directory = /
	passwd program = /bin/passwd
	passwd chat = *old*password* %o\n *new*password* %n\n *new*password* %n\n *changed*
	passwd chat debug = No
	username map = 
	password level = 0
	username level = 0
	unix password sync = Yes
	log level = 2
	syslog = 1
	syslog only = No
	log file = /usr/local/samba/var/log.%m
	max log size = 50
	timestamp logs = Yes
	protocol = NT1
	read bmpx = Yes
	read raw = Yes
	write raw = Yes
	nt smb support = Yes
	nt pipe support = Yes
	nt acl support = No
	announce version = 4.2
	announce as = NT
	max mux = 50
	max xmit = 65535
	name resolve order = lmhosts host wins bcast
	max packet = 65535
	max ttl = 259200
	max wins ttl = 518400
	min wins ttl = 21600
	time server = No
	change notify timeout = 60
	deadtime = 0
	getwd cache = Yes
	keepalive = 300
	lpq cache time = 10
	max disk size = 0
	max open files = 10000
	read prediction = No
	read size = 16384
	shared mem size = 1048576
	socket options = TCP_NODELAY
	stat cache size = 50
	load printers = Yes
	printcap name = /etc/printcap
	printer driver file = /usr/local/samba/lib/printers.def
	strip dot = No
	character set = 
	mangled stack = 50
	coding system = 
	client code page = 850
	stat cache = Yes
	domain groups = 
	domain admin group = 
	domain guest group = 
	domain admin users = 
	domain guest users = 
	machine password timeout = 604800
	add user script = 
	delete user script = 
	logon script = 
	logon path = \\%N\%U\profile
	logon drive = 
	logon home = \\%N\%U
	domain logons = Yes
	os level = 0
	lm announce = Auto
	lm interval = 60
	preferred master = No
	local master = No
	domain master = No
	browse list = Yes
	dns proxy = No
	wins proxy = Yes
	wins server = 192.168.1.15
	wins support = No
	kernel oplocks = Yes
	ole locking compatibility = Yes
	smbrun = /usr/local/samba/bin/smbrun
	config file = 
	preload = 
	lock dir = /usr/local/samba/var/locks
	default service = 
	message command = 
	dfree command = 
	valid chars = 
	remote announce = 
	remote browse sync = 
	socket address = 0.0.0.0
	homedir map = 
	time offset = 0
	unix realname = No
	NIS homedir = No
	panic action = 
	comment = 
	path = 
	alternate permissions = No
	revalidate = No
	username = 
	guest account = pcguest
	invalid users = 
	valid users = 
	admin users = 
	read list = 
	write list = 
	force user = 
	force group = 
	read only = Yes
	create mask = 0744
	force create mode = 00
	directory mask = 0755
	force directory mode = 00
	guest only = No
	guest ok = No
	only user = No
	hosts allow = 192.168.1. 192.168.2.  192.168.3. 127.
	hosts deny = 
	status = Yes
	max connections = 0
	min print space = 0
	strict sync = No
	sync always = No
	print ok = No
	postscript = No
	printing = bsd
	print command = lpr -r -P%p %s
	lpq command = lpq -P%p
	lprm command = lprm -P%p %j
	lppause command = 
	lpresume command = 
	queuepause command = 
	queueresume command = 
	printer name = 
	printer driver = NULL
	printer driver location = 
	default case = lower
	case sensitive = No
	preserve case = Yes
	short preserve case = Yes
	mangle case = No
	mangling char = ~
	hide dot files = Yes
	delete veto files = No
	veto files = 
	hide files = 
	veto oplock files = 
	map system = No
	map hidden = No
	map archive = Yes
	mangled names = Yes
	mangled map = 
	browseable = Yes
	blocking locks = Yes
	fake oplocks = No
	locking = Yes
	oplocks = Yes
	strict locking = No
	share modes = Yes
	copy = 
	include = 
	exec = 
	postexec = 
	root preexec = 
	root postexec = 
	available = Yes
	volume = 
	fstype = NTFS
	set directory = No
	wide links = Yes
	follow symlinks = Yes
	dont descend = 
	magic script = 
	magic output = 
	delete readonly = No
	dos filetimes = No
	dos filetime resolution = No
	fake directory create times = No

ps sorry if ive encluded a bit to much information. 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Wed Aug 25 12:31:22 1999
Delivered-To: freebsd-net@freebsd.org
Received: from maine.60north.net (maine.60north.net [198.143.201.10])
	by hub.freebsd.org (Postfix) with ESMTP
	id 69DED14ECF; Wed, 25 Aug 1999 12:31:01 -0700 (PDT)
	(envelope-from ankzt@maine.60north.net)
Received: from localhost (ankzt@localhost)
	by maine.60north.net (8.9.3/8.9.2) with ESMTP id PAA48085;
	Wed, 25 Aug 1999 15:30:22 -0400 (EDT)
	(envelope-from ankzt@maine.60north.net)
Date: Wed, 25 Aug 1999 15:30:22 -0400 (EDT)
From: Bill <ankzt@maine.60north.net>
To: freebsd-questions@freebsd.org
Cc: freebsd-net@freebsd.org
Subject: 3.2 Stable & ARP changes. 
Message-ID: <Pine.BSF.4.05.9908251500300.48041-100000@maine.60north.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


 Hi there, I run a server with two eathernet interfaces. 
One of the interfaces serves our unregistered networks - 192.168/16 and
the other is connected to our public ip space 198.146.203/24. The router
(cisco 2600) has the IP of 198.146.203.5, the default route of the BSD box
in question. Whats happening is I will loose connectivity to that (the
cisco's) ip address, however, it still shows up in my routing table with a
hardware address as well as the arp table with the correct MAC address. 
Pre 3.2 stable (3.1 stable) this would happen but I would loose all
reference to the address' in both the routing & arp table, this was fixed
by arp -s ipaddr macaddr PUB. What Ive noticed now is that when i try to
permenantly publish the ip & mac of the routers ethernet interface, arp -a
doesnt show it as (permenant published) but as [eathernet]. 

 The temporary fix for this siduation has been just to re arp -S ipaddr
macaddr, but it continues to sporatically loose connectivity. Another
peice to this puzzle is that both eathernet interfaces are plugged into
the same hub, this causes me to continually recieve console messages
stating kernel ipaddr is on ed1 but got reply from macaddr on ed2. I
really dont think that the kernel messages matter but it would be nice to
get rid of them. The ARP issue is big though, I have the crontab entry
from HE!! to re arp the routers ethernet interface every 5 mins. 
thanks for any & all help. 
    



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Thu Aug 26 20:46: 6 1999
Delivered-To: freebsd-net@freebsd.org
Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227])
	by hub.freebsd.org (Postfix) with ESMTP
	id C2FB715293; Thu, 26 Aug 1999 20:45:59 -0700 (PDT)
	(envelope-from jlemon@americantv.com)
Received: from right.PCS (right.PCS [148.105.10.31])
	by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id WAA28651;
	Thu, 26 Aug 1999 22:45:57 -0500 (CDT)
Received: (from jlemon@localhost)
	by right.PCS (8.8.5/8.6.4) id WAA29828;
	Thu, 26 Aug 1999 22:45:56 -0500 (CDT)
Message-ID: <19990826224556.04405@right.PCS>
Date: Thu, 26 Aug 1999 22:45:56 -0500
From: Jonathan Lemon <jlemon@americantv.com>
To: net@freebsd.org, committers@freebsd.org
Subject: Call for Review: TCP timer changes
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.61.1
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


This patch does the following:
   
        1. eliminates the fast/slow timeout lists for TCP and instead    
           uses a callout entry for each timer.
        2. Increases the TCP timer granularity to 10ms                  
        3. Implements "bad retransmit" recovery, as presented in
           "On Estimating End-to-End Network Path Properties", by
            Allman and Paxson.                                  

It has been used for a while in various places, and I'd like to 
invite more comments before committing it to -current.  The patches
are at http://www.freebsd.org/~jlemon.  Be sure to read the notes
at the top of the patch as well.
--
Jonathan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Thu Aug 26 21:12:19 1999
Delivered-To: freebsd-net@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP
	id 840CA154B4; Thu, 26 Aug 1999 21:12:15 -0700 (PDT)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id AAA04392;
	Fri, 27 Aug 1999 00:11:59 -0400 (EDT)
	(envelope-from wollman)
Date: Fri, 27 Aug 1999 00:11:59 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199908270411.AAA04392@khavrinen.lcs.mit.edu>
To: net@FreeBSD.ORG, committers@FreeBSD.ORG
Subject: Call for Review: TCP timer changes
In-Reply-To: <19990826224556.04405@right.PCS>
References: <19990826224556.04405@right.PCS>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

<<On Thu, 26 Aug 1999 22:45:56 -0500, Jonathan Lemon <jlemon@americantv.com> said:

> It has been used for a while in various places, and I'd like to 
> invite more comments before committing it to -current.

I'm particularly interesting in hearing from Alpha users.  There might
be a few places where the size of a variable was adequate to make the
transition from 2 Hz to 100 Hz timer ticks that would overflow for
1024 Hz timer ticks, although the one possible problem that I thought
of (RFC 1323 PAWS) turned out not to be a problem.

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA|                     - Susan Aglukark and Chad Irschick


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message


From owner-freebsd-net  Thu Aug 26 21:30:28 1999
Delivered-To: freebsd-net@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id 5FCD514F64
	for <net@FreeBSD.org>; Thu, 26 Aug 1999 21:30:25 -0700 (PDT)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id AAA04468;
	Fri, 27 Aug 1999 00:30:21 -0400 (EDT)
	(envelope-from wollman)
Date: Fri, 27 Aug 1999 00:30:21 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
To: net@FreeBSD.org
Subject: Call for Review: TCP timer changes
In-Reply-To: <199908270411.AAA04392@khavrinen.lcs.mit.edu>
Message-Id: <199908270419.AAA04425@khavrinen.lcs.mit.edu>
References: <19990826224556.04405@right.PCS>
	<199908270411.AAA04392@khavrinen.lcs.mit.edu>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

[Resending to -net after typo fix...]

<<On Fri, 27 Aug 1999 00:11:59 -0400 (EDT), I wrote:

> I'm particularly interesting in hearing from Alpha users.

Another area which might need further investigation is better tuning
of ncallout and callwheelsize.  Right now, the callout wheel is sized
on the assumption that there will only ever be `ncallout' callouts
active simultaneously.  (This is not a correctness constraint, but
affects efficiency.)  This means that the most efficient operation
for machines with large numbers of outstanding TCP connections will
likely require a partial decoupling of the two; since TCP allocates
its own callout structures, high values of ncallout would needlessly
waste memory.

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA|                     - Susan Aglukark and Chad Irschick


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message