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

    FX5621 NIC support in pfsense 2.0

    Scheduled Pinned Locked Moved Hardware
    4 Posts 2 Posters 1.6k 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.
    • S
      stenio
      last edited by

      This is a reply to retired question:
      http://forum.pfsense.org/index.php/topic,24133.msg124725.html#msg124725

      I've just tried to use a third interface with PF v2.0.1. I have my WAN on rl0 (which is the second rl 100 Mbps port(?)) and my LAN on et1 (1 Gbps second port) and et0 disabled by BIOS.
      Oddly I get the carrier only when I plug the ethernet cable on interface et0! The throughput that I get with this interface is on only 4Mbps and, after a while, the LAN interface stop working.

      [2.0.1-RELEASE][admin@firewall.b2]/root(10): dmesg | egrep 'rl[0-9]|et[0-9]' | grep -v promiscuous
      rl0: <realtek 10="" 8139="" 100basetx="">port 0xe800-0xe8ff mem 0xfcfffc00-0xfcfffcff irq 17 at device 10.0 on pci0
      miibus0: <mii bus="">on rl0
      rl0: [ITHREAD]
      rl1: <realtek 10="" 8139="" 100basetx="">port 0xe400-0xe4ff mem 0xfcfff800-0xfcfff8ff irq 18 at device 11.0 on pci0
      miibus1: <mii bus="">on rl1
      rl1: [ITHREAD]
      rl2: <realtek 10="" 8139="" 100basetx="">port 0xe000-0xe0ff mem 0xfcfff400-0xfcfff4ff irq 19 at device 12.0 on pci0
      miibus2: <mii bus="">on rl2
      rl2: [ITHREAD]
      et0: <agere et1310="" gigabit="" ethernet="">mem 0xfea00000-0xfebfffff irq 17 at device 0.0 on pci130
      miibus3: <mii bus="">on et0
      et0: [ITHREAD]
      et1: <agere et1310="" gigabit="" ethernet="">mem 0xfe600000-0xfe7fffff irq 16 at device 0.0 on pci129
      miibus4: <mii bus="">on et1
      et1: [ITHREAD]
      rl0: link state changed to UP
      et1: link state changed to UP
      et0: link state changed to UP
      rl1: link state changed to DOWN
      rl2: link state changed to DOWN
      et1: watchdog timed out
      et1: watchdog timed out
      rl0: <realtek 10="" 8139="" 100basetx="">port 0xe800-0xe8ff mem 0xfcfffc00-0xfcfffcff irq 17 at device 10.0 on pci0
      miibus0: <mii bus="">on rl0
      rl0: [ITHREAD]
      rl1: <realtek 10="" 8139="" 100basetx="">port 0xe400-0xe4ff mem 0xfcfff800-0xfcfff8ff irq 18 at device 11.0 on pci0
      miibus1: <mii bus="">on rl1
      rl1: [ITHREAD]
      rl2: <realtek 10="" 8139="" 100basetx="">port 0xe000-0xe0ff mem 0xfcfff400-0xfcfff4ff irq 19 at device 12.0 on pci0
      miibus2: <mii bus="">on rl2
      rl2: [ITHREAD]
      et0: <agere et1310="" gigabit="" ethernet="">mem 0xfea00000-0xfebfffff irq 17 at device 0.0 on pci130
      miibus3: <mii bus="">on et0
      et0: [ITHREAD]
      et1: <agere et1310="" gigabit="" ethernet="">mem 0xfe600000-0xfe7fffff irq 16 at device 0.0 on pci129
      miibus4: <mii bus="">on et1
      et1: [ITHREAD]
      et0: can't enable RX/TX
      rl0: link state changed to UP
      et1: link state changed to UP
      rl2: link state changed to DOWN
      rl1: link state changed to DOWN
      et0: Link up, enable TX/RX
      et0: link state changed to UP
      rl0: link state changed to DOWN
      rl0: link state changed to UP
      et0: link state changed to DOWN
      rl0: link state changed to DOWN
      rl0: link state changed to UP
      rl0: link state changed to DOWN
      rl0: link state changed to UP

      I don't know where is rl3. Maybe I've disabled the wrong NIC?

      Regards,
      Stenio</mii></agere></mii></agere></mii></realtek></mii></realtek></mii></realtek></mii></agere></mii></agere></mii></realtek></mii></realtek></mii></realtek>

      1 Reply Last reply Reply Quote 0
      • S
        stenio
        last edited by

        Hello,

        Do you know if there is a way to bypass the settings of the interfaces made at bios level? I'm not able to enter the bios setup using the serial console: I hit del but the boot loader  of pf starts immediately.

        Thanks,
        Stenio

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

          To access the bios via serial you need to have 'console redierct' (Award) or 'remote access' (AMI) enabled in the bios, not all bioses have these features typically only servers.
          Then when the POST screen appears you have to press TAB. This is because you can't send a 'delete' key via serial. Some AMI bioses allow sending F keys but require your terminal emulator to support it correctly.

          Looking at the FX5621 it probably does have console redirect.

          Steve

          Edit: Reading through the manual for that box it has LAN bypass so if that is not disabled it could be kicking in and disconnecting you.

          Edit: It doesn't appear to have remote access setup in the bios. It would usually appear in the 'Advanced' section. However it maybe enabled by default anyway.

          1 Reply Last reply Reply Quote 0
          • S
            stenio
            last edited by

            Hi Steve,

            Thank you for your answer. Now I remember that to enter the bios I was forced to use a keyboard and a monitor.

            From the dmesg output it seems that interface rl3 was erroneously disabled via bios instead interface et0, wasn't it?

            Regards,
            Stenio

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