From owner-freebsd-net  Sun Feb 20  8:30:35 2000
Delivered-To: freebsd-net@freebsd.org
Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14])
	by hub.freebsd.org (Postfix) with ESMTP id 2B71137BEBD
	for <freebsd-net@FreeBSD.ORG>; Sun, 20 Feb 2000 08:30:33 -0800 (PST)
	(envelope-from dermot@mcnally.de)
Received: from TIGGER (p3E9ED0CE.dip.t-dialin.net [62.158.208.206])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id IAA08516;
	Sun, 20 Feb 2000 08:29:05 -0800 (PST)
Message-Id: <4.2.0.58.20000220172816.00a38778@tim>
X-Sender: dermot@tim
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Sun, 20 Feb 2000 17:32:06 +0100
To: Brian Somers <brian@Awfulhak.org>
From: Dermot McNally <dermot@mcnally.de>
Subject: Solved: NAT with PPPoE problems (was: NAT issues with ppp)
Cc: freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org
In-Reply-To: <200002170051.AAA01707@hak.lan.Awfulhak.org>
References: <Message from Dermot McNally <dermot@mcnally.de>
 <4.2.0.58.20000215233615.02334c30@tim>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 00:51 17.02.2000 +0000, Brian Somers wrote:

>If it still happens with the latest verison, can you also try
>decreasing your network MTU to 1492 (or maybe even 1400 for kicks).
>This would stop IP fragmentation - it shouldn't make a difference,
>but, well....

OK, I've got it working now. Your suggestion to limit the MTU was the key. 
I tried 1400 on all the local boxes (pausing only briefly to find out how 
the !@#* to do this on Windows 2000) and all was well. It's odd that things 
didn't work with IP fragmentation, but I'm glad, on the whole, that they 
didn't, since stopping the fragmentation probably makes everything work 
more efficiently anyway.

Thanks,
Dermot


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


From owner-freebsd-net  Sun Feb 20  8:52:10 2000
Delivered-To: freebsd-net@freebsd.org
Received: from mail2.atl.bellsouth.net (mail2.atl.bellsouth.net [205.152.0.22])
	by hub.freebsd.org (Postfix) with ESMTP id 2E6E737BCAD
	for <freebsd-net@freebsd.org>; Sun, 20 Feb 2000 08:52:08 -0800 (PST)
	(envelope-from corigan@mindspring.com)
Received: from daskip (ifitl-214-101-203.atl.bellsouth.net [209.214.101.203] (may be forged))
	by mail2.atl.bellsouth.net (3.3.5alt/0.75.2) with SMTP id LAA22103;
	Sun, 20 Feb 2000 11:52:03 -0500 (EST)
Message-ID: <000f01bf7bc3$3a8cac00$0100a8c0@zeist.sweb.com>
From: "Corigan" <corigan@mindspring.com>
To: "Dermot McNally" <dermot@mcnally.de>
Cc: <freebsd-net@freebsd.org>
References: <Message from Dermot McNally <dermot@mcnally.de><4.2.0.58.20000215233615.02334c30@tim> <4.2.0.58.20000220172816.00a38778@tim>
Subject: Re: Solved: NAT with PPPoE problems (was: NAT issues with ppp)
Date: Sun, 20 Feb 2000 11:55:01 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


> OK, I've got it working now. Your suggestion to limit the MTU was the key.
> I tried 1400 on all the local boxes (pausing only briefly to find out how
> the !@#* to do this on Windows 2000) and all was well. It's odd that
things
> didn't work with IP fragmentation, but I'm glad, on the whole, that they
> didn't, since stopping the fragmentation probably makes everything work
> more efficiently anyway.

I've never really had a problem with the -nat command of ppp and my PPPoE
connection except that the http pages will not load up.  I just assume this
is cause of apache and setup a little proxy.  If it isn't, I wonder what is
up with that.  Glas to see you got it working friend.

Corigan



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


From owner-freebsd-net  Sun Feb 20  9:23:25 2000
Delivered-To: freebsd-net@freebsd.org
Received: from proxy4.ba.best.com (proxy4.ba.best.com [206.184.139.15])
	by hub.freebsd.org (Postfix) with ESMTP id AAC8A37BEB0
	for <freebsd-net@FreeBSD.ORG>; Sun, 20 Feb 2000 09:23:22 -0800 (PST)
	(envelope-from dermot@mcnally.de)
Received: from TIGGER (p3E9ECFC2.dip.t-dialin.net [62.158.207.194])
	by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id JAA00121;
	Sun, 20 Feb 2000 09:22:16 -0800 (PST)
Message-Id: <4.2.0.58.20000220182204.00a4f7d0@tim>
X-Sender: dermot@tim
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Sun, 20 Feb 2000 18:25:18 +0100
To: "Corigan" <corigan@mindspring.com>
From: Dermot McNally <dermot@mcnally.de>
Subject: Re: Solved: NAT with PPPoE problems (was: NAT issues with ppp)
Cc: <freebsd-net@FreeBSD.ORG>
In-Reply-To: <000f01bf7bc3$3a8cac00$0100a8c0@zeist.sweb.com>
References: <Message from Dermot McNally <dermot@mcnally.de>
 <4.2.0.58.20000215233615.02334c30@tim>
 <4.2.0.58.20000220172816.00a38778@tim>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 11:55 20.02.2000 -0500, Corigan wrote:

>I've never really had a problem with the -nat command of ppp and my PPPoE
>connection except that the http pages will not load up.

Well, this _is_ a problem, no? The whole point of NAT is that it's supposed 
to allow arbitrary connections through your gateway, and once HTTP fails, 
you can't tell what else might also go wrong. For me, HTTP was the most 
important and most noticeable failure, but there were others.

>   I just assume this
>is cause of apache and setup a little proxy.

No, simply having Apache installed on your gateway can't cause this 
problem. But as you say, a proxy will go some way to fixing it...

>   If it isn't, I wonder what is
>up with that.  Glas to see you got it working friend.

It looks like your problem is the same as mine. Try reducing the MTU on all 
of your local network interfaces. I used a setting of 1400 and everything 
now works the way I expect.

Dermot



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


From owner-freebsd-net  Sun Feb 20  9:45:52 2000
Delivered-To: freebsd-net@freebsd.org
Received: from mail.snickers.org (mail.snickers.org [216.126.90.4])
	by hub.freebsd.org (Postfix) with ESMTP id 399C137BEC5
	for <freebsd-net@freebsd.org>; Sun, 20 Feb 2000 09:45:50 -0800 (PST)
	(envelope-from josh@snickers.org)
Received: by mail.snickers.org (Postfix, from userid 1037)
	id 9F3993D84; Sun, 20 Feb 2000 12:45:44 -0500 (EST)
Date: Sun, 20 Feb 2000 12:45:44 -0500
From: Josh Tiefenbach <josh@zipperup.org>
To: Corigan <corigan@mindspring.com>
Cc: Dermot McNally <dermot@mcnally.de>, freebsd-net@freebsd.org
Subject: Re: Solved: NAT with PPPoE problems (was: NAT issues with ppp)
Message-ID: <20000220124544.A11945@snickers.org>
References: <Message <dermot@mcnally.de><4.2.0.58.20000215233615.02334c30@tim> <4.2.0.58.20000220172816.00a38778@tim> <000f01bf7bc3$3a8cac00$0100a8c0@zeist.sweb.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <000f01bf7bc3$3a8cac00$0100a8c0@zeist.sweb.com>
Organization: Hah
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> I've never really had a problem with the -nat command of ppp and my PPPoE
> connection except that the http pages will not load up.

I noticed this problem as well (at least with machines behind the NAT
gateway). The problem would be that you'd get pretty much the headers and the
first couple of lines from the page before the connection would hang.

I personally suspected that there was some evil interaction between my NAT
gateway and the transparent proxying that my provider does. Setting up squid
on the gateway solved the problem.

Just as a data point, the same behavior is evidenced in both ppp -nat and
using ipnat (part of IPFilter v3.3.8 in -current).

And just for the record, I tried reducing the MTU on the machine behind the
gateway, and things 'worked'. Interesting.

josh

-- 
Give me rampant intellectualism as a coping strategy!
                                   -- Chuck Palahniuk in Invisible Monsters


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


From owner-freebsd-net  Sun Feb 20 12: 8:41 2000
Delivered-To: freebsd-net@freebsd.org
Received: from awfulhak.org (dynamic-106.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.234])
	by hub.freebsd.org (Postfix) with ESMTP id 90F9737BED6
	for <freebsd-net@FreeBSD.ORG>; Sun, 20 Feb 2000 12:08:29 -0800 (PST)
	(envelope-from brian@Awfulhak.org)
Received: from hak.lan.Awfulhak.org (root@shift.lan.awfulhak.org [172.16.0.12])
	by awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA42834;
	Sun, 20 Feb 2000 20:08:07 GMT
	(envelope-from brian@hak.lan.Awfulhak.org)
Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1])
	by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA80998;
	Sun, 20 Feb 2000 20:07:56 GMT
	(envelope-from brian@hak.lan.Awfulhak.org)
Message-Id: <200002202007.UAA80998@hak.lan.Awfulhak.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Dermot McNally <dermot@mcnally.de>
Cc: Brian Somers <brian@Awfulhak.org>, freebsd-net@FreeBSD.ORG,
	brian@hak.lan.Awfulhak.org, brian@hak.lan.Awfulhak.org
Subject: Re: Solved: NAT with PPPoE problems (was: NAT issues with ppp) 
In-Reply-To: Message from Dermot McNally <dermot@mcnally.de> 
   of "Sun, 20 Feb 2000 17:32:06 +0100." <4.2.0.58.20000220172816.00a38778@tim> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 20 Feb 2000 20:07:56 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> At 00:51 17.02.2000 +0000, Brian Somers wrote:
> 
> >If it still happens with the latest verison, can you also try
> >decreasing your network MTU to 1492 (or maybe even 1400 for kicks).
> >This would stop IP fragmentation - it shouldn't make a difference,
> >but, well....
> 
> OK, I've got it working now. Your suggestion to limit the MTU was the key. 
> I tried 1400 on all the local boxes (pausing only briefly to find out how 
> the !@#* to do this on Windows 2000) and all was well. It's odd that things 
> didn't work with IP fragmentation, but I'm glad, on the whole, that they 
> didn't, since stopping the fragmentation probably makes everything work 
> more efficiently anyway.

I'll look into this - this is definitely a problem.  Thanks.

> Thanks,
> Dermot
> 

-- 
Brian <brian@Awfulhak.org>                        <brian@FreeBSD.org>
      <http://www.Awfulhak.org>                   <brian@OpenBSD.org>
Don't _EVER_ lose your sense of humour !          <brian@FreeBSD.org.uk>




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


From owner-freebsd-net  Mon Feb 21  2: 8: 4 2000
Delivered-To: freebsd-net@freebsd.org
Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id D224D37B960; Mon, 21 Feb 2000 02:07:58 -0800 (PST)
	(envelope-from asmodai@lucifer.bart.nl)
Received: (from asmodai@localhost)
	by lucifer.bart.nl (8.9.3/8.9.3) id LAA83901;
	Mon, 21 Feb 2000 11:07:52 +0100 (CET)
	(envelope-from asmodai)
Date: Mon, 21 Feb 2000 11:07:52 +0100
From: Jeroen Ruigrok van der Werven <asmodai@bart.nl>
To: freebsd-current@freebsd.org
Cc: freebsd-net@freebsd.org, diablo-list@list.bart.nl
Subject: Panic (TCP)
Message-ID: <20000221110752.A83583@lucifer.bart.nl>
Reply-To: freebsd-current@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Organisation: bART Internet Services B.V.
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Well,

this is fun...

Just caught panic #3 on my Diablo newstransit box running 4.0 from the
7th of February.

This box pushes around 360-380 GB in a weekend on network IO.

panic: tcp_setpersist: retransmit pending
Debugger("panic")
Stopped at      Debugger+0x35:  movb    $0,in_Debugger.354

db> trace
Debugger(c01e8063) at Debugger+0x35
panic(c01eddc0,d5ce6b60,d8d8bc48,c018bcb6,d5ce6b60) at panic+0x70
tcp_setpersist(d5ce6b60,d5ce6b60,c018bc24,d8d8bc6c,c0149279) at
tcp_setpersist+0x2c
tcp_timer_persist(d5ce6b60,40000000,160,c1cd0000,cdfae000) at
tcp_timer_persist+0x92
softclock(0,c0160010,cc4d0010,cc4d0010,cdfae000) at softclock+0xd1
doreti_swi(c1d7d000,50b0,2000) at doreti_swi+0xf
ffs_reallocblks(d8d8be04) at ffs_reallocblks+0x3d0
cluster_write(cc5213e8,4332000,0) at cluster_write+0x15a
ffs_write(d8d8bea0,d8cf79c0,fdc,c1f14800,c0201e80) at ffs_write+0x476
vn_write(c1f14800,d8d8beec,c1d30500,0,d8cf79c0) at vn_write+0xda
dofilewrite(d8cf79c0,c1f14800,6,280be020,fdc) at dofilewrite+0x91
write(d8cf79c0,d8d8bf80,280be000,15,280be000) at write+0x33
syscall(bfbf002f,280a002f,bfbf002f,280be000,15) at syscall+0x176
Xint0x80_syscall() at Xint0x80_syscall+0x26

This is from the serial console.  I'm going to dump the memory to swap
now and do some gdb with my kernel.debug.

Advice is wanted and highly appreciated.

-- 
Jeroen Ruigrok van der Werven          Network- and systemadministrator
<asmodai@bart.nl>                      bART Internet Services /
BSD: Technical excellence at its best  VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70          http://www.bart.nl


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


From owner-freebsd-net  Mon Feb 21  2:55:49 2000
Delivered-To: freebsd-net@freebsd.org
Received: from mail.di.uminho.pt (mail.di.uminho.pt [193.136.20.67])
	by hub.freebsd.org (Postfix) with SMTP id 9ED4637B960
	for <freebsd-net@freebsd.org>; Mon, 21 Feb 2000 02:55:44 -0800 (PST)
	(envelope-from jose@di.uminho.pt)
Received: (qmail 29838 invoked from network); 21 Feb 2000 11:12:10 -0000
Received: from bogalhinho.di.uminho.pt (HELO di.uminho.pt) (jose@193.136.20.38)
  by mail.di.uminho.pt with SMTP; 21 Feb 2000 11:12:10 -0000
Message-ID: <38B12866.5756FE2B@di.uminho.pt>
Date: Mon, 21 Feb 2000 11:58:30 +0000
From: =?iso-8859-1?Q?Jos=E9=20Lu=EDs?= Faria <jose@di.uminho.pt>
Organization: Universidade do Minho-Departamento de =?iso-8859-1?Q?Inform=E1tica?=
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-net@freebsd.org
Subject: Kernel
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hello 

I'm creating a litle update to a freebsd 3.4 kernel.
My program is for account some data: number of
packets by class, number of packets dropped by class, etc.
Now I need to pass this values to another program wich in X-Window
display this values on-line. After, I want to save this values
in a file.

I need some docs about how I can do this.
Which are the primitives in the kernel to do this.
I use the printf to put this data in /var/log/messages.
This inappropriate, I dont want this. This is only for testing now.

Can you help me ?

Thank you very much.


P.S. I'm sorry my english.



-- 

  :) cumprimentos
