Menu

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.

Show posts Menu

Messages - sbuckmann

#1
Eine Anleitung dazu findet sich in https://forum.opnsense.org/index.php?topic=17853.0.
UDP Port 5678 = MikroTik Neighbor Discovery protocol.
#2
Works fine here (24.7.1; Mellanox ConnectX-3; Supermicro M11SDV-8CT-LN4F).
#3
Thank you, Franco.

Cheers
Stefan
#4
I have a dynamic IPv4 address and a static IPv6 /48 prefix on my WAN interface.
Network adapter is a Mellanox ConnectX/3.
WAN config:

  • Block private networks [X]
  • Block bogon networks [ ] (due to default deny bogons rule blocking dhcpv6 traffic; see https://forum.opnsense.org/index.php?topic=33616.0)
  • IPv4 Configuration Type [DHCP]
  • IPv6 Configuration Type [DHCPv6]
  • Request only an IPv6 prefix [X]
  • Prefix delegation size [48]
  • all other checkboxes unticked
Every 8-10 seconds, a log entry "... configd.py[nnn]: [LogID] New IPv6 on mlxen0" is written.

The IPv6 WAN IP's for mxlen0 indeed do not change:

ifconfig mlxen0 | grep inet6
> inet6 fe80::e61d:2dff:fe1c:fe70%mlxen0 prefixlen 64 scopeid 0x9
> inet6 2a02:aaaa:bbbb:cccc:e61d:2dff:fe1c:fe70 prefixlen 64 autoconf

Hint: The IPv6 address 2a02:aaaa:bbbb:cccc:xxx shown above is outside the static /48 prefix.

/var/etc/dhcp6c.conf and /var/etc/dhcp6c_wan.conf:

interface mlxen0 {
  send ia-pd 0; # request prefix delegation
  request domain-name-servers;
  request domain-name;
  script "/var/etc/dhcp6c_wan_script.sh"; # we'd like some nameservers please
};


This problem exists since > 1 year. Today, I exported the config, reimported it and rebooted the router, but this had no effect. Everything works fine, but I wonder what is triggering the frequent log entries. Any idea ? Thank you.
#5
Same problem here upgrading from 20.7.3 to 20.7.4 (last line also "Reloading template OPNsense/xxxx").
Logged in via ssh, selected "6) Reboot system". After reboot and logging in via ssh again, I selected "12) Update from console". After that, the upgrade ran fine without further problems.
#6
I have the same problem, and it also started with 19.1.8 (never seen before),
#7
Similar problem here. My OPNsense has several network zones; resolving the router ip via nslookup/dig delivers all router ip addresses of all interfaces.
#8
Go to "System" - "Trust" - "Certificates", then click on "add or import certificate". Copy+Paste certificate and private key in the empty fields, give your certificate a name and save.
Then go to "System" - "Settings" - "Administration". The Listbox under "SSL certificate" should now show your imported certificate. Select and save.