if they're statically addressed devices, this is easily done with a limiter via normal firewall rules.

Also, the package should be integrated with an auto-mount feature in order to be able to use external drives/pens attached via USB…

There is an automount script here http://forums.freebsd.org/showthread.php?t=29895 , is there anything easier to manage an automount feature?

Thanks,
Michele

I found using IPSEC worked perfectly >_< I'm on ICS as well. There's a well written guide as well that I'll have to find and post.

u can have a rule in floating tab as shown below and it will give priority to voip based on voip server ip

CropperCapture[1].jpg
CropperCapture[1].jpg_thumb

Depending on the other side support of etherip(GIF in pfSense) you can bridge GIF with the LAN and have that working!?

u need to use captive portal for RADIUS

Usually you put how much you are willing to put as a start for such work and after you get better replies.

Normally if you want supported packages the best is to go through portal.pfsense.org which gives you better quality and support on these things.

@al1x:

In this case a freeze attack would involve an attacker intercepting a firmware update and feeding back to the update process the same version of the firmware as existed on the router. If the firmware update was released to patch a significant security hole the system would simply reinstall the unpatched version of pfSense leaving the system still vulnerable to the security hole the update was intended to patch, very much impacting the integrity of the system.

Which would be noticed by anyone paying any kind of attention, reboot and you're still on the same version. Still has no impact on the integrity, it would only install an official update. Besides if it's so hackable, why would anyone bother just ensuring it stays that way? Own the box and be done with it. In that case you'd likely want to patch it yourself after you owned it. Everything here, short of issues addressed by PBI signing, are way out there. If you care enough to put your time into addressing such things, we'd accept patches, but I'm not going to pay people to address theoretical problems that will never, ever happen because there are a million worse things you could do completely unrelated to the firewall if you were in a position to do those.

We have considered pulling everything via HTTPS at some point in the future and verifying the cert, which would help address all these too.

Unfortunately, this is incomplete - it shows the vendor code but not the device code. I found the ipheth driver after I requested the device codes. I suggest you try the driver with your phone then we work on getting more USB information about your iphone if it seems necessary.

Teamviewer info sent.

@podilarius:

I am thinking about it … there is a lot to be done for this. To be honest with you, I now use split dns (using the forwarder in pfSense) to access the servers by URL or names. This translates the names into local addresses (even on DMZ) and works without issue for me.

If you use split dns, how do you get around the fact that the external port address is different than the internal port address? For example, I NAT an internal service on port 123 to external 321. The client wants to be able to connect externally (mobile device) and internally when on wifi to port 321. The DNS part I get, how about the port issue?

Did this ever happen?

There are some guides to developing a theme as well as re-branding. For example:
http://devwiki.pfsense.org/ReBrandingSupport

Have a look around.

Also there are blue themes already:
http://forum.pfsense.org/index.php?topic=49768.0

Steve

When do you plan to start the build? And how shall we pay?