On Friday 29 July 2005 13:43, N White wrote:
I understand this now, and why it would be... as you put it yuck. Ha
Ha! Well thanks for answering my question and explaining it to me. Looks
like some custom scripting for me then. :-) My only problem now is going
to be figuring out how to send
[EMAIL PROTECTED] (Paul Hampson) wrote:
This last point seems trivial until you try to proxy backwards
through a chain you have only the last hop of, and the last hop
doesn't neccessarily know what the previous hop was.
Exaclty. Coupled with the problem that the server is *supposed* to
Alan DeKok wrote:
[EMAIL PROTECTED] (Paul Hampson) wrote:
This last point seems trivial until you try to proxy backwards
through a chain you have only the last hop of, and the last hop
doesn't neccessarily know what the previous hop was.
Exaclty. Coupled with the problem that the
N White [EMAIL PROTECTED] wrote:
Yes 192.168.1.1 is the NAS.
Then it's running FreeRADIUS. The error message you quoted above:
ad_recv: Disconnect-Request packet from host 192.168.1.2:47874, id=139,
length=31
Unknown packet code 40 from client 192.168.1.2:47874 - ID 139 : IGNORED
Can
Alan DeKok wrote:
N White [EMAIL PROTECTED] wrote:
Yes 192.168.1.1 is the NAS.
Then it's running FreeRADIUS. The error message you quoted above:
ad_recv: Disconnect-Request packet from host 192.168.1.2:47874, id=139,
length=31
Unknown packet code 40 from client 192.168.1.2
N White [EMAIL PROTECTED] wrote:
That's correct. Read my second reply. So other then writing custom
scripts, is there a way for the RADIUS server(FreeRADIUS) to be told to
send a disconnect packet to the NAS that a particular user is logged in
to(NAS could vary - Portmaster, Cisco, PPPoE
On Thu, Jul 28, 2005 at 06:20:35PM -0700, N White wrote:
That's correct. Read my second reply. So other then writing custom
scripts, is there a way for the RADIUS server(FreeRADIUS) to be told to
send a disconnect packet to the NAS that a particular user is logged in
to(NAS could vary -
server:
ad_recv: Disconnect-Request packet from host 192.168.1.2:47874, id=139,
length=31
Unknown packet code 40 from client 192.168.1.2:47874 - ID 139 : IGNORED
I also came across this:
http://www.freeradius.org/faq/#4.3
But why then is there a command as part of radclient to disconnect
Is 192.168.1.1 the IP address of the NAS?
ad_recv: Disconnect-Request packet from host 192.168.1.2:47874, id=139,
length=31
Unknown packet code 40 from client 192.168.1.2:47874 - ID 139 : IGNORED
FreeRADIUS doesn't listen for disconnect packets. And, you're
sending the disconnect packet
disconnect mysecret -x
Is 192.168.1.1 the IP address of the NAS?
ad_recv: Disconnect-Request packet from host 192.168.1.2:47874, id=139,
length=31
Unknown packet code 40 from client 192.168.1.2:47874 - ID 139 : IGNORED
FreeRADIUS doesn't listen for disconnect packets. And, you're
192.168.1.1 disconnect
mysecret -x
Is 192.168.1.1 the IP address of the NAS?
ad_recv: Disconnect-Request packet from host 192.168.1.2:47874,
id=139, length=31
Unknown packet code 40 from client 192.168.1.2:47874 - ID 139 : IGNORED
FreeRADIUS doesn't listen for disconnect packets
Yes 192.168.1.1 is the NAS. I thought that's what radclient did - told
the RADIUS server to send a disconnect to the NAS that the client(user)
is connected to. I've tried sending the disconnect to the
NAS(Portmaster). Any particular port?
Not sure about Portmaster, but the general
12 matches
Mail list logo
