I have the same problem with pfsense and Comcast. I have to reboot my modem, usually works. If not sometimes reassigning the WLAN/LANS works. Best of luck.

@0tt0:

@jigglywiggly:

So I am a pfsense noob obviously, and I have a question why is pfsense running port 80 over the web, I want my web server running on that port. Also I port forwarded other ports and they don't work, like they respond but they arn't doing their functions like SSH, RDP, VNC. I am totally lost.
Also openDNS doesn't seem to be working, it's set under the DNS, but it's not working… I am starting to dislike pfsense.

The most obvious choice of port for something to be reached by a web browser is port 80, the default port for http. Otherwise you'd have to append port number to the URL when browsing, so that's the most natural way to start with for a default installation. Otherwise other people would ask the opposite question instead..

Should you want to use another port for various reasons just change it. And you probably want https anyway.

Port forwarding is quite straight forward in pfSense I think. First go to "NAT" tab and enter the data and make sure it auto-adds a FW rule. Apply changes. Done. (Can't help thinking of Gordon Ramsey's way of saying it, writing that "recipe" LOL).
Maybe also reset states to be sure.

If you can't get that to work you may have chosen incorrect protocol or something, double check it.

I'm also running OpenDNS and it's working perfectly.
You should not be using "Allow DNS server list to be overridden by DHCP/PPP on WAN" obviously.

You probably want to stick to it and learn how to get it to work, pfSense is probably one of the most advanced open source firewall packages in existence. When a product is so flexible and has so many options and features there's always some risk of doing things incorrectly in the beginning.

Cheers,

Thanks for the advice, specifically about getting OpenDNS to work. I had the check box checked that said "Allow DNS server list to be overridden by DHCP/PPP on WAN" removing it worked nicely. Danke.

Ok I sort of understand. But this brings me to antoher quesiton why wont my forwarded ports work :P I'll create another thread to ask that.

I use the package Fit123 with it's DDNS, and cn99 should like this:
lynx -mime_header -auth=user : pass "http://www.3322.org/dyndns/update?system=dyndns&hostname=myhost.3322.org"

how can I  put them in Fit123's fields?

It should fit a string like this https://username:password@updates.opendns.com/nic/update?hostname=
AFAIK it's the normal way for those services.

How can I find more info about Fit123?

Based on http://forum.pfsense.org/index.php/topic,9729.msg55580.html#msg55580
Another way http://forum.pfsense.org/index.php/topic,15482.0.html

As those site you use doesn't seems to have a English pages I can't be of much help. but you can searching for ways to use curl or wget

Thanx for the info guys  ;)
I have installed the RC1 and got load balance working, but captive portal was not working.
The login page would not show.
If i enter http://pfsenseip:8000 i can see the login page and proceed from then on normally.
If i disable the captive portal everything works OK, but the captive portal is a must and i need it.
Besides this how can i apply this
http://cvstrac.pfsense.com/chngview?cn=26872
to a 1.2.3 installation?

REgards..  :)

A little more information is required.  At the very least why you have to disable the LAN.  What happens if you don't?

I can confirm that the procedure outlined by jimp worked well.

I am running 1.2.2… lost the admin password due to a twitchy finger... damn fingers...

Step 3: /sbin/mount -a -t ufs

@GruensFroeschli:

We already have filtering of OpenVPN in 1.2.3

I was experimenting with this a little today, and while it did work, there were plenty of quirks in getting it to do so… But it does work.

Agree. The explicit rule 'disable broadcast on WAN' should not affect DHCP IP renew process as server responds with unicast not broadcast packets.
Sorry for my previous comment, it does not make sence.

Hi,

I tried to make half bridge work on OPT1 (apparently Realtek 8139 recognised as rl1) with versions 1.2.1 and 1.2.3-RC1 using two different modems (Linksys AM200 and Zyxel P660R). I was not successful, even if everything worked perfectly with pfsense v1.2. Finally, I put one of the modems on router mode and pfsense in its DMZ and since then everything is working fine.

Cheers,