(RADIATOR) Radiator and Tagged L2TP attributes
Onno Becker Hof
onno at redback.com
Mon Oct 29 06:34:15 CST 2001
Hi All,
I am trying to send tagged tunneling attributes with radiator and having
some problems. I have read the FAQ/manual as per
"40. Does Radiator support the IETF Radius Tunnelling attributes? Yes. There
are a few tricks to using them though. " but this does not help me. I need
to be able to send (several other radius servers support this, before you
ask) sending arbitrary tunneling attributes with arbitrary tags. Your FAQ
suggests that all tags should be zero - this is not so.
The profile I want to send is like this, (using 1: to denote a tag of 1 on
that attribute as per certain other radius's syntax)
tunnel-assignment-ID=1:"ISP"
tunnel-server-endpoint=1:"192.168.100.1"
tunnel-type=1:l2tp
tunnel-medium=1:ip
tunnel-assignment-ID=2:"ISP"
tunnel-server-endpoint=2:"192.168.100.2"
tunnel-type=2:l2tp
tunnel-medium=2:ip
I simplified this out for testing to just one endpoint definition, with just
one tag value, i.e.
tunnel-assignment-ID=1:"ISP"
tunnel-server-endpoint=1:"192.168.100.1"
tunnel-type=1:l2tp
tunnel-medium=1:ip
The syntax for how to express this in a radiator config is file is where I
am having problems. I tried using this radiator config:
tunnel-assignment-ID="\001ISP"
tunnel-server-endpoint="\001192.168.100.1"
tunnel-type=\001l2tp
tunnel-medium=\001ip
the first two string attributes come out tagged with "1" as expected, they
work. The second two integer ones get screwed up because radiator appears to
treat the \001 as part of the value, can't look it up in the lookup table,
and ends up sending a value of zero with a tag of zero (which is useless,
and breaks the tunnel setup). If I define them without the \001
in front, they get sent untagged by radiator, which still breaks the tunnel
setup as its getting some attributes with a 0 tag and some with a
1.
basically what it comes down to is that I cannot work out how, in the
radiator configuration file, to configure a user radius profile to have
non-zero tagged values of the tunnel-type and tunnel-medium attributes, and
thus cannot get tagged tunneling to work properly. I've guessed
at/experimented with various ways I thought you might have implemented the
configuration of non-zero tags, couldn't get any to work.
regards,
Onno
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.
More information about the radiator
mailing list