Markus Krause <[EMAIL PROTECTED]> wrote:
> Sending Access-Accept of id 238 to 192.168.10.2:2430
> Session-Timeout = 600
> User-Name := "test1"
...
> rad_recv: Accounting-Request packet from host 192.168.10.2:9000, id=15,
> length=123
> Acct-Delay-Time = 0
> NAS-Ident
"Drew S. Dupont" <[EMAIL PROTECTED]> wrote:
> This app used to work just fine before my recent HD and MoBo crashes
> today. I had to restore the system from a backup and the app. will no
> longer work.
Uh... make sure it works on a machine that *doesn't* have hardware problems.
Alan DeKok.
When I run radiusd from the command line in a Fedora Core 1/RedHat 9
base system, it will start w/o any problems. However, when I try to
start radiusd from inside a helper app., it says it is ready to
process requests but then throws the following error to the
radius.log file:
Sun Nov 13 22:3
I am aware of the fact
that 1 VLAN per port is possible. Besides – I am using mac-based
authentication, so Ive tried what happens when I connect only one computer per
switch port, but as I already have written, the Radius-Reply is kind of ignored
L. Has anyone have such problems or its just
The 2626
supports 1 VLAN per port. I'm not sure exactly
how the 2626 deals with multiple supplicants... but I
would bet (based on passed experience on other switches)... the 2626
ignores all 802.1x (EAP Starts) from any subsequent endpoints
after the first successful authentication (until the
port
[EMAIL PROTECTED] wrote:
OK, I had no luck with my previous email so let's try a different approach.
Could I use the Counter module to count the number of times a user gets
their password wrong? I guess I need to call Counter on Access-Reject, or
just before the Reply packet is sent as I can ch
Sure – but that ain’t
working.. at least not on my switches and don’t ask me why... I usually
have 2-3 computers on one port ( but computers have the same VLANID in RADIUS
), so might that be the problem?
Regards,
Edvin Seferovic
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PR
First, this information is well documented
both by ProCurve and in RFC3580.
That said the AV pairs you're looking for are
as follows:
Tunnel-Medium-Type =
802
Tunnel-Private-Group-ID = 123 (the
VLAN)
Tunnel-Type = VLAN
Jeff
Original Message Subject:
assigning a vlan-id after
=?iso-8859-1?Q?Bj=F8rn_Mork?= <[EMAIL PROTECTED]> wrote:
> We don't really _know_ that rlm_perl is the cause, though...
Try grabbing revision 1.19 of rlm_perl from CVS.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Sebastian Mauer <[EMAIL PROTECTED]> wrote:
> The domain enabled machines are in ou=Machines,dc=rnet,dc=lan and
> their Machine Password is stored too in a SambaNTPassword Attribute.
So update the LDAP queries to look there.
> So it might work if FreeRadius is able to find the machine entry in
>
Alan DeKok schrieb:
>Sebastian Mauer <[EMAIL PROTECTED]> wrote:
>
>
>>I found a lot of helpful HowTos and Documentations but never
>>managed to get Information about Computer Logons with PEAP.
>>
>>
>
> This was discussed very recently on this list. See the list archives.
>
> Alan DeKok.
OK, I had no luck with my previous email so let's try a different approach.
Could I use the Counter module to count the number of times a user gets
their password wrong? I guess I need to call Counter on Access-Reject, or
just before the Reply packet is sent as I can check the attributes sent
bac
Hello,
I wonder if you were able to resolve this bug? ref
http://bugs.freeradius.org/show_bug.cgi?id=221
The reason I ask is that I've just experienced a serious memory leak
after upgrading from 1.0.1 to 1.0.5, and we do use rlm_perl so that is
one module to suspect. It seems that a colleague of
13 matches
Mail list logo
