6 Apr
2018
6 Apr
'18
1:44 p.m.
On Apr 6, 2018, at 1:34 PM, Phil Frost <phil@postmates.com> wrote:
But I'll offer an alternate direction of research in case adjusting the freeradius configuration turns out to be a dead end. If the sending socket isn't explicitly bound to an address, the kernel will consult the routing tables to decide on a source address. For example, on my Linux desktop packets destined for 8.8.8.8 will use the source address 192.168.1.102:
That's the answer here. And... this is why FreeRADIUS can be bound to to (a) a specific IP, such as the VPN IP, or (b) to a specific ethernet interface, such as the VPN interface This is documented in the configuration files. Alan DeKok.