--------------------------------
  Jose Luis Faria
  Administrador de Sistemas
  Universidade do Minho - Departamento de Informática
  Campus de Gualtar
  4710-057 Braga
  Portugal
  tel.: +351 253604440 Fax:+351 253604471
  http://admin.di.uminho.pt/~jose


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


From owner-freebsd-net  Mon Feb 21  3:12:35 2000
Delivered-To: freebsd-net@freebsd.org
Received: from pouet.noc.fr.clara.net (headache.noc.fr.clara.net [212.43.195.29])
	by hub.freebsd.org (Postfix) with ESMTP
	id EE9E537BC00; Mon, 21 Feb 2000 03:12:30 -0800 (PST)
	(envelope-from sameh@fr.clara.net)
Received: by pouet.noc.fr.clara.net (Postfix, from userid 1000)
	id EF1D3298; Mon, 21 Feb 2000 12:12:46 +0100 (CET)
Date: Mon, 21 Feb 2000 12:12:46 +0100
From: Sameh Ghane <sameh@fr.clara.net>
To: freebsd-current@FreeBSD.ORG
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: Panic (TCP)
Message-ID: <20000221121246.F18727@noc.fr.clara.net>
References: <20000221110752.A83583@lucifer.bart.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000221110752.A83583@lucifer.bart.nl>; from asmodai@bart.nl on Mon, Feb 21, 2000 at 11:07:52AM +0100
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Le Mon, Feb 21, 2000 at 11:07:52AM +0100, Jeroen Ruigrok van der Werven écrivit:
> Well,
> 
> this is fun...
> 
> Just caught panic #3 on my Diablo newstransit box running 4.0 from the
> 7th of February.
> 
> This box pushes around 360-380 GB in a weekend on network IO.
> 
> panic: tcp_setpersist: retransmit pending
> Debugger("panic")
> Stopped at      Debugger+0x35:  movb    $0,in_Debugger.354

This is interesting as we use 4.0 on a transit nntp server also, running diablo.

We have 60GB IN/OUT each day, and it runs fine:

$ uptime
12:09PM  up 46 days, 17:19, 1 user, load averages: 0.62, 0.66, 0.64

4.0-CURRENT FreeBSD 4.0-CURRENT #4: Wed Jan  5 14:36:46 CET 2000

Try downgrading ?

-- 
Sameh Ghane


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


From owner-freebsd-net  Mon Feb 21  3:35:23 2000
Delivered-To: freebsd-net@freebsd.org
Received: from proxy.outblaze.com (proxy.outblaze.com [202.77.223.120])
	by hub.freebsd.org (Postfix) with SMTP id E2AF737B6BA
	for <freebsd-net@freebsd.org>; Mon, 21 Feb 2000 03:35:15 -0800 (PST)
	(envelope-from yusufg@outblaze.com)
Received: (qmail 58896 invoked from network); 21 Feb 2000 11:35:08 -0000
Received: from unknown (HELO yusufg.portal2.com) (202.77.223.114)
  by proxy.outblaze.com with SMTP; 21 Feb 2000 11:35:08 -0000
Received: (qmail 386 invoked by uid 500); 21 Feb 2000 11:35:04 -0000
Date: 21 Feb 2000 11:35:04 -0000
Message-ID: <20000221113504.385.qmail@yusufg.portal2.com>
From: Yusuf Goolamabbas <yusufg@outblaze.com>
To: freebsd-stable@freebd.org, freebsd-net@freebsd.org
Subject: Understanding ifconfig output
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Here's some sample output from one of my machines (3.4-stable) which
has an Intel EEPro 100 attached to a Bay 350 switch

fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
<ip address deleted>
ether 00:90:27:8d:49:7b
media: autoselect (100baseTX <full-duplex>) status: active
supported media: autoselect 100baseTX <full-duplex> 100baseTX
10baseT/UTP <full-duplex> 10baseT/UTP

My question is , does SIMPLEX mean that the card is in half duplex
mode, However the media line seems to indicate that the connection to
the swithc is full duplex

What is the recommended way to determine link speed from a machine to
a hub/switch. (e.g A colo provider claims that there is 100 Mbit card
in the box and one would want to verify that)

Regards, Yusuf



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


From owner-freebsd-net  Mon Feb 21  3:36:29 2000
Delivered-To: freebsd-net@freebsd.org
Received: from proxy.outblaze.com (proxy.outblaze.com [202.77.223.120])
	by hub.freebsd.org (Postfix) with SMTP id F361137BC13
	for <freebsd-net@freebsd.org>; Mon, 21 Feb 2000 03:36:25 -0800 (PST)
	(envelope-from yusufg@outblaze.com)
Received: (qmail 58939 invoked from network); 21 Feb 2000 11:36:20 -0000
Received: from unknown (HELO yusufg.portal2.com) (202.77.223.114)
  by proxy.outblaze.com with SMTP; 21 Feb 2000 11:36:20 -0000
Received: (qmail 399 invoked by uid 500); 21 Feb 2000 11:36:15 -0000
Date: 21 Feb 2000 11:36:15 -0000
Message-ID: <20000221113615.398.qmail@yusufg.portal2.com>
From: Yusuf Goolamabbas <yusufg@outblaze.com>
To: freebsd-stable@freebsd.org, freebsd-net@freebsd.org
Subject: Understanding ifconfig output
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Sorry, typo in address in earlier post. Posting again

Here's some sample output from one of my machines (3.4-stable) which
has an Intel EEPro 100 attached to a Bay 350 switch

fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
<ip address deleted>
ether 00:90:27:8d:49:7b
media: autoselect (100baseTX <full-duplex>) status: active
supported media: autoselect 100baseTX <full-duplex> 100baseTX
10baseT/UTP <full-duplex> 10baseT/UTP

My question is , does SIMPLEX mean that the card is in half duplex
mode, However the media line seems to indicate that the connection to
the swithc is full duplex

What is the recommended way to determine link speed from a machine to
a hub/switch. (e.g A colo provider claims that there is 100 Mbit card
in the box and one would want to verify that)

Regards, Yusuf



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


From owner-freebsd-net  Mon Feb 21  3:39:27 2000
Delivered-To: freebsd-net@freebsd.org
Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8156337BC2B; Mon, 21 Feb 2000 03:39:21 -0800 (PST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from m5.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway)
	id UAA04827; Mon, 21 Feb 2000 20:39:19 +0900 (JST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master)
	id UAA15500; Mon, 21 Feb 2000 20:39:18 +0900 (JST)
Received: from localhost (dhcp25.pkt.ts.fujitsu.co.jp [10.36.204.25]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id UAA00279; Mon, 21 Feb 2000 20:39:17 +0900 (JST)
To: asmodai@bart.nl
Cc: sameh@fr.clara.net
Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG
Subject: Re: Panic (TCP)
In-Reply-To: <20000221121246.F18727@noc.fr.clara.net>
References: <20000221110752.A83583@lucifer.bart.nl>
	<20000221121246.F18727@noc.fr.clara.net>
X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN)
X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000221204008M.shin@nd.net.fujitsu.co.jp>
Date: Mon, 21 Feb 2000 20:40:08 +0900
From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 29
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> > Just caught panic #3 on my Diablo newstransit box running 4.0 from the
> > 7th of February.

> We have 60GB IN/OUT each day, and it runs fine:
> 
> $ uptime
> 12:09PM  up 46 days, 17:19, 1 user, load averages: 0.62, 0.66, 0.64
> 
> 4.0-CURRENT FreeBSD 4.0-CURRENT #4: Wed Jan  5 14:36:46 CET 2000
> 
> Try downgrading ?

Wmmm, there were much changes to tcp code for IPv6 support after Jan 5.

I reviewed tcp_setpersist related code and such problem not
seems to happen in correct state.
Might there be incorrect memory over writing?

Do you have any other date, such as *tt_persist value at
panic?

And is there any other person who experienced same kind of
problem and have any hints to diagnose this?

I'll again review my changes.

Thanks,
Yoshinobu Inoue



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


From owner-freebsd-net  Mon Feb 21  3:50:25 2000
Delivered-To: freebsd-net@freebsd.org
Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6D77337BDC1; Mon, 21 Feb 2000 03:50:17 -0800 (PST)
	(envelope-from asmodai@lucifer.bart.nl)
Received: (from asmodai@localhost)
	by lucifer.bart.nl (8.9.3/8.9.3) id MAA84857;
	Mon, 21 Feb 2000 12:50:10 +0100 (CET)
	(envelope-from asmodai)
Date: Mon, 21 Feb 2000 12:50:10 +0100
From: Jeroen Ruigrok van der Werven <asmodai@bart.nl>
To: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
Cc: sameh@fr.clara.net, freebsd-current@FreeBSD.ORG,
	freebsd-net@FreeBSD.ORG
Subject: Re: Panic (TCP)
Message-ID: <20000221125010.H84100@lucifer.bart.nl>
References: <20000221110752.A83583@lucifer.bart.nl> <20000221121246.F18727@noc.fr.clara.net> <20000221204008M.shin@nd.net.fujitsu.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000221204008M.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Mon, Feb 21, 2000 at 08:40:08PM +0900
Organisation: bART Internet Services B.V.
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

-On [20000221 12:45], Yoshinobu Inoue (shin@nd.net.fujitsu.co.jp) wrote:
>> > Just caught panic #3 on my Diablo newstransit box running 4.0 from the
>> > 7th of February.
>
>> We have 60GB IN/OUT each day, and it runs fine:
>> 
>> $ uptime
>> 12:09PM  up 46 days, 17:19, 1 user, load averages: 0.62, 0.66, 0.64
>> 
>> 4.0-CURRENT FreeBSD 4.0-CURRENT #4: Wed Jan  5 14:36:46 CET 2000
>> 
>> Try downgrading ?
>
>Wmmm, there were much changes to tcp code for IPv6 support after Jan 5.
>
>I reviewed tcp_setpersist related code and such problem not
>seems to happen in correct state.
>Might there be incorrect memory over writing?

How you mean?

>Do you have any other date, such as *tt_persist value at
>panic?

This is gdb -k /kernel.debug /var/crash/vmcore.0:

GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 2625536
initial pcb at 21cb00
panicstr: from debugger
panic messages:
---
panic: tcp_setpersist: retransmit pending
panic: from debugger
Uptime: 2d20h34m30s
amrd0: still open, can't shutdown

dumping to dev #da/0x20001, offset 524312
dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495
494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477
476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459
458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441
440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423
422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405
404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387
386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369
368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351
350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333
332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315
314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297
296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279
278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 262 261
260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243
242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225
224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207
206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189
188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171
170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153
152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135
134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117
116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99
98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75
74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51
50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27
26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 
---
#0  boot (howto=260) at ../../kern/kern_shutdown.c:304
304                     dumppcb.pcb_cr3 = rcr3();

(kgdb) backtrace
#0  boot (howto=260) at ../../kern/kern_shutdown.c:304
#1  0xc0143f59 in panic (fmt=0xc01e2894 "from debugger")
    at ../../kern/kern_shutdown.c:554
#2  0xc01245c1 in db_panic (addr=-1071885851, have_addr=0, count=-1, 
    modif=0xd8d8bac0 "") at ../../ddb/db_command.c:433
#3  0xc0124561 in db_command (last_cmdp=0xc020447c, cmd_table=0xc02042dc, 
    aux_cmd_tablep=0xc021917c) at ../../ddb/db_command.c:333
#4  0xc0124626 in db_command_loop () at ../../ddb/db_command.c:455
#5  0xc012673f in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71
#6  0xc01c4f89 in kdb_trap (type=3, code=0, regs=0xd8d8bbc8)
    at ../../i386/i386/db_interface.c:158
#7  0xc01d05dc in trap (frame={tf_fs = 16, tf_es = -1053687792, 
      tf_ds = -1072168944, tf_edi = 1073741824, tf_esi = 256, 
      tf_ebp = -656884720, tf_isp = -656884748, tf_ebx = -1071718976, 
      tf_edx = 1073872896, tf_ecx = 1021, tf_eax = 18, tf_trapno = 3, 
      tf_err = 0, tf_eip = -1071885851, tf_cs = 8, tf_eflags = 582, 
      tf_esp = -1071667873, tf_ss = -1071742877}) at ../../i386/i386/trap.c:531
#8  0xc01c51e5 in Debugger (msg=0xc01e8063 "panic") at machine/cpufunc.h:64
#9  0xc0143f50 in panic (fmt=0xc01eddc0 "tcp_setpersist: retransmit pending")
    at ../../kern/kern_shutdown.c:552
#10 0xc018abc4 in tcp_setpersist (tp=0xd5ce6b60)
    at ../../netinet/tcp_output.c:893
#11 0xc018bcb6 in tcp_timer_persist (xtp=0xd5ce6b60)
    at ../../netinet/tcp_timer.c:337
#12 0xc0149279 in softclock () at ../../kern/kern_timeout.c:131
#13 0xc01c6c9b in doreti_swi ()
#14 0xc0194658 in ffs_reallocblks (ap=0xd8d8be04)
    at ../../ufs/ffs/ffs_alloc.c:525
#15 0xc016961a in cluster_write (bp=0xcc5213e8, filesize=70459392)
    at vnode_if.h:1056
#16 0xc019ac02 in ffs_write (ap=0xd8d8bea0) at ../../ufs/ufs/ufs_readwrite.c:495
#17 0xc0173d22 in vn_write (fp=0xc1f14800, uio=0xd8d8beec, cred=0xc1d30500, 
    flags=0, p=0xd8cf79c0) at vnode_if.h:363
#18 0xc0150e5d in dofilewrite (p=0xd8cf79c0, fp=0xc1f14800, fd=6, 
    buf=0x280be020, nbyte=4060, offset=-1, flags=0) at ../../sys/file.h:156
#19 0xc0150d63 in write (p=0xd8cf79c0, uap=0xd8d8bf80)
    at ../../kern/sys_generic.c:298
#20 0xc01d0e7e in syscall (frame={tf_fs = -1078001617, tf_es = 671744047, 
      tf_ds = -1078001617, tf_edi = 671866880, tf_esi = 21, 
      tf_ebp = -1077971400, tf_isp = -656883756, tf_ebx = 671866880, 
      tf_edx = 0, tf_ecx = 0, tf_eax = 4, tf_trapno = 0, tf_err = 2, 
      tf_eip = 134595120, tf_cs = 31, tf_eflags = 514, tf_esp = -1077971444, 
      tf_ss = 47}) at ../../i386/i386/trap.c:1055
#21 0xc01c5886 in Xint0x80_syscall ()
#22 0x804ed66 in ?? ()
#23 0x804c18e in ?? ()
#24 0x804abaf in ?? ()
#25 0x804983d in ?? ()
#26 0x80490c5 in ?? ()
---Type <return> to continue, or q <return> to quit---
#27 0x8048829 in ?? ()
#28 0x80480f9 in ?? ()

>And is there any other person who experienced same kind of
>problem and have any hints to diagnose this?

I am updating the box as we speak to sources of today (which btw don't
seem to like a -j4 flag).

>I'll again review my changes.

Not sure if needed.  But I felt the reason to pipe up about this because
if it is a genuine bug stil in the system we need to get it out of the
system ASAP.

