Normally in those cases the ISP will route that block to whatever IP you receive on WAN. So you can use them internally on an interface or via 'other' type VIPs.

FYi. I re-assigned interfaces creating LAN addresses in made up 10.1.1.x range , restarted and got the webconfigurator to work. the rest would be reading and learning pfsense . thanks to NOYB who answered and to all who may have read.

Its a tweaked version of freebsd, so yeah those commands are pfsense commands

Recharged the UPS and now with halt (-h) command everything works as expected :) I`m posting this just in case someone should have same problem as me …

As noted here; though clearly the other way round for you. NFC what's up with the logging timezones.

@stan-qaz: Would it be possible to plug a GPS or other clock into the pfSense box to serve as a stable time source? Yes, of course, serial NMEA GPS is supported.

You should have a look on "Captive Portal" on pfsense. When a user connects to the ethernet and wants to open a webpage like google he will be redirected to the CaptivePortal page. You can designe this page as you like. User can login with username/password oder with a voucher or you do something with freeradius (additional pfsense package) + mysql with a self registration page. Perhaps have a look at this documentation: http://doc.pfsense.org/index.php/FreeRADIUS_2.x_package#CaptivePortal_Self-Registration:FreeRADIUS.2B_MySQL

172.16.8.3 is in private IP address space. I guess that IP address was a DNS server for some/all of the internal VPN-based network. The domain that is pointed to that is obscured in the screenshot, but I guess it is a private domain within the internal network? Without the override, the DNS  requests will be forwarded up to the DNS server/s that pfSense is using by default. Maybe those are somehow able to resolve the names. Without more detail of your internal network and where the internal DNS server/s are, it is speculation from me. If 172.16.8.3 is/was a gateway, presumably that gateway also had a DNS server or forwarder that could help resolve names. Maybe that functionality is no longer enabled on the gateway. Again, a bit of speculation from me.

I don't think there's anyway of doing that using the default options but you could use a cron job. Install the cron package (to make it easier) and write some very simple scripts that bing up your connection or kill it. Run them at appropriate times. Steve

Finally got a chance to sit down and take a deeper look at this issue… Turns out that it's squid3 package (Proxy Server) that is blocking GTV's youtube from functioning properly. After I disabled squid proxy everything started to work.

Or do something really scary… http://code.google.com/p/win-sshfs/ :-X

Yep.

changing using pfctl at the command line would be very, very temporary. There isn't a simple way to do what you want from the CLI. You could use viconfig to hand-edit the config to make the change and then manually trigger a filter reload, but that's not exactly simple. Best to use the GUI if you can. If you're looking to automate the process, it would take quite a bit of custom coding to make a command line utility to edit an existing rule in that way easily.

Give pfsense a try.  It will probably do most of the things you are doing on several boxes with just one box.

Use "iftop" instead, it will show you want you want (and probably more) in a nice curses GUI

Hi @sgo The Ip 10.64.64.0 or 10.64.64.1 is kinda a bridge. To monitor the gateway (and solve the trafic problem) i put in  "System->Routing->(e - edit 3g gateway ) -> Monitor IP (ex. 8.8.4.4 ). The gateway use the DNS google ip (you can use another pingable IP) to monitor the stat of the interface. I prefere have my main(ISP) getaway but, better this than nothing. With the monitor with green color pfsense chose the interface to pass traffic. Cya

Apinger, used for monitoring, doesn't currently support anything other than pings. To do this I guess you would need to replace apinger with something more flexible. Any suggestions? Steve