Thanks for that info. Although I have no plans of using the double NAT since I don't know what is double NAT or single NAT ???

As long as my system works, no problem.

Hi … I arranged whole setup ... All working good ... Finally everything is settled ... For the time being I am not too worried about the speedtest ... Well I really appreciate your help Steve and this forum ...!!!

Try reset state table it will go back to normal connection but after 3 to 4 days you'll experience it again. I dont know why but still the same issues with my box

jigp

Ok, awesome.  I'm going to set it up that way.

I host a few non ssl sites so I can share an ip.  For my ssl site, there is only one at the moment with a wildcard cert, shouldn't be a problem.  I'm more concerned for when I add ssl sites in the future, I'm sure it's easy enough though.

@mark2012:

I need to add this interface in order to bind it to specific IP address. Any help or advice on how to achieve this would be greatly appreciated.

I must be missing something: Why do you want to do this? Why not assign the specific IP address to one of the existing interfaces? Or assign the specific IP address as an additional IP address for one of the existing interfaces?

Hi !

Start reading https://github.com/bsdperimeter/pfsense/blob/master/etc/rc.php_ini_setup

Ok.  Thanks Jimp.

@jimp:

For that, see http://doc.pfsense.org/index.php/Why_can%27t_I_view_view_log_files_with_cat/grep/etc%3F_%28clog%29

And they never told me this won't be good for pfSense. My fault though. Arggggggggggg

So, why does pfSense recognize it? Also, I read that new FreeBSD 9.0 supports this chip. So, it won't be possible to upgrade pfSense to new kernel? If not, is it in the works for next 6 months?

Thanks

I decided to use a ping script to do this instead.

Are these full installs or nanobsd?

The crash dumps are only kept on full installs, nanobsd would just automatically reboot.

Without any other info it's hard to say, but you could be hitting this:
http://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards

Hmm, yes you are close. I have to say that I have only played with this a little and mostly under Ubuntu and that was a few years ago!
My own modem turned out to be supported by u3g on FreeBSD so I didn't need usb_modeswitch.

Does your modem have an SD card slot?

It looks like it's doing it's thing. From the log you see it has removed the virtual cd drive and you can see it receives the '1' response it's looking for.

From memory the creation of a new serial port does not generate any log entries which is why I initially thought my modem wasn't working.

Check the contents of /dev.
There are two ways in which serial ports are represented by FreeBSD and both are shown just to confuse you. Here is the output from my box before I connect my modem:

[2.0.1-RELEASE][root@pfsense.fire.box]/dev(2): ls ad0        ata        cuau0      devctl    klog      mem        ptmx      stdout    ttyu1.lock urandom ad0s1      bpf        cuau0.init devstat    kmem      nfslock    pts        ttyu0      ufs        usb ad0s1a    bpf0      cuau0.lock fd        led        null      random    ttyu0.init ufsid      usbctl ad0s2      console    cuau1      fido      md0        pci        speaker    ttyu0.lock ugen0.1    xpt0 ad0s2a    crypto    cuau1.init geom.ctl  md1        pf        stderr    ttyu1      ugen1.1    zero ad0s3      ctty      cuau1.lock io        mdctl      ppi0      stdin      ttyu1.init ugen2.1

And after:

[2.0.1-RELEASE][root@pfsense.fire.box]/dev(3): ls ad0          console      cuaU0.2.init devstat      mdctl        pts          ttyU0.1.init ttyu1.lock  xpt0 ad0s1        crypto      cuaU0.2.lock fd          mem          random      ttyU0.1.lock ufs          zero ad0s1a      ctty        cuau0        fido        nfslock      speaker      ttyU0.2      ufsid ad0s2        cuaU0.0      cuau0.init  geom.ctl    null        stderr      ttyU0.2.init ugen0.1 ad0s2a      cuaU0.0.init cuau0.lock  io          pass0        stdin        ttyU0.2.lock ugen1.1 ad0s3        cuaU0.0.lock cuau1        klog        pass1        stdout      ttyu0        ugen2.1 ata          cuaU0.1      cuau1.init  kmem        pci          ttyU0.0      ttyu0.init  ugen2.2 bpf          cuaU0.1.init cuau1.lock  led          pf          ttyU0.0.init ttyu0.lock  urandom bpf0        cuaU0.1.lock da0          md0          ppi0        ttyU0.0.lock ttyu1        usb cd0          cuaU0.2      devctl      md1          ptmx        ttyU0.1      ttyu1.init  usbctl

cua and tty devices are all serial ports. Those with a capital 'U' in the name are USB connected serial ports. You can see that my modem add three serial ports.

Steve

You can block ip, network ranges and hostnames with pfsense alias.

To block urls, you need a proxy server(squid)