Debugging tips are welcome, since I am not the biggest bulb wrt
debugging.

-- 
Jeroen Ruigrok van der Werven          Network- and systemadministrator
<asmodai@bart.nl>                      bART Internet Services /
BSD: Technical excellence at its best  VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70          http://www.bart.nl


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


From owner-freebsd-net  Mon Feb 21  4:26:13 2000
Delivered-To: freebsd-net@freebsd.org
Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37])
	by hub.freebsd.org (Postfix) with ESMTP
	id 076C837BBFC; Mon, 21 Feb 2000 04:26:08 -0800 (PST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from m3.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway)
	id VAA15904; Mon, 21 Feb 2000 21:26:06 +0900 (JST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master)
	id VAA23590; Mon, 21 Feb 2000 21:26:05 +0900 (JST)
Received: from localhost (dhcp25.pkt.ts.fujitsu.co.jp [10.36.204.25]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id VAA01467; Mon, 21 Feb 2000 21:26:05 +0900 (JST)
To: asmodai@bart.nl
Cc: sameh@fr.clara.net, freebsd-current@FreeBSD.ORG,
	freebsd-net@FreeBSD.ORG
Subject: Re: Panic (TCP)
In-Reply-To: <20000221125010.H84100@lucifer.bart.nl>
References: <20000221121246.F18727@noc.fr.clara.net>
	<20000221204008M.shin@nd.net.fujitsu.co.jp>
	<20000221125010.H84100@lucifer.bart.nl>
X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN)
X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000221212656L.shin@nd.net.fujitsu.co.jp>
Date: Mon, 21 Feb 2000 21:26:56 +0900
From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 36
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> >Might there be incorrect memory over writing?
> 
> How you mean?

I think one possibility of the problem is that some code is
incorrectly overwriting some part of the memory, and a tcpcb's
tt_persist->c_flags is happen to overwritten.

Now I am very much interested in the value of
tp->tt_persist->c_flags at panic, if CALLOUT_PENDING and
possibly other flags are just set, or completely broken data
is written on it.

And if later, I am also interested in other values around
tp->tt_persist->c_flags, to check what kind of value is
written around there.

> Debugging tips are welcome, since I am not the biggest bulb wrt
> debugging.

I am not also, and you might have already known these things,
but in case they are useful,

  -If DDB is specified in kernel config file, and all src/sys
   tree including sys/compile dir is saved onto another
   machine, it will be very useful at next panic, because remote GDB
   debugging is available by those data.

   (Though if the bug happens at very delicate timing, it
   might prevent the bug from happening again.)
   
  -Adding some printfs in tcp_output.c:tcp_setpersist() panic
   case might be useful.

Thanks,
Yoshinobu Inoue


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


From owner-freebsd-net  Mon Feb 21  4:47:44 2000
Delivered-To: freebsd-net@freebsd.org
Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7121137BBCB; Mon, 21 Feb 2000 04:47:30 -0800 (PST)
	(envelope-from asmodai@lucifer.bart.nl)
Received: (from asmodai@localhost)
	by lucifer.bart.nl (8.9.3/8.9.3) id NAA93976;
	Mon, 21 Feb 2000 13:47:24 +0100 (CET)
	(envelope-from asmodai)
Date: Mon, 21 Feb 2000 13:47:24 +0100
From: Jeroen Ruigrok van der Werven <asmodai@bart.nl>
To: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
Cc: sameh@fr.clara.net, freebsd-current@FreeBSD.ORG,
	freebsd-net@FreeBSD.ORG
Subject: Re: Panic (TCP)
Message-ID: <20000221134724.J84100@lucifer.bart.nl>
References: <20000221121246.F18727@noc.fr.clara.net> <20000221204008M.shin@nd.net.fujitsu.co.jp> <20000221125010.H84100@lucifer.bart.nl> <20000221212656L.shin@nd.net.fujitsu.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000221212656L.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Mon, Feb 21, 2000 at 09:26:56PM +0900
Organisation: bART Internet Services B.V.
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

-On [20000221 13:30], Yoshinobu Inoue (shin@nd.net.fujitsu.co.jp) wrote:
>> >Might there be incorrect memory over writing?
>> 
>> How you mean?
>
>I think one possibility of the problem is that some code is
>incorrectly overwriting some part of the memory, and a tcpcb's
>tt_persist->c_flags is happen to overwritten.

Hmmm, this box is a real disk io and network io bastard.  It serves as a
newspeer transit box based on diablo 1.27 with a fxp card and an amr
array.  Let me know if a dmesg is needed.

>Now I am very much interested in the value of
>tp->tt_persist->c_flags at panic, if CALLOUT_PENDING and
>possibly other flags are just set, or completely broken data
>is written on it.

(kgdb) up 10
#10 0xc018abc4 in tcp_setpersist (tp=0xd5ce6b60)
    at ../../netinet/tcp_output.c:893
warning: Source file is more recent than executable.

893
(kgdb) print tp->tt_persist->c_flags
$1 = 0

[I am upgrading the box to the latest sources as we speak, hence the
sourcecode is newer]

>And if later, I am also interested in other values around
>tp->tt_persist->c_flags, to check what kind of value is
>written around there.

(kgdb) print tp->tt_persist         
$2 = (struct callout *) 0xd5ce6c44
(kgdb) print *(tp->tt_persist)
$3 = {c_links = {sle = {sle_next = 0x0}, tqe = {tqe_next = 0x0, 
      tqe_prev = 0xcc401640}}, c_time = 22275044, c_arg = 0xd5ce6b60, 
  c_func = 0, c_flags = 0}

>> Debugging tips are welcome, since I am not the biggest bulb wrt
>> debugging.
>
>I am not also, and you might have already known these things,
>but in case they are useful,
>
>  -If DDB is specified in kernel config file, and all src/sys
>   tree including sys/compile dir is saved onto another
>   machine, it will be very useful at next panic, because remote GDB
>   debugging is available by those data.

I have a serial console active so I can do DDB from my workstation.

Hence I always have a kernel and kernel.debug from the same sources.

>   (Though if the bug happens at very delicate timing, it
>   might prevent the bug from happening again.)
>   
>  -Adding some printfs in tcp_output.c:tcp_setpersist() panic
>   case might be useful.

It might.

-- 
Jeroen Ruigrok van der Werven          Network- and systemadministrator
<asmodai@bart.nl>                      bART Internet Services /
BSD: Technical excellence at its best  VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70          http://www.bart.nl


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


From owner-freebsd-net  Mon Feb 21  4:59:19 2000
Delivered-To: freebsd-net@freebsd.org
Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6C8D337BAE7; Mon, 21 Feb 2000 04:59:15 -0800 (PST)
	(envelope-from asmodai@lucifer.bart.nl)
Received: (from asmodai@localhost)
	by lucifer.bart.nl (8.9.3/8.9.3) id NAA94103;
	Mon, 21 Feb 2000 13:59:13 +0100 (CET)
	(envelope-from asmodai)
Date: Mon, 21 Feb 2000 13:59:13 +0100
From: Jeroen Ruigrok van der Werven <asmodai@bart.nl>
To: Sameh Ghane <sameh@fr.clara.net>
Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG
Subject: Re: Panic (TCP)
Message-ID: <20000221135913.L84100@lucifer.bart.nl>
References: <20000221110752.A83583@lucifer.bart.nl> <20000221121246.F18727@noc.fr.clara.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 1.0i
In-Reply-To: <20000221121246.F18727@noc.fr.clara.net>; from sameh@fr.clara.net on Mon, Feb 21, 2000 at 12:12:46PM +0100
Organisation: bART Internet Services B.V.
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

-On [20000221 12:15], Sameh Ghane (sameh@fr.clara.net) wrote:
>Le Mon, Feb 21, 2000 at 11:07:52AM +0100, Jeroen Ruigrok van der Werven écrivit:
>> Just caught panic #3 on my Diablo newstransit box running 4.0 from the
>> 7th of February.

My first two were ffs related.  And I hadn't enabled DDB and dumpdev back
then =\
No soft-updates.

>> This box pushes around 360-380 GB in a weekend on network IO.
>> 
>> panic: tcp_setpersist: retransmit pending
>> Debugger("panic")
>> Stopped at      Debugger+0x35:  movb    $0,in_Debugger.354
>
>This is interesting as we use 4.0 on a transit nntp server also, running diablo.
>
>We have 60GB IN/OUT each day, and it runs fine:

60 GB is our daily incoming feed. ;)
And add to that between 90-120 GB outgoing a day.

>$ uptime
>12:09PM  up 46 days, 17:19, 1 user, load averages: 0.62, 0.66, 0.64

Nice.

I am currently preprocessing the messages with cleanfeed which causes my
average to be something like 3.xx 3.xx 3.xx

>4.0-CURRENT FreeBSD 4.0-CURRENT #4: Wed Jan  5 14:36:46 CET 2000
>
>Try downgrading ?

No thanks, I want 4.0 to be bugfree, not work around the problem. ;)

-- 
Jeroen Ruigrok van der Werven          Network- and systemadministrator
<asmodai@bart.nl>                      bART Internet Services /
BSD: Technical excellence at its best  VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70          http://www.bart.nl


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


From owner-freebsd-net  Mon Feb 21  5:34:19 2000
Delivered-To: freebsd-net@freebsd.org
Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36])
	by hub.freebsd.org (Postfix) with ESMTP
	id DEBA237BC79; Mon, 21 Feb 2000 05:34:13 -0800 (PST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from m5.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway)
	id WAA07413; Mon, 21 Feb 2000 22:34:10 +0900 (JST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master)
	id WAA17034; Mon, 21 Feb 2000 22:34:10 +0900 (JST)
Received: from localhost (dhcp25.pkt.ts.fujitsu.co.jp [10.36.204.25]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id WAA03283; Mon, 21 Feb 2000 22:34:08 +0900 (JST)
To: asmodai@bart.nl
Cc: sameh@fr.clara.net, freebsd-current@FreeBSD.ORG,
	freebsd-net@FreeBSD.ORG
Subject: Re: Panic (TCP)
In-Reply-To: <20000221134724.J84100@lucifer.bart.nl>
References: <20000221125010.H84100@lucifer.bart.nl>
	<20000221212656L.shin@nd.net.fujitsu.co.jp>
	<20000221134724.J84100@lucifer.bart.nl>
X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN)
X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000221223459W.shin@nd.net.fujitsu.co.jp>
Date: Mon, 21 Feb 2000 22:34:59 +0900
From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 14
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> >Now I am very much interested in the value of
> >tp->tt_persist->c_flags at panic, if CALLOUT_PENDING and
> >possibly other flags are just set, or completely broken data
> >is written on it.
> 
> 893
> (kgdb) print tp->tt_persist->c_flags
> $1 = 0

Woops sorry I was worng.
tp->tt_rexmt->c_flags is actually causing the panic, and the
necessary data is the contents of the tp->tt_rexmt->c_flags.

Yoshinobu Inoue


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


From owner-freebsd-net  Mon Feb 21  5:49:12 2000
Delivered-To: freebsd-net@freebsd.org
Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id A513437BC1D; Mon, 21 Feb 2000 05:49:03 -0800 (PST)
	(envelope-from asmodai@lucifer.bart.nl)
Received: (from asmodai@localhost)
	by lucifer.bart.nl (8.9.3/8.9.3) id OAA94506;
	Mon, 21 Feb 2000 14:48:59 +0100 (CET)
	(envelope-from asmodai)
Date: Mon, 21 Feb 2000 14:48:59 +0100
From: Jeroen Ruigrok van der Werven <asmodai@bart.nl>
To: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG
Subject: Re: Panic (TCP)
Message-ID: <20000221144858.O84100@lucifer.bart.nl>
References: <20000221125010.H84100@lucifer.bart.nl> <20000221212656L.shin@nd.net.fujitsu.co.jp> <20000221134724.J84100@lucifer.bart.nl> <20000221223459W.shin@nd.net.fujitsu.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000221223459W.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Mon, Feb 21, 2000 at 10:34:59PM +0900
Organisation: bART Internet Services B.V.
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

-On [20000221 14:40], Yoshinobu Inoue (shin@nd.net.fujitsu.co.jp) wrote:
>> >Now I am very much interested in the value of
>> >tp->tt_persist->c_flags at panic, if CALLOUT_PENDING and
>> >possibly other flags are just set, or completely broken data
>> >is written on it.
>> 
>> 893
>> (kgdb) print tp->tt_persist->c_flags
>> $1 = 0
>
>Woops sorry I was worng.
>tp->tt_rexmt->c_flags is actually causing the panic, and the
>necessary data is the contents of the tp->tt_rexmt->c_flags.

(kgdb) print tp->tt_rexmt->c_flags
$1 = 6

(kgdb) print tp->tt_rexmt         
$2 = (struct callout *) 0xd5ce6c2c

(kgdb) print (*tp->tt_rexmt)
$3 = {c_links = {sle = {sle_next = 0xd5cd7c2c}, tqe = {tqe_next = 0xd5cd7c2c,
      tqe_prev = 0xd5cd83ac}}, c_time = 22275144, c_arg = 0xd5ce6b60, 
  c_func = 0xc018bcdc <tcp_timer_rexmt>, c_flags = 6}

-- 
Jeroen Ruigrok van der Werven          Network- and systemadministrator
<asmodai@bart.nl>                      bART Internet Services /
BSD: Technical excellence at its best  VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70          http://www.bart.nl


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


From owner-freebsd-net  Mon Feb 21  5:52:22 2000
Delivered-To: freebsd-net@freebsd.org
Received: from btm4r4.alcatel.be (btm4r4.alcatel.be [195.207.101.110])
	by hub.freebsd.org (Postfix) with ESMTP id 1F2C037BD81
	for <freebsd-net@freebsd.org>; Mon, 21 Feb 2000 05:52:19 -0800 (PST)
	(envelope-from livensw@rc.bel.alcatel.be)
Received: from btmq9s.rc.bel.alcatel.be (root@btmq9s.rc.bel.alcatel.be [138.203.65.182])
	by btm4r4.alcatel.be (8.9.1a/8.9.1) with ESMTP id OAA03633;
	Mon, 21 Feb 2000 14:51:49 +0100 (MET)
Received: from btm161.rc.bel.alcatel.be (btm161 [138.203.65.238])
	by btmq9s.rc.bel.alcatel.be (8.8.8+Sun/8.8.8) with ESMTP id OAA27301;
	Mon, 21 Feb 2000 14:51:42 +0100 (MET)
Received: (from livensw@localhost)
	by btm161.rc.bel.alcatel.be (8.9.3/8.9.3) id OAA33959;
	Mon, 21 Feb 2000 14:51:41 +0100 (CET)
	(envelope-from livensw)
Date: Mon, 21 Feb 2000 14:51:41 +0100
From: Wim Livens <livensw@rc.bel.alcatel.be>
To: Yusuf Goolamabbas <yusufg@outblaze.com>
Cc: freebsd-net@freebsd.org
Subject: Re: Understanding ifconfig output
Message-ID: <20000221145141.L290@rc.bel.alcatel.be>
References: <20000221113504.385.qmail@yusufg.portal2.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <20000221113504.385.qmail@yusufg.portal2.com>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Mon, Feb 21, 2000 at 11:35:04AM -0000, Yusuf Goolamabbas wrote:
> Here's some sample output from one of my machines (3.4-stable) which
> has an Intel EEPro 100 attached to a Bay 350 switch
> 
> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> <ip address deleted>
> ether 00:90:27:8d:49:7b
> media: autoselect (100baseTX <full-duplex>) status: active
                     ^^^^^^^^^^^^^^^^^^^^^^^ 
