@bgbearcatfan:

Sorry, i don't understand the wording of your question.

OK sorry  :'(
"why one should all the firewall rules" i forgat the word delete. so it should say "why one should delete all the firewall rules". I thought that was not nessesary. And indeed it was'nt. I didn't have the forwarding rule for the passive ports  :-. Everything works fine now.
Thanks for the help.
Rgds,
Hellsblade

I had the same issue while trying to receive incoming calls from my sip provider to my asterisk server which is nat'ed behind a pfsense box.

What resolved my issue was setting up my asterisk server to refresh it's connection to my sip provider every 10 sec in sip_nat.conf. "externrefresh=10" thus avoiding the expiration of the udp session which occurs every 30 to 60 seconds.

I think the same thing can be done with an ATA or VoIP telephone, by setting "Nat keep alive = yes" and "Use DNS SRV = yes"

Hope i was helpful.

@cmb:

http://wiki.pfsense.com/wikka.php?wakka=StaticPort

perfect post that solved my problems.

Thanks for all the info guys.

@sullrich:

I have some serious reservations about folks running 1.0.1.  1.2 even in beta stage has thousands of fixes not included in 1.0.1.

Right, but remember that it is still beta and some folks aren't keen on using that. The latest stable release for now is 1.0.1 so I would guess lots of folks (still) using it. However, this will change with the release of 1.2 stable.

The beginning of this thread showed that it would be helpful to have something like a 'big picture' of pfSense.
What, where and in which order would be great! Recently you suggested a nice Web drawing tool…
What do you think?

Chris

Really?
Thanks, I'm going to upgrade!

advanced outbound nat?

Search the forum for static port.

Search the forum for "static-port".

Assuming you put a NIC in the existing firewall and address it 10.10.1.254/21, connect it the new network. You would then go to system, static routes on the second box and add a route to 192.168.0.0/21 gateway 10.10.1.254. Then make sure firewall rules on both sides allow the traffic.

I'm interested in this too, I got two IP address, but the only way I can grab them is to use DHCP to grab them, so it would be great if there was a solution to this, at the moment I'm thinking of having two "Wan" port on the machine one to grab the first IP, then second one to grab the second IP, then do NAT on it.

@ppolymorphe:

Hello,
My LAN subnet is 192.168.1.0/24. for maintenance purpose I have to plug some modems on the 10.0.0.0/8 subnet.
so I created a VLAN (OPT1) with LAN as parent and subnet 10.0.0.0/8 .
What do I need to do to make LAN and OPT1 comunicate ?

Thanks in advance
Patrice

All I did was copy the same rule by default for LAN to the OPT1 interface.  I thought there was an additional setting similar to say a Cisco PIX config but that was not the case.

Joe

Thx a lot once again Perry, you made my day  ;D

The real difficult thing was to add the firewall rule for the whole pool :)

@GruensFroeschli:

maybe with the captiv portal?

Yes, captive portal is nice solution. But which? It is very important that have setting:

how often is user redirected (every 2-3 minutes, or every 10th page, …)

Do you know any?

Thanx for response.

Fixed, Thanks.

I have upgraded to the latest snapshot and so far so good. Been up for 3 days or so no problems.

Use Outbound NAT.

Yeah, you wouldn't need the port-forward if you didn't want to make any services on the box available via the outside. The gateway and outbound public would be handled via the firewall/NAT rules.