@mxx:

It would be great to know/be notified when this book updated for v2 is/will be available. I'll definitely buy it too.

Before we can do too much the GUI options have to be finalized for v2. Things are still changing quite a bit so it's difficult to write instructions yet.

There are a couple chapters which are just about done, but it's a small percentage of the book overall.

Without giving any information about your setup (No, saying that you have 3 interfaces is NOT giving information) noone will be able to help you.

Start with the basic things like:
How is your network set up (diagram, inclusive the used IPs),
what firewallrules you have where (screenshots of the rules),
NAT-rules (screenshots of them),
how you test (where is the testclient,
to what do you connect),
what you expect,
and what actually happens.

Thanks guys, I feel better. I am by no means fluent in networking but, I have come across some pretty funky situations with Vodafone Portugal.

Thanks

…which is why it's not supposed to have a compiler... :-)

Not sure how the gcc binary ended up in the release image, it really shouldn't be there.

Yes, pfsense WAN would be *.99.6 and pfsense lan needs to be on a different subnet, something like 10.21.1.0

@brcisna

The two boxes are on different networks, different public IPs but same ISP. I did notice the spike when logging in to view some stats and check the logs. The network didn't appear to slow down, but our pipe to these boxes is really pretty small. But I do not think that any throughput suffered. A reboot cured the problem for now so if our ISP was doing 'something' it cured our little anomaly.

@woeper:

Who will help me on this ?
I have no idea how the exact syntax is to be able to allow this to work ….
I modified /etc/rc.bootup ...

Try this:

echo "Initializing..."; echo "Reset LED panel..."; exec("/bin/lprled -r"); echo "Set unarmed mode and current boot slice on LED panel."; if (`mount | grep /dev/ufs/pfsense | cut -d' ' -f1` == "/dev/ufs/pfsense0") exec("/bin/lprled -b 0 -w 0x9"); else exec("/bin/lprled -b 0 -w 0x5");

Squid can be used in that manner, see the Squid documentation examples.

Both are effective solutions.  Try both and see which suits your needs better, both in terms of capability and ease of use.

You can solve that with a single IP and either the HAProxy package (to direct connections to the appropriate physical server) or one web server and virtual hosts (vhosts).

Thanks to all who provided ideas on a resolve for the BB email problem.
I wound up deleting all port forwards,and recreated tcp 25,110,143 along with 80/VIP for imap and BB works fine now.
Also used the tcpdump  command provided by Eugene to see interaction between pfSense box and BB servers as well.
Hope some day I become important as well.

Thanks,
Barry

@CurlyBrackets:

Alright, everything is working now.

Just for the record, what did you change to make it work?

arp entries generally disappear after a timeout. Hence you need to do the ping first THEN fairly promptly issue the command to display the arp entries.

There appears something wrong here. The original complaint was that WLAN wasn't working. You should be pinging the pfSense WLAN interface from a system on the WLAN not on the LAN.

The data suggests your PC is connected to the LAN. In that case the ping to pfSense comes in on the LAN interface and is responded to "internally" and hence the counters for the WLAN interface don't move since there were no packets received on the interface and no packets transmitted on the interface. I have assumed you were reporting with your PC connected to WLAN.

Please provide output from pfSense shell command ifconfig -a so we can check your interfaces are in the correct state.

I finally found the problem  ;D

Certainly, the problem has nothing to do with the pfSense package repository.

The problem was that I configured the Outbound NAT with a Public IP address that my ISP blocked erroneously in pass years.

When I detected the error I configured an Outbound NAT with a proven Public IP address and the connection doesn't presented any problem.

@wallabybob:

Thanks for the output command, it help me very very much(I didn't know that the package repository is in www.pfsense.com:80).

Connect the access point to a third interface (OPT1) on your pfSense host and configure the firewall rules, or the captive portal, to suit your needs.

Lol ok that simple thank you and sorry for the stupid question then hehe  8) have a nice day.