This is the info you want---^

I don't know what SIMPLEX means, I use the same card in 100Mb
full-duplex and get similar output.

-- 
Wim Livens.



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


From owner-freebsd-net  Mon Feb 21  6: 5:17 2000
Delivered-To: freebsd-net@freebsd.org
Received: from hydrant.intranova.net (hydrant.intranova.net [209.201.95.10])
	by hub.freebsd.org (Postfix) with SMTP id 2836A37BC63
	for <freebsd-net@freebsd.org>; Mon, 21 Feb 2000 06:04:59 -0800 (PST)
	(envelope-from oogali@intranova.net)
Received: (qmail 4925 invoked from network); 21 Feb 2000 14:04:51 -0000
Received: from localhost (user37805@127.0.0.1)
  by hydrant.intranova.net with SMTP; 21 Feb 2000 14:04:51 -0000
Date: Mon, 21 Feb 2000 09:04:51 -0500 (EST)
From: Omachonu Ogali <oogali@intranova.net>
To: Yusuf Goolamabbas <yusufg@outblaze.com>
Cc: freebsd-stable@freebd.org, freebsd-net@freebsd.org
Subject: Re: Understanding ifconfig output
In-Reply-To: <20000221113504.385.qmail@yusufg.portal2.com>
Message-ID: <Pine.BSF.4.10.10002210846590.790-100000@hydrant.intranova.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Simplex means the Ethernet card can't see its own broadcast packets (I
think), otherwise all the other information shows the card is un
100Base-TX full duplex mode.

On 21 Feb 2000, Yusuf Goolamabbas wrote:

> Here's some sample output from one of my machines (3.4-stable) which
> has an Intel EEPro 100 attached to a Bay 350 switch
> 
> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> <ip address deleted>
> ether 00:90:27:8d:49:7b
> media: autoselect (100baseTX <full-duplex>) status: active
> supported media: autoselect 100baseTX <full-duplex> 100baseTX
> 10baseT/UTP <full-duplex> 10baseT/UTP
> 
> My question is , does SIMPLEX mean that the card is in half duplex
> mode, However the media line seems to indicate that the connection to
> the swithc is full duplex
> 
> What is the recommended way to determine link speed from a machine to
> a hub/switch. (e.g A colo provider claims that there is 100 Mbit card
> in the box and one would want to verify that)
> 
> Regards, Yusuf
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-net" in the body of the message
> 

-- 
+-------------------------------------------------------------------------+
| Omachonu Ogali                                     oogali@intranova.net |
| Intranova Networking Group                 http://tribune.intranova.net |
| PGP Key ID:                                                  0xBFE60839 |
| PGP Fingerprint:       C8 51 14 FD 2A 87 53 D1  E3 AA 12 12 01 93 BD 34 |
+-------------------------------------------------------------------------+



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


From owner-freebsd-net  Mon Feb 21  7:39:45 2000
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 0943937BBA2
	for <freebsd-net@FreeBSD.ORG>; Mon, 21 Feb 2000 07:39:41 -0800 (PST)
	(envelope-from lloyd@brunel.uk1.vbc.net)
Received: from localhost (lloyd@localhost)
	by brunel.uk1.vbc.net (8.9.3/8.9.3) with ESMTP id PAA64530;
	Mon, 21 Feb 2000 15:39:14 GMT
Date: Mon, 21 Feb 2000 15:39:14 +0000 (GMT)
From: Lloyd Rennie <lloyd@vbc.net>
To: Wim Livens <livensw@rc.bel.alcatel.be>
Cc: Yusuf Goolamabbas <yusufg@outblaze.com>, freebsd-net@FreeBSD.ORG
Subject: Re: Understanding ifconfig output
In-Reply-To: <20000221145141.L290@rc.bel.alcatel.be>
Message-ID: <Pine.BSF.4.05.10002211533070.63343-100000@brunel.uk1.vbc.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Mon, 21 Feb 2000, Wim Livens wrote:

> On Mon, Feb 21, 2000 at 11:35:04AM -0000, Yusuf Goolamabbas wrote:
> > Here's some sample output from one of my machines (3.4-stable) which
> > has an Intel EEPro 100 attached to a Bay 350 switch
> > 
> > fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > <ip address deleted>
> > ether 00:90:27:8d:49:7b
> > media: autoselect (100baseTX <full-duplex>) status: active
>                      ^^^^^^^^^^^^^^^^^^^^^^^ 
> This is the info you want---^
> 
> I don't know what SIMPLEX means, I use the same card in 100Mb
> full-duplex and get similar output.

Same here.  The media autoselects FD, but still the simplex flag is set.
*shrug*

> What is the recommended way to determine link speed from a machine to
> a hub/switch. (e.g A colo provider claims that there is 100 Mbit card
> in the box and one would want to verify that)

A fairly foolproof method is to make sure there's a fair amount of traffic
running in both directions, then do a 'netstat -I fxp0 -w1'.  Watch the
collisions - if you see any then it's not FD.

--
Lloyd Rennie                   VBCnet GB Ltd	             lloyd@vbc.net
tel +44 (0) 117 929 1316    http://www.vbc.net    fax +44 (0) 117 927 2015





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


From owner-freebsd-net  Mon Feb 21  8:35:36 2000
Delivered-To: freebsd-net@freebsd.org
Received: from d12lmsgate-3.de.ibm.com (d12lmsgate-3.de.ibm.com [195.212.91.201])
	by hub.freebsd.org (Postfix) with ESMTP id D6C3237BB7F
	for <freebsd-net@FreeBSD.ORG>; Mon, 21 Feb 2000 08:35:30 -0800 (PST)
	(envelope-from DRHAGER@de.ibm.com)
Received: from d12relay01.de.ibm.com (d12relay01.de.ibm.com [9.165.215.22])
	by d12lmsgate-3.de.ibm.com (1.0.0) with ESMTP id RAA66360;
	Mon, 21 Feb 2000 17:34:54 +0100
From: DRHAGER@de.ibm.com
Received: from d12mta01.de.ibm.com (d12mta01_cs0 [9.165.222.237])
	by d12relay01.de.ibm.com (8.8.8m2/NCO v2.06) with SMTP id RAA70806;
	Mon, 21 Feb 2000 17:34:53 +0100
Received: by d12mta01.de.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id C125688C.005B0314 ; Mon, 21 Feb 2000 17:34:05 +0100
X-Lotus-FromDomain: IBMDE
To: livensw@rc.bel.alcatel.be
Cc: yusufg@outblaze.com, freebsd-net@FreeBSD.ORG, lloyd@vbc.net
Message-ID: <C125688C.005AFEF2.00@d12mta01.de.ibm.com>
Date: Mon, 21 Feb 2000 17:33:46 +0100
Subject: Re: Understanding ifconfig output
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org



The SIMPLEX flag is entirely hardware.
There are some flags which tell the OS how to treat the adapter.
They can be changed by buying a new adapter ......

SIMPLEX means, that the adapter cant hear himself talk during his
transmissions.
I have seen some obscure and dated IBM adapters which where able to listen
while transmitting - there is the choice between ECHO and NOECHO.

On ethernet the signal is quenched; on token rings it comes arround again -
I think simplex is reminding you on this fact.

All current ethernet adapters should show SIMPLEX, I guess.

On AIX I can see the actual media speed via netstat -v.

Orm





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


From owner-freebsd-net  Mon Feb 21 12:22:47 2000
Delivered-To: freebsd-net@freebsd.org
Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2445C37BF5A; Mon, 21 Feb 2000 12:22:41 -0800 (PST)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <115205>; Tue, 22 Feb 2000 07:23:22 +1100
Content-return: prohibited
From: Peter Jeremy <peter.jeremy@alcatel.com.au>
Subject: Re: Understanding ifconfig output
In-reply-to: <20000221113615.398.qmail@yusufg.portal2.com>; from
 yusufg@outblaze.com on Mon, Feb 21, 2000 at 10:38:13PM +1100
To: Yusuf Goolamabbas <yusufg@outblaze.com>
Cc: freebsd-stable@FreeBSD.ORG, freebsd-net@FreeBSD.ORG
Message-Id: <00Feb22.072322est.115205@border.alcanet.com.au>
MIME-version: 1.0
X-Mailer: Mutt 1.0i
Content-type: text/plain; charset=us-ascii
References: <20000221113615.398.qmail@yusufg.portal2.com>
Date: Tue, 22 Feb 2000 07:23:21 +1100
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On 2000-Feb-21 22:38:13 +1100, Yusuf Goolamabbas <yusufg@outblaze.com> wrote:
>does SIMPLEX mean that the card is in half duplex mode,

No. From /usr/include/net/if.h:
#define IFF_SIMPLEX     0x800           /* can't hear own transmissions */

>What is the recommended way to determine link speed from a machine to
>a hub/switch.

