"Failed to obtain IP address" ?? DHCP problem

johnpoz

"the lan is connected to a hub."

A hub really – is this 2000? Hub? You mean a switch..

"is configured with static IP (192.0.2.1 )"

Why would you have a static set for that address???
NetRange: 192.0.2.0 - 192.0.2.255
CIDR: 192.0.2.0/24
NetName: TEST-NET-1
NetHandle: NET-192-0-2-0-1
Parent: NET192 (NET-192-0-0-0-0)
NetType: IANA Special Use

That is not some network you should be using -- why would you not be using normal rfc1918??

And yeah this is a PROBLEM!!
Sep 18 21:59:06 dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 via re2
Sep 18 21:59:06 dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 via re1

You clearly have an issue - maybe that your using a "hub" ?? And plugging to different networks into a "hub" ???

It should be impossible to see discover on 2 different physical interfaces that are suppose to be in different networks.. So running your networks on the same wire.. Have connection between 2 networks that shouldn't be, etc.

Why is re2 doing a dhcp? That looks to be opt1 why would it be trying to get an IP? Do you have it set for dhcp? Is a lan iterface or a wan?

Mellowlynx

Yep you are right, it's a switch, but I'm used to say hub when you can't configure it.

I switched it this afternoon to make sure the DHCP was working by trying to connect from my phone and see if I got the new range.
It used to be 192.168.2.0/24

Situation:

Wan - re0 - DHCP
Lan - re1 - Static IP - private network for POS, and wifi upstairs
OPT1 - re2 - Static IP - Public wifi with Captive Portal

I will check tomorrow to see if any cables are not correctly connected.

johnpoz

Well why are you seeing this then?
Sep 18 21:53:38 php-fpm[55680]: /rc.newwanip: rc.newwanip: on (IP address: 192.0.2.1) (interface: OPT1[opt1]) (real interface: re2).

If wan is re0? And again why would you be using a 192.0.2 network anywhere??? This is NOT a network to use!!!

Also a switch that you can not manage would be a dumb switch not a "hub" A hub is completely different tech, old tech to be sure.

Mellowlynx

@johnpoz:

Well why are you seeing this then?
Sep 18 21:53:38 php-fpm[55680]: /rc.newwanip: rc.newwanip: on (IP address: 192.0.2.1) (interface: OPT1[opt1]) (real interface: re2).

You can see that at Sep 18 18:42:26 I turned off the guest wifi access point
and at Sep 18 21:53:38 I turned it on again.

Proving that nothing else is connected to the re2 interface.

Derelict

The point is why does pfSense think re2 is a WAN interface? Did you assign a gateway to it? That is wrong.

You have two different interfaces receiving DHCPDISCOVER packets from the same MAC at the same time. Your network is hosed.

johnpoz

You can not plug multiple interfaces from pfsense into the same dumb switch.. You need a smart/managed switch that supports vlans to use same switch.. Plugging 2 different interfaces not on the same network into same switch gets you what your seeing

Sep 18 21:59:06 dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 via re2
Sep 18 21:59:06 dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 via re1

And you also have something else wrong with re2 since its trying to renew wanip on it??

I would suggest you draw out your network and document what networks are suppose to be where.. And if you mention use of 192.0.2 your doing it WRONG!! And clearly we see that is in use from the logs as well.

Mellowlynx

@johnpoz:

You can not plug multiple interfaces from pfsense into the same dumb switch..

No one say we did.
Once agian, I'm 100% sure that re2 is directly connected to the guest access point
The re1, has a switch yes, and that on there the POS, music computer, a laptop and the private wifi for upstairs is connected.

@johnpoz:

And if you mention use of 192.0.2 your doing it WRONG!!

DUDE, your message is CLEAR!
I appreciate the feedback and help, and I will edit it back if I'm there and I can access the web config, because now I can't do anything.
Cafe is closed, boss is not home and I can't remotely access the web config.

@Derelict:

The point is why does pfSense think re2 is a WAN interface? Did you assign a gateway to it? That is wrong.

Don't know, I will check, thanks

Mellowlynx

I changed the IP of re2 back, and removed the gateway address.
Now it's running a bit better, but not as fast as normal yet.

At the start I tested a bit to quick I think and it could not keep up with my switching between the WiFi networks.
At the end I tuned off the WiFi on my phone and switched it back of after a view minutes, and it connected in about 20 sec.

Here the logs after the edits.
Like to hear if everything is good now or that there are still changes that need to be made.
For now I will see how this will run for the next days.

Thanks johnpoz, Derelict and KOM for the replays and assistance.

Status: System logs: General


