Changing port forward - websocket behavior?


  • Moderator

    Good morning!

    We have a port forward configured for a customer to one of his webservers. On that forward (80/tcp, 443/tcp) he's also running a websocket for an application. That all works fine. Now he wants us to switch the forwarding target to a second webserver (a newer copy of the other one).
    I'm curious: what will happen to the states belonging to the clients talking to the application via the websocket? Aren't these active states/connections that won't get purged by a filter reload and so will still be connected to the old server after a rule reload?

    Thanks for input :)
    Jens


  • Rebel Alliance Developer Netgate

    Open states will stay open. They will need to be closed, expired, or otherwise killed/reset to point to the new server.