Arp: 192.168.1.xxx moved from 38:xx:xx:xx:1c:c4 to 00:xx:xx:xx:3e:7c question..



  • ok fellows and ladies…i have a problem with wireless devices. ...

    the setup...
    2.0-RC3 (i386) - built on Tue Aug 2 19:07:41 EDT 2011
    traffic shaper not installed, no failover (yet), and i only have two rules setup (one for bogon networks, and another NAT rule for an internal webserver) ....i am currently stress testing my hardware to make sure this can be part of my future design. palo alto firewalls are so much overkill its not even funny.
    sk0 is my LAN adapter
    dhcp is NOT handled by pfsense ...it is handed off to an internal windows domain controller(s)

    the following happens in the system log when i connect with my android (sprint EVO 4g with stock firmware 2.3.3), and another android with stock firmware 2.3. it does not matter if i connect to a different access point, and i have tried three different ones.
    this does NOT happen to regular devices like my laptops (i have MANY connect without a problem)...

    system log entries below (mac addresses xx'd out for security reasons, but you get the picture.)

    Aug 3 09:16:49 kernel: arp: 192.168.1.55 moved from 38:xx:xx:xx:1c:c4 to 00:xx:xx:xx:3e:7c on sk0
    Aug 3 09:15:22 kernel: arp: 192.168.1.55 moved from 00:xx:xx:xx:3e:7c to 38:xx:xx:xx:1c:c4 on sk0
    Aug 3 09:14:32 kernel: arp: 192.168.1.55 moved from 38:xx:xx:xx:1c:c4 to 00:xx:xx:xx:3e:7c on sk0
    Aug 3 09:13:32 kernel: arp: 192.168.1.55 moved from 00:xx:xx:xx:3e:7c to 38:xx:xx:xx:1c:c4 on sk0
    Aug 3 09:13:22 kernel: arp: 192.168.1.55 moved from 38:xx:xx:xx:1c:c4 to 00:xx:xx:xx:3e:7c on sk0
    Aug 3 09:12:13 kernel: arp: 192.168.1.55 moved from 00:xx:xx:xx:3e:7c to 38:xx:xx:xx:1c:c4 on sk0
    Aug 3 09:11:43 kernel: arp: 192.168.1.55 moved from 38:xx:xx:xx:1c:c4 to 00:xx:xx:xx:3e:7c on sk0
    Aug 3 09:11:37 kernel: arp: 192.168.1.55 moved from 00:xx:xx:xx:3e:7c to 38:xx:xx:xx:1c:c4 on sk0

    as soon as the move happens ..the device still says it is connected wireless, but it looses connectivity to the outside world. when i try to reconnect it...everything works fine until the move to the different MAC address. this didnt happen on older RC3 builds.

    this did not start happening until i updated to the latest couple builds (i would say the last four or five?). i have also notice pfTOP showing (null) values where it used to show the IP addresses connected, but thats a different topic.

    could anyone give me some insight into what might be causing this? i am loving pfsense, and the nightly builds have been surprisingly stable. that says a LOT aboot a project like this.

    thanks in advance  :-\





  • Not sure if this is related, but if you have one of Apple's wireless base stations and a recent mac, this happens a lot.
    In that case, it is a side effect of a technology that Apple uses called sleep proxy.



  • @iFloris:

    Not sure if this is related, but if you have one of Apple's wireless base stations and a recent mac, this happens a lot.
    In that case, it is a side effect of a technology that Apple uses called sleep proxy.

    thanks for the info, but i have zero apple tech in my network.



  • fixed. it was a stale dhcp lease that i overlooked. …guess i need to release those lease a little bit faster  :D

    thank you for the help.

    i love this product more and more each day. i have a couple VERY expensive palo alto's sitting there collecting dust since i switched the pfSense. ...too bad i couldnt find a single one on ebay. the same goes with KEMP load balancers (which happen to be freaking awesome for exchange 2k10, sharepoint, and some other products) ....fairly cheap for load balancers too.. 15k for largers ones and 5k for smallers ones.

    thanks again.


Locked