On 10/12/2011 6:22 PM, Vassilis V. wrote: > Jim Pingle wrote on 12.10.2011 23:55: >> In 2.0 each interface is renamed in a unique way so you do not need dev >> tun or any similar entries in the options. >> >> You can assign the interfaces if you want (set an IP type of 'none' on >> them) and filter individually if you want, too. >> >> I run with two of mine assigned and 3+ more unassigned and have no issues. > > Thank you for the info! Would the rules on the assigned tabs have > priority over the unassigned OpenVPN Tab? Or is the unassigned Tab > bypassed as long as there is a assigned one?
I'd have to check the code to be sure, but I know that the per-interface rules take precedence, and I believe once it's assigned the rules on the OpenVPN tab no longer apply to that interface. > I noticed the unique renaming, is it also stable? E.g. ovpns1 will > always be the same server as written in () next to it? It will be stable. Each OpenVPN instance is given a unique ID that never changes, and that is used as the interface number, combined with the type. So if you have two, a server and a client (client made first) you'd have ovpnc1 and ovpns2. If you make a new client, it would be ovpnc3, and so on. Jim _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
