OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of Sar6e »
  • Show Posts »
  • Topics
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

  • Messages
  • Topics
  • Attachments

Topics - Sar6e

Pages: [1]
1
Hardware and Performance / FreeBSD Issue with M.2 NIC?
« on: January 25, 2024, 05:03:33 am »
I'm trying to migrate my current OPNsense gateway to new hardware.  Dell Wyse 5070 thin clients can be had pretty cheap at present and support expansion to a second ethernet port.  All up I landed the hardware for less than $100.

The problem I am having is routing traffic via the second ethernet port.

The second ethernet port is connected via an M.2 slot.  Both the onboard and the second ethernet port are Realtek 8111F chipsets. 

To confirm the second ethernet port works at a hardware level, I did a desktop Linux install (Fedora) and connected the second ethernet port.  A network connection was made, a DHCP lease obtained and the correct DNS settings discovered.  All working as expected.  This to me indicates there are no problems with the ethernet port, the M.2 card or the BIOS settings.

I next tried to install FreeBSD 13.2.  I configured the onboard ethernet port (re0) during the installation and again had no problems in getting a DHCP lease and discovering the DNS service.  This implies to me there is no problem with the driver BSD is using for the Realtek 8111 chipset.

If I repeat the install process for BSD and configure the second (M.2) ethernet port, it fails to obtain a DHCP lease.  The interface (re1) is reported as up, but it can't route traffic through it (?), or it cannot discover the router advertisement(?).  TBH, I have no idea what is going on. 

I think I've identified this is not an OPNsense issue but more an issue in the underlying FreeBSD operating system.  So maybe I'm posting in the wrong place, but I figure the people most likely to have tried to use a second M.2 NIC are more likely here than on a FreeBSD forum.

Thanks in advance for any assistance or direction to take with this problem!

2
General Discussion / Name resolution that includes port number?
« on: September 09, 2022, 01:28:17 am »
I'd like to not have to remember all the port numbers for the various docker containers running on a single host.  Ideally I'd be able to type "service.server.domain" and have the DNS be able to resolve that to ip:port.

For example if my wiki is exposed as port 9082 on the server fred at hb.com at 192.168.1.100, it would be great to just type wiki.fred.hb.com and have that resolve to 192.168.1.100:9082 rather than having to remember which port the wiki uses.

Is there a way to achieve this or am I dreaming?

Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2