Leandro Pereira de Lima e Silva - ViaLink [EMAIL PROTECTED] wrote:
I've already set up a sniffer on the machine to check to what port they
are sending the packets and it's to 1812.
To 1812, or from 1812?
That message is printed only when Access-Request packets go to
non-1812 ports.
Alan, it's going to 1812. As we can see at the log that I posted, it's
coming from port 49852.
Thanks, Leandro.
Alan DeKok escreveu:
Leandro Pereira de Lima e Silva - ViaLink [EMAIL PROTECTED] wrote:
I've already set up a sniffer on the machine to check to what port they
are sending the
By the way, there is any way of authorizing the other ports (1813 and
1814) to receive auth packets?
I tried that with listen directive, but the port was already open so it
didn't worked.
Thanks, Leandro.
Alan DeKok escreveu:
Leandro Pereira de Lima e Silva - ViaLink [EMAIL PROTECTED] wrote:
Leandro Pereira de Lima e Silva - ViaLink [EMAIL PROTECTED] wrote:
Alan, it's going to 1812. As we can see at the log that I posted, it's
coming from port 49852.
OK. I've never seen that problem before, so I'm not sure what to
say.
Alan DeKok.
-
List info/subscribe/unsubscribe? See
Alan,
thank you very much for your help. I saw in sniffer packets going to
1812 and 1813, so I presumed that auth and acct ports were correct.
Today I modified freeradius source to show me the destination port in
the error and got a little surprise.
They were sending auth to 1813 and acct to
to a non-authentication port from client
nas-intelig-1:49852 - ID 141 : IGNORED
--- Walking the entire request list ---
Nothing to do. Sleeping until we see a request.
rad_recv: Access-Request packet from host 200.184.x.x:49852, id=141,
length=124
Authentication-Request sent to a non-authentication
6 matches
Mail list logo
