Yes, I did restart the service.
I have redesigned everything now as well. I eliminated one VLAN interface
so that I only have VLANs 96-100 now.
VLAN 100 normal, management
VLAN 99 registration
VLAN 98 isolation
VLAN 97 mac detection (no ip configured)
VLAN 96 inline
I am not using inline mode as I am out of band.
Can you verify my logic?
Switch has a trunked port for VLANs 96-100 (IPs are .1 in each VLAN)
Wireless switch has VLANs 96-100 (IPs are .2 in each VLAN
Server has VLANs 96-100 (IPs are .3 in each VLAN)
Traffic flows from AP to controller (via a tunnel), then controller sends
802.1x to packetfence/radius, then packetfence should assign DHCP with the
correct VLAN.
Problem: 802.1x is complete, but the IP is assigned from the wrong VLAN.
Do I understand things correctly?
On Wed, Dec 14, 2011 at 11:53 AM, Francois Gaudreault <
[email protected]> wrote:
> **
> When you fixed your switches.conf, did you restart packetfence?
>
>
> On 11-12-14 11:14 AM, lint wrote:
>
> I believe I need to focus on why the VLANs are not changing. Basically,
> why it places me into the normal VLAN when PacketFence knows that I am
> unregistered. I can access the portal automatically by using local DNS, so
> I know that is not the issue.
>
> Any ideas why I am being placed into the normal VLAN instead of the
> registration?
>
> On Tue, Dec 13, 2011 at 11:44 AM, lint <[email protected]> wrote:
>
>> PacketFence is behaving differently now.
>>
>> I receive an IP from PacketFence. It still places me into the normal
>> VLAN though (not sure why). Then, I can only ping the devices in the
>> normal VLAN. Captive portal page does load by default. I must type the
>> URL manually, and can only access by IP. DNS is not allowed because the
>> IP of the DNS server is on the management network.
>>
>> The switch, wireless controller and PacketFence are all aware of the
>> VLANs. Switch is x.x.x.1, wireless is x.x.x.2, and PacketFence is x.x.x.3
>> on each.
>>
>> I know that my design must be flawed somewhere. Any thoughts?
>>
>>
> ------------------------------------------------------------------------------
> Cloud Computing - Latest Buzzword or a Glimpse of the Future?
> This paper surveys cloud computing today: What are the benefits?
> Why are businesses embracing it? What are its payoffs and
> pitfalls?http://www.accelacomm.com/jaw/sdnl/114/51425149/
>
>
> _______________________________________________
> Packetfence-users mailing
> [email protected]https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
>
>
> --
> Francois Gaudreault, ing. [email protected] :: +1.514.447.4918
> (x130) :: www.inverse.ca
> Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
> (www.packetfence.org)
>
>
>
> ------------------------------------------------------------------------------
> Cloud Computing - Latest Buzzword or a Glimpse of the Future?
> This paper surveys cloud computing today: What are the benefits?
> Why are businesses embracing it? What are its payoffs and pitfalls?
> http://www.accelacomm.com/jaw/sdnl/114/51425149/
> _______________________________________________
> Packetfence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
>
------------------------------------------------------------------------------
Cloud Computing - Latest Buzzword or a Glimpse of the Future?
This paper surveys cloud computing today: What are the benefits?
Why are businesses embracing it? What are its payoffs and pitfalls?
http://www.accelacomm.com/jaw/sdnl/114/51425149/
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
