OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of boersencrash »
  • Show Posts »
  • Messages
  • 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

Messages - boersencrash

Pages: [1]
1
23.1 Legacy Series / Re: 23.1.7 broke wireguard routing
« on: May 13, 2023, 09:19:21 pm »
The patch c1784ad1ad5e and the following search for duplicates didn't find anything.
However, I found these entries in my warning log after reboot:

Code: [Select]
2023-05-13T21:06:35 Error opnsense /usr/local/etc/rc.routing_configure: The command '/sbin/route add -host -'inet' '10.100.0.1' '10.100.0.9'' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable add host 10.100.0.1: gateway 10.100.0.9 fib 0: Network is unreachable'
2023-05-13T21:06:35 Error opnsense /usr/local/etc/rc.routing_configure: The command '/sbin/route add -host -'inet' '10.100.0.1' '10.100.0.9'' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable add host 10.100.0.1: gateway 10.100.0.9 fib 0: Network is unreachable'
2023-05-13T21:06:24 Warning opnsense /usr/local/etc/rc.bootup: The required WireGuard_GW IPv4 interface address could not be found, skipping.
2023-05-13T21:06:22 Error opnsense /usr/local/etc/rc.bootup: The command '/bin/kill -'TERM' '69570'' returned exit code '1', the output was 'kill: 69570: No such process'
2023-05-13T21:06:16 Error opnsense /usr/local/etc/rc.bootup: Unable to configure nonexistent interface opt10 (wg0)
2023-05-13T21:06:15 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/ifconfig 'bce0_vlan4' media '1000baseT' mediaopt 'full-duplex'' returned exit code '1', the output was 'ifconfig: SIOCSIFMEDIA (media): Invalid argument'
2023-05-13T21:06:15 Error opnsense /usr/local/etc/rc.bootup: The command '/usr/sbin/arp -s '10.0.10.103' 'xxxxxxxxxxxxx'' returned exit code '1', the output was 'arp: writing to routing socket: No such process arp: 10.0.10.103: No such process'
2023-05-13T21:06:15 Error opnsense /usr/local/etc/rc.bootup: The command '/usr/sbin/arp -s '10.0.10.102' 'xxxxxxxxxxxxx'' returned exit code '1', the output was 'arp: writing to routing socket: No such process arp: 10.0.10.102: No such process'
2023-05-13T21:06:15 Error opnsense /usr/local/etc/rc.bootup: The command '/usr/sbin/arp -s '10.0.10.100' 'xxxxxxxxxxxxx'' returned exit code '1', the output was 'arp: writing to routing socket: No such process arp: 10.0.10.100: No such process'
2023-05-13T21:06:15 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/ifconfig 'bce0_vlan20' media '1000baseT' mediaopt 'full-duplex'' returned exit code '1', the output was 'ifconfig: SIOCSIFMEDIA (media): Invalid argument'

Reverting to 23.1.6 via "opnsense-revert -r 23.1.6 opnsense" immediately fixes the wireguard issues, patching to 23.1.7 brings them back.

2
23.1 Legacy Series / Re: 23.1.7 broke wireguard routing
« on: May 11, 2023, 06:59:53 pm »
Same here. A quick
"opnsense-revert -r 23.1.6 opnsense"
fixed it temporarily after I found no other solution after a few hours. Wireguard does successfully connect to the other opnsense (handshake is working), but after that nothing is happening, if somehow all the routing was gone.

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