Note that since I do not get headers, on msgs that do not include addresses
I can only reply to the group - sorry).
>I work for a government agency and we currently go through an internet
>provider for our internet services. We are looking at setting up our own
>connection to the internet by tapping into the backbone of our local
>university. As firewall administrators, I am curious as to the time and
>effort necessary in maintaining a firewall on a day-to-day basis.
Would think this would be covered by a FAQ but the answer must be hedged
depending on the complexity of the connection. If all you want is E-mail,
otward Telnet & FTP, it is really pretty easy, just turn everything off
except those three and only allow inward to Mail.
Now if you want Network News delivered to your server and you want your
own web server etc. etc. etc. things can get very complicated very fast
so it is a matter of:
1) Develop a plan of what services you need
2) Determine the accesses required
3) Then determine what kind of firewall is necessary (and that is just
one piece of the entire envelope).
However, when designing a firewall a paraphrase of the immortal line
spoken by Joe Don Baker in "Hunt for Red October" is in order: "Don't
take a dump without a plan."