Le 2014-01-22 10:41, Estival Guillaume a écrit :
> Le 22/01/2014 15:07, Fabrice DURAND a écrit :
>> Hello Guillaume,
>>
>> in network.conf, remove :
>>
>> [192.168.0.0]
>> dns=192.168.0.101
>>
> [cut]
> thanks, I think I've messed up this whole configuration.
> I will test it through the day if the dhcp now works, but I think this
> is all set :)
>> About the FQDN, it doesn´t matter, in fact on the inline network
>> packetfence is the dns, dhcp.
>> If your device is unreg then iptables will forward the dns traffic to
>> packetfence (and packetfence will always be the inline ip address) and
>> when your device will be reg then the dns traffic will reach the real
>> dns server.
>>
> I think I didn't explain this problem clearly, sorry about that.
>
> I want to use a wifi laptop, connected on the 192.168.100.0/24 subnet. I
> set up the wifi connexion, and when I tried going into the Internet, the
> captive portal take over and force a FQDN URL:
> http://packetfence.example.com/captive-portal?...
> On the web interface, I did set the domain to "example.com" and the
> hostname to "packetfence" but the FQDN is invalid. The packetfence
> system didn't have a public IP so it didn't have any FQDN. So the URL is
> invalid and the browser can't reach it.
No it´s wrong, in the dhcp configuration of this network 
(192.168.100.1/24) packetfence is of course the dhcp server, the default 
gateway and the dns server (the dns traffic is forwarded to pfdns by the 
iptables rules).
So if you try to resolv www.fdfsdkjfsdfhjvff18892e28i009403.gigo then 
the answer will be the ip adddress of packetfence, so it´s the same 
thing with packetfence.example.com the will be resolved to 192.168.100.254.


> I wanted to force the use of IP (192.168.100.254) instead of FQDN when a
> client try to access Internet, but I don't know how to do it.
> Or try to find a way that http://packetfence.example.com/ get resolved.
>
> Thanks in advance.
>


-- 
Fabrice Durand
[email protected] ::  +1.514.447.4918 (x135) ::  www.inverse.ca
Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence 
(http://packetfence.org)


------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to