Ok, thanks

Go to Diagnostics -> Backup/Restore and download your config.

Next time please search the forum.

Thank you efonne, I've end up removing the sixth nic from my pfsense box, and when I did that, I broke pfsense completely. Couldn't do anything like get to shell locally or ssh into the box, something about 214 xml, even tho dhcpd was still working. Had to do a wipe and reload, I had configuration backup just before I started messing with it. I'll setup another pfsense box try your suggestion if it works, I'll implement it into my primary. If it doesn't work I'll get a managed switch.

Thanks kindly for your answers. You're right, it seems that the fault lies in the hotel's internet server, not something he did to my computer or connection settings. So that's a relief.

Strangely, yesterday when I tried what you suggested (adding the absolute path of wol to the command), it worked, and I set the cron job to 4PM (16.00) everyday.  Today, at 3.55PM, I was randomly chatting on my laptop and suddenly remembered that normally, my server should wake up at 4PM.. it didnt….  I wonder why!?

I tried to manually launch the script via the pfsense web config (command) but it did not work.  I noticed everytime I launch the script, my router's light would flash all at one.  I imagine this means that the pfsense machine is effectively broadcasting a wol command to the network.  However, on my laptop, I successfully woke up the server using "wol 192.68.0.101"... nothing more.

Is there an incompatibility between freebs and linux (slackware)?

Additionally, if you really wanted to, you could create NAT rules such that all requests from the LAN to the DNS port (53) would be redirected to the DNS server of your choice (just one though), regardless of what server the client was trying to use. This would allow invalid configs to work but still only go to the allowed server. A similar setup (not specific to DNS but should work) is described in the pfSense book when discussing NAT.

It's been a while and I'm not sure if they still do it, but the other thing I've seen from OpenDNS is that they've (transparent) proxied Google in the past, to resolve a specific issue they were having. I discovered this when I was using it and Google wouldn't load for anyone (a proxy issue on their end) but everything else worked. I forget what the exact reason was (there was a technical reason that went along with the way they were doing "shortcuts" or something), and like I said I don't know if they still do this. I haven't had any issues with that or any other part of the service for a long time, and I use them pretty regularly.

Still dead, heres the error:
503 Service Unavailable
No server is available to handle this request.

Post them here or at a different site.

Are you trying to have each nic point to the other? because thats what you are doing and it wont work.
Heres what one would do for a basic setup
WAN:Card1: DHCP or Static
LAN: Card 2: 192.168.1.1/24

Sorry, that I have not reply to this for a while. If I am going to use the option 1 how do I physically connect both networks, I am guessing an ordinary patch cable would work by connecting it to pfsense OPT2 and the other end was connected to sonicwall available port. Is this how you connect to establish the connection?

Thanks.

The way "DNS override" works is exactly how it sounds.  If a LAN client makes a DNS request for a resource that you've configured a DNS override for, the DNS forwarder will reply with that IP address instead of the IP address the DNS server which has authority for that device would.  As an example, if you had a web server inside your DMZ and it was called dmz.webserver.cx, there would be a DNS server somewhere with that machine's public IP address.  If you were trying to access that device from inside your LAN, you would not want to try to connect to the public IP address of that device, that would be inefficient (and wouldn't work without using NAT reflection which is an ugly hack).  Instead, you'd configure a DNS override so that your DNS forwarder would hand back the private IP address of that device and the connection would be made directly from LAN -> DMZ instead of LAN -> WAN -> DMZ.  Glad you have it working, I hope this makes the rest clear.

@torontob:

In the meanwhile, if I use SSH tunneling to webGUI what if the SSH service of the router goes down? That would be still crazy as I will again lock myself out. Wouldn't I?

Yes but I've seen about every problem there is to see, and never seen that happen. There's a much higher probability that the web interface will become inaccessible or unresponsive (though virtually always only if you're messing with non-stable packages).

ah yes.  I forgot to uncheck the box that allows dhcp to override the dns servers.  So now I'm getting answers from 208.67.222.222!  Perfect!  Thank you!

No.  The web interface for pfSense exists only within pfSense.

Hi there,

Thanks for the quick response.

I apologize for not stating the hardware of the PFsense box. It does have two NICs. One from the motherboard and the other is a Intel GT NIC.

So from what you have just said. I can simply leave it up to the VMed PFsense to do the DHCP and so forth.

Thanks!

Hey all. I'm gonna revive this thread here.

I, too, am seeing alot of

in my 'System Logs'. I have a PS3 and it seems that after I'm done playing online with it, my PC's on the LAN seem to time out briefly [roughly 60 secs.] after sending requests for web pages. A Google search lead me to this page – http://redmine.pfsense.org/issues/show/122. So I take it I'm stuck with this for now until 2.0. Unless anyone has any ideas on a manual patch/fix?