Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - oisteink

#1
I'm in the same boat as you :)

Here's what the most recent paper I found on dummynet states:
QuoteIn some situations it is useful to aggregate traffic into flows, and pass each flow through a separate pipe. This is achieved with a feature called "dynamic pipes": "mask" parameters can be specified in the configuration of a pipe, which indicate the bits in the 5-tuple of a packet (protocol, addresses and ports) that should be used to group packets into flows. For each pattern resulting after masking, a new pipe will be created, and matching traffic will be directed to it. As an example, the rule:
ipfw pipe 4 config mask src-ip 0x000000ff bw 1Mbit/s
will group packets with the same value of the least significant 8 bits in the source address, and direct each flow to a new instance of pipe 4. The bandwidth of each instance is 1 Mbit/s.

Reference: http://info.iet.unipi.it/~luigi/papers/20100304-ccr.pdf

Setting mask on a pipe to destination gives: mask:  0x00 0x00000000/0x0000 -> 0xffffffff/0x0000
While setting mask to source gives: mask:  0x00 0xffffffff/0x0000 -> 0x00000000/0x0000

I will stay away from dynamic pipes until I can fully understand how they work.
#2
Note: I've just started looking at opnsense.
This guide has the following settings (adjusted to your values):

Upstream pipe
Bandwidth: 9500 kbit/s
Mask: Destination

Downstream pipe
Bandwidth: 48 Mbit/s
Mask: Destination

Upstream rule:
Interface: WAN
Source: 192.168.1.0/24 (Your lan net)
Target: Upstream pipe

Downstream rule:
Interface: WAN
destination: 192.168.1.0/24 (Your lan net)
Target: Downstream pipe

As I said i'm not familiar with opnsense terminology yet, and not with the dynamic queue creation. Your settings differ in that you have SOURCE set on one of your pipes. The general help on pipes say:
Dynamic queue creation by source or destination address.
choose destination here to share the total bandwidth of this pipe among all connected clients.
choose source to provide all connected clients up to a maximum of this pipe configured bandwidth

What I've done myself, and can verify that works are:
Make a hard limit upstream and downstream pipe and make rules to put traffic into these.
To do so :
- I made two pipes with only bandwidth limit set.
- I made two rules to put traffic into these pipes. One rule on wan putting data into my downstream and one rule on lan putting into my upstream. As I have no automatic queue creation this will only limit data, and not do any queueing.
#3
Sorry to resurrect an old thread but it shows fairly high up on google when you search.

I had the same issue and solved it by:
Setting up an LDAP server for VPN acces
- Setting memberOf=<my vpn group dn here> in the extended search.

Works as intended - only tried Open VPN so far. Users that are member of the VPN group can connect, other users can not.