Windows New Network Names
-
My pfsense box has been running for the last 2-3 weeks now and as a software dev Im really happy with the peace of mind and speed & performance it is giving me. Also networking is not my specialty as it is a means to an end for me so pardon my ignorance :)
Only problem is I am getting new network names all the time I.e Network 13,network 17
I have got my pfsense box up and running with an i350 x4NIC adapter with Bind configured for my .local domain with 192.168.0.0/24 ,192.168.1.0/24, 192.168.2.0/24 192.168.3.0/24 and a bridged cable modem
I dont know whether pfsense is not recycling the IP's (i.e assigning the same ip to mac as is pretty normal from my XP) or there is something else that pfsense is doing that Windows 10/7 is not liking.
This was happening when I was using UNBOUND as well so I dont think its specific with BIND.
I do think (95%) certain that the machines/servers that have static mappings are OK and I feel its just the RIGS that might be getting a new IP either on the renew or when i have to bounce the box and It may be giving them a new IP ?
If I am correct in that a new IP on restart of pfsense , is there some way to tell it to remember the mac/ip combos
Any advice would be greatly appreciated
-
I think but im not 100% sure its to do with the firewall doing packet scrubbing, I could be totally wrong.
It seemed to disapear for me when I switched off packet scrubbing via System -> Advanced -> Firewall & NAT -> Disable Firewall Scrub.
-
Do you maybe have your LAN setup as a bridge? If so, each time the firewall is rebooted, the bridge will receive a new random MAC address which will cause windows to think it's a new version of the network.
If that is the case, enter a MAC address to spoof on the bridge (even just the one it has now) and it should stop.
-
I'm running pfsense on a hyper-v server and I switch between different snapshots, so this happens quite often. I'm pretty sure that if you switch the pc from one router NIC to another, another network will be created, so it's probably the MAC address of the router NIC. If you switch back, it should recognize the profile and reuse it.
If you want to clean it up, use regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles. There will be a profile for every configuration (e.g., {30AE5914-D584-4667-9D30-FB004A39FFE2}). You can remove all of the unwanted profiles. You can also change the name back to Network, without the number.
-
Do you maybe have your LAN setup as a bridge? If so, each time the firewall is rebooted, the bridge will receive a new random MAC address which will cause windows to think it's a new version of the network.
If that is the case, enter a MAC address to spoof on the bridge (even just the one it has now) and it should stop.
Yes I have my Cable modem in bridge mode… That definitely sounds like the culprit :D
-
Do you maybe have your LAN setup as a bridge? If so, each time the firewall is rebooted, the bridge will receive a new random MAC address which will cause windows to think it's a new version of the network.
If that is the case, enter a MAC address to spoof on the bridge (even just the one it has now) and it should stop.
Ah I had bridging on for a while.
-
Cable modem would always be in "bridge" mode - did you mean a cable gateway? Either way what you had on the internet side of pfsense would have ZERO to do with what your clients saw on the lan side of pfsense. What Jimp meant is if you were running a bridge on the lan side between multiple interfaces of pfsense then this bridge if you were using that as your lan side gateway the mac would change on it.
-
Cable modem would always be in "bridge" mode - did you mean a cable gateway? Either way what you had on the internet side of pfsense would have ZERO to do with what your clients saw on the lan side of pfsense. What Jimp meant is if you were running a bridge on the lan side between multiple interfaces of pfsense then this bridge if you were using that as your lan side gateway the mac would change on it.
I had my LAN & OPT1 bridged, with my timecapsule connected to OPT1
-
for what reason? Opt interfaces on pfsense are not a switch ports, bridging them does not get you a switch. I you need more ports on same network/vlan then use a switch.
-
for what reason? Opt interfaces on pfsense are not a switch ports, bridging them does not get you a switch. I you need more ports on same network/vlan then use a switch.
I had my ethernet over power connected to the LAN port and the time-capsule connected to the OPT1 port, so when I rebooted the time-capsule I didn't loose the ethernet connections connected via the ethernet over power.
It's not connected that way now, LAN -> time-capsule.
