On Fri, Mar 23, 2007 at 02:00:11PM -0500, Tim Byrne wrote: > On 3/23/07, Randy Shipp <[EMAIL PROTECTED]> wrote: > > > > How can I force VASSAL to "fail to connect to the server" without > > disconnecting my Internet connection? > > > > It would be nice if VASSAL had a simple way to force peer-to-peer. But alas > it does not (currently). I think your options are to disable your internet > connection, or disable access to the vassal server with some type of > firewall.
Temporarily poison your own ns cache. It is trivial to do under Linux, Mac, or Windows. Linux edit /etc/hosts Windows edit c:\windows\system32\drivers\etc\hosts I don't remember where it is on the mac Basically, edit the line that says something like 127.0.0.1 localhost to look like 127.0.0.1 localhost servername.com (just adding whatever server you are trying to connect to) This'll trick anything trying to connect to servername.com to instead try to connect internally, which will fail in ths case since you don't have a VASSAL server implementation. If you want to undo it, just remove the servername from the file -- ---------------------------------------------------------------------------- Hofstadter's Law states: It always takes longer than you expect, even when you take into account Hofstadter's Law. ---------------------------------------------------------------------------- [Non-text portions of this message have been removed]
