On Tue, 16 Mar 2004 23:39:56 -0800
"Crist J. Clark" <[EMAIL PROTECTED]> wrote:
> But it looks like my guess is probably correct. The receive buffer at
> the FreeBSD end is full. When it receives more TCP data, it cannot
> accept it so it ACKs up to whatever it has in the buffer and not what
> the
On Wed, Mar 17, 2004 at 10:14:53AM +0300, Zherdev Anatoly wrote:
> On Tue, 16 Mar 2004 16:06:11 -0800
> "Crist J. Clark" <[EMAIL PROTECTED]> wrote:
>
>
> [Skip...]
> ^
> > The zero window-size tells me the TCP buffer on the FreeBSD
On Tue, 16 Mar 2004 16:06:11 -0800
"Crist J. Clark" <[EMAIL PROTECTED]> wrote:
[Skip...]
^
> The zero window-size tells me the TCP buffer on the FreeBSD side is
> full. The Cisco is trying to send that last byte of data and the FIN
On Tue, Mar 16, 2004 at 12:53:35PM +0300, Zherdev Anatoly wrote:
> Hello.
>
> I have problem with tcp session close between cisco and freebsd
> Looks like that it bug in freebsd tcp stack.
>
> CISCO state:
>
> sh tcp brief
> 62935208 CISCO..990FREEBSD.513 FINWAIT1
>
>
> FreeBSD state:
>
On Tue, 16 Mar 2004 15:34:24 +0300
Gleb Smirnoff <[EMAIL PROTECTED]> wrote:
> Z> But in IPFW i have ACCEPT by default and only this deny rules:
> Z>
> Z> 00200 deny ip from any to 127.0.0.0/8
> Z> 00300 deny ip from 127.0.0.0/8 to any
> Z> 00400 deny log logamount 100 tcp from any to any 135-139,
On Tue, Mar 16, 2004 at 03:18:32PM +0300, Zherdev Anatoly wrote:
Z> > > So no obvious suspect. Before digging deep into the code its better
Z> > > to have some more surrounding information.
Z> >
Z> > Another question: any packet filters in between ?
Z>
Z> Yes i have IPFW1 on this servers (it was
On Tue, 16 Mar 2004 11:29:45 + (UTC)
"Bjoern A. Zeeb" <[EMAIL PROTECTED]> wrote:
> > > FreeBSD 4.9-STABLE cvsupped March 3
> > > Cisco IOS 12.2.19a ip only Cisco 5300
> >
> > Do you know when it was working correctly the last time? Do you have
> > another machine (4.9R or lower, or 5.2 or 5.
On Tue, 16 Mar 2004 11:34:52 +0100
Andre Oppermann <[EMAIL PROTECTED]> wrote:
> Do you know when it was working correctly the last time?
I can't say closely because i first time look that situation on tcp level. But i have
rlogin sessions that was'nt closed but cisco send stop packet in RADIUS
On Tue, 16 Mar 2004, Andre Oppermann wrote:
> Zherdev Anatoly wrote:
> >
> > On Tue, 16 Mar 2004 10:59:06 +0100
> > Andre Oppermann <[EMAIL PROTECTED]> wrote:
> >
> > > Zherdev Anatoly wrote:
> > > >
> > > > Hello.
> > > >
> > > > I have problem with tcp session close between cisco and freebsd
> >
Zherdev Anatoly wrote:
>
> On Tue, 16 Mar 2004 10:59:06 +0100
> Andre Oppermann <[EMAIL PROTECTED]> wrote:
>
> > Zherdev Anatoly wrote:
> > >
> > > Hello.
> > >
> > > I have problem with tcp session close between cisco and freebsd
> > > Looks like that it bug in freebsd tcp stack.
> >
> > What ve
On Tue, 16 Mar 2004 10:59:06 +0100
Andre Oppermann <[EMAIL PROTECTED]> wrote:
> Zherdev Anatoly wrote:
> >
> > Hello.
> >
> > I have problem with tcp session close between cisco and freebsd
> > Looks like that it bug in freebsd tcp stack.
>
> What version of FreeBSD and Cisco IOS do you run on
Zherdev Anatoly wrote:
>
> Hello.
>
> I have problem with tcp session close between cisco and freebsd
> Looks like that it bug in freebsd tcp stack.
What version of FreeBSD and Cisco IOS do you run on these machines?
--
Andre
> CISCO state:
>
> sh tcp brief
> 62935208 CISCO..990FREEBSD
Hello.
I have problem with tcp session close between cisco and freebsd
Looks like that it bug in freebsd tcp stack.
CISCO state:
sh tcp brief
62935208 CISCO..990FREEBSD.513 FINWAIT1
FreeBSD state:
netstat -an
tcp4 57352 0 FREEBSD.513CISCO.990 ESTABLISHED
TCP sess
13 matches
Mail list logo
