Hello Fabrice, Here is the information you requested. The domain has been changed and the DNS is hidden.
[root@sl006282 ~]# cat /usr/local/pf/conf/networks.conf [192.168.60.0] dns=192.168.xxx.xxx split_network=enabled dhcp_start=192.168.60.10 gateway=192.168.60.2 domain-name=inlinel2.domaine.com <http://inlinel2.domaine.com/> nat_enabled=enabled named=enabled dhcp_max_lease_time=30 fake_mac_enabled=disabled dhcpd=enabled dhcp_end=192.168.63.246 type=inlinel2 netmask=255.255.252.0 dhcp_default_lease_time=30 [root@sl006282 ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb state UP group default qlen 1000 link/ether 40:6c:8f:b8:95:cd brd ff:ff:ff:ff:ff:ff inet 192.168.2.186/24 brd 192.168.2.255 scope global enp9s0 valid_lft forever preferred_lft forever inet6 fe80::426c:8fff:feb8:95cd/64 scope link valid_lft forever preferred_lft forever 3: enp10s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb state UP group default qlen 1000 link/ether 40:6c:8f:b8:8a:f4 brd ff:ff:ff:ff:ff:ff inet 192.168.60.2/22 brd 192.168.63.255 scope global enp10s0 valid_lft forever preferred_lft forever inet6 fe80::426c:8fff:feb8:8af4/64 scope link valid_lft forever preferred_lft forever I'm aware that a configuration problem seems to be causing this address assignment problem. What I explain myself is why the problem appeared after a reboot. Regards Olivier > Le 11 avr. 2019 à 08:38, Durand fabrice via PacketFence-users > <[email protected]> a écrit : > > Hello Olivier, > > can you share your networks.conf pf.conf and do an "ip a" and paste the > result. > > If the dhcp server is not able to assign the requested address then it mean > that it's a configuration issue. > > Regards > > Fabrice > > > > Le 19-04-10 à 03 h 27, Olivier Gelin via PacketFence-users a écrit : >> Hello, >> >> I restarted the pfdhcp server just for fun. The service does not start >> anymore. >> >> pfdhcp: 2019/04/10 09:17:17 cannot assign requested address >> >> How to check the assignment address of pfdhcp. The goal is to understand why >> pfhdcp does not see itself. The PF we are talking about here is a test PF. I >> can do all the desired operations to understand why and how. >> >> /etc/sysconfig/network-scripts/ifcfg-enp10s0 is correct >> >> >> >>> Le 9 avr. 2019 à 15:50, Olivier Gelin via PacketFence-users >>> <[email protected] >>> <mailto:[email protected]>> a écrit : >>> >>> Hello Nicolas, >>> >>> >>>> Le 9 avr. 2019 à 13:29, Nicolas Quiniou-Briand <[email protected] >>>> <mailto:[email protected]>> a écrit : >>>> >>>> Hello Olivier, >>>> >>>> On 2019-04-08 1:36 p.m., Olivier Gelin wrote: >>>>> I applied the maintenance script and restarted right after. >>>> >>>> 1. Did you mean that pfdhcp broke after applying maintenance script ? Do >>>> you have done some customization in pfdhcp binary ? >>> >>> pfdhcp did not work before applying the maintenance scripts. It worked >>> again when I applied the script and updated the binaries. >>> >>>> >>>> 2. Each time pfdhcp complains about it "cannot assign requested address", >>>> I see these messages: >>>> ``` >>>> Apr 8 12:33:40 sl006282 pfdhcp[5695]: t=2019-04-08T12:33:40+0200 lvl=info >>>> msg="Setting log level to INFO" >>>> Apr 8 12:33:40 sl006282 pfdhcp[5695]: t=2019-04-08T12:33:40+0200 lvl=info >>>> msg="enp10s0 got the VIP" pid=5695 >>>> [..] >>>> Apr 8 12:33:41 sl006282 pfdhcp[5708]: t=2019-04-08T12:33:41+0200 lvl=info >>>> msg="Setting log level to INFO" >>>> Apr 8 12:33:41 sl006282 pfdhcp[5708]: t=2019-04-08T12:33:41+0200 lvl=info >>>> msg="enp10s0 got the VIP" pid=5708 >>>> [..] >>>> Apr 8 12:33:41 sl006282 pfdhcp[5717]: t=2019-04-08T12:33:41+0200 lvl=info >>>> msg="Setting log level to INFO" >>>> Apr 8 12:33:41 sl006282 pfdhcp[5717]: t=2019-04-08T12:33:41+0200 lvl=info >>>> msg="enp10s0 got the VIP" pid=5717 >>>> ``` >>>> Your network interface which get VIP doesn't seem stable. Are you in a >>>> cluster ? >>> >>> No cluster. The link between my PF and the network element following a good >>> quality Ethernet cable. It was working properly before restarting pf. >>> >>>> >>>>> The pfdhcp service has restarted, however the prefixed network is no >>>>> longer the same. the network took into consideration was the one >>>>> introduced in "Registration IP Address CIDR format" >>>> >>>> Could you give more details like: >>>> - expected results >>>> - actual results >>>> >>>> ? >>> >>> Distribution of DHCP on the "Inline" network. No address is given to the >>> devices present on the range defined in the enp10s0 interface. The current >>> status is that no device has got IP addresses. >>> >>> >>>> -- >>>> Nicolas Quiniou-Briand >>>> [email protected] <mailto:[email protected]> :: +1.514.447.4918 *140 :: >>>> https://inverse.ca <https://inverse.ca/> >>>> Inverse inc. :: Leaders behind SOGo (https://sogo.nu <https://sogo.nu/>), >>>> PacketFence (https://packetfence.org <https://packetfence.org/>) and >>>> Fingerbank (http://fingerbank.org <http://fingerbank.org/>) >>> >>> >>> >>> _______________________________________________ >>> PacketFence-users mailing list >>> [email protected] >>> <mailto:[email protected]> >>> https://lists.sourceforge.net/lists/listinfo/packetfence-users >>> <https://lists.sourceforge.net/lists/listinfo/packetfence-users> >> >> >> >> >> _______________________________________________ >> PacketFence-users mailing list >> [email protected] >> <mailto:[email protected]> >> https://lists.sourceforge.net/lists/listinfo/packetfence-users >> <https://lists.sourceforge.net/lists/listinfo/packetfence-users> > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
