Re: Long Story

[vhamberg@xxxxxxxxx]

Jon

The LinkSys is at your place? Then it would need to have
forwarding turned on for the port (4200) that the
CODE400 server wants to broadcast to. In a way, the
CODE400 is a client of your PC (?).

As you say, traffic that goes out can come back without
restriction. So autostart servers have the conversation
initiated by you, so the router recognizes the return
traffic and lets it through.

This is the basis for a hole, based on traffic that
imitates other kinds of traffic. That is what SPI
(stateful packet inspection) is for, and some LinkSys
routers have this, albeit in what seems to be a beta
state for now. This keeps track of outgoing traffic, and
incoming has to match on many levels of the TCP stack.

That's as little as I know.

Vern
>  >> That's interesting    as I have had the opposite experience (though I
> admit  I may be missing something besides the CODE help system).
>
> I don't understand firewalls etc. but they do seem to figure in the picture
> here.  When working from my home office via a DSL connection (and LinkSys
> router) I can get autostart servers to work just fine.  STRCODE will not
> work unless I open port 4200 on the firewall in the router.  I have made the
> assumption (which seems to be born out by experiments that I and others have
> made) that at least the LinkSys unit will allow inbound messages to a port
> if that port (4200) initiated the conversation.  What it will not do is
> accept incoming traffic on that port unless it is unlocked.
>
> This has been my experience anyway - does it match yours?
>
> Jon Paris
> Partner400