• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Changing port forward - websocket behavior?

Scheduled Pinned Locked Moved NAT
2 Posts 2 Posters 389 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    JeGr LAYER 8 Moderator
    last edited by Oct 9, 2018, 7:34 AM

    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

    Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

    If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

    1 Reply Last reply Reply Quote 0
    • J
      jimp Rebel Alliance Developer Netgate
      last edited by Oct 9, 2018, 12:55 PM

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

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      1 Reply Last reply Reply Quote 0
      2 out of 2
      • First post
        2/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received