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

help with wan static address

Scheduled Pinned Locked Moved TNSR Feedback
5 Posts 2 Posters 1.8k 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.
  • G
    Galbiere
    last edited by Jul 2, 2019, 9:15 PM

    Good afternoon,

    I'm new here, I've been studying a lot these days and I've made a lot of progress.
    I'm configuring my WAN in pfsense with static ip, but it does not work as expected.

    I changed the WAN settings this way:
    Static IPv4
    Disable IPv6
    Ip: 177.xx.xx.90
    And I added a new Gateway 177.xx.xx.89
    The mask provided by my ISP is 255.255.255.252, so I used / 30 I tried it too / 24

    The network card flashes slowly.
    When accessing the status interface it stays: no carrier

    These same settings on an ordinary router work normally.
    Another class of ip also worked ...
    If I provide another address on this network card it works, then this is not the problem ...
    Anyone know what it could be?

    appreciate

    1 Reply Last reply Reply Quote 0
    • J
      JeGr LAYER 8 Moderator
      last edited by Jul 3, 2019, 12:43 PM

      @Galbiere said in help with wan static address:

      When accessing the status interface it stays: no carrier

      No carrier means that - that interface has no connection to anything or the cable is faulty.

      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
      • G
        Galbiere
        last edited by Jul 3, 2019, 5:59 PM

        @JeGr thanks for answering

        is exactly that the problem, if I put this same cable on an ordinary router it works normally.
        I tested it on another UTM and another router recently, strange as it sounds in pfsense does not recognize, but on other platforms it works, alias, I'm using it now

        1 Reply Last reply Reply Quote 0
        • G
          Galbiere
          last edited by Aug 2, 2019, 5:46 PM

          Hi @JeGr how are you?

          After much research I discovered the reason for my failure.
          In the WAN interface I selected in Speed ​​and Duplex the autoselect option. This caused the firewall to recognize the connection and identified it as
          <10baseT / UTP <full duplex, flowcontrol, rxpause, txpause>

          Problem solved.

          Thank you

          1 Reply Last reply Reply Quote 1
          • J
            JeGr LAYER 8 Moderator
            last edited by Sep 3, 2019, 9:01 PM

            Fine thanks, nice to hear back. Also autoselect is the default when setting up an interface so that should have been the case for you, too. So if you configured it manually no wonder it failed the auto-negotiating and thus reported no L2 carrier :)

            But good for you that it worked out and you found it! Just let it on auto-negotiating the next time ;)

            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
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
              [[user:consent.lead]]
              [[user:consent.not_received]]