Sep 19 16:15:48    check_reload_status: Syncing firewall
Sep 19 16:17:13    check_reload_status: Syncing firewall
Sep 19 16:18:43    check_reload_status: Restarting ipsec tunnels
Sep 19 16:19:01    php-fpm[12012]: /interfaces.php: The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid re1 re2' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.2.8 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ bad range, address 192.0.2.5 not in subnet 192.168.2.0 netmask 255.255.255.0 If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-bugs at isc.org mailing list, please read the section on the README about submitting bug reports and requests for help. Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appr
Sep 19 16:19:02    check_reload_status: updating dyndns opt1
Sep 19 16:22:14    kernel: re2: link state changed to DOWN
Sep 19 16:22:24    check_reload_status: Linkup starting re2
Sep 19 16:22:30    check_reload_status: Linkup starting re2
Sep 19 16:22:30    kernel: re2: link state changed to UP
Sep 19 16:26:36    check_reload_status: Reloading filter
Sep 19 16:26:36    php-fpm[12012]: /interfaces.php: Creating rrd update script
Sep 19 16:27:29    check_reload_status: Syncing firewall
Sep 19 16:29:32    php-fpm[10867]: /rc.linkup: Hotplug event detected for OPT1(opt1) but ignoring since interface is configured with static IP (192.168.2.1 )
Sep 19 16:29:32    check_reload_status: Syncing firewall
Sep 19 16:29:32    php-fpm[10867]: /rc.linkup: Hotplug event detected for OPT1(opt1) but ignoring since interface is configured with static IP (192.168.2.1 )
Sep 19 16:29:32    check_reload_status: rc.newwanip starting re2
Sep 19 16:30:20    php-fpm[44284]: /rc.newwanip: rc.newwanip: Info: starting on re2.
Sep 19 16:30:20    php-fpm[44284]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.2.1) (interface: OPT1[opt1]) (real interface: re2).
Sep 19 16:30:20    php-fpm[44284]: /rc.newwanip: IP has changed, killing states on former IP 192.0.2.1.
Sep 19 16:31:16    php-fpm[44284]: /rc.newwanip: Ignoring IPsec reload since there are no tunnels on interface opt1
Sep 19 16:31:16    php-fpm[44284]: /rc.newwanip: Resyncing OpenVPN instances for interface OPT1.
Sep 19 16:31:16    php-fpm[44284]: /rc.newwanip: Creating rrd update script
Sep 19 16:31:18    php-fpm[44284]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 192.0.2.1 -> 192.168.2.1 - Restarting packages.
Sep 19 16:31:18    check_reload_status: Starting packages
Sep 19 16:34:02    check_reload_status: Syncing firewall
Sep 19 16:36:09    check_reload_status: Syncing firewall
Sep 19 16:36:49    php-fpm[21488]: /rc.start_packages: Restarting/Starting all packages.
Sep 19 16:39:23    check_reload_status: Syncing firewall
Sep 19 16:39:53    check_reload_status: Linkup starting re0
Sep 19 16:39:53    kernel: re0: link state changed to DOWN
Sep 19 16:39:55    check_reload_status: Linkup starting re0
Sep 19 16:39:55    kernel: re0: link state changed to UP
Sep 19 16:39:57    php-fpm[10867]: /rc.linkup: DEVD Ethernet detached event for wan
Sep 19 16:40:01    check_reload_status: rc.newwanip starting re0
Sep 19 16:40:11    php-fpm[10867]: /rc.linkup: Shutting down Router Advertisment daemon cleanly
Sep 19 16:40:11    php-fpm[97112]: /rc.linkup: DEVD Ethernet attached event for wan
Sep 19 16:40:11    php-fpm[97112]: /rc.linkup: HOTPLUG: Configuring interface wan
Sep 19 16:40:35    check_reload_status: updating dyndns WAN_DHCP
Sep 19 16:40:35    check_reload_status: Restarting ipsec tunnels
Sep 19 16:40:35    check_reload_status: Restarting OpenVPN tunnels/interfaces
Sep 19 16:40:35    check_reload_status: Reloading filter
Sep 19 16:40:38    kernel: arpresolve: can't allocate llinfo for XX.XX.XX.X on re0
Sep 19 16:40:47    php-fpm[12012]: /rc.newwanip: rc.newwanip: Info: starting on re0.
Sep 19 16:40:47    php-fpm[12012]: /rc.newwanip: rc.newwanip: on (IP address: 0.0.0.0) (interface: WAN[wan]) (real interface: re0).
Sep 19 16:40:47    php-fpm[12012]: /rc.newwanip: rc.newwanip: Failed to update wan IP, restarting...
Sep 19 16:40:47    check_reload_status: Configuring interface wan
Sep 19 16:40:48    php-fpm[12012]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Sep 19 16:41:52    check_reload_status: updating dyndns WAN_DHCP
Sep 19 16:41:52    check_reload_status: Restarting ipsec tunnels
Sep 19 16:41:52    check_reload_status: Restarting OpenVPN tunnels/interfaces
Sep 19 16:41:52    check_reload_status: Reloading filter
Sep 19 16:42:04    php-fpm[97112]: /rc.linkup: The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf re0 > /tmp/re0_output 2> /tmp/re0_error_output' returned exit code '15', the output was ''
Sep 19 16:42:04    php-fpm[97112]: /rc.linkup: Accept router advertisements on interface re0
Sep 19 16:42:04    check_reload_status: rc.newwanip starting re0
Sep 19 16:42:04    php-fpm[97112]: /rc.linkup: ROUTING: setting default route to XX.XX.XX.X
Sep 19 16:42:04    check_reload_status: Restarting ipsec tunnels
Sep 19 16:42:29    check_reload_status: updating dyndns WAN_DHCP
Sep 19 16:42:29    check_reload_status: Restarting ipsec tunnels
Sep 19 16:42:29    check_reload_status: Restarting OpenVPN tunnels/interfaces
Sep 19 16:42:29    check_reload_status: Reloading filter
Sep 19 16:42:49    php-fpm[12012]: /rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
Sep 19 16:43:22    kernel: arpresolve: can't allocate llinfo for XX.XX.XX.X on re0
Sep 19 16:43:22    kernel: arpresolve: can't allocate llinfo for XX.XX.XX.X on re0
Sep 19 16:43:33    kernel: arpresolve: can't allocate llinfo for XX.XX.XX.X on re0
Sep 19 16:43:45    kernel: arpresolve: can't allocate llinfo for XX.XX.XX.X on re0
Sep 19 16:43:56    kernel: arpresolve: can't allocate llinfo for XX.XX.XX.X on re0
Sep 19 16:44:20    check_reload_status: updating dyndns wan
Sep 19 16:44:22    check_reload_status: rc.newwanip starting re0
Sep 19 16:44:22    php-fpm[99392]: /rc.interfaces_wan_configure: Accept router advertisements on interface re0
Sep 19 16:44:26    check_reload_status: updating dyndns WAN_DHCP
Sep 19 16:44:26    check_reload_status: Restarting ipsec tunnels
Sep 19 16:44:26    check_reload_status: Restarting OpenVPN tunnels/interfaces
Sep 19 16:44:26    check_reload_status: Reloading filter
Sep 19 16:47:13    check_reload_status: Syncing firewall
Sep 19 16:47:27    php-fpm[12012]: /rc.newwanip: rc.newwanip: Info: starting on re0.
Sep 19 16:47:27    php-fpm[12012]: /rc.newwanip: rc.newwanip: on (IP address: XX.XX.XX.XXX (interface: WAN[wan]) (real interface: re0).
Sep 19 16:47:59    php-fpm[97112]: /rc.newwanip: rc.newwanip: Info: starting on re0.
Sep 19 16:47:59    php-fpm[97112]: /rc.newwanip: rc.newwanip: on (IP address: XX.XX.XX.XXX) (interface: WAN[wan]) (real interface: re0).
Sep 19 16:47:59    php-fpm[12012]: /rc.newwanip: ROUTING: setting default route to XX.XX.XX.X
Sep 19 16:48:00    php-fpm[97112]: /rc.newwanip: ROUTING: setting default route to XX.XX.XX.X
Sep 19 16:49:59    php-fpm[12012]: /rc.newwanip: The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid re1 re2' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.2.8 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Wrote 20 leases to leases file. Listening on BPF/re2/10:fe:ed:06:ad:da/192.168.2.0/24 Sending on BPF/re2/10:fe:ed:06:ad:da/192.168.2.0/24 Listening on BPF/re1/10:fe:ed:06:b2:62/192.168.1.0/24 Sending on BPF/re1/10:fe:ed:06:b2:62/192.168.1.0/24 Can't bind to dhcp address: Address already in use Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before reques
Sep 19 16:50:00    php-fpm[97112]: /rc.newwanip: Ignoring IPsec reload since there are no tunnels on interface wan
Sep 19 16:50:00    php-fpm[12012]: /rc.newwanip: Ignoring IPsec reload since there are no tunnels on interface wan
Sep 19 16:50:00    php-fpm[12012]: /rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Sep 19 16:50:00    php-fpm[97112]: /rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Sep 19 16:50:00    php-fpm[12012]: /rc.newwanip: Creating rrd update script
Sep 19 16:50:00    php-fpm[97112]: /rc.newwanip: Creating rrd update script
Sep 19 16:50:02    php-fpm[97112]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - XX.XX.XX.XXX -> XX.XX.XX.XXX - Restarting packages.  <- Both same IP
Sep 19 16:50:02    check_reload_status: Starting packages
Sep 19 16:50:02    php-fpm[12012]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - XX.XX.XX.XXX -> XX.XX.XX.XXX - Restarting packages. <- Both same IP
Sep 19 16:50:02    check_reload_status: Starting packages
Sep 19 16:50:03    php-fpm[97112]: /rc.start_packages: Restarting/Starting all packages.
Sep 19 16:50:03    php-fpm[97112]: /rc.start_packages: Restarting/Starting all packages.
Sep 19 17:01:49    syslogd: exiting on signal 15
Sep 19 17:01:54    syslogd: kernel boot file is /boot/kernel/kernel
Sep 19 17:17:33    syslogd: exiting on signal 15
Sep 19 17:17:33    syslogd: kernel boot file is /boot/kernel/kernel

Status: System logs: DHCP


Sep 19 16:53:17    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 16:53:17    dhcpd: unexpected ICMP Echo Reply from 82.73.80.1
Sep 19 16:53:18    dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 16:53:36    dhcpd: DHCPREQUEST for 192.168.2.5 (192.168.2.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 16:53:36    dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 16:53:43    dhcpd: DHCPREQUEST for 192.168.2.5 (192.168.2.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 16:53:43    dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 16:54:18    dhcpd: DHCPREQUEST for 192.168.2.5 (192.168.2.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 16:54:18    dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 16:54:18    dhcpd: DHCPREQUEST for 192.0.2.7 from bc:e5:9f:6b:b5:9f via re2: wrong network.
Sep 19 16:54:18    dhcpd: DHCPNAK on 192.0.2.7 to bc:e5:9f:6b:b5:9f via re2
Sep 19 16:54:19    dhcpd: DHCPDISCOVER from bc:e5:9f:6b:b5:9f via re2
Sep 19 16:54:20    dhcpd: unexpected ICMP Echo Reply from 82.73.80.1
Sep 19 16:54:20    dhcpd: DHCPOFFER on 192.168.2.8 to bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re2
Sep 19 16:54:27    dhcpd: DHCPREQUEST for 192.168.2.8 (192.168.2.1) from bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re2
Sep 19 16:54:27    dhcpd: DHCPACK on 192.168.2.8 to bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re2
Sep 19 16:54:45    dhcpd: DHCPREQUEST for 192.168.2.8 (192.168.2.1) from bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re2
Sep 19 16:54:45    dhcpd: DHCPACK on 192.168.2.8 to bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re2
Sep 19 16:55:35    dhcpd: DHCPINFORM from 192.168.1.123 via re1
Sep 19 16:55:35    dhcpd: DHCPACK to 192.168.1.123 (20:cf:30:3c:c7:5f) via re1
Sep 19 16:58:16    dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 via re1
Sep 19 16:58:16    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:27    dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:27    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:27    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:27    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:27    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:27    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:27    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:27    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:29    dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:29    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31    dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31    dhcpd: DHCPINFORM from 192.168.1.123 via re1
Sep 19 16:58:31    dhcpd: DHCPACK to 192.168.1.123 (20:cf:30:3c:c7:5f) via re1
Sep 19 16:58:31    dhcpd: DHCPINFORM from 192.168.1.123 via re1
Sep 19 16:58:31    dhcpd: DHCPACK to 192.168.1.123 (20:cf:30:3c:c7:5f) via re1
Sep 19 16:58:31    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:33    dhcpd: DHCPREQUEST for 192.168.1.144 (192.168.1.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:33    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:01:13    dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 via re2
Sep 19 17:01:13    dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:15    dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:15    dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:15    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:15    dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:15    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:15    dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:15    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:15    dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:17    dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:17    dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:19    dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:19    dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:19    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:19    dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:19    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:19    dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:19    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:19    dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:01:21    dhcpd: DHCPREQUEST for 192.168.1.133 from 00:d0:b8:0c:c5:9e via re1
Sep 19 17:01:21    dhcpd: DHCPACK on 192.168.1.133 to 00:d0:b8:0c:c5:9e via re1
Sep 19 17:01:23    dhcpd: DHCPREQUEST for 192.168.1.133 from 00:d0:b8:0c:c5:9e via re1
Sep 19 17:01:23    dhcpd: DHCPACK on 192.168.1.133 to 00:d0:b8:0c:c5:9e via re1

Sep 19 17:09:35    dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X
Sep 19 17:09:35    dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X
Sep 19 17:09:35    dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X
Sep 19 17:09:35    dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X
Sep 19 17:09:35    dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X
Sep 19 17:09:35    dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X
Sep 19 17:09:35    dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X
Sep 19 17:09:35    dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X
Sep 19 17:09:35    dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X
Sep 19 17:09:36    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:21    dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:21    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:21    dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 via re2
Sep 19 17:10:25    dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:25    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:25    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:25    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:25    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:25    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:25    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:25    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:27    dhcpd: DHCPREQUEST for 192.168.1.148 from 70:56:81:0a:10:e8 (iPod-touch-4) via re1
Sep 19 17:10:27    dhcpd: DHCPACK on 192.168.1.148 to 70:56:81:0a:10:e8 (iPod-touch-4) via re1
Sep 19 17:10:29    dhcpd: DHCPREQUEST for 192.168.1.146 from 70:56:81:52:9f:15 (Coen) via re1
Sep 19 17:10:29    dhcpd: DHCPACK on 192.168.1.146 to 70:56:81:52:9f:15 (Coen) via re1
Sep 19 17:10:29    dhcpd: DHCPOFFER on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:10:33    dhcpd: DHCPREQUEST for 192.168.1.148 from 70:56:81:0a:10:e8 (iPod-touch-4) via re1
Sep 19 17:10:33    dhcpd: DHCPACK on 192.168.1.148 to 70:56:81:0a:10:e8 (iPod-touch-4) via re1
Sep 19 17:10:35    dhcpd: DHCPREQUEST for 192.168.1.146 from 70:56:81:52:9f:15 (Coen) via re1
Sep 19 17:10:35    dhcpd: DHCPACK on 192.168.1.146 to 70:56:81:52:9f:15 (Coen) via re1
Sep 19 17:10:37    dhcpd: DHCPREQUEST for 192.168.1.144 (192.168.1.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:37    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:37    dhcpd: DHCPDISCOVER from 70:56:81:52:9f:15 (Coen) via re1
Sep 19 17:10:37    dhcpd: DHCPOFFER on 192.168.1.146 to 70:56:81:52:9f:15 (Coen) via re1
Sep 19 17:10:39    dhcpd: DHCPREQUEST for 192.168.2.108 (192.168.2.1) from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:10:39    dhcpd: DHCPACK on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:10:41    dhcpd: DHCPREQUEST for 192.168.2.108 (192.168.2.1) from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:10:41    dhcpd: DHCPACK on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:10:43    dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:43    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:46    dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:46    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:46    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:46    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:46    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:46    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:10:46    dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:10:46    dhcpd: DHCPOFFER on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:10:46    dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:10:46    dhcpd: DHCPOFFER on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:12:04    dhcpd: DHCPREQUEST for 192.168.1.144 (192.168.1.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:12:04    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:12:12    dhcpd: DHCPREQUEST for 192.168.2.108 (192.168.2.1) from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:12:12    dhcpd: DHCPACK on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:12:18    dhcpd: DHCPREQUEST for 192.168.2.108 (192.168.2.1) from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:12:18    dhcpd: DHCPACK on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:12:22    dhcpd: DHCPREQUEST for 192.168.2.108 (192.168.2.1) from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:12:22    dhcpd: DHCPACK on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:12:26    dhcpd: DHCPREQUEST for 192.168.2.108 (192.168.2.1) from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:12:26    dhcpd: DHCPACK on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:12:56    dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:12:56    dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:13:55    dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:13:55    dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:13:55    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:13:55    dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:13:55    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:13:55    dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:14:14    dhcpd: DHCPREQUEST for 192.168.1.144 (192.168.1.1) from cc:3a:61:91:fb:f0 via re1
Sep 19 17:14:14    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:14:20    dhcpd: DHCPREQUEST for 192.168.1.144 (192.168.1.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:14:20    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:14:51    dhcpd: DHCPREQUEST for 192.168.1.144 (192.168.1.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:14:51    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:16:05    dhcpd: DHCPREQUEST for 192.168.1.131 from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:16:05    dhcpd: DHCPACK on 192.168.1.131 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:16:45    dhcpd: DHCPREQUEST for 192.168.1.131 from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:16:45    dhcpd: DHCPACK on 192.168.1.131 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:16:45    dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:16:45    dhcpd: DHCPOFFER on 192.168.1.131 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:16:45    dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:16:45    dhcpd: DHCPOFFER on 192.168.1.131 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:16:45    dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:16:45    dhcpd: DHCPOFFER on 192.168.1.131 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:16:59    dhcpd: DHCPREQUEST for 192.168.1.131 from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:16:59    dhcpd: DHCPACK on 192.168.1.131 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:17:23    dhcpd: DHCPREQUEST for 192.168.1.131 from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:17:23    dhcpd: DHCPACK on 192.168.1.131 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:17:23    dhcpd: DHCPDISCOVER from 88:9b:39:16:10:53 via re2
Sep 19 17:17:28    dhcpd: DHCPREQUEST for 192.168.2.7 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Sep 19 17:17:28    dhcpd: DHCPACK on 192.168.2.7 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Sep 19 17:17:32    dhcpd: DHCPREQUEST for 192.168.2.7 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Sep 19 17:17:32    dhcpd: DHCPACK on 192.168.2.7 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Sep 19 17:17:32    dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Sep 19 17:17:32    dhcpd: DHCPOFFER on 192.168.2.7 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Sep 19 17:17:32    dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:17:39    dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 via re1
Sep 19 17:18:15    dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:18:15    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:18:23    dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:18:23    dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:18:23    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:18:23    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:18:23    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:18:23    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:18:23    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:18:23    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:18:31    dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 via re1: wrong network.
Sep 19 17:18:31    dhcpd: DHCPNAK on 192.168.2.5 to cc:3a:61:91:fb:f0 via re1
Sep 19 17:18:31    dhcpd: DHCPOFFER on 192.168.2.9 to 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:18:31    dhcpd: DHCPOFFER on 192.168.1.131 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re1
Sep 19 17:18:31    dhcpd: DHCPOFFER on 192.168.1.147 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1
Sep 19 17:18:31    dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 via re2
Sep 19 17:18:31    dhcpd: DHCPDISCOVER from 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:18:41    dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 via re2
Sep 19 17:18:41    dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:18:41    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:18:41    dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 17:19:03    dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 via re1
Sep 19 17:19:03    dhcpd: DHCPOFFER on 192.168.2.7 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Sep 19 17:19:03    dhcpd: DHCPOFFER on 192.168.2.9 to 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:03    dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X
Sep 19 17:19:03    dhcpd: DHCPDISCOVER from 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:03    dhcpd: DHCPOFFER on 192.168.2.9 to 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:03    dhcpd: DHCPDISCOVER from 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:03    dhcpd: DHCPOFFER on 192.168.2.9 to 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:03    dhcpd: DHCPDISCOVER from 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:03    dhcpd: DHCPOFFER on 192.168.2.9 to 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:03    dhcpd: DHCPDISCOVER from 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:03    dhcpd: DHCPOFFER on 192.168.2.9 to 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:03    dhcpd: DHCPDISCOVER from 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:03    dhcpd: DHCPOFFER on 192.168.2.9 to 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:03    dhcpd: DHCPDISCOVER from 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:03    dhcpd: DHCPOFFER on 192.168.2.9 to 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:05    dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 via re2
Sep 19 17:19:05    dhcpd: DHCPDISCOVER from 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:05    dhcpd: DHCPOFFER on 192.168.2.9 to 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:07    dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X
Sep 19 17:19:07    dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 17:19:07    dhcpd: DHCPOFFER on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:19:07    dhcpd: DHCPDISCOVER from 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:07    dhcpd: DHCPOFFER on 192.168.2.9 to 88:9b:39:16:10:53 (android-f80691ecff173161) via re2
Sep 19 17:19:07    dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:19:07    dhcpd: DHCPOFFER on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:19:07    dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:19:07    dhcpd: DHCPOFFER on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:19:07    dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:19:07    dhcpd: DHCPOFFER on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:19:07    dhcpd: DHCPDISCOVER from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:19:07    dhcpd: DHCPOFFER on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:19:13    dhcpd: DHCPREQUEST for 192.168.2.108 (192.168.2.1) from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:19:13    dhcpd: DHCPACK on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:19:20    dhcpd: DHCPREQUEST for 192.168.2.108 (192.168.2.1) from 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:19:20    dhcpd: DHCPACK on 192.168.2.108 to 84:38:38:34:79:34 (android-1832579c57ad3a7d) via re2
Sep 19 17:20:11    dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 via re2
Sep 19 17:20:11    dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2

Added
I just walked away to a house 3 doors down for 5 minutes, when I came back I did not get connected as it should.

Status: System logs: DHCP


Sep 19 18:04:33	dhcpd: DHCPDISCOVER from 0c:30:21:db:3f:6c (iPhonevWoudstra) via re2
Sep 19 18:04:33	dhcpd: DHCPOFFER on 192.168.2.11 to 0c:30:21:db:3f:6c (iPhonevWoudstra) via re2
Sep 19 18:04:33	dhcpd: DHCPDISCOVER from 0c:30:21:db:3f:6c (iPhonevWoudstra) via re2
Sep 19 18:04:33	dhcpd: DHCPOFFER on 192.168.2.11 to 0c:30:21:db:3f:6c (iPhonevWoudstra) via re2
Sep 19 18:04:33	dhcpd: DHCPDISCOVER from 0c:30:21:db:3f:6c (iPhonevWoudstra) via re2
Sep 19 18:04:33	dhcpd: DHCPOFFER on 192.168.2.11 to 0c:30:21:db:3f:6c (iPhonevWoudstra) via re2
Sep 19 18:05:00	dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:05:00	dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:05:16	dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:05:16	dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:05:16	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:05:16	dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:05:16	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:05:16	dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:05:16	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:05:16	dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:05:16	dhcpd: DHCPINFORM from 192.168.1.123 via re1
Sep 19 18:05:16	dhcpd: DHCPACK to 192.168.1.123 (20:cf:30:3c:c7:5f) via re1
Sep 19 18:05:16	dhcpd: DHCPINFORM from 192.168.1.123 via re1
Sep 19 18:05:16	dhcpd: DHCPACK to 192.168.1.123 (20:cf:30:3c:c7:5f) via re1
Sep 19 18:06:00	dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:06:00	dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:06:02	dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:06:02	dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:06:02	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:06:02	dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:06:02	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:06:02	dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:06:02	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:06:02	dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:06:04	dhcpd: DHCPREQUEST for 192.168.1.123 from 20:cf:30:3c:c7:5f (Gebruiker-PC) via re1
Sep 19 18:06:04	dhcpd: DHCPACK on 192.168.1.123 to 20:cf:30:3c:c7:5f (Gebruiker-PC) via re1
Sep 19 18:06:06	dhcpd: DHCPREQUEST for 192.168.1.123 from 20:cf:30:3c:c7:5f (Gebruiker-PC) via re1
Sep 19 18:06:06	dhcpd: DHCPACK on 192.168.1.123 to 20:cf:30:3c:c7:5f (Gebruiker-PC) via re1
Sep 19 18:06:08	dhcpd: DHCPREQUEST for 192.168.1.123 from 20:cf:30:3c:c7:5f (Gebruiker-PC) via re1
Sep 19 18:06:08	dhcpd: DHCPACK on 192.168.1.123 to 20:cf:30:3c:c7:5f (Gebruiker-PC) via re1
Sep 19 18:06:08	dhcpd: DHCPINFORM from 192.168.1.123 via re1
Sep 19 18:06:08	dhcpd: DHCPACK to 192.168.1.123 (20:cf:30:3c:c7:5f) via re1
Sep 19 18:06:08	dhcpd: DHCPINFORM from 192.168.1.123 via re1
Sep 19 18:06:08	dhcpd: DHCPACK to 192.168.1.123 (20:cf:30:3c:c7:5f) via re1
Sep 19 18:06:15	dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:06:15	dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:06:17	dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:06:17	dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:06:17	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:06:17	dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:06:17	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:06:17	dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:07:21	dhcpd: DHCPREQUEST for 192.168.1.144 (192.168.1.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:07:21	dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:07:21	dhcpd: DHCPDISCOVER from 0c:30:21:db:3f:6c (iPhonevWoudstra) via re2
Sep 19 18:08:01	dhcpd: DHCPREQUEST for 192.168.1.144 (192.168.1.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:01	dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:08	dhcpd: DHCPREQUEST for 192.168.1.144 (192.168.1.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:08	dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:48	dhcpd: DHCPREQUEST for 192.168.1.144 (192.168.1.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:48	dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:52	dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:52	dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:54	dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:54	dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:54	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:54	dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:54	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:54	dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:54	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:54	dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:08:54	dhcpd: DHCPOFFER on 192.168.2.11 to 0c:30:21:db:3f:6c (iPhonevWoudstra) via re2
Sep 19 18:09:00	dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 via re2
Sep 19 18:09:00	dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:02	dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:02	dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:02	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:02	dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:02	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:02	dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:02	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:02	dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:05	dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:05	dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:07	dhcpd: DHCPREQUEST for 192.168.2.5 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:07	dhcpd: DHCPACK on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:07	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:07	dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:07	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:07	dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:07	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:07	dhcpd: DHCPOFFER on 192.168.2.5 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re2
Sep 19 18:09:11	dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 via re1
Sep 19 18:09:11	dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:09:13	dhcpd: DHCPREQUEST for 192.168.1.144 from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:09:13	dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:09:13	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:09:13	dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:09:13	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:09:13	dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:09:13	dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:09:13	dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:09:15	dhcpd: DHCPREQUEST for 192.168.1.144 (192.168.1.1) from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 18:09:15	dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1

I also get this one allot

Status: System logs: Gateways


apinger: Could not bind socket on address(XX.XX.XX.XXX) for monitoring address XX.XX.XX.X(WAN_DHCP) with error Can't assign requested address

johnpoz

which one is you? You see for example this guy
Sep 19 16:58:31 dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31 dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31 dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31 dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1

He gets offered an IP multiple times and he just keeps asking.. Is he not seeing the offer? Seem he does because he sends an ack
Sep 19 16:58:29 dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1

But continues to ask with discover again and again.

Why are you seeing what looks like wan request on re2?
Sep 19 16:30:20 php-fpm[44284]: /rc.newwanip: rc.newwanip: Info: starting on re2.
Sep 19 16:30:20 php-fpm[44284]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.2.1) (interface: OPT1[opt1]) (real interface: re2).

Why are you seeing hotplug events
Sep 19 16:29:32 php-fpm[10867]: /rc.linkup: Hotplug event detected for OPT1(opt1) but ignoring since interface is configured with static IP (192.168.2.1 )
Sep 19 16:29:32 check_reload_status: Syncing firewall
Sep 19 16:29:32 php-fpm[10867]: /rc.linkup: Hotplug event detected for OPT1(opt1) but ignoring since interface is configured with static IP (192.168.2.1 )
Sep 19 16:29:32 check_reload_status: rc.newwanip starting re2

Is this a USB interface? So your router for a business setup is using usb devices? That is just asking for trouble? You can not setup a decent router/firewall with actual interfaces to support a business that could be had for 200 bucks? An actual nic could be had for as little as $20..

Mellowlynx

@johnpoz:

which one is you? You see for example this guy
Sep 19 16:58:31 dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31 dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31 dhcpd: DHCPDISCOVER from cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1
Sep 19 16:58:31 dhcpd: DHCPOFFER on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1

He gets offered an IP multiple times and he just keeps asking.. Is he not seeing the offer? Seem he does because he sends an ack
Sep 19 16:58:29 dhcpd: DHCPACK on 192.168.1.144 to cc:3a:61:91:fb:f0 (android-10e9ec552f40a2c0) via re1

But continues to ask with discover again and again.

Thats me ;)
I have no idea why my phone keeps asking, maybe because it takes longer than normal?
At home I have no problems and I also use pfSense there.

@johnpoz:

Why are you seeing what looks like wan request on re2?
Sep 19 16:30:20 php-fpm[44284]: /rc.newwanip: rc.newwanip: Info: starting on re2.
Sep 19 16:30:20 php-fpm[44284]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.2.1) (interface: OPT1[opt1]) (real interface: re2).

I have no idea, hope you can tell me ;)

@johnpoz:

Why are you seeing hotplug events
Sep 19 16:29:32 php-fpm[10867]: /rc.linkup: Hotplug event detected for OPT1(opt1) but ignoring since interface is configured with static IP (192.168.2.1 )
Sep 19 16:29:32 check_reload_status: Syncing firewall
Sep 19 16:29:32 php-fpm[10867]: /rc.linkup: Hotplug event detected for OPT1(opt1) but ignoring since interface is configured with static IP (192.168.2.1 )
Sep 19 16:29:32 check_reload_status: rc.newwanip starting re2

Once again, I don't know

@johnpoz:

Is this a USB interface? So your router for a business setup is using usb devices? That is just asking for trouble? You can not setup a decent router/firewall with actual interfaces to support a business that could be had for 200 bucks? An actual nic could be had for as little as $20..

Nope, It's a normal tower case with a 80GB drive.

Let me know If you like me to post more logs.

Derelict

php-fpm[10867]: /rc.linkup: Hotplug event detected for OPT1(opt1) but ignoring since interface is configured with static IP (192.168.2.1 )

Could that be some power management powering off the NIC? (just a guess)

Once agian, I'm 100% sure that re2 is directly connected to the guest access point

I have seen layer 2 loops created by people who connect an AP to LAN then set it to connect in client mode (Airport Express "join a wireless network" mode) to another AP on the same LAN. Then the phone rings with them asking, "Are you guys having network problems??"

Mellowlynx

@Derelict:

php-fpm[10867]: /rc.linkup: Hotplug event detected for OPT1(opt1) but ignoring since interface is configured with static IP (192.168.2.1 )

Could that be some power management powering off the NIC? (just a guess)

Once agian, I'm 100% sure that re2 is directly connected to the guest access point

I have seen layer 2 loops created by people who connect an AP to LAN then set it to connect in client mode (Airport Express "join a wireless network" mode) to another AP on the same LAN. Then the phone rings with them asking, "Are you guys having network problems??"

Guess I can check the power management tomorrow morning.

Nope, this access point makes it's own open wifi network.

Upstairs WiFi is protected and has a different name.

divsys

Can you tell us what the NICs are in that box?

There's something weird going on with those "hotplug events".

Can you post the "System Message Buffer (Boot)" section from the (hidden) status.php page? That should give us a little better understanding of some of the hardware involved.

Another option is to try and swap the NIC card assignments to see if the problem migrates with a different NIC.

Mellowlynx

I think it's the PCI Network Adapter TF-3239DL, but not 100% sure.
I use the same nic's in more systems and don't have any problems.

System Message Buffer (Boot)


Copyright (c) 1992-2014 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.1-RELEASE-p15 #0 c5ab052(releng/10.1)-dirty: Sat Jul 25 20:20:58 CDT 2015
    root@pfs22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10 amd64
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
CPU: Intel(R) Core(TM)2 Duo CPU     E7300  @ 2.66GHz (2666.70-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x10676  Family = 0x6  Model = 0x17  Stepping = 6
  Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x8e39d <sse3,dtes64,mon,ds_cpl,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1>AMD Features=0x20100800 <syscall,nx,lm>AMD Features2=0x1 <lahf>TSC: P-state invariant, performance statistics
real memory  = 2147483648 (2048 MB)
avail memory = 2040926208 (1946 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <a_m_i_ oemapic="">FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0 <version 0.3="">irqs 0-23 on motherboard
ioapic1 <version 0.3="">irqs 24-47 on motherboard
iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff806345e0, 0) error 1
iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff80634690, 0) error 1
iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff80634740, 0) error 1
wlan: mac acl policy registered
ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff8060ce10, 0) error 1
ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff8060cec0, 0) error 1
ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff8060cf70, 0) error 1
random: <software, yarrow="">initialized
kbd1 at kbdmux0
cryptosoft0: <software crypto="">on motherboard
padlock0: No ACE support.
acpi0: <a_m_i_ oemrsdt="">on motherboard
acpi0: Power Button (fixed)
acpi0: reservation of fed02000, 1000 (3) failed
acpi0: reservation of fec00000, 1000 (3) failed
acpi0: reservation of fee00000, 1000 (3) failed
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 7ff00000 (3) failed
cpu0: <acpi cpu="">on acpi0
ACPI BIOS Warning (bug): Incorrect checksum in table [OEMB] - 0xF1, should be 0xE9 (20130823/tbprint-233)
cpu1: <acpi cpu="">on acpi0
hpet0: <high precision="" event="" timer="">iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
attimer0: <at timer="">port 0x40-0x43 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0: <at realtime="" clock="">port 0x70-0x71 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
pci0: <acpi pci="" bus="">on pcib0
agp0: <via 3364="" (p4m900)="" host="" to="" pci="" bridge="">on hostb0
agp0: aperture size is 128M
pcib1: <acpi pci-pci="" bridge="">at device 1.0 on pci0
pci1: <acpi pci="" bus="">on pcib1
pcib2: <acpi pci-pci="" bridge="">irq 27 at device 2.0 on pci0
pci2: <acpi pci="" bus="">on pcib2
vgapci0: <vga-compatible display="">port 0xd800-0xd8ff mem 0xd0000000-0xdfffffff,0xfbdc0000-0xfbddffff irq 24 at device 0.0 on pci2
vgapci0: Boot video device
hdac0: <ati rv810="" hda="" controller="">mem 0xfbdfc000-0xfbdfffff irq 25 at device 0.1 on pci2
pcib3: <acpi pci-pci="" bridge="">irq 31 at device 3.0 on pci0
pci3: <acpi pci="" bus="">on pcib3
atapci0: <via 8237="" sata300="" controller="">port 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f,0xc000-0xc0ff irq 21 at device 15.0 on pci0
ata2: <ata channel="">at channel 0 on atapci0
ata3: <ata channel="">at channel 1 on atapci0
atapci1: <via 8237="" udma133="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0
ata0: <ata channel="">at channel 0 on atapci1
ata1: <ata channel="">at channel 1 on atapci1
uhci0: <via 83c572="" usb="" controller="">port 0xb480-0xb49f irq 20 at device 16.0 on pci0
usbus0 on uhci0
uhci1: <via 83c572="" usb="" controller="">port 0xb800-0xb81f irq 22 at device 16.1 on pci0
usbus1 on uhci1
uhci2: <via 83c572="" usb="" controller="">port 0xb880-0xb89f irq 21 at device 16.2 on pci0
usbus2 on uhci2
uhci3: <via 83c572="" usb="" controller="">port 0xbc00-0xbc1f irq 23 at device 16.3 on pci0
usbus3 on uhci3
ehci0: <via vt6202="" usb="" 2.0="" controller="">mem 0xfbcffc00-0xfbcffcff irq 21 at device 16.4 on pci0
usbus4: EHCI version 1.0
usbus4 on ehci0
isab0: <pci-isa bridge="">at device 17.0 on pci0
isa0: <isa bus="">on isab0
vr0: <via 10="" vt6102="" rhine="" ii="" 100basetx="">port 0xb000-0xb0ff mem 0xfbcff800-0xfbcff8ff irq 23 at device 18.0 on pci0
vr0: Quirks: 0x0
vr0: Revision: 0x7c
miibus0: <mii bus="">on vr0
atphy0: <atheros 10="" 100="" f2="" phy="">PHY 1 on miibus0
atphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
vr0: Ethernet address: 00:1e:8c:ce:a0:69
pcib4: <acpi pci-pci="" bridge="">at device 19.1 on pci0
pci4: <acpi pci="" bus="">on pcib4
re0: <realtek 8169="" 8169s="" 8169sb(l)="" 8110s="" 8110sb(l)="" gigabit="" ethernet="">port 0xe800-0xe8ff mem 0xfbeffc00-0xfbeffcff irq 17 at device 4.0 on pci4
re0: Chip rev. 0x10000000
re0: MAC rev. 0x00000000
miibus1: <mii bus="">on re0
rgephy0: <rtl8169s 8211="" 8110s="" 1000base-t="" media="" interface="">PHY 1 on miibus1
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
re0: Ethernet address: 10:fe:ed:06:a2:37
re1: <realtek 8169="" 8169s="" 8169sb(l)="" 8110s="" 8110sb(l)="" gigabit="" ethernet="">port 0xe400-0xe4ff mem 0xfbeff800-0xfbeff8ff irq 18 at device 5.0 on pci4
re1: Chip rev. 0x10000000
re1: MAC rev. 0x00000000
miibus2: <mii bus="">on re1
rgephy1: <rtl8169s 8211="" 8110s="" 1000base-t="" media="" interface="">PHY 1 on miibus2
rgephy1:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
re1: Ethernet address: 10:fe:ed:06:b2:62
re2: <realtek 8169="" 8169s="" 8169sb(l)="" 8110s="" 8110sb(l)="" gigabit="" ethernet="">port 0xe000-0xe0ff mem 0xfbeff400-0xfbeff4ff irq 19 at device 6.0 on pci4
re2: Chip rev. 0x10000000
re2: MAC rev. 0x00000000
miibus3: <mii bus="">on re2
rgephy2: <rtl8169s 8211="" 8110s="" 1000base-t="" media="" interface="">PHY 1 on miibus3
rgephy2:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
re2: Ethernet address: 10:fe:ed:06:ad:da
acpi_button0: <sleep button="">on acpi0
acpi_button1: <power button="">on acpi0
pcib5: <acpi host-pci="" bridge="">on acpi0
pcib5: could not evaluate _ADR - AE_NOT_FOUND
pci128: <acpi pci="" bus="">on pcib5
hdac1: <via vt8251="" 8237a="" hda="" controller="">mem 0xfbffc000-0xfbffffff irq 17 at device 1.0 on pci128
fdc0: <floppy drive="" controller="" (fde)="">port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
sc0: <system console="">at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
atkbd0: <at keyboard="">irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
ppc0: cannot reserve I/O port range
est0: <enhanced speedstep="" frequency="" control="">on cpu0
p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
est1: <enhanced speedstep="" frequency="" control="">on cpu1
p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
hdacc0: <ati r6xx="" hda="" codec="">at cad 0 on hdac0
hdaa0: <ati r6xx="" audio="" function="" group="">at nid 1 on hdacc0
pcm0: <ati r6xx="" (hdmi)="">at nid 3 on hdaa0
hdacc1: <realtek alc662="" hda="" codec="">at cad 0 on hdac1
hdaa1: <realtek alc662="" audio="" function="" group="">at nid 1 on hdacc1
pcm1: <realtek alc662="" (rear="" analog)="">at nid 20 and 24,26 on hdaa1
pcm2: <realtek alc662="" (front="" analog)="">at nid 27 and 25 on hdaa1
pcm3: <realtek alc662="" (onboard="" digital)="">at nid 30 on hdaa1
random: unblocking device.
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 12Mbps Full Speed USB v1.0
usbus3: 12Mbps Full Speed USB v1.0
usbus4: 480Mbps High Speed USB v2.0
ugen0.1: <via>at usbus0
uhub0: <via 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
ugen1.1: <via>at usbus1
uhub1: <via 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
ugen3.1: <via>at usbus3
uhub2: <via 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus3
ugen2.1: <via>at usbus2
uhub3: <via 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2
ugen4.1: <via>at usbus4
uhub4: <via 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
uhub4: 8 ports with 8 removable, self powered
ugen1.2: <usb>at usbus1
ukbd0: <usb 0="" 2="" usb="" keykoard,="" class="" 0,="" rev="" 1.10="" 1.10,="" addr="">on usbus1
kbd2 at ukbd0
uhid0: <usb 0="" 2="" usb="" keykoard,="" class="" 0,="" rev="" 1.10="" 1.10,="" addr="">on usbus1
ada0 at ata2 bus 0 scbus0 target 0 lun 0
ada0: <maxtor stm380215as="" 3.aad="">ATA-7 SATA 1.x device
ada0: Serial Number 9QZ3A1QT
ada0: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)
ada0: 76319MB (156301488 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4
SMP: AP CPU #1 Launched!
Timecounter "TSC-low" frequency 1333347740 Hz quality 1000
Trying to mount root from ufs:/dev/ufsid/55e31e651aa14f5d [rw]...
WARNING: / was not properly dismounted
WARNING: /: mount pending error: blocks 0 files 8</maxtor></usb></usb></usb></via></via></via></via></via></via></via></via></via></via></realtek></realtek></realtek></realtek></realtek></ati></ati></ati></cpu></enhanced></cpu></enhanced></at></keyboard></generic></system></floppy></via></acpi></acpi></power></sleep></rtl8169s></mii></realtek></rtl8169s></mii></realtek></rtl8169s></mii></realtek></acpi></acpi></atheros></mii></via></isa></pci-isa></via></via></via></via></via></ata></ata></via></ata></ata></via></acpi></acpi></ati></vga-compatible></acpi></acpi></acpi></acpi></via></acpi></acpi></at></at></high></acpi></acpi></a_m_i_></software></software,></version></version></a_m_i_></lahf></syscall,nx,lm></sse3,dtes64,mon,ds_cpl,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>

Hope this can help.

Derelict

You should probably draw a diagram. I know it sounds like a pretty simple network but you have something fundamentally wrong.

If I were you I'd save the config for reference, reset, and start over. Basic config of WAN, LAN. And when something doesn't work, don't look for the solution in pfSense and get all clicky clicky. Look at the logs and figure out what you have screwed up elsewhere. Ask here if you don't know. Then move to OPT1, same thing.

Mellowlynx

@Derelict:

If I were you I'd save the config for reference, reset, and start over. Basic config of WAN, LAN. And when something doesn't work, don't look for the solution in pfSense and get all clicky clicky. Look at the logs and figure out what you have screwed up elsewhere. Ask here if you don't know. Then move to OPT1, same thing.

That is my next step, but I hope this can be fixed, so we know what went wrong.

divsys

We got a new case with motherboard, hard drive, etc
After installation I restored the config and edited some IP settings (switched from 4 to 3 nic's, we had a conflict with the internal network port so I disabled it)

From the hardware list. it looks like you may have an internal WiFi card, is that correct?

What was the "conflict with the internal network port"?

I also agree with Derelict, a save then reset from scratch and work one step at a time in rebuilding could save a bunch of hassles in the long run.

Derelict

@rcktboy:

@Derelict:

If I were you I'd save the config for reference, reset, and start over. Basic config of WAN, LAN. And when something doesn't work, don't look for the solution in pfSense and get all clicky clicky. Look at the logs and figure out what you have screwed up elsewhere. Ask here if you don't know. Then move to OPT1, same thing.

That is my next step, but I hope this can be fixed, so we know what went wrong.

You can always diff the two configs later.

Mellowlynx

@divsys:

We got a new case with motherboard, hard drive, etc
After installation I restored the config and edited some IP settings (switched from 4 to 3 nic's, we had a conflict with the internal network port so I disabled it)

From the hardware list. it looks like you may have an internal WiFi card, is that correct?

What was the "conflict with the internal network port"?

I also agree with Derelict, a save then reset from scratch and work one step at a time in rebuilding could save a bunch of hassles in the long run.

Not that I know off, only onboard lan.

It was a IRQ conflict (can't remember what it sad, sorry) and disabled the onboard lan.

On Monday they are closed all day, so until than I'm open for thinks to try.
Else Monday I will reset it and start over.

Thanks for your replays Derelict and divsys.

@Derelict:

You can always diff the two configs later.

True, but if it works the pressure is gone and so has the time to look at it ;)

We will see :D

divsys

Hmmmm, an IRQ conflict could lead to any number of "flakey" issues. Can you manually assign IRQ's for the NIC's or barring that, try moving the NICs to different slots to see if they get assigned differently?

Might be worth looking to see if there's a BIOS update available for the MB as well.

Was this a new bought board or something older that's being re-purposed?

If you have any other NIC cards available for testing (especially non-Realtek) that may be worthwhile as well.
I know the Realtek's are cheap and readily available, but there's often a reason they're cheap ….. :-X