• All
  • Test
  • Startup
  • Experience Case
  • FAQ
Product line
Search
Cancel
Documents type
Author
Time
Search

S5130S-28P-EI The AccessVLANID & the AuthorizationVLANID is not the same in the radius massage.

2020-08-09 18:34:01 Published
  • 0Followed
  • 1Collected ,535Browsed
fans:0 follow:0

Network Topology

Null

Problem Description

About dot.1x dynamic vlan assignment.

 

User auth and dynamic vlan assignment are all ok. Except only the log sent to the radius is not correct. So dynamic vlan assignment operation is correct but  the vlan info sent to the radius is wrong.

 

Example:

User authenticated+ dynamic vlan 160 assigned + accounting info sent to radius says vlan 150 assigned.

Log has to say vlan 160 not vlan 150...

 

So all operations are correct, but only log information sent to the radius is wrong, it always informs vlan 2 assigned which is port default vlan(pvid).

Process Analysis

We can clearly see the log about the authorization vlan from Radius server on the device as following:

%Jan  1 01:52:28:313 2013 H3C DOT1X/6/DOT1X_LOGIN_SUCC: -IfName=GigabitEthernet1/0/2-MACAddr=28d2-4491-4e77-AccessVLANID=150-AuthorizatiOnVLANID=160-Username=MAYCYBER\h3c1; User passed 802.1X authentication and came online.


And according to the packets capture from the device to the server:


We know the device feedback Radius with the accessVlanID which is the vlan of access clients before authentication, while without the AuthorizationVlanID.


So even the server authorize the vlan itself, it can only receive the access vlan anyway. The requirements from customer is receiving the AuthorizationVLANID, which not support at the current software version.

Solution

Modified feature of version Release 6317

Information included in RADIUS accounting request packets

Feature change description:

As from this version, the device supports including the User-VLAN-ID attribute in RADIUS accounting request packets sent to the RADIUS server. This attribute is used to carry authorization VLAN information for 802.1X and MAC authentication users. The modification ensures that the logs output by the RADIUS server can include user authorization VLAN information.

If the RADIUS server assigns a VLAN ID or VLAN name as the authorization VLAN to a user, the device includes the server-assigned authorization VLAN in the User-VLAN-ID attribute.

If the RADIUS server assigns a group of VLANs in the authorization VLAN information to a user, the device includes a VLAN in the User-VLAN-ID attribute as described in Table 1.

Table 1 Including a VLAN in the User-VLAN-ID attribute of RADIUS accounting packets

Please rate this case:   
0 comments

No comments

Add Comments:

举报

×

侵犯我的权益 >
对根叔知了社区有害的内容 >
辱骂、歧视、挑衅等(不友善)

侵犯我的权益

×

泄露了我的隐私 >
侵犯了我企业的权益 >
抄袭了我的内容 >
诽谤我 >
辱骂、歧视、挑衅等(不友善)
骚扰我

泄露了我的隐私

×

您好,当您发现根叔知了上有泄漏您隐私的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您认为哪些内容泄露了您的隐私?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)

侵犯了我企业的权益

×

您好,当您发现根叔知了上有关于您企业的造谣与诽谤、商业侵权等内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到 zhiliao@h3c.com 邮箱,我们会在审核后尽快给您答复。
  • 1. 您举报的内容是什么?(请在邮件中列出您举报的内容和链接地址)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
  • 3. 是哪家企业?(营业执照,单位登记证明等证件)
  • 4. 您与该企业的关系是?(您是企业法人或被授权人,需提供企业委托授权书)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

抄袭了我的内容

×

原文链接或出处

诽谤我

×

您好,当您发现根叔知了上有诽谤您的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您举报的内容以及侵犯了您什么权益?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

对根叔知了社区有害的内容

×

垃圾广告信息
色情、暴力、血腥等违反法律法规的内容
政治敏感
不规范转载 >
辱骂、歧视、挑衅等(不友善)
骚扰我
诱导投票

不规范转载

×

举报说明

提出建议

    +

Login before you can operate!

login

你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作