> On Nov 25, 2015, at 10:01 , Christian Hanster <[email protected]>
> wrote:
>
> Hello everybody,
>
> I just updated to 5.5.0 but now there are some problems with the
> dhcplistener. We have PF running in a two node cluster in inline mode.
An active/active or active/passive cluster?
Inline is not supported in active/active. Not everything can be replicated.
> Our devices are remote, connected via a vpn-server in the inline network. We
> have configured a inlinel3 network for the remote clients. On the remote side
> the DHCP Server is configured, that it relays all dhcp traffic to PF so that
> PF gets all necessary information. This was working quite good in 5.4 (only
> the pfdhcplistener had to be started by hand at startup).
> However now it is not working anymore. It seems that the dhcp traffic is not
> recognised by PF. The log says the following:
>
> Nov 25 14:43:06 httpd.portal(19425) WARN: [mac:0] Unable to match MAC address
> to IP '10.1.13.43' (pf::iplog::ip2mac)
> Nov 25 14:43:06 httpd.portal(19425) INFO: [mac:0] Instantiate profile default
> (pf::Portal::ProfileFactory::_from_profile)
> Nov 25 14:43:06 httpd.portal(19425) WARN: [mac:0] Unable to match MAC address
> to IP '10.1.13.43' (pf::iplog::ip2mac)
> Nov 25 14:43:06 httpd.portal(19425) INFO: [mac:0] Instantiate profile default
> (pf::Portal::ProfileFactory::_from_profile)
>
> When I switch the inline mode to fake mac addresses, everything is working
> smoothly of course. But then I do not have the information about the
> mac-addresses... Can anybody explain what changed with the dhcplistener
> especially in connection with a cluster.
>
> pfdhcplistener.log:
>
> Nov 25 14:16:52 pfdhcplistener(19238) INFO: Reload configuration on eth0 with
> status 0 (main::reload_config)
> Nov 25 14:16:52 pfdhcplistener(19238) INFO: pfdhcplistener_eth0 starting and
> writing 19239 to /usr/local/pf/var/run/pfdhcplistener_eth0.pid
> (pf::services::util::createpid)
> Nov 25 14:16:52 pfdhcplistener(19238) WARN: Unable to open VLAN proc
> description for eth0: No such file or directory (pf::util::get_vlan_from_int)
> Nov 25 14:16:52 pfdhcplistener(19238) INFO: The listener process is on the
> same server as the DHCP server. (main::)
> Nov 25 14:16:52 pfdhcplistener(19238) WARN: DHCP detector on an inline
> interface (main::)
> Nov 25 14:16:52 pfdhcplistener(19238) WARN: DHCP detector on an inline
> interface (main::)
> Nov 25 14:16:52 pfdhcplistener(19238) INFO: DHCP detector on eth0 enabled
> (main::)
> Nov 25 14:16:55 pfdhcplistener(19242) INFO: Reload configuration on eth1 with
> status 0 (main::reload_config)
> Nov 25 14:16:55 pfdhcplistener(19242) INFO: pfdhcplistener_eth1 starting and
> writing 19243 to /usr/local/pf/var/run/pfdhcplistener_eth1.pid
> (pf::services::util::createpid)
> Nov 25 14:16:55 pfdhcplistener(19242) WARN: Unable to open VLAN proc
> description for eth1: No such file or directory (pf::util::get_vlan_from_int)
> Nov 25 14:16:55 pfdhcplistener(19242) INFO: DHCP detector on eth1 enabled
> (main::)
Are all PacketFence services running?
Especially pfqueue, redis_queue and obviously the pfdhcplistener?
Are dhcp requests being received on the interface?
What does this report?
# tcpdump -tnl -i eth0 port bootpc or port bootps
Regards,
--
Louis Munro
[email protected] :: www.inverse.ca
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
