Talked to the ISP and they've had a look and reset the password and I'm now getting the static IP. I've changed the password again since and the IP's sticking so seems to be sorted.

well I finally figured the problem out. Wasn't a bad nic. I could ping google from wan, lan and wlan, but could not access with computers on each *lan. so, I reset my settings from scratch and started over, works great now the internal routing mechanism stopped working right. Never sure what exactly was wrong, but somehow pfsense internally f'd up enough to partially route intermittently.

Couldn't get bridge mode working : / I don't know, pfsense never got an IP, put it in PPPOE on the interface, put correct username and pass, but could never get an IP… oh well, stupid DSl being on 192.168.1.254 and not awesome like cable and being 192.168.100.1 lol

That's typical of switching a time zone and then not rebooting/restarting a process. Processes only pick up a new time zone when (re)started.

Guess I can narrow down my problem. It seem's to be a DNS problem and I'm able to browse site's like: www.google.de, www.youtube.de etc. Since my SDSL need's a static IP and I'm not receiving any DNS IP from my provider: 1. I've set up manually two DNS IP addresses - 8.8.8.8 and 217.237.151.115 in the "General setup" and assigned them to the WAN interface 2. Unchecked the option "Allow DNS server to be overridden by DHCP/PPP" 3. Enabled the DNS forwarder because of the note: "The DNS forwarder will use the DNS servers entered in System: General setup or those obtained via DHCP and …" I was able to use my MacBook for pinging my WAN interface, my WAN gateway and 8.8.8.8. But it was not possible to browse like www.google.de. 1. Then i added the DNS IP to the Service: DHCP server under DNS servers: 8.8.8.8 and tried again. It worked... 2. I've deleted the assigned DNS IP's on the "General setup" and it worked either Now the question: Did and do I understand the option of the "General setup" with the entering of the DNS IP's and assigning them to the WAN interface in a wrong way? I have a second WAN connection from T-Online and want to use it with the LoadBalance but with the DNS IP's given by this provider and not by the Google DNS IP's. Using the option of entering a static DNS IP would mean, my DHCP will push allways the DNS 8.8.8.8, wouldn't it? Cheers    

Steve one more time thank you for info and searched links. The great news is that seems I do not need to write into config every website domain together with IP address of the server. HAproxy let write just IP address of servers and then requets searching the necessary server for website by his own, if I understood correctly? If anyone knows more way to achieve this goals, please let me know.

OK, Thanks Jimp. I was make maintenance to my PC. and reinstall pfsense. now it look ok.

I'm working on it! I've found the problem was my server got hacked, and it's fixed now. What can I do on the pfsense side to help in the future?

@PANiCnz: At the moment I'm solving the issue by restarting pfSense, is their an easier option to force pfSense to aquire a new WAN IP? Thanks I also have the same question. how to get rid of blemishes garlic breath tips plr private label rights

Yes, make sure they are both disabled, and you may want to reboot for good measure. Though on a new snapshot it should be safe to have one or both enabled.

Its ok..Tqvrm.. ;D

Probably right.  Yesterday I discovered the Tivo could connect to its service but could not download Netflix videos.  I also discovered the Xbox 360 couoldn't connect to Live because of an invalid MTU.  I did everything the forums told me indluding turning the Upnp but no dice. Wife got ticked.  Had to throw slap the Smoothwall drive back in.  I may give this one a break and check out Monowall or Untangle.  Thanks again though!

If there is no connection state when the first packet is seen, it logs the first packet. It won't log again unless the state expires and a new state is created.

@jimp: Is this still happening on current snapshots? If so, what theme are you using? Current snapshot solved my problem. Graphs are now working again. ;D

There is an open ticket for the PPPoE server in 2.0 right now because it's not 100% working. The firewall rules aren't properly added yet. It's a known issue. (And there are other threads already open for it as well)

Anything in the firewall log when this happens? You could be getting some asymmetric routing going on.

Thanks for answer. I set up additionaly outbond NAT on link 192.168.50.0/24: on router 1: outbound nat from 192.168.1.0/24 to any (via interface assigned to 192.168.50.0/24 network - OPT) NAT'ed to 192.168.50.1 on router 2: outbound nat from 192.168.1.0/24 to any (via interface assigned to 192.168.50.0/24 network - OPT) NAT'ed to 192.168.50.2 And it doesn't work with NAT 1:1… I can connect to 90.90.90.200:25 from LAN2 only if additionaly to NAT 1:1 i configure port forward (Firewall->NAT->port forward) to 90.90.90.200:25 (using Virutal IP) Any idea how to make NAT 1:1 work in this scenario?

There's a lot of useful information in the documentation wiki including: http://doc.pfsense.org/index.php/InstallationGuide That's pretty basic but there are guides for most other stuff. Steve

A lot of this stuff is beyond my experience. I'm aware it can be done but I've never tried it. I assume you are using this on your home network and not some public hotspot!  :P I'd be interested in your experiences if only to get some idea of how straight forward it is. Here's some info on the packet capture facilities in pfSense. Steve

1.2.3 And it is a VIA C7 mini ITX box http://www.newegg.com/Product/Product.aspx?Item=N82E16813153062