Miku Jha wrote:
[ ... ]
The situation is that if the client crashes, the server eventually sends a
RST (10.39.53) Following this RST, the client comes back in lets say around
2-3 minutes. Now when the client sends a SYN(10.42.23), there is no
timestamp option.
If the client opens a connection
--- Chuck Swiger <[EMAIL PROTECTED]> wrote:
> jha miku wrote:
> > In case of active open, the SYN segments always
> have
> > timestamp enabled, since the RFC flg is set. But,
> > Currently, I am seeing some SYN segments without
> > timestamp option.
>
> FreeBSD (and OS X, and other things using
jha miku wrote:
In case of active open, the SYN segments always have
timestamp enabled, since the RFC flg is set. But,
Currently, I am seeing some SYN segments without
timestamp option.
FreeBSD (and OS X, and other things using a BSD network stack) will generate
initial TCP SYN packets contain
Does anybody have a patch for FreeBSD which provides the same functionality as
obsd does as in the following? (Basicly I'm looking at carping a bridge0
interface)
http://www.monkey.org/openbsd/archive2/tech/200412/msg4.html
This patch has been merged into obsd's -HEAD best I can see.
--
Donatas wrote:
hello,
I am sorry for a previous diagram that got wrapped .
If someone could take a look at the picture explaining the problem, I would be
thankfull.
ftp://temp:[EMAIL PROTECTED]/routing_problem.jpg - 136Kbytes.
Short description of a problem: I can't find a way to divert or route
Hi Claudio, Steve,
> > While user is blocked by _our_ generated MAC! Btw, could anyone advice
> > me how to block user IP block without touching ipfw (I think to use
> > route + ``-blackhole' to that user that have no his MAC in my ARP
> > table), any ideas?
I'm just wondering why you don't want
