Windows detected network as new network after 2.2.3?



  • After I did the upgrade from 2.2.2 -> 2.2.3, all wireless devices (through an AP on a switch) popped up the new network window as if it was the first time being plugged into the network.

    I haven't had a chance to look at the AP to see if something coincidentally got changed there (which is unlikely) but was there anything that could have caused this on the Pfsense end?  It lines up perfectly with that upgrade.



  • 'new networks' generally popup if the windows-client detect a new mac-address being used for its gateway.



  • I know, that's what's so strange.

    I checked the AP, nobody other than me logging in to check has logged in for months, so it wasn't that.

    And I wasn't using a custom MAC for that interface on PFSense, so I don't know what would've changed to trigger that.


  • Banned

    Seeing the same across desktops and servers.



  • A packet capture might show up the differences. Think of windows as Big Brother.



  • @firewalluser:

    A packet capture might show up the differences. Think of windows as Big Brother.

    I'd need to have a comparison from before for that to be any help, no?



  • @Trel:

    @firewalluser:

    A packet capture might show up the differences. Think of windows as Big Brother.

    I'd need to have a comparison from before for that to be any help, no?

    Correct, windows is usually pretty quick at spotting network changes so might not take long.



  • It's too late at this point.
    It already happened to all computers.

    I'm trying to figure out what happened after the fact.



  • @Trel:

    It's too late at this point.
    It already happened to all computers.

    I'm trying to figure out what happened after the fact.

    So you have no rollback contingency in case something that affected your setup wasnt caught before ESF rolled out an update?



  • @firewalluser:

    @Trel:

    It's too late at this point.
    It already happened to all computers.

    I'm trying to figure out what happened after the fact.

    So you have no rollback contingency in case something that affected your setup wasnt caught before ESF rolled out an update?

    I have a backup of my old config and a 2.2.2 iso.

    This is a home network.  I am allowed to hit people who complain about downtime.


  • Banned

    Thing is regariding rollback contingency.

    If nothing has changed and MAC address is the same on the firewall, then you will have another network when rolling back.

    If nothing is compromised and everything works, then we need to locate the cause and report it.



  • I'm aware of that.  It's just not something I do on a home network.
    I'll verify the settings when I'm home again, but that's the extent of what I can do now.



  • @Trel:

    This is a home network.  I am allowed to hit people who complain about downtime.

    Good answer, put another way, how quickly could you get back up and running?

    I can do pfsense iso/mem stick plus backup in under 10mins depending on what I change in the XML backup before restoring it.

    One thing, if you decide to do this, make sure the AP & windows machines are not connected until you the packet capture already running.



  • I couldn't do that per say.

    What I did do was compare a new config backup to the one I did prior to the install.

    I don't see anything that could have caused it.  The only change other than the packages being in a different order and a few new preferences existing (such as hiding deprecated ones, etc) that should have no bearing, is an internal nat rule which again shouldn't cause this.

    Short of rolling back to 2.2.2 and testing with actual monitoring happening, is there anything else I could look at?



  • Maybe this holds your answer?
    https://forum.pfsense.org/index.php?topic=5231.msg41202#msg41202

    In particular server-duid "xyz";


  • Banned

    I dont run DHCP on any of the networks…



  • I run DHCP, but it's static entries.


Log in to reply