With FreeBSD, the `media' line of ifconfig output:
>media: autoselect (100baseTX <full-duplex>) status: active

> (e.g A colo provider claims that there is 100 Mbit card
>in the box and one would want to verify that)

Configure the other end to 100baseTX only and verify the link comes up.

Peter


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


From owner-freebsd-net  Mon Feb 21 14:51:49 2000
Delivered-To: freebsd-net@freebsd.org
Received: from lanturn.express.ru (lanturn.kmost.express.ru [212.24.37.109])
	by hub.freebsd.org (Postfix) with ESMTP id BF96A37B58E
	for <freebsd-net@freebsd.org>; Mon, 21 Feb 2000 14:51:41 -0800 (PST)
	(envelope-from vova@express.ru)
Received: from vova (helo=localhost)
	by lanturn.express.ru with local-esmtp (Exim 3.11 #1)
	id 12N1fF-000MOo-00
	for freebsd-net@FreeBSD.ORG; Tue, 22 Feb 2000 01:50:49 +0300
Date: Tue, 22 Feb 2000 01:50:49 +0300 (MSK)
From: "Vladimir B. Grebenschikov" <vova@express.ru>
X-Sender: vova@lanturn.kmost.express.ru
To: freebsd-net@FreeBSD.ORG
Subject: tcpdump and nfs packets
Message-ID: <Pine.BSF.4.21.0002220149050.86090-100000@lanturn.kmost.express.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Does anybody patch/port tcpdump's parsenfsfh.c for 
reading nfs packets of FreeBSD nfs server ? 

I want to audit my nfs traffic but don't know how to do it. 

--
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  Mon Feb 21 20:22:53 2000
Delivered-To: freebsd-net@freebsd.org
Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2ECE137B67F; Mon, 21 Feb 2000 20:22:44 -0800 (PST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from m5.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway)
	id NAA25932; Tue, 22 Feb 2000 13:22:39 +0900 (JST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master)
	id NAA25301; Tue, 22 Feb 2000 13:22:37 +0900 (JST)
Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id NAA23872; Tue, 22 Feb 2000 13:22:36 +0900 (JST)
To: asmodai@bart.nl
Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG
Subject: Re: Panic (TCP)
In-Reply-To: <20000221144858.O84100@lucifer.bart.nl>
References: <20000221134724.J84100@lucifer.bart.nl>
	<20000221223459W.shin@nd.net.fujitsu.co.jp>
	<20000221144858.O84100@lucifer.bart.nl>
X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN)
X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000222132327B.shin@nd.net.fujitsu.co.jp>
Date: Tue, 22 Feb 2000 13:23:27 +0900
From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 82
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> >Woops sorry I was worng.
> >tp->tt_rexmt->c_flags is actually causing the panic, and the
> >necessary data is the contents of the tp->tt_rexmt->c_flags.
> 
> (kgdb) print tp->tt_rexmt->c_flags
> $1 = 6
> 
> (kgdb) print tp->tt_rexmt         
> $2 = (struct callout *) 0xd5ce6c2c
> 
> (kgdb) print (*tp->tt_rexmt)
> $3 = {c_links = {sle = {sle_next = 0xd5cd7c2c}, tqe = {tqe_next = 0xd5cd7c2c,
>       tqe_prev = 0xd5cd83ac}}, c_time = 22275144, c_arg = 0xd5ce6b60, 
>   c_func = 0xc018bcdc <tcp_timer_rexmt>, c_flags = 6}

Wmm, the contents of tp->tt_rexmt not seems to be broken.

As the result of more review, I found one part which might
cause the problem in very delicate timing, tcp_output.c around line 776.

		if (!callout_active(tp->tt_rexmt) &&
		    tp->snd_nxt != tp->snd_una) {
			callout_reset(tp->tt_rexmt, tp->t_rxtcur,
				      tcp_timer_rexmt, tp);
			if (callout_active(tp->tt_persist)) {
				callout_stop(tp->tt_persist);
				tp->t_rxtshift = 0;
			}
		}

If persist timer is working, and if it happen to timeout between
			callout_reset(tp->tt_rexmt, tp->t_rxtcur,
				      tcp_timer_rexmt, tp);
and
				callout_stop(tp->tt_persist);
then the panic might happen at tcp_setpersist().

This is same as Jan 5 version, but in more previous version,
the code was like below,

		if (tp->t_timer[TCPT_REXMT] == 0 &&
		    tp->snd_nxt != tp->snd_una) {
			tp->t_timer[TCPT_REXMT] = tp->t_rxtcur;
			if (tp->t_timer[TCPT_PERSIST]) {
				tp->t_timer[TCPT_PERSIST] = 0;
				tp->t_rxtshift = 0;
			}
		}

Same problem might also happen in this case but the running
step were more fewer than now, so it was more difficult to
happen.

I think applying following patch will be safer.
Please review this patch.
(Same kind of patch might better to be applied into stable also.)

Thanks,
Yoshinobu Inoue

Index: tcp_output.c
===================================================================
RCS file: /home/ncvs/src/sys/netinet/tcp_output.c,v
retrieving revision 1.39
diff -u -r1.39 tcp_output.c
--- tcp_output.c	2000/02/09 00:34:40	1.39
+++ tcp_output.c	2000/02/22 04:13:32
@@ -775,12 +775,12 @@
 		 */
 		if (!callout_active(tp->tt_rexmt) &&
 		    tp->snd_nxt != tp->snd_una) {
-			callout_reset(tp->tt_rexmt, tp->t_rxtcur,
-				      tcp_timer_rexmt, tp);
 			if (callout_active(tp->tt_persist)) {
 				callout_stop(tp->tt_persist);
 				tp->t_rxtshift = 0;
 			}
+			callout_reset(tp->tt_rexmt, tp->t_rxtcur,
+				      tcp_timer_rexmt, tp);
 		}
 	} else
 		if (SEQ_GT(tp->snd_nxt + len, tp->snd_max))


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


From owner-freebsd-net  Tue Feb 22  1:12:23 2000
Delivered-To: freebsd-net@freebsd.org
Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id C36F337B6EE; Tue, 22 Feb 2000 01:12:15 -0800 (PST)
	(envelope-from asmodai@lucifer.bart.nl)
Received: (from asmodai@localhost)
	by lucifer.bart.nl (8.9.3/8.9.3) id KAA05740;
	Tue, 22 Feb 2000 10:12:06 +0100 (CET)
	(envelope-from asmodai)
Date: Tue, 22 Feb 2000 10:12:06 +0100
From: Jeroen Ruigrok van der Werven <asmodai@bart.nl>
To: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG
Subject: Re: Panic (TCP)
Message-ID: <20000222101206.B5555@lucifer.bart.nl>
References: <20000221134724.J84100@lucifer.bart.nl> <20000221223459W.shin@nd.net.fujitsu.co.jp> <20000221144858.O84100@lucifer.bart.nl> <20000222132327B.shin@nd.net.fujitsu.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000222132327B.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Tue, Feb 22, 2000 at 01:23:27PM +0900
Organisation: bART Internet Services B.V.
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

It looks fine to me.

Perhaps Garrett has something to say about it?

-- 
Jeroen Ruigrok van der Werven          Network- and systemadministrator
<asmodai@bart.nl>                      bART Internet Services /
BSD: Technical excellence at its best  VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70          http://www.bart.nl


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


From owner-freebsd-net  Tue Feb 22  1:29: 8 2000
Delivered-To: freebsd-net@freebsd.org
Received: from btm4r4.alcatel.be (btm4r4.alcatel.be [195.207.101.110])
	by hub.freebsd.org (Postfix) with ESMTP id DEA1037B691
	for <freebsd-net@freebsd.org>; Tue, 22 Feb 2000 01:29:03 -0800 (PST)
	(envelope-from livensw@rc.bel.alcatel.be)
Received: from btmq9s.rc.bel.alcatel.be (btmq9s.rc.bel.alcatel.be [138.203.65.182])
	by btm4r4.alcatel.be (8.9.1a/8.9.1) with ESMTP id KAA04300;
	Tue, 22 Feb 2000 10:27:52 +0100 (MET)
Received: from btm161.rc.bel.alcatel.be (btm161 [138.203.65.238])
	by btmq9s.rc.bel.alcatel.be (8.8.8+Sun/8.8.8) with ESMTP id KAA24637;
	Tue, 22 Feb 2000 10:26:22 +0100 (MET)
Received: (from livensw@localhost)
	by btm161.rc.bel.alcatel.be (8.9.3/8.9.3) id KAA35094;
	Tue, 22 Feb 2000 10:26:21 +0100 (CET)
	(envelope-from livensw)
Date: Tue, 22 Feb 2000 10:26:20 +0100
From: Wim Livens <livensw@rc.bel.alcatel.be>
To: "Vladimir B. Grebenschikov" <vova@express.ru>
Cc: freebsd-net@freebsd.org
Subject: Re: tcpdump and nfs packets
Message-ID: <20000222102620.M290@rc.bel.alcatel.be>
References: <Pine.BSF.4.21.0002220149050.86090-100000@lanturn.kmost.express.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <Pine.BSF.4.21.0002220149050.86090-100000@lanturn.kmost.express.ru>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, Feb 22, 2000 at 01:50:49AM +0300, Vladimir B. Grebenschikov wrote:
> 
> Does anybody patch/port tcpdump's parsenfsfh.c for 
> reading nfs packets of FreeBSD nfs server ? 
> 
> I want to audit my nfs traffic but don't know how to do it. 

I think 'ethereal' can do this. 


-- Wim Livens.



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


From owner-freebsd-net  Tue Feb 22  2:26: 6 2000
Delivered-To: freebsd-net@freebsd.org
Received: from lanturn.express.ru (lanturn.kmost.express.ru [212.24.37.109])
	by hub.freebsd.org (Postfix) with ESMTP id EF65C37B552
	for <freebsd-net@freebsd.org>; Tue, 22 Feb 2000 02:25:56 -0800 (PST)
	(envelope-from vova@express.ru)
Received: from vova (helo=localhost)
	by lanturn.express.ru with local-esmtp (Exim 3.11 #1)
	id 12NCVv-000O5q-00; Tue, 22 Feb 2000 13:25:55 +0300
Date: Tue, 22 Feb 2000 13:25:54 +0300 (MSK)
From: "Vladimir B. Grebenschikov" <vova@express.ru>
X-Sender: vova@lanturn.kmost.express.ru
To: Wim Livens <livensw@rc.bel.alcatel.be>
Cc: freebsd-net@freebsd.org
Subject: Re: tcpdump and nfs packets
In-Reply-To: <20000222102620.M290@rc.bel.alcatel.be>
Message-ID: <Pine.BSF.4.21.0002221322560.89179-100000@lanturn.kmost.express.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, 22 Feb 2000, Wim Livens wrote:

> On Tue, Feb 22, 2000 at 01:50:49AM +0300, Vladimir B. Grebenschikov wrote:
> > 
> > Does anybody patch/port tcpdump's parsenfsfh.c for 
> > reading nfs packets of FreeBSD nfs server ? 

so nobody done it ?

> > I want to audit my nfs traffic but don't know how to do it. 
> 
> I think 'ethereal' can do this. 

Ok, thanks, not best idea install X11* things on router, but I'll try
that.

> -- Wim Livens.

--
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  Tue Feb 22  2:48:34 2000
Delivered-To: freebsd-net@freebsd.org
Received: from lanturn.express.ru (lanturn.kmost.express.ru [212.24.37.109])
	by hub.freebsd.org (Postfix) with ESMTP id 2913037B58C
	for <freebsd-net@freebsd.org>; Tue, 22 Feb 2000 02:48:28 -0800 (PST)
	(envelope-from vova@express.ru)
Received: from vova (helo=localhost)
	by lanturn.express.ru with local-esmtp (Exim 3.11 #1)
	id 12NCsy-000Oxp-00; Tue, 22 Feb 2000 13:49:44 +0300
Date: Tue, 22 Feb 2000 13:49:43 +0300 (MSK)
From: "Vladimir B. Grebenschikov" <vova@express.ru>
X-Sender: vova@lanturn.kmost.express.ru
To: Wim Livens <livensw@rc.bel.alcatel.be>
Cc: freebsd-net@freebsd.org
Subject: Re: tcpdump and nfs packets
In-Reply-To: <20000222102620.M290@rc.bel.alcatel.be>
Message-ID: <Pine.BSF.4.21.0002221346540.95945-100000@lanturn.kmost.express.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, 22 Feb 2000, Wim Livens wrote:

> > I want to audit my nfs traffic but don't know how to do it. 
> 
> I think 'ethereal' can do this. 

No :(

It shows even less than tcpdump (tcpdump shows nsfs operation like
write/read, but ethereal not). 

In sources of tcpdump I found resolution of filesnames/inode
of operation, but there is no switch case for FreeBSD filehandle
onle for brand unixes, so tcpdump simple drop additional data and 
does not show it.

 
> -- Wim Livens.

--
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  Tue Feb 22  5: 7: 6 2000
Delivered-To: freebsd-net@freebsd.org
Received: from zirafe.carrier.kiev.ua (sivka.carrier.kiev.ua [193.193.193.101])
	by hub.freebsd.org (Postfix) with ESMTP id 3D22237B60E
	for <freebsd-net@freebsd.org>; Tue, 22 Feb 2000 05:06:46 -0800 (PST)
	(envelope-from samj@itcj.kiev.ua)
Received: from mails.itci.kiev.ua (gw1.itci.kiev.ua [62.244.54.196])
        by zirafe.carrier.kiev.ua (8.Who.Cares/Kilkenny_is_better) with ESMTP id PCO64246
        for <freebsd-net@freebsd.org>; Tue, 22 Feb 2000 15:06:36 +0200 (EET)
        (envelope-from samj@itcj.kiev.ua)
Received: from primsrv (primsrv.itci.kiev.ua [62.244.54.220])
	by mails.itci.kiev.ua (8.8.8/8.8.8) with ESMTP id PAA27042
	for <freebsd-net@freebsd.org>; Tue, 22 Feb 2000 15:06:33 +0200 (EET)
	(envelope-from samj@itcj.kiev.ua)
Message-Id: <200002221306.PAA27042@mails.itci.kiev.ua>
From: "Yuriy" <samj@itcj.kiev.ua>
To: <freebsd-net@freebsd.org>
Subject: Why tty and wtmp has defined cuaaa as cuaa10 ?
Date: Tue, 22 Feb 2000 15:05:45 +0200
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1155
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I 'm use mgetty and wtmp for personification users.
But tty and wtmp has defined cuaaa as cuaa10.
It was cuaaa early and all was fine.
How can i do cuaaa both in wtmp and in mgetty ?
Thanks.
_______
Yuriy Samartsev,
Firm ITC Ltd,     http://www.itci.net.


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


From owner-freebsd-net  Tue Feb 22  7: 5:27 2000
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 70B3837B697; Tue, 22 Feb 2000 07:05:23 -0800 (PST)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA07676;
	Tue, 22 Feb 2000 10:05:16 -0500 (EST)
	(envelope-from wollman)
Date: Tue, 22 Feb 2000 10:05:16 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200002221505.KAA07676@khavrinen.lcs.mit.edu>
To: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
Cc: asmodai@bart.nl, freebsd-current@FreeBSD.ORG,
	freebsd-net@FreeBSD.ORG
Subject: Re: Panic (TCP)
In-Reply-To: <20000222132327B.shin@nd.net.fujitsu.co.jp>
References: <20000221134724.J84100@lucifer.bart.nl>
	<20000221223459W.shin@nd.net.fujitsu.co.jp>
	<20000221144858.O84100@lucifer.bart.nl>
	<20000222132327B.shin@nd.net.fujitsu.co.jp>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

<<On Tue, 22 Feb 2000 13:23:27 +0900, Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp> said:

> If persist timer is working, and if it happen to timeout between
> 			callout_reset(tp->tt_rexmt, tp->t_rxtcur,
> 				      tcp_timer_rexmt, tp);
> and
> 				callout_stop(tp->tt_persist);
> then the panic might happen at tcp_setpersist().

This should never happen, since this code is supposed to be running at
splnet(), which is supposed to block timeouts.  Rather than papering
over the problem, I'd like to understand how it's possible.

-GAWollman

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


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


From owner-freebsd-net  Tue Feb 22  7:28:29 2000
Delivered-To: freebsd-net@freebsd.org
Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184])
	by hub.freebsd.org (Postfix) with ESMTP id D0F9037B68C
	for <net@freebsd.org>; Tue, 22 Feb 2000 07:28:23 -0800 (PST)
	(envelope-from luigi@info.iet.unipi.it)
Received: (from luigi@localhost)
	by info.iet.unipi.it (8.9.3/8.9.3) id QAA98086;
	Tue, 22 Feb 2000 16:27:53 +0100 (CET)
	(envelope-from luigi)
From: Luigi Rizzo <luigi@info.iet.unipi.it>
Message-Id: <200002221527.QAA98086@info.iet.unipi.it>
Subject: does ipfw forward work with non-local addresses ?
To: net@freebsd.org
Date: Tue, 22 Feb 2000 16:27:53 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL61 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

am looking at implementing some kind of redirection mechanism (similar
to layer-4 switching, used to see a farm of servers as a single node) in
ipfw, and was wondering how (if) ipfw forwarding works when you specify a
non-local forwarding address e.g. something like

	ipfw add fwd some_other_host tcp from any to my_ip 80

The rule of course seems to match incoming packets, but then
the forward routine will likely fail because the destination address
in the packet seems to be unchanged.
(Not that the return packets can work at all, as there is no way
to set a matching rule at the moment for this...)

	cheers
	luigi
-----------------------------------+-------------------------------------
  Luigi RIZZO, luigi@iet.unipi.it  . Dip. di Ing. dell'Informazione
  http://www.iet.unipi.it/~luigi/  . Universita` di Pisa
  TEL/FAX: +39-050-568.533/522     . via Diotisalvi 2, 56126 PISA (Italy)
  Mobile   +39-347-0373137
-----------------------------------+-------------------------------------


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


From owner-freebsd-net  Tue Feb 22  7:33:14 2000
Delivered-To: freebsd-net@freebsd.org
Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8728037B68C; Tue, 22 Feb 2000 07:33:09 -0800 (PST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from m4.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway)
	id AAA23320; Wed, 23 Feb 2000 00:32:01 +0900 (JST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from incapgw.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master)
	id AAA10819; Wed, 23 Feb 2000 00:32:01 +0900 (JST)
Received: from localhost ([192.168.245.60]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002)
	id AAA01669; Wed, 23 Feb 2000 00:31:59 +0900 (JST)
To: wollman@khavrinen.lcs.mit.edu
Cc: asmodai@bart.nl, freebsd-current@FreeBSD.ORG,
	freebsd-net@FreeBSD.ORG
Subject: Re: Panic (TCP)
In-Reply-To: <200002221505.KAA07676@khavrinen.lcs.mit.edu>
References: <20000221144858.O84100@lucifer.bart.nl>
	<20000222132327B.shin@nd.net.fujitsu.co.jp>
	<200002221505.KAA07676@khavrinen.lcs.mit.edu>
X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN)
X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000223003250I.shin@nd.net.fujitsu.co.jp>
Date: Wed, 23 Feb 2000 00:32:50 +0900
From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 31
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> > If persist timer is working, and if it happen to timeout between
> > 			callout_reset(tp->tt_rexmt, tp->t_rxtcur,
> > 				      tcp_timer_rexmt, tp);
> > and
> > 				callout_stop(tp->tt_persist);
> > then the panic might happen at tcp_setpersist().
> 
> This should never happen, since this code is supposed to be running at
> splnet(), which is supposed to block timeouts.  Rather than papering
> over the problem, I'd like to understand how it's possible.

I also later thought so, but again I suspect that the part is
also one of the cause of the problem. Because as the value of
tp->t_rexmt at panic, retransmit timer also seemed to be
running at the time, and I can't find any other place which
might cause this situation.
Also I think anyway the patch is better to be applied.

My assumption might be wrong but I am now trying if I can
create some patch that make the problem very likely to happen.

Thanks,
Yoshinobu Inoue

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


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


From owner-freebsd-net  Tue Feb 22 11: 2:34 2000
Delivered-To: freebsd-net@freebsd.org
Received: from fep02-svc.mail.telepac.pt (fep02-svc.mail.telepac.pt [194.65.5.201])
	by hub.freebsd.org (Postfix) with ESMTP
	id E330037B739; Tue, 22 Feb 2000 11:02:15 -0800 (PST)
	(envelope-from jpedras@webvolution.net)
Received: from manecao.tafkap.priv ([194.65.206.92])
          by fep02-svc.mail.telepac.pt
          (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP
          id <20000222190458.NCWD4775.fep02-svc.mail.telepac.pt@manecao.tafkap.priv>;
          Tue, 22 Feb 2000 19:04:58 +0000
Content-Length: 2719
Message-ID: <XFMail.000222190124.jpedras@webvolution.net>
X-Mailer: XFMail 1.3.1 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Tue, 22 Feb 2000 19:01:24 -0000 (GMT)
Reply-To: Joao Pedras <jpedras@webvolution.net>
From: Joao Pedras <jpedras@webvolution.net>
To: freebsd-net@freebsd.org
Subject: dropping connection
Cc: freebsd-isdn@freebsd.org
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hello all.

I have been using FreeBSD to use ordinary pc's as routers. Several of those
machines use the i4b daemon.
Althought this IS NOT a FreeBSD or i4b problem, I would like to submit it to
your consideration, so I could have an independent opinion about it.
Several of these routers connect through one of the major isp in our country.

Only in these installations I face the problem of disconnection when idle after
'x' time, to don't work (i.e. no matter how I configure the isdnd it never
drops the connection). The exact same configuration on other isp works properly
and performs the disconnect.
The problem is that this particular isp has their routers configured to send
some kind of keep alive, whenever the connection is idle.

