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

    Outgoing port 22 vanishing through cable modem

    Scheduled Pinned Locked Moved Firewalling
    4 Posts 3 Posters 679 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.
    • W
      watkinsufs
      last edited by

      My client's info:
      Internet provider: Cox
      Connections:
      Cable Modem -> SG-5100 -> SG-7100 -> office LAN

      SG-5100 is being use as the simple CIDR block router for Cox CIDR block range.
      SG-7100 is the main firewall.

      They are on a Cox biz account. The other day they had to replace my client's cable modem. Ever since then everything going outbound from inside our network to port 22 vanishes through the cable modem. Example: if I log into the shell on the SG-5100 and ssh to my home office (SG-3100) on port 22 which is blocked, my SG-3100 shows nothing in the firewall log, but if I use some other port like 52022 the SG-3100 immediately shows it's been blocked. Every Netgate device that myself and my clients use are on ports other than 22 for ssh access. Even though that has nothing to do with outgoing.

      The tech. at Cox was trying to say they are not blocking anything. I tried to explain to him that it's not even an inbound port, it's outbound and it's vanishing where any other port is getting through. I tried to tell him that a network engineer there needs to check the network traffic. We just kept going back and forth. He finally submitted a ticket.

      Nothing has changed in the configs for the SG-5100 or the SG-7100 it all started after the cable modem swap. Everything has been power cycled several times.

      Just for my own sanity I am right that it's something on the Cox end and not something in the SG-5100 when it's trying to ssh out from the shell? Has anyone else had this issue with cable providers?

      JKnottJ S 2 Replies Last reply Reply Quote 0
      • W
        watkinsufs
        last edited by

        Cox called back. They said it probably is the cable modem since our last modem was more of a pass through and this one is a gateway modem. Even though it's in bridge mode he said they still have issues with ports.

        1 Reply Last reply Reply Quote 0
        • JKnottJ
          JKnott @watkinsufs
          last edited by

          @watkinsufs

          You could try something like nmap to see if that port can get through.

          PfSense running on Qotom mini PC
          i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
          UniFi AC-Lite access point

          I haven't lost my mind. It's around here...somewhere...

          1 Reply Last reply Reply Quote 0
          • S
            SteveITS Galactic Empire @watkinsufs
            last edited by

            Are there any security settings on the Cox modem that can be disabled?

            Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
            When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
            Upvote 👍 helpful posts!

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.