I will do a "cold swap" means Take down the present Firewall and keep it intact Test the new one and if everything works well stay on the new one I have a quad Port Intel Card in the present Firewall and will move that one to the new box Thank for help

There is no index.html there, so lighty tosses a 404. It is not meant to be used by a browser.

Thanks,  Tried the second controller and it worked perfectly. Much Appreciated! ;D

I can get everything to work if I leave one IP associated with the parent interface instead of having all assigned to a VLAN.  This also means I then need to have the switch configured with the native vlan tied to that. This is what's working: pfsense vr0 = vlan20 (LAN) vr0_vlan10 = vlan10 (internet) vr0_vlan30 = vlan30 (VoIP) [typo in previous post had me showing this as 20 also] vr0_vlan40 = vlan40 (DMZ) switch interface FastEthernet0/23 description Neoware CA-10 Trunk switchport trunk encapsulation dot1q switchport trunk native vlan 10 switchport mode trunk spanning-tree portfast end Not sure why I need an untagged IP on this and it's obviously the "wrong" way to configure it but the only way I can get it to work on this nic driver.  I haven't found anything searching google about this driver behaving this way, but I did run across the re0 drivers having this problem. The only issue now that I see is poor network performance with max throughput at about 4-5Mbps which I haven't determined if that's due to the nic/driver or cpu. I'm glad it's working but would be happier if I could get tagging working as it should with no IP on the parent interface and all IP's on vlan interfaces only. Thanks for the pointers as it helped get me going in the right direction.  If you have in further insights I would appreciate those as well.

@cmb: Yeah you will have to re-flash in that instance. Upgrade overwrites the partition on the card, not the entire card, so you have to re-flash to rewrite the partitions to be the larger size. Thank you cmb!

I prefer to install packages and then restore config.

ok thanks for the fast reply

I would suggest you also set your self up a free opendns account and turn on most of the options. Two reasons, it will help you control your users in the form of stopping them accessing high bandwidth source sand consuming your bandwidth -although I don't think you're going to have bandwidth issues per say. The other thing it will help with is that you have a responsibility to prevent the cconnection being used for illegal use. Sounds very big brother, but sadly the digital economy bill does apply to what you are doing. You can't possibly know what is installed on each computer on your network, what they are going to download. Etc, We use pfsense in two locations, one is holiday apartments and the other is a leisure facility, you'll be surprised what appears on the blocked domains list report generated by opendns. And these are family environments…...oooooo Good luck with your project.

Ok thank you. It works  :)

For sure … I hope to get back to 64bit when 2.1 comes around. I am hoping that FreeBSD 9 improves on 64bit stability. ( I think it will as part of that time progression thing).

Hi conehead, On your screen the size reported is close than 4Go. I had the same question when I wrote a 4Go image, because physdiskwrite reported less byte than total byte written… In fact writen byte equal exactly the file size of image (see attached file). Did you check your real file size ? [image: physdiskwrite_size.png] [image: physdiskwrite_size.png_thumb]

Thank you for your aswer. In fact, when the modem is not plugged the Wan is "disabled". I have changed the computers and the wan does to be linked with the pppoe0 interface. The public IP appears on the console and the wan is up and enabled. I was afraid for nothing  ;)

@stephenw10: Looks like you've had some fun!  ;D Where are you using the 500GB drive? What are you going to be running Samba on? Steve Samba and Transmission are actually running on the pfSense router itself, thus freeing me from needing my computer on all the time. For those long downloads with few seeders, I can now divert that task to the router instead. I'll explain in more detail how to get multiple static IPs combined with a dynamic IP on Cox HSI in my next post, after that I'll probably delve into the Samba + Transmission setup, the highlights of the setup. The 500GB is connected to the router ideally, I haven't set that up just yet, but if that becomes another adventure, I'll document that too.

thanks for the ideas have to give g4u a try and the check out rc.fullbackup thanks all

@dsagud: What can I do ? Follow the suggestion and verify you have correctly configured the pfSense interfaces (WAN interface particularly), verify you have correctly configured DNS for pfSense and verify that your connection to the Internet is working (that it is up and you get a response when you ping your ISP's router). It would also be helpful to provide some information about your configuration and the results of the troubleshooting you have done so far.

Thanks guys for the input … I will test the firewall again without the Wireless device and hope it will not panic anymore or whatever happened. The CPU might be te culprit too, it doesn't have a fan since it's an embedded one ... But it's in a cool enough environment that it shouldn't be a problem, guess I'll be monitoring that one as well. The strange thing is that it happened only the next day, while before it worked without a problem, but that's the name of the game isn't it. Thanks again.

@argie01: Hi, and thank you for the link. I fixed the problem. The cause was I setup aditional network interfaces on Vmware as "VMXNET 3", and PFS didn't detect them. When I changed it to "flexible" the interfaces were detected correctly. Where did you make this change? I'm asking because I'm setting up pfSense to run in a VMWare virtual enviroment as well.

Thanks for the quick reply and happy hollidays

Update: Today i've got an IP from VLAN1002 (public wifi) from the PFSense router : 10.102.0.100. Screenshot:http://kris.derocker.name/pfsense/merakivlans/pfsense-dhcpoffervlan1002.jpg But : no IP on the other SSID's and no internet activity…