I ran tcpdump on the isp0 interface and got the following :

19:45:36.787026 ID-063 LCP: Echo-Request, Magic-Number=-495599889
                         093f 000c e275 beef 0258 d272
19:45:36.787052 ID-063 LCP: Echo-Reply, Magic-Number=1285595741
                         0a3f 000c 4ca0 a25d 0258 d272
19:45:46.789844 ID-064 LCP: Echo-Request, Magic-Number=-495599889
                         0940 000c e275 beef 0258 d272
19:45:46.789865 ID-064 LCP: Echo-Reply, Magic-Number=1285595741
                         0a40 000c 4ca0 a25d 0258 d272
19:45:56.793551 ID-065 LCP: Echo-Request, Magic-Number=-495599889
                         0941 000c e275 beef 0258 d272
19:45:56.793570 ID-065 LCP: Echo-Reply, Magic-Number=1285595741
                         0a41 000c 4ca0 a25d 0258 d272
19:46:06.796127 ID-066 LCP: Echo-Request, Magic-Number=-495599889
                         0942 000c e275 beef 0258 d272
19:46:06.796147 ID-066 LCP: Echo-Reply, Magic-Number=1285595741
                         0a42 000c 4ca0 a25d 0258 d272

Frankly, I do not know of to interpret this data.

Do you find this situation normal ? I spoke with them and they didn't gave me
any 'real' reason to be doing this. They said they won't change their
configuration.

They suggested me to write some kind of filter to ignore this. Is this easily
achiavable ?

Just for curiosity, I read in the IOS 12.0 Configurartion book, that the keep
alive in Cisco routers could be enabled optionally.

I really don't see any use to this configuration. ]:(

Thanks for your help

Joao

                                          ^\   /^
                                            O O
----------------------------------------o00-(_)-00o--------------------------

I often quote myself; it adds spice to my conversation.
                -- G. B. Shaw

-----------------------------------------------------------------------------
PGP key available upon request or may be cut at 
http://pedras.webvolution.net/pgpkey.html



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


From owner-freebsd-net  Tue Feb 22 13:26:36 2000
Delivered-To: freebsd-net@freebsd.org
Received: from Brigada-A.Ethereal.RU (Brigada-A.ethereal.ru [195.230.65.30])
	by hub.freebsd.org (Postfix) with ESMTP id 40B7F37B6A5
	for <freebsd-net@FreeBSD.ORG>; Tue, 22 Feb 2000 13:26:32 -0800 (PST)
	(envelope-from nms@Brigada-A.Ethereal.RU)
Received: by Brigada-A.Ethereal.RU (Postfix, from userid 1002)
	id 21DB61D9; Wed, 23 Feb 2000 00:26:22 +0300 (MSK)
Date: Wed, 23 Feb 2000 00:26:21 +0300
From: Nikolai Saoukh <nms@Brigada-A.Ethereal.RU>
To: Archie Cobbs <archie@whistle.com>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: NETGRAPH patches (proposal)
Message-ID: <20000223002621.A25661@Draculina.Universe>
References: <20000221143707.21862.qmail@web119.yahoomail.com> <200002222104.NAA30708@bubba.whistle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <200002222104.NAA30708@bubba.whistle.com>; from archie@whistle.com on Tue, Feb 22, 2000 at 01:04:34PM -0800
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, Feb 22, 2000 at 01:04:34PM -0800, Archie Cobbs wrote:

> > Here is the description. ng_ether node has two hooks ``divert'' and
> > ``orphan''.
> > It is possible to connect to the one of the hooks and intercept row Ethernet
> > frames. But there is no clean way to intercept frame, do something and
> > return it back to kernel.
> > 
> > This patch provides additional hook ``divertin'' (mmm... name is not good,
> > i think) for each ng_ether node. 
> > 
> > Implementation issues
> > 
> > This will not work for ``orphan'' frames. Since kernel drops it anyway, i
> > decided to leave it as it is. But is is possible to intercept ``orphan''
> > packets, change it, and write back to ``divertin''.
> 
> The "divertin" hook is a useful idea.. after 4.0-REL we can check
> something in based on your patches...

I was under impression that hooks are bidirectional. Is not it?


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


From owner-freebsd-net  Tue Feb 22 13:53:45 2000
Delivered-To: freebsd-net@freebsd.org
Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7])
	by hub.freebsd.org (Postfix) with ESMTP id 9471137B747
	for <freebsd-net@FreeBSD.ORG>; Tue, 22 Feb 2000 13:53:41 -0800 (PST)
	(envelope-from archie@whistle.com)
Received: (from archie@localhost)
	by bubba.whistle.com (8.9.3/8.9.2) id NAA37333;
	Tue, 22 Feb 2000 13:53:32 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <200002222153.NAA37333@bubba.whistle.com>
Subject: Re: NETGRAPH patches (proposal)
In-Reply-To: <20000223002621.A25661@Draculina.Universe> from Nikolai Saoukh at "Feb 23, 2000 00:26:21 am"
To: nms@Brigada-A.Ethereal.RU (Nikolai Saoukh)
Date: Tue, 22 Feb 2000 13:53:32 -0800 (PST)
Cc: freebsd-net@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Nikolai Saoukh writes:
> > > Here is the description. ng_ether node has two hooks ``divert'' and
> > > ``orphan''.
> > > It is possible to connect to the one of the hooks and intercept row Ethernet
> > > frames. But there is no clean way to intercept frame, do something and
> > > return it back to kernel.
> > > 
> > > This patch provides additional hook ``divertin'' (mmm... name is not good,
> > > i think) for each ng_ether node. 
> > > 
> > > Implementation issues
> > > 
> > > This will not work for ``orphan'' frames. Since kernel drops it anyway, i
> > > decided to leave it as it is. But is is possible to intercept ``orphan''
> > > packets, change it, and write back to ``divertin''.
> > 
> > The "divertin" hook is a useful idea.. after 4.0-REL we can check
> > something in based on your patches...
> 
> I was under impression that hooks are bidirectional. Is not it?

Yes they are.. but we need two hooks: one for packets going out
on the wire, and one for packets going into the protocol stack.. right?
It doesn't seem like overloading "orphan" for the latter task
is the right answer.

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com


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


From owner-freebsd-net  Tue Feb 22 19:38:12 2000
Delivered-To: freebsd-net@freebsd.org
Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248])
	by hub.freebsd.org (Postfix) with ESMTP id 9F14437B830
	for <freebsd-net@freebsd.org>; Tue, 22 Feb 2000 19:38:08 -0800 (PST)
	(envelope-from wes@softweyr.com)
Received: from mailhub.xylan.com (mailhub [198.206.181.70])
	by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id TAA07013;
	Tue, 22 Feb 2000 19:37:13 -0800 (PST)
X-Origination-Site: <ind.alcatel.com>
Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB]))
	id TAA29116; Tue, 22 Feb 2000 19:37:12 -0800
Received: from softweyr.com (homer.softweyr.com [204.68.178.39])
	by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id TAA14570;
	Tue, 22 Feb 2000 19:37:09 -0800 (PST)
Message-ID: <38B35790.EA9CADF@softweyr.com>
Date: Tue, 22 Feb 2000 20:44:16 -0700
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Lloyd Rennie <lloyd@vbc.net>
Cc: Wim Livens <livensw@rc.bel.alcatel.be>,
	Yusuf Goolamabbas <yusufg@outblaze.com>, freebsd-net@freebsd.org
Subject: Re: Understanding ifconfig output
References: <Pine.BSF.4.05.10002211533070.63343-100000@brunel.uk1.vbc.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Lloyd Rennie wrote:
> 
> On Mon, 21 Feb 2000, Wim Livens wrote:
> 
> > On Mon, Feb 21, 2000 at 11:35:04AM -0000, Yusuf Goolamabbas wrote:
> > > Here's some sample output from one of my machines (3.4-stable) which
> > > has an Intel EEPro 100 attached to a Bay 350 switch
> > >
> > > fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > > <ip address deleted>
> > > ether 00:90:27:8d:49:7b
> > > media: autoselect (100baseTX <full-duplex>) status: active
> >                      ^^^^^^^^^^^^^^^^^^^^^^^
> > This is the info you want---^
> >
> > I don't know what SIMPLEX means, I use the same card in 100Mb
> > full-duplex and get similar output.
> 
> Same here.  The media autoselects FD, but still the simplex flag is set.
> *shrug*

They have completely different meanings.  A quick look at the ifconfig
source would tell you that.  The 'flags=8843<...>' part of the output
is the network interface options; IFF_SIMPLEX and friends are defined in
/usr/include/net/if.h:

...
#define IFF_ALLMULTI    0x200           /* receive all multicast packets */  
#define IFF_OACTIVE     0x400           /* transmission in progress */
#define IFF_SIMPLEX     0x800           /* can't hear own transmissions */
#define IFF_LINK0       0x1000          /* per link layer defined bit */  
...

As you can see, the IFF_SIMPLEX flags means this interface cannot hear it's
own transmissions.

Later, the media options are printed, showing you that your network interface
card is configured for 100Base-TX full-duplex.

> > What is the recommended way to determine link speed from a machine to
> > a hub/switch. (e.g A colo provider claims that there is 100 Mbit card
> > in the box and one would want to verify that)
> 
> A fairly foolproof method is to make sure there's a fair amount of traffic
> running in both directions, then do a 'netstat -I fxp0 -w1'.  Watch the
> collisions - if you see any then it's not FD.

For the link speed, just look at the ifconfig output.  If the interface is
set to 100Base-TX and is working, it's in 100 Mbps mode.  The only other 
option is 10Base-T.  100Base-TX full duplex is actually 200 Mbps - 100 each
way.

-- 
            "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                         Softweyr LLC
wes@softweyr.com                                           http://softweyr.com/


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


From owner-freebsd-net  Tue Feb 22 21:27:51 2000
Delivered-To: freebsd-net@freebsd.org
Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248])
	by hub.freebsd.org (Postfix) with ESMTP id 008C837B8B2
	for <freebsd-net@freebsd.org>; Tue, 22 Feb 2000 21:27:38 -0800 (PST)
	(envelope-from wes@softweyr.com)
Received: from mailhub.xylan.com (mailhub [198.206.181.70])
	by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id VAA07871;
	Tue, 22 Feb 2000 21:27:18 -0800 (PST)
X-Origination-Site: <ind.alcatel.com>
Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB]))
	id VAA02001; Tue, 22 Feb 2000 21:27:18 -0800
Received: from softweyr.com (homer.softweyr.com [204.68.178.39])
	by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id VAA19032;
	Tue, 22 Feb 2000 21:27:05 -0800 (PST)
Message-ID: <38B37155.21D6BD82@softweyr.com>
Date: Tue, 22 Feb 2000 22:34:13 -0700
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Vladimir B. Grebenschikov" <vova@express.ru>
Cc: Wim Livens <livensw@rc.bel.alcatel.be>, freebsd-net@freebsd.org
Subject: Re: tcpdump and nfs packets
References: <Pine.BSF.4.21.0002221322560.89179-100000@lanturn.kmost.express.ru>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

"Vladimir B. Grebenschikov" wrote:
> 
> On Tue, 22 Feb 2000, Wim Livens wrote:
> 
> > On Tue, Feb 22, 2000 at 01:50:49AM +0300, Vladimir B. Grebenschikov wrote:
> > >
> > > Does anybody patch/port tcpdump's parsenfsfh.c for
> > > reading nfs packets of FreeBSD nfs server ?
> 
> so nobody done it ?

As usual, we await your patches.  ;^)

> > > I want to audit my nfs traffic but don't know how to do it.
> >
> > I think 'ethereal' can do this.
> 
> Ok, thanks, not best idea install X11* things on router, but I'll try
> that.

Why not?  You don't need to install or configure the X server, just 
the libraries and use a network DISPLAY.

-- 
            "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                         Softweyr LLC
wes@softweyr.com                                           http://softweyr.com/


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


From owner-freebsd-net  Wed Feb 23  1:28:50 2000
Delivered-To: freebsd-net@freebsd.org
Received: from d12lmsgate.de.ibm.com (d12lmsgate.de.ibm.com [195.212.91.199])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3CDAE37B83E; Wed, 23 Feb 2000 01:28:40 -0800 (PST)
	(envelope-from DRHAGER@de.ibm.com)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate.de.ibm.com (1.0.0) with ESMTP id JAA64902;
	Wed, 23 Feb 2000 09:59:53 +0100
From: DRHAGER@de.ibm.com
Received: from d12mta01.de.ibm.com (d12mta01_cs0 [9.165.222.237])
	by d12relay02.de.ibm.com (8.8.8m2/NCO v2.06) with SMTP id JAA28450;
	Wed, 23 Feb 2000 09:59:52 +0100
Received: by d12mta01.de.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id C125688E.00316BAA ; Wed, 23 Feb 2000 09:59:48 +0100
X-Lotus-FromDomain: IBMDE
To: Joao Pedras <jpedras@webvolution.net>
Cc: freebsd-net@FreeBSD.ORG, Freebsd-net@FreeBSD.ORG
Message-ID: <C125688E.003164C1.00@d12mta01.de.ibm.com>
Date: Wed, 23 Feb 2000 09:59:27 +0100
Subject: Re: dropping connection
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org



I had a similar problem:
The ISDN link kept coming up every 10 min, and in tcpdump
I found ICMP ECHO-REQUEST in this intervall.
(*from* my net....)
So the link came up and down constantly.

This turned out to be PMTU Discovery re-checking a route via
the link.
You can find the IP of the offending machine and the process ID
in the packet - I am not familiar with the tcpdump-output, sorry.

Orm


########################################################################
Hello all.

I have been using FreeBSD to use ordinary pc's as routers. Several of those
machines use the i4b daemon.
Althought this IS NOT a FreeBSD or i4b problem, I would like to submit it
to
your consideration, so I could have an independent opinion about it.
Several of these routers connect through one of the major isp in our
country.

Only in these installations I face the problem of disconnection when idle
after
'x' time, to don't work (i.e. no matter how I configure the isdnd it never
drops the connection). The exact same configuration on other isp works
properly
and performs the disconnect.
The problem is that this particular isp has their routers configured to
send
some kind of keep alive, whenever the connection is idle.

I ran tcpdump on the isp0 interface and got the following :

19:45:36.787026 ID-063 LCP: Echo-Request, Magic-Number=-495599889
                         093f 000c e275 beef 0258 d272
19:45:36.787052 ID-063 LCP: Echo-Reply, Magic-Number=1285595741
                         0a3f 000c 4ca0 a25d 0258 d272
19:45:46.789844 ID-064 LCP: Echo-Request, Magic-Number=-495599889
                         0940 000c e275 beef 0258 d272
19:45:46.789865 ID-064 LCP: Echo-Reply, Magic-Number=1285595741
                         0a40 000c 4ca0 a25d 0258 d272
19:45:56.793551 ID-065 LCP: Echo-Request, Magic-Number=-495599889
                         0941 000c e275 beef 0258 d272
