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

    WAN Interface Status: no carrier for Adtran T1 router

    General pfSense Questions
    2
    3
    3.9k
    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.
    • L
      LilGator
      last edited by

      Running a dual WAN config, I have our T1 line (via an Adtran Total Access 612) on WAN (vr0), and a DSL line as OPT1 (vr1).

      The DSL line is DHCP and is doing great, I have all LAN IP's being forwarded through it and it's working fine.

      I can't get the WAN to do anything other than "no carrier". I've tried setting the media, as shown below- if I leave it auto (ifconfig vr0 media autoselect), I would get Media: None.

      Our ISP has set the Adtran's gateway IP as 192.168.16.1 (as shown below I have set this). Connecting a Windows PC straight to the router, static config'd 192.168.16.x (I tried 22), Subnet Mask: 255.255.255.0, and gateway 192.168.16.1 works fine, and I can see the outside world.

      WAN interface (vr0)
      Status no carrier
      MAC address 00:1c:f0:d5:5f:a8
      IP address 192.168.16.22
      Subnet mask 255.255.255.0
      Gateway 192.168.16.1
      Media  100baseTX <full-duplex>In my ISP's "Router IP Information" provided I have:

      ISP WAN IP: 10.4.39.237 | Subnet: 255.255.255.252
      Customer WAN IP: 10.4.39.238 | Subnet: 255.255.255.252
      Customer LAN IP: 192.168.16.1 | Subnet: 255.255.255.248

      I tried two different cables, and even one that (should) have been a crossover.

      Tomorrow I'll try calling the ISP and having them set the router to DHCP, probably something simple like 192.168.1.1/24 as well, and see what happens.

      I probably should mention my internal LAN IP's are 192.168.16.31-200, the pfsense gateway IP is 192.168.16.254. This (16.x) is because I have two CC processing machines who are required to keep their internal IP's the same as when first config'd (both 192.168.16.x). Though I don't think this should cause any issues with the WAN finding a gateway @ 16.1…

      Any ideas?  ???</full-duplex>

      1 Reply Last reply Reply Quote 0
      • GruensFroeschliG
        GruensFroeschli
        last edited by

        No carrier means as much as: "no cable is plugged in".
        Did you connect it via a crossovercable?
        have you tried a switch in between?

        We do what we must, because we can.

        Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

        1 Reply Last reply Reply Quote 0
        • L
          LilGator
          last edited by

          I did put it on our switch and tried that way … no dice. I'll check to make sure what I thought was a crossover, really was. I've always swapped the OPT1/WAN assignments (and physically), and it worked exactly in reverse- DSL was fine on the card that can't see the router, T1 no carrier.

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