Hi,
I've been pondering the same issue and am currently running 5.3-R modified
in the
way you've described. (diff at http://jodocus.org/ipsec-pfil.diff I'm not
an
experienced kernel-hacker, so use at own risk)
Great, I'll have to try this.
For IPSEC this also means that the resulting ESP and A
Hi,
I am experiencing the same problem as well when I updated from a March
6, 2004 -CURRENT to the October 19, 2004 -CURRENT. The problem still
exists with the October 27, 2004 -CURRENT. I'm using ipfw/dummynet
for outgoing queues with the ACK packets having the highest priority
in it's own queue
I am experiencing the same problem as well when I updated from a March
6, 2004 -CURRENT to the October 19, 2004 -CURRENT. The problem still
exists with the October 27, 2004 -CURRENT. I'm using ipfw/dummynet
for outgoing queues with the ACK packets having the highest priority
in it's own queue. H
> This looks promising:
> http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcp-dcr-01.txt
>
> Sounds as if it has been prototyped under the Linux stack. I will
> try to find out more.
Ethan Blanton and I have started working with these folks and we are
going to soon have a new i-d out. We ar
This looks promising:
http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcp-dcr-01.txt
Sounds as if it has been prototyped under the Linux stack. I will
try to find out more.
Regards,
BMS
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mai
This has long bugged me and tonight I finally snapped and had to do
something about it. Example output:
64 bytes from a.b.c.d: icmp_seq=935 ttl=126 time=33.824 ms
64 bytes from a.b.c.d: icmp_seq=936 ttl=126 time=29.138 ms
64 bytes from a.b.c.d: icmp_seq=937 ttl=126 time=28.262 ms
64 bytes from a.b
On Sun, 31 Oct 2004, Sean Chittenden wrote:
> This has long bugged me and tonight I finally snapped and had to do
> something about it. Example output:
>
> 64 bytes from a.b.c.d: icmp_seq=935 ttl=126 time=33.824 ms
> 64 bytes from a.b.c.d: icmp_seq=936 ttl=126 time=29.138 ms
> 64 bytes from a.b.c
Sean Chittenden wrote:
[ ...cleaning up ping's output... ]
Anyone mind if I commit the attached patch? I'm sure I'm not the only
one who's wanted to commit the following. -sc
Yay! By all means, please commit this change.
--
-Chuck
___
[EMAIL PROTECTED
This has long bugged me and tonight I finally snapped and had to do
something about it. Example output:
64 bytes from a.b.c.d: icmp_seq=935 ttl=126 time=33.824 ms
64 bytes from a.b.c.d: icmp_seq=936 ttl=126 time=29.138 ms
64 bytes from a.b.c.d: icmp_seq=937 ttl=126 time=28.262 ms
64 bytes from a
On Sun, 31 Oct 2004, kamal kc wrote:
> I have made a bridge using the Packet Capture Library I set the two nics
> to promiscous mode and transfer packet between the two packet capture
> handles A piece of the code I use for initializing the packet capture
Copying every packet into and out of use
I have made a bridge using the Packet Capture Library
I set the two nics to promiscous mode and transfer packet
between the two packet capture handles
A piece of the code I use for initializing the packet capture device descriptor---
.
pcap_t *pd;
pd = (pcap_t *)malloc(sizeof(*pd));
if (pd ==
11 matches
Mail list logo