19:45:56.793570 ID-065 LCP: Echo-Reply, Magic-Number=1285595741
                         0a41 000c 4ca0 a25d 0258 d272
19:46:06.796127 ID-066 LCP: Echo-Request, Magic-Number=-495599889
                         0942 000c e275 beef 0258 d272
19:46:06.796147 ID-066 LCP: Echo-Reply, Magic-Number=1285595741
                         0a42 000c 4ca0 a25d 0258 d272

Frankly, I do not know of to interpret this data.

Do you find this situation normal ? I spoke with them and they didn't gave
me
any 'real' reason to be doing this. They said they won't change their
configuration.

They suggested me to write some kind of filter to ignore this. Is this
easily
achiavable ?

Just for curiosity, I read in the IOS 12.0 Configurartion book, that the
keep
alive in Cisco routers could be enabled optionally.

I really don't see any use to this configuration. ]:(

Thanks for your help

Joao

                                          ^\   /^
                                            O O
----------------------------------------o00-(_)-00o--------------------------


I often quote myself; it adds spice to my conversation.
                -- G. B. Shaw

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

PGP key available upon request or may be cut at
http://pedras.webvolution.net/pgpkey.html



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





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


From owner-freebsd-net  Wed Feb 23  7: 2: 3 2000
Delivered-To: freebsd-net@freebsd.org
Received: from godfather.webvolution.net (unknown.cust-X.hecenter.com [208.231.0.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id ABB3637B8E3; Wed, 23 Feb 2000 07:01:52 -0800 (PST)
	(envelope-from jpedras@webvolution.net)
Received: (from nobody@localhost)
	by godfather.webvolution.net (13.5.3/13.5.3) id PAA37329;
	Wed, 23 Feb 2000 15:00:58 GMT
	(envelope-from jpedras@webvolution.net)
Date: Wed, 23 Feb 2000 15:00:58 GMT
Message-Id: <200002231500.PAA37329@godfather.webvolution.net>
X-Authentication-Warning: godfather.webvolution.net: nobody set sender to jpedras@webvolution.net using -f
From: Joao Pedras <jpedras@webvolution.net>
To: Gary Jennejohn <garyj@muc.de>
Reply-To: Joao Pedras <jpedras@webvolution.net>
Cc: freebsd-net@freebsd.org, freebsd-isdn@freebsd.org
References: <200002231102.MAA45542@peedub.muc.de>
In-Reply-To: <200002231102.MAA45542@peedub.muc.de>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP3 Imap webMail Program 2.0.11
X-Originating-IP: 193.137.208.1
Subject: Re: dropping connection
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Quoting Gary Jennejohn <garyj@peedub.muc.de>:

> Joao Pedras writes:
> [snip keep-alives from ISP]
> >Do you find this situation normal ? I spoke with them
and they didn't gave
> me
> >any 'real' reason to be doing this. They said they
won't change their
> >configuration.
> >
>
> They're probably doing it so they can catch
connections which were not
> shut down in a clean manner. It's a legitimate thing
to do.

But is it necessary to do it every 5/10 seconds ?

>
> >They suggested me to write some kind of filter to
ignore this. 
> >
> contrib/lcp-patch2.tar.uu in the isdn4bsd distribution
is supposed to
> fix this. The problem is that it turns off the normal
short hold timeout
> handling. And it's against a really old version of
isdn4bsd. But it
> may help.

I will look into it.

Thanks


-------------------------------
Powered by Webvolution Networks


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


From owner-freebsd-net  Wed Feb 23 12:19:37 2000
Delivered-To: freebsd-net@freebsd.org
Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65])
	by hub.freebsd.org (Postfix) with ESMTP id 3760437B973
	for <freebsd-net@FreeBSD.ORG>; Wed, 23 Feb 2000 12:19:28 -0800 (PST)
	(envelope-from jonny@jonny.eng.br)
Received: (from uucp@localhost)
	by roma.coe.ufrj.br (8.9.3/8.9.3) id RAA62284;
	Wed, 23 Feb 2000 17:19:11 -0300 (EST)
	(envelope-from jonny@jonny.eng.br)
Received: from localhost.coe.ufrj.br(127.0.0.1), claiming to be "jonny.eng.br"
 via SMTP by localhost.coe.ufrj.br, id smtpdI62268; Wed Feb 23 17:19:03 2000
Message-ID: <38B43EFD.9384FF1C@jonny.eng.br>
Date: Wed, 23 Feb 2000 17:11:41 -0300
From: Joao Carlos Mendes Luis <jonny@jonny.eng.br>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Masahiro Ariga <mariga@cd.mbn.or.jp>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: arp wrongs in Multicast
References: <001101bf740f$4b529ce0$064ca8c0@gateway>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Masahiro Ariga wrote:
> 09:49:45.001329 0:a0:c9:93:ba:2f Broadcast arp 42: arp who-has 234.5.6.7
> tell 192.168.76.69
> 
> 192.168.76.69 is a Server's own output interface IP.
> It looks like there's  no reply for multicast address 234.5.6.7.
> 
> My questions are:
> 1.Does arp correctly work during multicast transmission ?

  There should be NO arp for multicast addresses.

  The MAC addresses for multicast IPs are created from a static
"conversion table".

  You should probably go search why these arp requests are beeing
generated.

> 2.If it works,why one of interfaces' address becomes "incomplete" after 20
> minutes.

  Check if mrouted is still running.

					Jonny

-- 
João Carlos Mendes Luís			jonny@jonny.eng.br
  Networking Engineer			jcml@ieee.org



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


From owner-freebsd-net  Thu Feb 24  8:56: 6 2000
Delivered-To: freebsd-net@freebsd.org
Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184])
	by hub.freebsd.org (Postfix) with ESMTP id 1420D37BC90
	for <net@freebsd.org>; Thu, 24 Feb 2000 08:55:55 -0800 (PST)
	(envelope-from luigi@info.iet.unipi.it)
Received: (from luigi@localhost)
	by info.iet.unipi.it (8.9.3/8.9.3) id RAA08060;
	Thu, 24 Feb 2000 17:55:25 +0100 (CET)
	(envelope-from luigi)
From: Luigi Rizzo <luigi@info.iet.unipi.it>
Message-Id: <200002241655.RAA08060@info.iet.unipi.it>
Subject: where to place a database of ethernet addresses ?
To: net@freebsd.org
Date: Thu, 24 Feb 2000 17:55:25 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL61 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

what would be the right place to put a database of ethernet addresses ?
There are various reasons i need this, one is to wire the ARP table
so that machines cannot steal too easily other people's IPs,
to do autoconfiguration on PicoBSD floppies, etc. etc.

Right now (in picobsd at least) i have put records of the form

	# 01:23:45:67:89:a0	hostname

(where the '#' is part of the format) in /etc/hosts, but perhaps
there is a better standard place ?

	cheers
	luigi

-----------------------------------+-------------------------------------
  Luigi RIZZO, luigi@iet.unipi.it  . Dip. di Ing. dell'Informazione
  http://www.iet.unipi.it/~luigi/  . Universita` di Pisa
  TEL/FAX: +39-050-568.533/522     . via Diotisalvi 2, 56126 PISA (Italy)
  Mobile   +39-347-0373137
-----------------------------------+-------------------------------------


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


From owner-freebsd-net  Thu Feb 24  9: 3: 9 2000
Delivered-To: freebsd-net@freebsd.org
Received: from mx01-ext.netapp.com (mx01-ext.netapp.com [198.95.224.34])
	by hub.freebsd.org (Postfix) with SMTP id 5935537BF8E
	for <net@FreeBSD.ORG>; Thu, 24 Feb 2000 09:03:05 -0800 (PST)
	(envelope-from jeff.mohler@netapp.com)
Received: (qmail 2692 invoked from network); 24 Feb 2000 17:11:33 -0000
Received: from herra.netapp.com (HELO herra.corp.netapp.com) (198.95.224.184)
  by mx01-ext.netapp.com with SMTP; 24 Feb 2000 17:11:33 -0000
Received: from tahoe.corp.netapp.com (tahoe.netapp.com [10.10.10.112])
	by herra.corp.netapp.com (8.9.3/8.9.3/NTAP-1.0) with ESMTP id JAA02593;
	Thu, 24 Feb 2000 09:03:02 -0800 (PST)
Received: by tahoe.corp.netapp.com with Internet Mail Service (5.5.2650.21)
	id <DJV2YD3L>; Thu, 24 Feb 2000 09:03:01 -0800
Message-ID: <242EA98B2B7DD311985A0090277AED5101355D83@CLEARCREEK.corp.netapp.com>
From: "Mohler, Jeff" <jeff.mohler@netapp.com>
To: "'Luigi Rizzo'" <luigi@info.iet.unipi.it>, net@FreeBSD.ORG
Subject: RE: where to place a database of ethernet addresses ?
Date: Thu, 24 Feb 2000 09:03:27 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

/etc/ethers is a great place to store those.  Some programs/utilties will look
in there for things like that.

-----Original Message-----
From: Luigi Rizzo [mailto:luigi@info.iet.unipi.it]
Sent: Thursday, February 24, 2000 8:55 AM
To: net@FreeBSD.ORG
Subject: where to place a database of ethernet addresses ?


Hi,

what would be the right place to put a database of ethernet addresses ?
There are various reasons i need this, one is to wire the ARP table
so that machines cannot steal too easily other people's IPs,
to do autoconfiguration on PicoBSD floppies, etc. etc.

Right now (in picobsd at least) i have put records of the form

	# 01:23:45:67:89:a0	hostname

(where the '#' is part of the format) in /etc/hosts, but perhaps
there is a better standard place ?

	cheers
	luigi

-----------------------------------+-------------------------------------
  Luigi RIZZO, luigi@iet.unipi.it  . Dip. di Ing. dell'Informazione
  http://www.iet.unipi.it/~luigi/  . Universita` di Pisa
  TEL/FAX: +39-050-568.533/522     . via Diotisalvi 2, 56126 PISA (Italy)
  Mobile   +39-347-0373137
-----------------------------------+-------------------------------------


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


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


From owner-freebsd-net  Thu Feb 24  9: 5:37 2000
Delivered-To: freebsd-net@freebsd.org
Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56])
	by hub.freebsd.org (Postfix) with ESMTP id ECC9B37C1F0
	for <net@FreeBSD.ORG>; Thu, 24 Feb 2000 09:05:27 -0800 (PST)
	(envelope-from bmah@nimitz.ca.sandia.gov)
Received: (from bmah@localhost)
	by nimitz.ca.sandia.gov (8.10.0.Beta12/8.10.0.Beta12) id e1OH54P30001;
	Thu, 24 Feb 2000 09:05:04 -0800 (PST)
Message-Id: <200002241705.e1OH54P30001@nimitz.ca.sandia.gov>
X-Mailer: exmh version 2.1.1-cvs 10/15/1999
To: Luigi Rizzo <luigi@info.iet.unipi.it>
Cc: net@FreeBSD.ORG
Subject: Re: where to place a database of ethernet addresses ? 
In-Reply-To: <200002241655.RAA08060@info.iet.unipi.it> 
References: <200002241655.RAA08060@info.iet.unipi.it>
Comments: In-reply-to Luigi Rizzo <luigi@info.iet.unipi.it>
   message dated "Thu, 24 Feb 2000 17:55:25 +0100."
