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

    Micro USB Fell Off

    Scheduled Pinned Locked Moved
    Official Netgate® Hardware
    3
    7
    212
    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.
    • H
      Hans 1
      last edited by

      My 1100 stopped working - would not get a WAN IP from ISP Modem.
      I used another router and it got an IP from the ISP modem.
      When I disconnected the 1100 to connect it to another computer for debugging, I noticed something knocking around inside the 1100. I unscrewed it and found the Micro USB had disconnected itself from the board. I had never used the Micro USB, so the connector had not been stressed.
      It's been 2 years since I purchased it. I'd like to re-image the 1100 so maybe that will fix it, but without the Micro USB and no warranty, I'm SOL. Any thoughts, for next steps ?

      johnpozJ 1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Are you still able to connect to the webgui or SSH via the LAN?

        H 1 Reply Last reply Reply Quote 0
        • H
          Hans 1 @stephenw10
          last edited by

          @stephenw10
          I can ssh to it and http to GUI display but it does not show an IP from the IPS. Also the syslog says "promiscuous mode enabled/disabled" on and off. The green light flashes.

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Ok is your WAN using DHCP?

            Does the WAN port show as linked? Does the WAN interface show as UP in Status > Interfaces?

            H 1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator @Hans 1
              last edited by

              @Hans-1 said in Micro USB Fell Off:

              I used another router and it got an IP from the ISP modem.

              If your on a cable modem, when you change the device connected to it - you almost always have to power cycle the modem to get a new device to work.

              Whenever the mac changes that is connected to cable modem, you normally need to power cycle the modem. So if you have router X connected, and then want to connect router Y.. Disconnect X, power cycle the cable modem. Wait for it to show that its connected to your isp. Then connect your router Y and and turn it on.

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.03 | Lab VMs 2.7.2, 24.03

              1 Reply Last reply Reply Quote 1
              • H
                Hans 1 @stephenw10
                last edited by

                @stephenw10
                Here's the dhcp log after a dhcp release/renew.
                It appears to loop while trying to get an IP from the ISP.
                Sep 3 11:26:38 NTG1100 dhclient[77467]: PREINIT
                Sep 3 11:26:38 NTG1100 dhclient[78059]: EXPIRE
                Sep 3 11:26:38 NTG1100 dhclient[78238]: Deleting old routes
                Sep 3 11:26:38 NTG1100 dhclient[78854]: PREINIT
                Sep 3 11:26:40 NTG1100 dhclient[77056]: DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 2
                Sep 3 11:26:42 NTG1100 dhclient[77056]: DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 5
                Sep 3 11:26:47 NTG1100 dhclient[77056]: DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 8
                Sep 3 11:26:55 NTG1100 dhclient[77056]: DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 8
                Sep 3 11:27:03 NTG1100 dhclient[77056]: DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 8
                Sep 3 11:27:11 NTG1100 dhclient[77056]: DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 17
                Sep 3 11:27:28 NTG1100 dhclient[77056]: DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 10
                Sep 3 11:27:38 NTG1100 dhclient[77056]: DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 1
                Sep 3 11:27:39 NTG1100 dhclient[77056]: No DHCPOFFERS received.
                Sep 3 11:27:39 NTG1100 dhclient[77056]: No working leases in persistent database - sleeping.
                Sep 3 11:27:39 NTG1100 dhclient[96102]: FAIL
                Sep 3 11:27:39 NTG1100 dhcp6c[96714]: failed initialize control message authentication
                Sep 3 11:27:39 NTG1100 dhcp6c[96714]: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
                Sep 3 11:27:39 NTG1100 dhcp6c[96714]: skip opening control port
                Sep 3 11:27:40 NTG1100 dhcp6c[96853]: Sending Solicit
                Sep 3 11:27:41 NTG1100 dhcp6c[96853]: restarting
                Sep 3 11:27:41 NTG1100 dhcp6c[96853]: Sending Solicit
                Sep 3 11:27:42 NTG1100 dhcp6c[96853]: Sending Solicit
                Sep 3 11:27:43 NTG1100 dhcp6c[96853]: Sending Solicit
                Sep 3 11:27:45 NTG1100 dhcp6c[96853]: Sending Solicit
                Sep 3 11:27:49 NTG1100 dhcp6c[96853]: Sending Solicit
                Sep 3 11:27:54 NTG1100 dhclient[96222]: DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 1
                Sep 3 11:27:55 NTG1100 dhclient[96222]: DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 2
                Sep 3 11:27:57 NTG1100 dhclient[96222]: DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 3

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Right it's just seeing no DHCP replies at all. I assume the port does show as linked though since it is trying?

                  As @johnpoz said the upstream device could be locked to the MAC of your other router. You could try spoofing that in pfSense. Or rebooting the modem.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post