Its often hard to tell how much people already know, but when you describe your question as a "dumb N00B" question its possible you may need this level of detail:
To exit from the shell (CLI) type Control-D (hold the Ctrl key down while you tap the D key).
What you did would possibly be more accurately described as entering shell mode rather than exiting the pfSense configuration menu. On exiting the shell you return to the menu.
If you are looking for a hard interface failure (e.g. the port is unplugged or CPE powered off) look into the link events in /etc/devd.conf (read the FreeBSD man page)
As for a "soft" failure, such as a high delay or connectivity loss (no pings returned) you might be able to get that info from /tmp/apinger.status
Or just route the system logs to another server (the system log settings page can do this) and have something that watches/parses the log and reports on failures there.
Edit the LAN rule (or rules you want this limit to apply to) and click the "Advanced" button, this will give you options to limit states, connections and the like.
You could use things like xmarks which you dont need to to add plugins and able to access from their website. This way I am not fixed to one computer or browser and not locked into any 1 system. Though using their service may not be what a lot of security conscience person find safe but so far for over 1 year been available 24x7 and free. I am not confined in anyway nor need to leave unnecessary information on any computer. Unless of course that computer is infected with key logger. Just my thoughts and the way I am using now.
Hi submicron,
Don't worry it's only in a test production site with part live :) No harm done just need to show that its possible without incurring huge cost for them. So to everyone reading this please do make sure not to put any beta or untested stuff on production sites giving a bad reputation to any opensource or pfsense. At least let your clients know that this is all beta still.
Tks all
Eric
The key in the box is the public key in the form that OpenSSH uses on the server end and the export OpenSSH key saves the private key needed for using OpenSSH as the client.
@darklogic82:
OK, so what do you need help with? Ask the question/s and I will do my best to help assist in your setup needs.
Take Care,
Matt
Thanks for giving me your assurance to assist, i will PM you ASAP when i am fully ready.
thanks so much.
Working, thanks so much for getting this back up for me. If you like, you could remove my darklogic82 account I had to create in order to post to the fourms.
Take Care,
Matt
Link down means the NIC can't see the signal from the station at the other end of the cable - broken cable is the most likely cause but could include broken socket, broken NIC, loose connection etc.
