Re: netsync with port forwarding -- SOLVED

>I believe I got it to work?  I found one more trick in the cofiguration=20
>menu.  Theres a firewall, which knows about proper redirection for a=20
>large number of protocols, but not netsync.
>It turns out to have a garbage destination -- where to send all packets=20
>that it doesn't know what to do with.  This is presumably intended to ba=20=

>a machine that cac collect statistics and check for ossible attacks.
>
>So I just designate my server as my garbage machine.

I believe you could also enable the incoming connections on the port in
the firewall settings=E2=80=A6 on the other hand, if you want incoming=20
connections, it's on the server, so I guess you can call it a win=E2=80=A6

>It will ignore any port that's not open, and I control that by what=20
>services I choose to provide.
>
>And if netsync uses the familiar trick of initiating a connexion on port=20=

>4691 and than replying to say what port the rest of the comminication=20
>should take place on,
>* it ould formerly get lost because redirection treats it as a attack,
>* But now it's sent to the garbage machine, which does know what to do=20
>with it.

Pretty sure it does not=E2=80=A6

>And I went to a coffee shop to check it's working.

Oh well, that's what matters