On Fri, Dec 12, 2014 at 09:06:46PM +1100, Luigi Rizzo wrote:
> you can set the limit for the pipe, create two queues with different
> weights attached to the pipe, and then schedule.
>
> ipfw pipe 12 config bw 3456 Kbit/s
> ipfw queue 34 config weight 2 pipe 12
> ipfw queue 56 config weight 1 pipe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194515
--- Comment #4 from Craig Rodrigues ---
-- Forwarded message --
From: Ivan UAdm
Date: Wed, Dec 10, 2014 at 8:49 AM
Subject: bug id 194515
Hi, Craig
i was update enviroment to 10.1-release, but bug is still there
> Can
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194515
--- Comment #3 from Craig Rodrigues ---
Created attachment 150527
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=150527&action=edit
pf_min.conf
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194515
--- Comment #2 from Craig Rodrigues ---
Created attachment 150526
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=150526&action=edit
fatal_trap12-p1.png
--
You are receiving this mail because:
You are the assignee for the bug.
_
Hello,
My searching indicates I need urndis but it isn't in ports and I don't
know what to do with the C source file...
Is there a simple cookbook way to tether?
TIA
Bernard Higonnet
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/
At 10:35 AM 12/12/2014, John Nielsen wrote:
Is there a reason you can't use a separate pipe for each direction?
We want to limit the total amount of bandwidth consumed, based on
the formula 2U + D <= L. If we used two pipes, there would be no
way to keep track of the sum.
What I need (and
> On Friday, December 12, 2014 12:26:24 PM Jack Vogel wrote:
> > I think I'd go along with Mike, keeping it simpler seems like a good idea.
> >
> > Jack
> If the userland ABI impact isn't too broad I think this is fine. Mike, do you
> know off hand how many user-facing things would be affected?
On Friday, December 12, 2014 12:26:24 PM Jack Vogel wrote:
> I think I'd go along with Mike, keeping it simpler seems like a good idea.
>
> Jack
If the userland ABI impact isn't too broad I think this is fine. Mike, do you
know off hand how many user-facing things would be affected?
> On Fri, D
I think I'd go along with Mike, keeping it simpler seems like a good idea.
Jack
On Fri, Dec 12, 2014 at 6:39 AM, Mike Karels wrote:
>
> > Any other thoughts, or should I start looking at seeing what I can take
> > copy from net80211?
>
> > Also adding -net, since this is pretty relevant.
>
> I
On Dec 12, 2014, at 8:23 AM, Brett Glass wrote:
> At 03:06 AM 12/12/2014, Luigi Rizzo wrote:
>
>> you can set the limit for the pipe, create two queues with different
>> weights attached to the pipe, and then schedule.
>>
>> ipfw pipe 12 config bw 3456 Kbit/s
>> ipfw queue 34 config weight 2 pi
At 03:06 AM 12/12/2014, Luigi Rizzo wrote:
you can set the limit for the pipe, create two queues with different
weights attached to the pipe, and then schedule.
ipfw pipe 12 config bw 3456 Kbit/s
ipfw queue 34 config weight 2 pipe 12
ipfw queue 56 config weight 1 pipe 12
ipfw add queue 34 in re
> Any other thoughts, or should I start looking at seeing what I can take
> copy from net80211?
> Also adding -net, since this is pretty relevant.
I had the same reaction as Adrian initially, as an int with numerous fields
seems really messy. However, I don't think we have the challenges of 802.
--On 12 Dec 2014 14:48:51 +0300 "Andrey V. Elsukov"
wrote:
On 12.12.2014 14:13, Göran Löwkrantz wrote:
Host: 10.1-STABLE FreeBSD 10.1-STABLE #0 r275046
Sw: strongswan-5.2.0_1
Putting up an ESP tunnel between 192.168.2.0/24 and 192.168.40.8/29 over
endpoints X and W. The outgoing traffic is p
On 12.12.2014 14:13, Göran Löwkrantz wrote:
> Host: 10.1-STABLE FreeBSD 10.1-STABLE #0 r275046
> Sw: strongswan-5.2.0_1
>
> Putting up an ESP tunnel between 192.168.2.0/24 and 192.168.40.8/29 over
> endpoints X and W. The outgoing traffic is passed through a DMZ and
> exists on my side through a f
Host: 10.1-STABLE FreeBSD 10.1-STABLE #0 r275046
Sw: strongswan-5.2.0_1
Putting up an ESP tunnel between 192.168.2.0/24 and 192.168.40.8/29 over
endpoints X and W. The outgoing traffic is passed through a DMZ and exists
on my side through a firewall with inner address Y and outer address U.
A
you can set the limit for the pipe, create two queues with different
weights attached to the pipe, and then schedule.
ipfw pipe 12 config bw 3456 Kbit/s
ipfw queue 34 config weight 2 pipe 12
ipfw queue 56 config weight 1 pipe 12
ipfw add queue 34 in recv halfduplexlink0
ipfw add queue 56 out xmit
Everyone:
I have an interesting problem that I'm trying to solve with
FreeBSD's IPFW and DUMMYNET facilities. I have an application in
which, due to arbitration overhead, a half duplex data link has
significantly higher costs -- typically about twice as much -- in
one direction than in the ot
17 matches
Mail list logo