Another approach, still using GPIO, and possibly easier to do, would be to still hook a push button to the gpio, but, this time, while the board is lit.. If the button is pressed, trigger the slice selection routine, than reboot the box But i really feel it'll be better if done before the board is turned on ..

Well the third option would be to get access to the phoneline distributor panel. Patch one of the 4 lines from her to your home, have at your home an DSLAM and let her access you. But since i doubt that you have: A: Access to the distributor panel B: A schema of the distributor panel (good luck finding the right wires) C: An Access Multiplexer lying around It's really easier to just go the "official" way. (We had to go with this option for a setup in our town, but that included a lot of paperwork with the telephone company and quite expensive hardware)

Not in pfSense 1.2.3 I believe it is already on PHP 5 for pfSense 2.0, however.

@sullrich: Looks like Chris got you squared away? YES!! I am going to start with the 5 hour pack! I am on my to pfsense heaven!!

Be aware that D-Star is almost exclusively used for Amateur Radio.  Anyone planning to use the Icom ID-1 (at least in the US) will need an Amateur Radio license and no commercial and/or encrypted traffic of any form can be transmitted on the amateur radio frequencies. Icom does offer the IDAS system which is designed for business use and provides much of the same functionality.

Mark the box "Enable Secure Shell" from  System: Advanced functions  of the WebGUI and there you go with puTTY, WinSCP et al.

I know how to do so, i just asked myself the reason why it can not be done through the gui, and if it was do able to get it in the GUI? Found that it is in 2.0. Thanks for the reply! regards, Johan

I've only got a single IP address, so it's pretty much useless huh?  I think I'll boot it up and see what it's got but I'm not expecting anymore.

If you specify it as: 45 0 * * * /sbin/halt -p Then it should shut down at quarter to one in the morning.  That format works on a standard FreeBSD host.

In this case, the power of the system is in its infinite configurability. I would venture to say there is really no "right" or "wrong" way to use pfSense. There is also no way for pfSense to know what your real intent is, especially when it comes to configuring packages (which is mainly what you're talking about, squid, squidguard, etc). I don't know about you, but to me what you're suggesting sounds a lot like "Clippy" of Microsoft Office infamy. It shouldn't really be pfSense's place to second guess what an administrator is trying to do, since that is really up to the administrator. The kinds of things you discuss are, as you hint at, things for the manual or book. There is a book in the works, and there is a lot of documentation on the Doc Wiki. Alternate scenarios and suggestions for better ways to accomplish a given task are wonderful to have there. That said, I wouldn't want them in the WebGUI trying to alter my behavior.

hi everybody, i think i found a solution:     >Go to the proxy content     >In the default tab     >Disable "not allow ip adress in the url"     >Save Changes and apply i hope this help you with your problem hola a todos, creo que encontre la solucion:   >Ir al proxy content   >en la ficha de default   >Desmarca "not allow ip adress in the url"   >Guarda los cambios y aplicalos Espero que esto resuelva tu problema Jass Arenas Mex