From: bmah@CA.Sandia.GOV (Bruce A. Mah)
Reply-To: bmah@CA.Sandia.GOV
X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5<Pi&akO)o^8;[r
 %l(8ZHlbF`dD>v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A
 2V%N&+
X-Url: http://www.ca.sandia.gov/~bmah/
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-250528048P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 24 Feb 2000 09:05:04 -0800
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

--==_Exmh_-250528048P
Content-Type: text/plain; charset=us-ascii

If memory serves me right, Luigi Rizzo wrote:

> what would be the right place to put a database of ethernet addresses ?
> There are various reasons i need this, one is to wire the ARP table
> so that machines cannot steal too easily other people's IPs,
> to do autoconfiguration on PicoBSD floppies, etc. etc.
> 
> Right now (in picobsd at least) i have put records of the form
> 
> 	# 01:23:45:67:89:a0	hostname
> 
> (where the '#' is part of the format) in /etc/hosts, but perhaps
> there is a better standard place ?

man 5 ethers

Or is that not what you had in mind?

Cheers,

Bruce.





--==_Exmh_-250528048P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: iUSS63YHRuuKMWtuFAx9vWYRS1WX65xY

iQA/AwUBOLVkwNjKMXFboFLDEQIqRwCfR+YuPabTMfNtr3RdTGprd0VVpEQAnAy6
pbagd6ArEd0ATwnKkVcpq1IP
=/nJY
-----END PGP SIGNATURE-----

--==_Exmh_-250528048P--


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


From owner-freebsd-net  Thu Feb 24 15:18:33 2000
Delivered-To: freebsd-net@freebsd.org
Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248])
	by hub.freebsd.org (Postfix) with ESMTP id 7D50437BC24
	for <net@FreeBSD.ORG>; Thu, 24 Feb 2000 15:18:24 -0800 (PST)
	(envelope-from wes@softweyr.com)
Received: from mailhub.xylan.com (mailhub [198.206.181.70])
	by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id PAA19529;
	Thu, 24 Feb 2000 15:17:29 -0800 (PST)
X-Origination-Site: <ind.alcatel.com>
Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB]))
	id PAA10093; Thu, 24 Feb 2000 15:17:25 -0800
Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL]))
	id QAA15291; Thu, 24 Feb 2000 16:17:12 -0700
Message-ID: <38B5BDAE.9C444187@softweyr.com>
Date: Thu, 24 Feb 2000 16:24:30 -0700
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Luigi Rizzo <luigi@info.iet.unipi.it>
Cc: net@FreeBSD.ORG
Subject: Re: where to place a database of ethernet addresses ?
References: <200002241655.RAA08060@info.iet.unipi.it>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Luigi Rizzo wrote:
> 
> Hi,
> 
> what would be the right place to put a database of ethernet addresses ?
> There are various reasons i need this, one is to wire the ARP table
> so that machines cannot steal too easily other people's IPs,
> to do autoconfiguration on PicoBSD floppies, etc. etc.
> 
> Right now (in picobsd at least) i have put records of the form
> 
>         # 01:23:45:67:89:a0     hostname
> 
> (where the '#' is part of the format) in /etc/hosts, but perhaps
> there is a better standard place ?

/etc/ethers?  See ethers(5) and ethers(3) for more info.

-- 
            "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                         Softweyr LLC
wes@softweyr.com                                           http://softweyr.com/


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


From owner-freebsd-net  Thu Feb 24 17:57: 5 2000
Delivered-To: freebsd-net@freebsd.org
Received: from pooky.bmk.com.au (pooky.bmk.com.au [203.36.170.246])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8E06B37BD2F; Thu, 24 Feb 2000 17:56:46 -0800 (PST)
	(envelope-from brendan@bmk.com.au)
Received: from garfield (gateway.ozi.nu [203.36.170.241])
	by pooky.bmk.com.au (8.8.7/8.8.7) with SMTP id MAA06747;
	Fri, 25 Feb 2000 12:56:32 +1100
Date: Fri, 25 Feb 2000 12:57:32 +1100 (EST)
From: Brendan Kosowski <brendan@bmk.com.au>
X-Sender: brendan@garfield
To: FreeBSD Questions <freebsd-questions@freebsd.org>,
	FreeBSD Networking <freebsd-net@freebsd.org>
Subject: natd/pppd problem
Message-ID: <Pine.BSF.3.96.1000225124454.22491A-100000@garfield>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


I am trying to run natd using ppp0 as the public interface.

I have set up IPFIREWALL and IPDIVERT in my kernel.
My system has the following interfaces: ed1 and ppp0.

When my system boots the kernel gives me the following message:

"IP packet filtering initialized, divert disabled, logging disabled."

I have set up an OPEN firewall and enabled NATD with ppp0 as the public
interface in my rc.conf. GATEWAY is also ON.

If I drop the divert rule from my firwall rules the box works O.K. as a
gateway.

Can anyone help ???

Thanks.


-----------



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


From owner-freebsd-net  Fri Feb 25  0: 6: 0 2000
Delivered-To: freebsd-net@freebsd.org
Received: from hydrant.intranova.net (hydrant.intranova.net [209.201.95.10])
	by hub.freebsd.org (Postfix) with SMTP id F160337B799
	for <freebsd-net@freebsd.org>; Fri, 25 Feb 2000 00:05:52 -0800 (PST)
	(envelope-from oogali@intranova.net)
Received: (qmail 11100 invoked from network); 25 Feb 2000 08:05:56 -0000
Received: from localhost (user66504@127.0.0.1)
  by hydrant.intranova.net with SMTP; 25 Feb 2000 08:05:56 -0000
Date: Fri, 25 Feb 2000 03:05:56 -0500 (EST)
From: Omachonu Ogali <oogali@intranova.net>
To: Brendan Kosowski <brendan@bmk.com.au>
Cc: FreeBSD Questions <freebsd-questions@freebsd.org>,
	FreeBSD Networking <freebsd-net@freebsd.org>
Subject: Re: natd/pppd problem
In-Reply-To: <Pine.BSF.3.96.1000225124454.22491A-100000@garfield>
Message-ID: <Pine.BSF.4.10.10002250305140.10961-100000@hydrant.intranova.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Read the man page for natd, it will not work with ppp0, use ppp(8) with
the -alias option if you want aliasing/masquerading.

On Fri, 25 Feb 2000, Brendan Kosowski wrote:

> 
> I am trying to run natd using ppp0 as the public interface.
> 
> I have set up IPFIREWALL and IPDIVERT in my kernel.
> My system has the following interfaces: ed1 and ppp0.
> 
> When my system boots the kernel gives me the following message:
> 
> "IP packet filtering initialized, divert disabled, logging disabled."
> 
> I have set up an OPEN firewall and enabled NATD with ppp0 as the public
> interface in my rc.conf. GATEWAY is also ON.
> 
> If I drop the divert rule from my firwall rules the box works O.K. as a
> gateway.
> 
> Can anyone help ???
> 
> Thanks.
> 
> 
> -----------
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-net" in the body of the message
> 

-- 
+-------------------------------------------------------------------------+
| Omachonu Ogali                                     oogali@intranova.net |
| Intranova Networking Group                 http://tribune.intranova.net |
| PGP Key ID:                                                  0xBFE60839 |
| PGP Fingerprint:       C8 51 14 FD 2A 87 53 D1  E3 AA 12 12 01 93 BD 34 |
+-------------------------------------------------------------------------+



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


From owner-freebsd-net  Fri Feb 25  2:41: 1 2000
Delivered-To: freebsd-net@freebsd.org
Received: from sirius.stella-net.fr (sirius.stella-net.fr [195.154.71.2])
	by hub.freebsd.org (Postfix) with ESMTP id 21A5337BD7D
	for <freebsd-net@freebsd.org>; Fri, 25 Feb 2000 02:40:53 -0800 (PST)
	(envelope-from garry@stella-net.fr)
Received: from stella-net.fr ([193.48.73.34])
	by sirius.stella-net.fr (8.9.3/8.9.3) with ESMTP id LAA28171
	for <freebsd-net@freebsd.org>; Fri, 25 Feb 2000 11:40:50 +0100
Message-ID: <38B65E21.D0891CCD@stella-net.fr>
Date: Fri, 25 Feb 2000 11:49:05 +0100
From: Philippe Charron <garry@stella-net.fr>
Organization: Alcatel Space Industries
X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-net@freebsd.org
Subject: Natd/Mrouted
Content-Type: multipart/mixed;
 boundary="------------9732B810AEEF5DAC28249953"
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

This is a multi-part message in MIME format.
--------------9732B810AEEF5DAC28249953
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

I try to use Mrouted and natd on the same computer (FreeBSD 3.4) over
the following Network

Mbone ---[Router 1]----public_Lan_1---[FreeBSD 3.4]--- Private_Lan
                                           |
                                      [FreeBSD 3.2]--- Public_Lan_2

(Public_Lan_1 and Public_Lan_2 are connected using a FreeBSD 3.2 box
running Mrouted)

On the FreeBSD 3.4 I have 2 network cards : xl0 and xl1
xl0 is on a private LAN (192.168.1.0) and
xl1 is on a Public_Lan_1 (w.x.y.z)

Natd is configure for adress translation and seems to run fine: I can do
FTP and WWW on the private LAN.
When I run Mrouted (private addresses are filtered before accessing to
the MBone, by router 1) I have the following message :

> mrouted[5178]: mrouted version 3.9-beta3+IOS12
> mrouted[5178]: warning - received DVMRP message from self (check
device loopback): w.x.y.z

I can see Mbone session on the private Lan.
When I contribute to this session :
People can't see me on the MBone (correct)
People can see me on the Public_Lan_1 (correct)
People can't see me on the Public_Lan_2 (not correct as my TTL is big
enought)

If I start the computer without Natd, Mrouted work fine and people can
see me on the Public_lan_2

someone has an idee to configure Natd or/and Mrouted to work together ?
What about other multicast routing deamons (MBGP with mrtd or zebra for
example?)

Thanx
Philippe


--------------9732B810AEEF5DAC28249953
Content-Type: text/x-vcard; charset=us-ascii;
 name="garry.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Philippe Charron
Content-Disposition: attachment;
 filename="garry.vcf"

begin:vcard 
n:Charron;Philippe
tel;cell:+33 6 62 57 66 50
tel;fax:+33 4 92 92 76 10
tel;work:+33 4 92 92 79 89
x-mozilla-html:TRUE
org:Alcatel Space Industries;Departement Multimedia
version:2.1
email;internet:garry@stella-net.fr
adr;quoted-printable:;;BP 99=0D=0A100 Bvd du Midi;Cannes La Bocca;;06 156;France
x-mozilla-cpt:;0
fn:Philippe Charron
end:vcard

--------------9732B810AEEF5DAC28249953--



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


From owner-freebsd-net  Fri Feb 25  3:40:26 2000
Delivered-To: freebsd-net@freebsd.org
Received: from netcom.com (netcom11.netcom.com [199.183.9.111])
	by hub.freebsd.org (Postfix) with ESMTP id 5B7BA37BE8C
	for <freebsd-net@FreeBSD.ORG>; Fri, 25 Feb 2000 03:40:22 -0800 (PST)
	(envelope-from stanb@netcom.com)
Received: (from stanb@localhost)
	by netcom.com (8.9.3/8.9.3) id DAA02145
	for freebsd-net@FreeBSD.ORG; Fri, 25 Feb 2000 03:40:19 -0800 (PST)
From: Stan Brown <stanb@netcom.com>
Message-Id: <200002251140.DAA02145@netcom.com>
Subject: ep OACTIVE problem. help please
To: freebsd-net@FreeBSD.ORG (FreeBSD Networking)
Date: Fri, 25 Feb 2000 06:40:18 -0500 (EST)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

	I have a hP Vectra 486/33 with 2 4COM cards in it that I have been
	using for a gateway between 2 networks for about a month now. yesterday
	I started trying to use amanda across this gateway. It would go fine
	for a while and then hang.

	Debuging revelaed that one of the cards had changed it's flags as read
	with ifconfig. It had added the flag OACTIVE. A simple ifconfig down
	ep1 and ifconfig up ep1 wouyld restore this card to normal operation.
	No packets were being sent out this card while the OACTIVE flag was
	set.

	The ep man page does not give me a clue as to what this flag means.
	Could some kind soul tell me what this flag means?

	Also any advice as to why this is hapeneing woudl be appreciated. The
	2computers doing the manda exchange are both fairly fas (PII/350
	FreeBSD machine and  HP B1000). 3.4 STABLE if it matters.

	Thanks for any help on this. I need to get this fixed ASAP.

-- 
Stan Brown     stanb@netcom.com                                    404-996-6955
Factory Automation Systems
Atlanta Ga.
-- 
Look, look, see Windows 95.  Buy, lemmings, buy!   
Pay no attention to that cliff ahead...            Henry Spencer
(c) 1998 Stan Brown.  Redistribution via the Microsoft Network is prohibited.


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


From owner-freebsd-net  Fri Feb 25 14: 9: 2 2000
Delivered-To: freebsd-net@freebsd.org
Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5F03137BD3D; Fri, 25 Feb 2000 14:08:53 -0800 (PST)
	(envelope-from archie@whistle.com)
Received: (from archie@localhost)
	by bubba.whistle.com (8.9.3/8.9.2) id OAA07017;
	Fri, 25 Feb 2000 14:08:09 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <200002252208.OAA07017@bubba.whistle.com>
Subject: Re: natd/pppd problem
In-Reply-To: <Pine.BSF.3.96.1000225124454.22491A-100000@garfield> from Brendan Kosowski at "Feb 25, 2000 12:57:32 pm"
To: brendan@bmk.com.au (Brendan Kosowski)
Date: Fri, 25 Feb 2000 14:08:09 -0800 (PST)
Cc: freebsd-questions@FreeBSD.ORG (FreeBSD Questions),
	freebsd-net@FreeBSD.ORG (FreeBSD Networking)
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Brendan Kosowski writes:
> I have set up IPFIREWALL and IPDIVERT in my kernel.
> My system has the following interfaces: ed1 and ppp0.
> 
> When my system boots the kernel gives me the following message:
> 
> "IP packet filtering initialized, divert disabled, logging disabled."

For one thing you didn't compile properly with IPDIVERT, because otherwise
it would have said "divert enabled"..

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com


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


From owner-freebsd-net  Fri Feb 25 18:11:56 2000
Delivered-To: freebsd-net@freebsd.org
Received: from ultra.ultra.net.au (ultra.ultra.net.au [203.20.237.5])
	by hub.freebsd.org (Postfix) with ESMTP id 163C937B9EC
	for <freebsd-net@FreeBSD.ORG>; Fri, 25 Feb 2000 18:11:53 -0800 (PST)
	(envelope-from lbarton@ultra.net.au)
Received: from ultranet (p142.prem3-tsv.ultra.net.au [202.80.67.142])
	by ultra.ultra.net.au (8.9.3/8.9.3) with SMTP id MAA17106
	for <freebsd-net@FreeBSD.ORG>; Sat, 26 Feb 2000 12:11:49 +1000 (EST)
Message-ID: <013a01bf7fff$31196880$140bfea9@ultranet.ultra.net.au>
From: "Lee-Ann Barton" <lbarton@ultra.net.au>
To: <freebsd-net@FreeBSD.ORG>
Subject: 
Date: Sat, 26 Feb 2000 12:14:18 +1000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0137_01BF8053.019EF9E0"
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_0137_01BF8053.019EF9E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

unsubscribe freebsd-net@FreeBSD.ORG lbarton@ultra.net.au

------=_NextPart_000_0137_01BF8053.019EF9E0
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#ffffff>
<DIV><FONT color=3D#000000 size=3D2>unsubscribe <A=20
href=3D"mailto:freebsd-net@FreeBSD.ORG">freebsd-net@FreeBSD.ORG</A> <A=20
href=3D"mailto:lbarton@ultra.net.au">lbarton@ultra.net.au</A></FONT></DIV=
></BODY></HTML>

------=_NextPart_000_0137_01BF8053.019EF9E0--



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


From owner-freebsd-net  Sat Feb 26  3:42:24 2000
Delivered-To: freebsd-net@freebsd.org
Received: from awfulhak.org (dynamic-117.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.245])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6804037BBFE; Sat, 26 Feb 2000 03:42:19 -0800 (PST)
	(envelope-from brian@Awfulhak.org)
Received: from hak.lan.Awfulhak.org (root@shift.lan.awfulhak.org [172.16.0.12])
	by awfulhak.org (8.9.3/8.9.3) with ESMTP id KAA58674;
	Sat, 26 Feb 2000 10:56:26 GMT
	(envelope-from brian@hak.lan.Awfulhak.org)
Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1])
	by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id KAA63695;
	Sat, 26 Feb 2000 10:56:27 GMT
	(envelope-from brian@hak.lan.Awfulhak.org)
Message-Id: <200002261056.KAA63695@hak.lan.Awfulhak.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Omachonu Ogali <oogali@intranova.net>
Cc: Brendan Kosowski <brendan@bmk.com.au>,
	FreeBSD Questions <freebsd-questions@FreeBSD.org>,
	FreeBSD Networking <freebsd-net@FreeBSD.org>
Subject: Re: natd/pppd problem 
In-Reply-To: Message from Omachonu Ogali <oogali@intranova.net> 
   of "Fri, 25 Feb 2000 03:05:56 EST." <Pine.BSF.4.10.10002250305140.10961-100000@hydrant.intranova.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 26 Feb 2000 10:56:27 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> Read the man page for natd, it will not work with ppp0, use ppp(8) with
> the -alias option if you want aliasing/masquerading.

That's not true, although the comment in the natd man page is 
misleading.  It's possible to use natd w/ pppd or ppp, it's just not 
as easy as using ``ppp -nat''.  Hmm, I must fix that comment in the 
man page - it's -nat, not -alias.

> On Fri, 25 Feb 2000, Brendan Kosowski wrote:
> 
> > 
> > I am trying to run natd using ppp0 as the public interface.
> > 
> > I have set up IPFIREWALL and IPDIVERT in my kernel.
> > My system has the following interfaces: ed1 and ppp0.
> > 
> > When my system boots the kernel gives me the following message:
> > 
> > "IP packet filtering initialized, divert disabled, logging disabled."
> > 
> > I have set up an OPEN firewall and enabled NATD with ppp0 as the public
> > interface in my rc.conf. GATEWAY is also ON.
> > 
> > If I drop the divert rule from my firwall rules the box works O.K. as a
> > gateway.
> > 
> > Can anyone help ???
> > 
> > Thanks.
[.....]
> -- 
> +-------------------------------------------------------------------------+
> | Omachonu Ogali                                     oogali@intranova.net |
> | Intranova Networking Group                 http://tribune.intranova.net |
> | PGP Key ID:                                                  0xBFE60839 |
> | PGP Fingerprint:       C8 51 14 FD 2A 87 53 D1  E3 AA 12 12 01 93 BD 34 |
> +-------------------------------------------------------------------------+

-- 
Brian <brian@Awfulhak.org>                        <brian@FreeBSD.org>
      <http://www.Awfulhak.org>                   <brian@OpenBSD.org>
Don't _EVER_ lose your sense of humour !          <brian@FreeBSD.org.uk>




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