HI, I added ‘!dhclient \$if’ to the /etc/hostname.em0 and removed ‘dhcp’. It is working now with no errors on startup and the interface ‘pflow0’ now working properly.
pf enabled net.inet.ip.forwarding: 0 -> 1 net.inet6.ip6.forwarding: 0 -> 1 starting network em0: no link....got link em0: no lease.....got lease em0: 122.199.32.172 lease accepted from 116.255.18.1 (3c:fd:fe:bd:95:13) reordering libraries: done. starting early daemons: syslogd pflogd unbound ntpd. starting RPC daemons:. savecore: no core dump checking quotas: done. clearing /tmp kern.securelevel: 0 -> 1 creating runtime link editor directory cache. preserving editor files. starting network daemons: sshd snmpd dhcpd rad smtpd. starting package daemons: dhcpcd. starting local daemons: cron. Sun Oct 17 12:24:00 AEDT 2021 Many thanks for your help Antonino Sidoti > On 17 Oct 2021, at 1:12 am, Brian Brombacher <br...@planetunix.net> wrote: > > > >> On Oct 15, 2021, at 10:56 PM, Antonino Sidoti <n...@sidoti.id.au> wrote: >> >> HI, >> >> Yes, on my em0 interface I am using ‘dhcp’ and this is the source IP for >> pflow. The setup is a basic firewall as described in the PF example >> firewall. >> >> Interface em0 = external using dhcp (Static IP assigned by carrier) >> Interface em1 = internal with static IP (Lan using 10.0.x.x/24) >> >> Output from /etc/hostname.pflow0 (Not real IPs) >> flowdst 203.0.113.1:3001 flowsrc 198.51.100.1 >> pflowproto 10 >> >> Thanks >> >> Antonino Sidoti >> >> > > Thanks for the details. A recent change in 7.0 introduced a change in > behavior for DHCP configured interfaces. The IP could be assigned after > other interfaces are configured. You may need to assign the static IP in > hostname.em0 before the dhcp line, or run dhclient directly from hostname.em0 > and avoid using “dhcp” in there. > >> >>>> On 16 Oct 2021, at 10:39 am, Brian Brombacher <br...@planetunix.net> wrote: >>>> >>>> >>>> >>>>> On Oct 15, 2021, at 7:09 PM, Antonino Sidoti <n...@sidoti.id.au> wrote: >>>> >>>> HI, >>>> >>>> I am getting this error since upgrading to v7.0; >>>> >>>> pf enabled >>>> net.inet.ip.forwarding: 0 -> 1 >>>> net.inet6.ip6.forwarding: 0 -> 1 >>>> starting network >>>> >>>> ifconfig: SIOCSETPFLOW: Can't assign requested address >>>> ifconfig: SIOCSETPFLOW: Can't assign requested address >>>> >>>> reordering libraries: done. >>>> starting early daemons: syslogd pflogd unbound ntpd. >>>> starting RPC daemons:. >>>> savecore: no core dump >>>> checking quotas: done. >>>> clearing /tmp >>>> kern.securelevel: 0 -> 1 >>>> creating runtime link editor directory cache. >>>> preserving editor files. >>>> starting network daemons: sshd snmpd dhcpd rad smtpd. >>>> starting package daemons: dhcpcd. >>>> starting local daemons: cron. >>>> Sat Oct 16 08:06:39 AEDT 2021 >>>> >>>> I am assuming it is related to the interface ‘pflow0’ which was working >>>> fine in version 6.9. The /etc/hostname.pflow0 is exactly the same as the >>>> examples in the man pages only that the source and destination IP >>>> addresses are different. >>>> >>>> Many thanks >>>> >>>> Antonino Sidoti >>>> >>>> >>>> >>> >>> Are you using DHCP to configure the interface the source IP is on? Provide >>> some more details of the network setup.