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 list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
