[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]



I think a second way to bypass it, would be to move a PC from the firewalled segment on to the open segment. I do not have DHCP turned on on my router, but a clever person with networking 101 could try various IP addresses and subnets and get it right fairly quickly. So I would need to block port 80 from everything but my proxy to prevent that. Someone halfway familiar with the type of router I use could get the password fairly quickly - so I need to change that (and document it).

A third way would be to simply go dial-up. No LAN, no proxy, no firewall.

I guess for home users, you just keep an eye out, and if you have those problems, you have more than a simple problem of ocasionally clicking the wrong link. In a business environment you would have different issues as well. Have you guys found people bypassing proxies? Any ways to keep that in hand? 



</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00114.html">[ale] New Server &amp; Discussion Topic</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00116.html">Test</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00119.html">[ale] New Server &amp; Discussion Topic</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00116.html">Test</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00115"><strong>Date</strong></a></li>
<li><a href="threads.html#00115"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>