I did not impicitly say that PF uses SNMP to change the VLAN.
The question was about how do you get the client machine to ‘recognise’ the 
change and to request a new IP address so that it would
no longer hit the captive portal.

I implied that SNMP was used as a mechanism to achieve the same results as CoA 
(which is predominantly a WiFi contrsucts by the way not a
wired one and is not as well supported .

If a PC is connected to the data port of a switch that does NOT support CoA 
then no amount of changing the VLAN is going to ‘persuade’
a  windows PC to get a new IP address. The only mechanism I have found to get 
that working (on an old 8 port 2940 for instance) is in the
SNMP settings of the switch where you specify the timings whereby the SHUT is 
sent a certain time after a VLAN change and the
NO SHUT is sent a certain timer after that.

CoA is relatively badly supported in older Cisco switches and IOS versions but 
there are alternatives and that is what I was advising.

Andrew





Andrew Torry

Senior Infrastructure Engineer



Tel: 01326 370760

Email: [email protected]




[cid:[email protected]]
        [Falmouth Exeter Plus]                  
[cid:[email protected]]


        [Twitter] <https://twitter.com/falmouthexeter>          [Facebook] 
<https://www.facebook.com/falmouthexeter>            [Instagram] 
<https://www.instagram.com/falmouthexeterplus/>             [YouTube] 
<https://www.youtube.com/channel/UC5-Jq4vTOhWgYoJJDYrZHWw>

[cid:[email protected]]


[Falmouth University]

Falmouth Exeter Plus is an exempt charity established by Falmouth University 
and the University of Exeter to deliver their shared Higher Education services 
in Cornwall.
From: Louis Munro [mailto:[email protected]]
Sent: 07 April 2017 14:37
To: [email protected]
Subject: Re: [PacketFence-users] How to configure switch for VLAN changes ?


On Apr 7, 2017, at 4:48 AM, Torry, Andrew 
<[email protected]<mailto:[email protected]>> wrote:

Pretty sure it uses SNMP to perform a shut/no shut on the interface so make 
sure that is set up correctly.
I think it can also use SSH access with credentials and the enable password if 
you define it.



Sorry Andrew, it does not.
The VLAN is contained in the attributes returned in the RADIUS reply.

Remember that RADIUS takes care of the three "A"s:
* Authentication (is it allowed on the network?)
* Authorization (where should it be allowed, and with which privileges)
* Accounting (how much of a give resource does it use)

If you run freeradius in debug mode you will see the VLAN being returned in an 
access-accept packet, typically in the "Tunnel-Private-Group-Id" attribute.
There is no need to involve SNMP or SSH for that.

The only case where PacketFence needs SNMP is when a switch either does not 
support RADIUS dynamic assignment at all, or when it does not support RFC 3576 
(Dynamic Authorization Extensions to RADIUS), which allows a RADIUS request to 
be sent to a NAS in order to e.g. force a disconnection, reauthenticate etc.
That by the way is how we force VLANs to change when a device's registration 
status changes (from registered to unregistered or the reverse).
PacketFence sends a RADIUS disconnect or CoA packet to the switch, the switch 
issues a new RADIUS request the reply to which will contain the new VLAN.

So when people ask why their VLANs are not changing after registration and they 
are stuck behind the captive portal, the answer is almost always because RADIUS 
CoA is not enabled on the switch, or there is an ACL preventing the packet from 
reaching the switch (either UDP 3799 or 1700 depending on the switch and 
firmware).

Googling around for "cisco switch dynamic vlan assignment" brings this up, 
which may clarify some things better that I can explain:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960/software/release/12-2_58_se/configuration/guide/2960scg/sw8021x.html#pgfId-1289244

Regards,
--
Louis Munro
[email protected]<mailto:[email protected]>  ::  
www.inverse.ca<http://www.inverse.ca>
+1.514.447.4918 x125  :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu<http://www.sogo.nu>) and 
PacketFence (www.packetfence.org<http://www.packetfence.org>)

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to