a.l.m.bu...@lboro.ac.uk wrote:
Hi,
My guess is dual-stack NAS-RADIUS is going to be rare.
ummm. take a hold on that assertion. the joy of dual-stack deployment
is that you need to ensure your servers are ready on IPv4 and IPv6 -
and as part of that, you need to ensure that your using both
Hi,
Sorry, I've been unclear. What I meant was that I strongly suspect
nas-radius comms will either be v4 or v6 for a given pairing at any one
time, for periods of minutes or hours. Hence treating the addresses as
separately should be fine
hmm, yes, we treat each as a seperate
Hi,
while using radtest, I got some strange results:
# ./radtest swinter testpwd [::1] 123 testing123
radclient: Failed to find IP address for host ::1: Success
# ./radtest swinter testpwd ipv6-localhost 123 testing123
radclient: Failed to find IP address for host ipv6-localhost: Success
ipv6
Stefan Winter wrote:
while using radtest, I got some strange results:
# ./radtest swinter testpwd [::1] 123 testing123
radclient: Failed to find IP address for host ::1: Success
It defaults to IPv4.
# ./radtest swinter testpwd ipv6-localhost 123 testing123
radclient: Failed to find IP
On 22 Jul 2013, at 13:32, Stefan Winter stefan.win...@restena.lu wrote:
Hi,
Does radtest not support IPv6? I could have sworn it did IPv6 earlier,
but not totally sure.
ahem
-4 Use IPv4 for the NAS address (default)
-6 Use IPv6
Hi,
Does radtest not support IPv6? I could have sworn it did IPv6 earlier,
but not totally sure.
ahem
-4 Use IPv4 for the NAS address (default)
-6 Use IPv6 for the NAS address
Uh. Sorry.
Still... maybe for a later version
On 22/07/13 13:47, Arran Cudbard-Bell wrote:
It'd be nice to get some feedback from people though... do you think
you'll ever need to record both your NAS IPv4 and IPv6 addresses?
I'm guessing for dual stacking it'd be nice to record
Framed-IP-Address and Framed-IPv6-Prefix, should they both
On 22 Jul 2013, at 14:15, Phil Mayers p.may...@imperial.ac.uk wrote:
On 22/07/13 13:47, Arran Cudbard-Bell wrote:
It'd be nice to get some feedback from people though... do you think
you'll ever need to record both your NAS IPv4 and IPv6 addresses?
I'm guessing for dual stacking it'd
.
ipv6-localhost only returns ::1. And ::1 successfully parses neither as
an IPv4, nor a hostname, but as an IPv6 address. Both are unambiguous
and could be auto-detected.
Sure.
That would add a little user-friendliness for users who didn't have
enough sleep :-)
Yes.
Alan DeKok
On 22/07/13 14:32, Arran Cudbard-Bell wrote:
On 22 Jul 2013, at 14:15, Phil Mayers p.may...@imperial.ac.uk
wrote:
On 22/07/13 13:47, Arran Cudbard-Bell wrote:
It'd be nice to get some feedback from people though... do you
think you'll ever need to record both your NAS IPv4 and IPv6
Hi,
Still... maybe for a later version... if the input looks like an IP
address, guessing the address family isn't all that hard.
unlike your using IPv4 in its IPv6 incantation
What if the NAS started just using the SRC IPv6 address in packets, and
source IP protection was enabled
Hi,
My guess is dual-stack NAS-RADIUS is going to be rare.
ummm. take a hold on that assertion. the joy of dual-stack deployment
is that you need to ensure your servers are ready on IPv4 and IPv6 -
and as part of that, you need to ensure that your using both methods
in case either your IPv4
I updated my ippool table to increase the length of the varchar.
Then I set the Pool-Name attribute to an IPv6 pool.
I set up this in mysql base:
radcheck
6 | testadsl-sagem-ds-1 | Pool-Name | := | poolipv6
radippool
5 | poolipv6 | 2a0a:8e80:0400:0202::/64
Ok thanks for the reply.
Not right now. I'd suggest writing SQL queries to handle that. The
sql_ippool module should be able to do it, if the queries are updated.
I aim to use the module to manage IPv4 pool and IPv6 prefix pool.
Do you think I should update the module or create another one
You may be able to re-use the module, just with a different configuration.
Is there a way to change the %reply returned by rlm_sqlippool?
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 14 Jun 2013, at 14:05, Alan DeKok al...@deployingradius.com wrote:
William DELORAINE wrote:
I aim to use the module to manage IPv4 pool and IPv6 prefix pool.
Do you think I should update the module or create another one?
You may be able to re-use the module, just with a different
Hello,
I'm running FreeRadius 2.1.12 and I would like to know if it is able to manage
IPv6 address pool?
I would like my freeradius to provide IPv6 Prefix to the clients.
If so, could you point me the way to do it?
I checked ip_pool and sql_ippool with no luck.
Best regards,
William
-
List
William DELORAINE wrote:
I’m running FreeRadius 2.1.12 and I would like to know if it is able to
manage IPv6 address pool?
Not right now. I'd suggest writing SQL queries to handle that. The
sql_ippool module should be able to do it, if the queries are updated.
Alan DeKok.
-
List info
On 05/24/2013 05:18 AM, Stefan Winter wrote:
simply isn't an IPv6 address
Very true.
fe80::215:17ff:fed0:d278%eth0
is the valid address. I don't know if the FreeRADIUS address parser is
prepared to handle such interface-scoped addresses. There's not much use
case for this.
Not sure I
Using global IPV6 addresses worked. Thanks for the help.
Mike
-Original Message-
From: freeradius-users-
bounces+michael.sherman=exfo@lists.freeradius.org
[mailto:freeradius-users-
bounces+michael.sherman=exfo@lists.freeradius.org] On Behalf Of
Alan DeKok
Sent: Friday, May
:17ff:fed0:d278 {
require_message_authenticator = no
secret = bigsecret
shortname = test-net
nastype = other
}
...
radiusd: Opening IP addresses and Ports
listen {
type = auth
ipv6addr = :: IPv6 address [::]
port = 0
}
listen
with an interface
scope. So
fe80::215:17ff:fed0:d278
simply isn't an IPv6 address.
fe80::215:17ff:fed0:d278%eth0
is the valid address. I don't know if the FreeRADIUS address parser is
prepared to handle such interface-scoped addresses. There's not much use
case for this.
Greetings,
Stefan
HI All,
I'm testing freeradius server version 2.2.0. Worked fine using IPv4.
When I switched to IPv6 I got the following error:
Ignoring request to authentication address :: port 1812 from unknown
client fe80::215:17ff:fed0:d278 port 41189
Here is the entry from the clients.conf:
client
Hi,
Here is the entry from the clients.conf:
client goya {
ipv6addr= fe80::215:17ff:fed0:d278
# netmask = 128
secret = test
shortname = test-net
}
what does this do...
client
Tobias Hachmer wrote:
is there a way to gather statistics for an IPv6 Socket with the status
server?
No. Use radmin for that.
1. How can I gather statistics for the IPv6 sockets, I didn't find any
IPv6 attributes like FreeRADIUS-Stats-Server-IPv6-Address.
Send a patch.
2
Hello list,
is there a way to gather statistics for an IPv6 Socket with the status
server?
For example my radius server has the following listen sections:
udp0 0 127.0.0.1:18120 0.0.0.0:*
2355/radiusd
udp0 0 0.0.0.0:1645
Hi all,
ippool can't handle IPv6 addresses, but sql ippool should be able to, right?
At least in postgres, inet data type accepts both v4 and v6 addresses.
Anyone using it?
Any handy tools to fill the database/generate pool addresses?
Any other hints?
Regards...
-
List info/subscribe
Hello,
I have configured my server to run radius on ipv6 and I was also able to
successfully connect to radius server using radclient binary on my
client machine.
I installed radiusclient as well my machine and I am trying to run
radexample to login to radius server over ipv6, however I am
advise to do it that way - as all you are doing
there is using one client balance - with the alternates being the same
server ie roaming0 or roaming-ipv6
- if roaming0 was down/dead then the ipv6 one is too.
so, better with eg
ja-net-roaming0_server6
ja-net-roaming1_server6
ja-net
Working that through with what happens in each case, your way does a
better job of coping with a server going down; I think my way is better at
coping with one of an IPv4 or IPv6 failure.
How about mixing it up a bit more:
roaming0_server
roaming1_server6
roaming2_server
Hello,
I'd just just to check FreeRADIUS operates as I'm expecting (and have
observed, in the limited amount of testing I've been able to do, before
plugging things into the real world). I'm trying to get our FreeRADIUS
2.1.12 servers ready to handle IPv4 and IPv6 and, in particular,
IPv6
Bob Franklin wrote:
I'd just just to check FreeRADIUS operates as I'm expecting (and have
observed, in the limited amount of testing I've been able to do, before
plugging things into the real world). I'm trying to get our FreeRADIUS
2.1.12 servers ready to handle IPv4 and IPv6
Ciao.
Just wondering if FR supports IPv6 addresses since I'm unable to start the
server when using IPv6.
I've changed (or uncommented) a couple of lines in radiusd.conf under 'listen'
section: ipv6addr = :: and then I tried to start the server but no way. It
works ok when using IPv4.
FR
On Mon, Oct 31, 2011 at 3:11 PM, Sergio NNX sfhac...@hotmail.com wrote:
Ciao.
Just wondering if FR supports IPv6 addresses
Sure it does. If you want it to listen on both ipv4 and ipv6, just add
extra listen blocks
listen {
ipv6addr = ::
port = 0
type = auth
}
listen
Hi,
Just wondering if FR supports IPv6 addresses since I'm unable to start the
server when using IPv6.
yes. we use it fine with IPv6 - both receiving and sending RADIUS packets.
Another question is: are you aware of any (client) tool for testing FR
when using IPv6 addresses
Thank you all for your help. I added two more listen blocks in radiusd.conf and
I updated detail { ... with the following:
%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}} and it works but .
(there's always a but). if we use an IPv6 address, then Packet-Src-APv6-Address
value
On 31/10/11 15:32, Sergio NNX wrote:
Thank you all for your help. I added two more listen blocks in
radiusd.conf and I updated detail { ... with the following:
%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}} and it works but
. (there's always a but). if we use an IPv6 address
Thanks Phil. Can you try 'mkdir 0:0:0:0:0:0:0:0' on a Windows box and let mw
know if it works?
Date: Mon, 31 Oct 2011 15:46:47 +
From: p.may...@imperial.ac.uk
To: freeradius-users@lists.freeradius.org
Subject: Re: IPv6 ready?
On 31/10/11 15:32, Sergio NNX wrote:
Thank you all
On 31/10/11 15:58, Sergio NNX wrote:
Thanks Phil. Can you try 'mkdir 0:0:0:0:0:0:0:0' on a Windows box and
let mw know if it works?
I can tell you for absolute certain it won't without even having to try.
It's a Windows limitation.
-
List info/subscribe/unsubscribe? See
On 2011/10/31 05:58 PM, Sergio NNX wrote:
Thanks Phil. Can you try 'mkdir 0:0:0:0:0:0:0:0' on a Windows box and let mw
know if it works?
C:\junkmkdir 0:0:0:0:0:0:0:0
The system cannot find the drive specified.
C:\junkmkdir '0:0:0:0:0:0:0:0'
The filename, directory name, or volume label
Subject: Re: IPv6 ready?
On 31/10/11 15:58, Sergio NNX wrote:
Thanks Phil. Can you try 'mkdir 0:0:0:0:0:0:0:0' on a Windows box and
let mw know if it works?
I can tell you for absolute certain it won't without even having to try.
It's a Windows limitation.
-
List info/subscribe
Johan Meiring wrote:
Why not simply remove the Ip address from the log path?
Do they HAVE to be in directories with the IP address as part of the name?
No. That's why the config files are editable.
Edit them.
Alan DeKok.
-
List info/subscribe/unsubscribe? See
Sergio NNX wrote:
Thank you all for your help. I added two more listen blocks in
radiusd.conf and I updated detail { ... with the following:
%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}} and it works but
. (there's always a but). if we use an IPv6 address, then
Packet-Src-APv6
On Mon, Oct 31, 2011 at 11:19 PM, Sergio NNX sfhac...@hotmail.com wrote:
Cool, what can i do about it? I'm new to FR so I don't know how to implement
a rule or something like that. Can you provide an example or an url where I
can find more info?
Just edit them.
You could put everyting on one
On 31/10/11 16:19, Sergio NNX wrote:
Cool, what can i do about it? I'm new to FR so I don't know how to
Personally I'd advise running it on a Unix system at the moment.
implement a rule or something like that. Can you provide an example or
an url where I can find more info?
@lists.freeradius.org
Subject: Re: IPv6 ready?
On 31/10/11 16:19, Sergio NNX wrote:
Cool, what can i do about it? I'm new to FR so I don't know how to
Personally I'd advise running it on a Unix system at the moment.
implement a rule or something like that. Can you provide an example or
an url
Hi,
Thank you all for your help. I added two more listen blocks in
radiusd.conf and I updated detail { ... with the following:
%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}} and it works but
. (there's always a but). if we use an IPv6 address, then
Packet-Src-APv6
Hello.
I'm trying to include Delegated-IPv6-Prefix attribute to reply, here is
contents of radreply table:
id | username | attribute | op | value
Dmitry Kozlov wrote:
I'm trying to include Delegated-IPv6-Prefix attribute to reply, here is
contents of radreply table:
...
But it rejects Access-Request and writes to log:
rlm_sql: Failed to create the pair: Invalid octet string fc00:1:2:2::/64
for attribute name Delegated-IPv6-Prefix
Use a version of FreeRADIUS which has a dictionary entry for
Delegated-IPv6-Prefix.
i.e. upgrade.
Thanks.
Actual problem was that dictionary.rfc4818 was not included in dictionary file.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Can someone point me to docs or help me get my head around what changes
need to be done for IPv6 Accounting?
Looks like I may need to add some fields to radacct and update the
INSERT and UPDATE statements with IPv6 variables.
Is it necessary to run freeradius dual stack for IPv6 AAA?
Version
On 27/05/11 14:37, Shannon Ward wrote:
Can someone point me to docs or help me get my head around what changes
need to be done for IPv6 Accounting?
Looks like I may need to add some fields to radacct and update the
INSERT and UPDATE statements with IPv6 variables.
Assuming your NAS supports
Shannon Ward wrote:
Can someone point me to docs or help me get my head around what changes
need to be done for IPv6 Accounting?
What does that mean?
Looks like I may need to add some fields to radacct and update the
INSERT and UPDATE statements with IPv6 variables.
No. Read
On 05/27/2011 09:44 AM, Phil Mayers wrote:
On 27/05/11 14:37, Shannon Ward wrote:
Can someone point me to docs or help me get my head around what changes
need to be done for IPv6 Accounting?
Looks like I may need to add some fields to radacct and update the
INSERT and UPDATE statements
Hello,
this is about 2.1.10. In my proxy.conf, I have two clauses for a host (
see [1] and [2] below), once with ipaddr for IPv4 and once with ipv6addr
for IPv6.
If I set the pool to use the IPv4 one (see [3]) , packets get proxied
just fine. If I replace with IPv6, no packet leaves the server
Stefan Winter wrote:
As soon as I change the proxy pool definition back to the v4 variant,
things start working again.
That's a bit strange...
Bug #143, fixed in the v2.1.x branch.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
That's a bit strange...
Bug #143, fixed in the v2.1.x branch.
Cool! Looking forward to 2.1.11...
Stefan
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
--
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau
Hi,
this is about 2.1.10. In my proxy.conf, I have two clauses for a host (
see [1] and [2] below), once with ipaddr for IPv4 and once with ipv6addr
for IPv6.
I was going to be reporting the same thing - however, I've delayed since
I could only see this behaviour on a VM system so wasnt sure
.
however, if latest 2.1.x code fixes this, then i can certainly try to verify
this
Verified only minutes after reading the other Alan's answer - now stuff
works. BTW: The parameter src_ipaddr in home_server {} can also take an
IPv6 address as argument, which is quite a blessing for my deployment
Hi
I'm busy with a FreeRadius Eduroam setup, but it only works with ipv4 and not
with ipv6.
My Setup:
wifi-client -- my-FreeRadius-proxy --- eduroam-proxy --- remote-site
My server:
FreeBSD 8.1-STABLE with freeradius-2.1.10_1 that was build from the ports,
with ipv6 enabled.
Here is a list
Excerpts from Johann Hugo's message of Mon Dec 06 09:01:09 + 2010:
I'm busy with a FreeRadius Eduroam setup, but it only works with ipv4 and not
with ipv6.
You seem to be using the same ipv6 address for your proxy as well as for the
eduroam proxy; is that intentional?
From example 1
/radiusd/radiusd.sock
Listening on proxy address * port 1814
Ready to process requests.
ganymede# sockstat | grep 1812
freeradius radiusd 39438 5 udp4 *:1812*:*
freeradius radiusd 39438 6 udp6 *:1812*:*
But I never see the IPv6 packets going out of the ethernet
Excerpts from Johann Hugo's message of Mon Dec 06 09:41:40 + 2010:
listen {
type = auth
#ipaddr = *
ipv6addr = ::
#ipv6addr = 2001:4200:7000:1:21c:c0ff:fefb:dc67
port = 0
}
radius -X
...
Listening on authentication address * port 1812
find a reference at the moment.
It works for ipv4, but not for ipv6
IPv4:
listen {
type = auth
#ipaddr = *
ipaddr = 146.64.8.17
port = 0
}
radius -X
...
Listening on authentication address 146.64.8.17 port 1812
Listening on authentication address :: port 1812
at the moment.
ISTR that you cannot listen to v4 and v6 in the same virtual server -
setup a new VS with ipv6 listener - its what we do here successfully
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Alan Buxey wrote:
ISTR that you cannot listen to v4 and v6 in the same virtual server -
Hmm... There shouldn't be a problem with that.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Johann Hugo wrote:
radius -X
...
Failed binding to authentication address 2001:4200:7000:1:21c:c0ff:fefb:dc67
port 1812: Can't assign requested address
Try and find out why the OS won't let the server bind to that address.
See also the code in src/main/listen.c Maybe there's an issue
are:
# dotted quad (1.2.3.4)
# hostname(radius.example.com)
# wildcard(*)
ipaddr = *
# OR, you can use an IPv6 address, but not both
# at the same time.
# ipv6addr = :: # any. ::1 == localhost
alan
-
List info/subscribe
On Monday, December 06, 2010 02:05:14 pm Alan DeKok wrote:
Johann Hugo wrote:
radius -X
...
Failed binding to authentication address
2001:4200:7000:1:21c:c0ff:fefb:dc67 port 1812: Can't assign requested
address
Try and find out why the OS won't let the server bind to that address.
# IP address on which to listen.
# Allowed values are:
# dotted quad (1.2.3.4)
# hostname(radius.example.com)
# wildcard(*)
ipaddr = *
# OR, you can use an IPv6 address, but not both
# at the same time.
From some
an IPv6 address, but not both
# at the same time.
# ipv6addr = :: # any. ::1 == localhost
I'll clarify that: A network socket can only listen on one IP/port.
You can't have one socket listening on two UDP ports, or two TCP
ports, or two IP addresses.
You *can* have two
Thanks a lot Bjørn and Alan.
I believe it is time to revisit the Ascend dictionary fixup.
I think so, yes.
Yes, I can see the point that this will break existing setups. But I
will argue that such setups have *always* been broken. At least when we
are discussing the FreeRADIUS 2.x era.
ichiro tanaka i_tan...@hotmail.co.jp writes:
Proxy-Server recognition was repaired, if proxy-server did not include
dictionary.ascend.
I believe it is time to revisit the Ascend dictionary fixup. This was
done once, and then reverted for between 2.1.7 and 2.1.8:
commit
Bjørn Mork wrote:
I believe it is time to revisit the Ascend dictionary fixup.
I think so, yes.
Yes, I can see the point that this will break existing setups. But I
will argue that such setups have *always* been broken. At least when we
are discussing the FreeRADIUS 2.x era. You cannot
ichiro tanaka wrote:
My freeradius proxy already includes dictionary.rfc4818.
Do I need something?
No idea. Maybe the attribute isn't in the correct format.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Thanks its working..After coverting it into hex format (start with 0x) and
modifying the attribute type to octets.
On Wed, Oct 20, 2010 at 12:38 PM, Alan DeKok al...@deployingradius.comwrote:
janardhan madabattula wrote:
Hi,
I am trying to create IPv6 Ascend Data Filter in Free radius
) format.
Delegated-IPv6-Prefix attribute that auth-server replied and reply_log looks
correct.
http://tools.ietf.org/html/rfc4818
Proxy-Server recognition was repaired, if proxy-server did not include
dictionary.ascend.
--- auth-server [[ users ]] ---
u...@example.jp Cleartext-Password := password
Hi.
auth-server reply attribute Delegated-IPv6-Prefix, but proxy recognize
Attr-123 = 0x00401234567890abcdef.
I used ntradping-1.5 and freeradius-2.1.10.
--hosts--
ntradping-1.5 10.233.55.200
proxy (freeradius-2.1.10) 10.233.36.101
auth-server (freeradius-2.1.10
ichiro tanaka wrote:
auth-server reply attribute Delegated-IPv6-Prefix, but proxy recognize
Attr-123 = 0x00401234567890abcdef.
Fix the proxy so that it's using the dictionaries from 2.1.10. The
debug *claims* it's 2.1.10, but the Delegated-IPv6-Prefix attribute *is*
defined
Hi,
I am trying to create IPv6 Ascend Data Filter in Free radius. but
unfortunately its not happening. Any help?
I have created Ascend-Data-Filter 242 abinary attribute in dictinary
filter.
Following is the record I am trying to parse.
ipv6 Password := test
Service-Type
janardhan madabattula wrote:
Hi,
I am trying to create IPv6 Ascend Data Filter in Free radius. but
unfortunately its not happening. Any help?
See the FAQ for it doesn't work.
I have created Ascend-Data-Filter 242 abinary attribute in dictinary
filter.
Why? The attribute is already
thanks Alan.
(i couldn't get your reply to my mailbox. so, i made a new mail. sorry...)
Fix the proxy so that it's using the dictionaries from 2.1.10. The
debug *claims* it's 2.1.10, but the Delegated-IPv6-Prefix attribute *is*
defined in the dictionaries for 2.1.10.
Alan DeKok.
My
and thus all of the detail logs for ANY IPv6 client get munged into the
top level directory.
Use:
%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}
That should work.
Or:
%{%{client:ipaddr}:-%{client:ipv6addr}}
Alan DeKok.
-
List info/subscribe/unsubscribe? See http
Hi,
Use:
%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}
That should work.
Or:
%{%{client:ipaddr}:-%{client:ipv6addr}}
thanks, I guess this change can be made to the 2.1.10 default config?
this issue also affects the acct_unique module too:
acct_unique
dumps auth log etc into a subdirectory of the radius log directory eg
radacct/127.0.0.1/auth-log- or such
however, this only works when the client is using IPv4.
when the client is using IPv6 then this directory is not made and
therefore no nice detail logs are kept for those things...(well
Hello all,
I am running FreeRadius 2.1.8 with two NAS clients and a
couple of end devices being authenticated successfully with EAP-TTLS. My
setup was running just fine on IPv4 and I would like to jump to IPv6. My
first trial seems ok, but not ideal, so here are my IPv6 related
Panagiotis Georgopoulos wrote:
a) Why am I seeing in my radius –X output lines as the following :
[unix] IPv6 is not supported!
The unix module stores user login information into a wtmp style
file. It doesn't support IPv6.
rlm_radutmp: IPv6 not supported!
Same thing here
Hello Alan,
Thanks for your replies, they are helpful.
Regarding the last question...
c) Is there a plan to get a dual stack FreeRadius? It would be
really advantageous to be able to run FreeRadius in both ipv4 and
ipv6 at the same time.
Uh... it's *already
Panagiotis Georgopoulos wrote:
I guess the emphasis on my question above is on *at the same time*.
Now radiusd.conf explicitly says :
# OR, you can use an IPv6 address, but not both
# at the same time.
In other words FR to listen to both an IPv4
Hi Alan,
Panagiotis Georgopoulos wrote:
I guess the emphasis on my question above is on *at the same
time*.
Now radiusd.conf explicitly says :
# OR, you can use an IPv6 address, but not both
# at the same time.
In other words FR to listen to both
Hi,
In other words FR to listen to both an IPv4 and an IPv6 address
simultaneously for ipv4 and ipv6 NAS clients.
simply define another virtual server...exactly the same as default, but listing
to the IPv6 instead?
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org
John Dennis wrote:
All you should need to do is create a bugzilla login, no different than
the FreeRADIUS bugzilla, but no problem, I attached the patch to the the
FreeRADIUS bug, should be easy to see now.
Tried, still the same error. Oh well.
From what I can tell, the issue is that
Hello John, Alan, all,
John Dennis wrote:
We also just discovered a bug with IPv6 usage in radclient (and
radtest), you may want to take a look at these two bugzilla's:
https://bugs.freeradius.org/bugzilla/show_bug.cgi?id=80
The better fix is to take unknown options starting
users mailing list
Subject: Re: radtest and IPv6 support
Panagiotis Georgopoulos wrote:
I am trying to use radtest to test my freeradius
configuration over IPv6. I have configured IPv6 on my freeradius
server
and a client machine from which I am firing radtest. However when I
On 06/03/2010 01:57 PM, Panagiotis Georgopoulos wrote:
Hello all,
I am trying to use radtest to test my freeradius configuration over
IPv6. I have configured IPv6 on my freeradius server and a client
machine from which I am firing radtest. However when I issue “radtest
We also just discovered
John Dennis wrote:
We also just discovered a bug with IPv6 usage in radclient (and
radtest), you may want to take a look at these two bugzilla's:
https://bugs.freeradius.org/bugzilla/show_bug.cgi?id=80
The better fix is to take unknown options starting with -, and pass
them directly
On 06/07/2010 05:33 PM, Alan DeKok wrote:
John Dennis wrote:
We also just discovered a bug with IPv6 usage in radclient (and
radtest), you may want to take a look at these two bugzilla's:
https://bugs.freeradius.org/bugzilla/show_bug.cgi?id=80
The better fix is to take unknown options
Panagiotis Georgopoulos wrote:
I am trying to use radtest to test my freeradius
configuration over IPv6. I have configured IPv6 on my freeradius server
and a client machine from which I am firing radtest. However when I
issue “radtest bob hello 2001:db95::100 100 testing123
Hello all,
I am trying to use radtest to test my freeradius
configuration over IPv6. I have configured IPv6 on my freeradius server and
a client machine from which I am firing radtest. However when I issue
radtest bob hello 2001:db95::100 100 testing123 on my client I get
Ram Akuka wrote:
I want to manage my ipv6 users using ip_pool from FreeRadius. And I have
few question regarding this.
1. how can I use ip_pool to allocate ipv6 address to a users?
That isn't currently supported.
2. How can I assign ipv6 address to client based on the NAS he
1 - 100 of 171 matches
Mail list logo
