|
|
> > > * Source addresses on VPN packets coming from a > > > particular client must be associated with that > > > client in the OpenVPN internal routing table. > > > > How is protocols other than IP handled? Do they pass or are they dropped? > > Perhaps that should be an option? > > This code is only active when you are running in IPv4 routing mode (i.e. > --mode server --dev tun). When you are running --mode server --dev tap, > OpenVPN internally bridges between the server's tap interface and the tap > interfaces of all clients, and this source address check will not occur > because OpenVPN's internal routing table consists of MAC addresses rather than > IPv4 addresses. And as a bridge, OpenVPN will be scanning packets to "learn" > which MAC addresses are associated with which client. Just got another idea. Havn't really thought if it is good or not yet but.. If it would be possible to push a mac address to the client, then you could check the source mac address instead of checking the ip address. This would solve the problem regardless of which protcol is used above the ethernet layer (IPv4, IPv6, IPX etc). Then one could apply diffrent firewall rules based on the mac address instead. Ofcource this would have to be an option set individually for each user, as some clients might be a bridge to a whole network, and then this wouldn't work. /Mathias -- _____________________________________________________________ Mathias Sundman (^) ASCII Ribbon Campaign NILINGS AB X NO HTML/RTF in e-mail Tel: +46-(0)8-666 32 28 / \ NO Word docs in e-mail ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |