Question for the group.
We
were doing our own dial-ups and have Big Planet in as a pass through in
radius. We are changing to exclusively Global Pops. Here is the
problem. Global pops is already passing through other customers from Big
Planet so I am not able to use bigplanet.com as a realm at Global
Pops.
Is
there a way that those customers from Big Planet could use our realm and have
radius strip that realm and put bigplanet in its place?
Thanks
| |||||||||||||||||||
| |||||||||||||||||||
| Add me to your address book... | |||||||||||||||||||
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Sylvain Savignac
Sent: Thursday, November 25, 2004 9:55 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [VOPRadius] New VOP Radius 4.0 update 19 available on My Vircom.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Sylvain Savignac
Sent: Thursday, November 25, 2004 9:55 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [VOPRadius] New VOP Radius 4.0 update 19 available on My Vircom.
To all
customers running VOPRadius version 4.0.228.
A new
cumulative update is now
available.
Just log
into MY Vircom and download the update.
Here is the new content Vs last update
16.
--------------------------------------------------------------------------------
- VOP
Radius allows to assign an IP address to an outbound user
whose
outbound service type has been changed to framed user.
outbound service type has been changed to framed user.
- VOP
Radius logs matched profile name.
- VOP
Radius sends both SESSION_LIMIT and ASCEND_SESSION_LIMIT to
ASCEND
units. (As well as both IDLE_TIMEOUT and ASCEND_IDLE_TIMEOUT)
units. (As well as both IDLE_TIMEOUT and ASCEND_IDLE_TIMEOUT)
- VOP
Radius avoids raising warning if the server can not open the
client
definition file when it is open by the console or the wizard.
definition file when it is open by the console or the wizard.
- VOP
Radius provides option to turn off Windows Event Viewer
Logging.
-
Renaming of "Authenticated" column within the console users
online
listing for "Authentication", as well as use of DONE and NONE rather
than YES and NO to indicate whether user went through the authentication
phase.
listing for "Authentication", as well as use of DONE and NONE rather
than YES and NO to indicate whether user went through the authentication
phase.
-
VOPCom does not unconditionnally insert anymore attribute 61
(NAS-Port-Type)
with a value of 5 (Virtual) when opening a request with a NAS port value of
zero. A NAS-Port-Type = Virtual will rather remove the NasPortID attribute
from the packet.
with a value of 5 (Virtual) when opening a request with a NAS port value of
zero. A NAS-Port-Type = Virtual will rather remove the NasPortID attribute
from the packet.
-
Calling Station ID Concurrency feature implementation. If this option
is
checked, many users or a same user can be granted access to a same NAS port
using different Calling Station IDs. This option is useful for anyone using
a wireless NAS which make use of Calling Station ID to store MAC address
(e.g. Nomadix, etc.).
If this option is checked, user port limit and NAS port limit are treated
like connection limits no matter the type of the different connections being
NAS ports and/or Calling Station IDs.
In addition if this option is checked, VOP Radius considers Calling Station
ID to be universally unique if the Calling Station ID is at least
10-character long (The latter encompasses MAC address, E.163 and E.164
format types). Normally VOP Radius in order to prevent ghost connections
when an access request comes in from a same NAS for a port VOP Radius has
a user already connected to, the new connection is allowed to replace the
ghost connection rather than being rejected. In case this option is checked,
VOP Radius considers Calling Station ID to be a non-sharable resource too.
In order to prevent ghost connections when an access request comes in for
a Calling Station ID VOP Radius had a user already connected to, the new
connection is allowed to replace the ghost connection rather than being
rejected. Therefore this option is also useful for anyone using a carrier
not providing any means to monitor their NAS activity (e.g. GlobalPOPs, etc.).
checked, many users or a same user can be granted access to a same NAS port
using different Calling Station IDs. This option is useful for anyone using
a wireless NAS which make use of Calling Station ID to store MAC address
(e.g. Nomadix, etc.).
If this option is checked, user port limit and NAS port limit are treated
like connection limits no matter the type of the different connections being
NAS ports and/or Calling Station IDs.
In addition if this option is checked, VOP Radius considers Calling Station
ID to be universally unique if the Calling Station ID is at least
10-character long (The latter encompasses MAC address, E.163 and E.164
format types). Normally VOP Radius in order to prevent ghost connections
when an access request comes in from a same NAS for a port VOP Radius has
a user already connected to, the new connection is allowed to replace the
ghost connection rather than being rejected. In case this option is checked,
VOP Radius considers Calling Station ID to be a non-sharable resource too.
In order to prevent ghost connections when an access request comes in for
a Calling Station ID VOP Radius had a user already connected to, the new
connection is allowed to replace the ghost connection rather than being
rejected. Therefore this option is also useful for anyone using a carrier
not providing any means to monitor their NAS activity (e.g. GlobalPOPs, etc.).
-
Additional accounting attributes for Rodopi data source are allowed even
if
the packet is not a CISCO VoIP packet. However, a CISCO VoIP attribute value
MAY NOT be added in the SQL request if your VOP Radius license does not
support VoIP (the value will be 'NULL' instead).
the packet is not a CISCO VoIP packet. However, a CISCO VoIP attribute value
MAY NOT be added in the SQL request if your VOP Radius license does not
support VoIP (the value will be 'NULL' instead).
--------------------------------------------------------------------------------
Regards,
Sylvain Savignac, P. Eng.
Development Lead
RADIUS Development Unit
Vircom Inc.
2055, Peel St, suite 200
Montr�al (Qu�bec) Canada H3A 1V4
Phone: 514-845-1666 ext. 266
Fax: 514-845-6922
