Problems after update to ver 2.3.2
-
A couple days ago I upgraded my PFsense to ver 2.3.2. Since them I have been having some problems. My connection to my ISP is now dropping out a few times per day whereas PFSense had a stable connection for almost 3 mnths. Additionally there appears to be some problem with DNS. I am running unRAID on another box and whenever I type "tower/" in a browser address bar I receive a message that "tower's server DNS adddress could not be found." My mapped network drives "tower/documents" and so forth also do not work. I am able to connect to my unRAID box by typing the IP address. External domains are resolving fine however something appears to have broke internally.
Any ideas what the issue would be? Other than the update to 2.3.2 nothing has changed on my PFSense or unRAID boxes for months.
-
What did you upgrade from?
-
mm..I thought it was 2.3.1
Anyway I can see in the logs what upgrade was performed?
-
mm..I thought it was 2.3.1
Anyway I can see in the logs what upgrade was performed?
Problem solved. It seems PFSense doesn't like my main PC having a static IP. Every time I set one NAT doesn't seem to work. Set it to auto provide and all works fine. Bit of a pain in the arse for my printer but atleast I can access networked resources.
-
Then you are doing something wrong. Works fine.
Never seen anything like what you are describing on any installation. This one here is a mix of DHCP pool, DHCP Static mappings, and static assignments outside the pool.
NAT does not care how an address is assigned. Maybe using statics you're making a duplicate? System log should have some sort of entry in that case.
