source ip check
Bassem Mettichi
mettichi at gmail.com
Fri Apr 6 18:50:20 CEST 2018
Hello,
thakns a lot Alan for this response this is really my problem. because when
i send the packet from the client side the destion IP is the VIP ( ported
by keeplaived)
however when i receive the response i get source IP of freerdaius server
instead of the VIP ( normally the source IP of the response packet should
be the VIP ) .
but i don't know this behavior why keepalived and lvs are changing the IP
source of the packet.
thanaks a lot Alan
Mettichi Bassem
2018-04-06 17:26 GMT+01:00 Alan DeKok <aland at deployingradius.com>:
> On Apr 6, 2018, at 12:19 PM, Bassem Mettichi <mettichi at gmail.com> wrote:
> >
> > i have keeplaived and lvs with 2 freerdaius servers running version
> 3.0.16
> > on redhat 7 ( keeplaived is configured with NAT option)
> >
> > when i send an accounting start from a client vm using radclient i get
> this
> > response:
> >
> > radclient: Received reply to request we did not send. (id=134 socket 3)
>
> Your network is broken. Fix that.
>
> FreeRADIUS works. It sends correct replies when it receives correct
> requests.
>
> Since that isn't happening here, it's because of something *else* in the
> network. Which isn't the fault of FreeRADIUS.
>
> Read the source and destination IPs of the request and reply packet.
> They should match. If they don't (and they won't), it's because something
> else is breaking RADIUS.
>
> This shouldn't be difficult. Install a simple configuration. It WILL
> work. And *understand* the system you've built.
>
> Alan DeKok.
>
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/
> list/users.html
More information about the Freeradius-Users
mailing list