Messages

271

23.7 Legacy Series / Re: Dpinger broken

« on: October 23, 2023, 09:31:59 am »

Hi,

could you be more specific on your issue:
- Is DPinger still "RUNNING" in services or stopped?
- Does it help to restart it?
- Is there any information in your log file about dpinger when you reconnect?
- What kind of IPs are you pinging? Is it the next hop or some far host?

272

Virtual private networks / Re: OpenVPN to VLAN

« on: October 23, 2023, 09:14:43 am »

If you don't trust yourself and your local, yes a VPN may be an option. But actually, you'd have to set up a server on the target host itself.

But jokes aside: You just may want to add a pass rule on the LAN interface to allow traffic with destination in the VLAN network for the intended traffic. To limit its usage you might switch on/off your rules manually or on a schedule.

273

23.7 Legacy Series / Re: dpinger behaviour after WAN IF down [SOLVED - bug filed]

« on: October 18, 2023, 02:49:55 pm »

Thanks!

274

23.7 Legacy Series / Re: ipv6 gateway bug

« on: October 17, 2023, 09:12:56 pm »

In had a similar issue that could be related. In the referenced github there's a workaround.
Issue seems to arise on statically assigned IPv6 adresses.


https://forum.opnsense.org/index.php?topic=36277.msg176884#msg176884

275

General Discussion / Re: belgium.be not reachable via opnsense/pfsense?

« on: October 15, 2023, 03:54:14 pm »

Hi,

your OPNsense is blocking IPv6?

belgium.be to me (Germany) is not accessible via IPv4, seems as if packet filtering on their side happens
via IPv6 I get a stable page hit as already mentioned

276

General Discussion / Re: Direct URL to IP

« on: October 15, 2023, 09:13:46 am »

That depends on your actual requirements.

You should make sure first unbound is up and running. And that it is deployed as dns server for all your clients in LAN and VPN. The latter is achieved usually by configuring DHCP server to deliver the proper address. Or the VPN server accordingly.

Make sure traffic coming in on OPNsense interface for VPN (don't know what you are using, so it is hard to say exactly) directed to your server on port 80,443 is allowed to pass.

Maybe you're lucky and your server is registered as static lease in dhcp. Then, resolving it in a URL should work already. But again, i don't know your setup

277

General Discussion / Re: Direct URL to IP

« on: October 13, 2023, 09:44:10 am »

1. Set up unbound, see https://docs.opnsense.org/manual/unbound.html
2. Define Hostname/Domain and IP for your server in unbound
3. Make unbound your DNS in LAN and VPN
4. Make sure firewall rules are enabling traffic

278

French - Français / Re: Redirection de ports sur opnsense

« on: October 09, 2023, 09:41:51 am »

Salut,

il faut adapter les règles de filtrage ou OPNsense pourrait ça faire.

plus simple :
Il faut selectionner seulement : "Ajouter une règle de filtrage associé ". Efface les règles en pare-feu avant !

méthode manuel:

Les règles sont comme les règles NAT ( pour IF WAN ) :
Source: *
Destination: LAN address
Source port: *
Destination port: 7777, ...

NAT est appliqué avant la filtrage.

Il faut aussi faire attention pour NAT reflection . Quelques info en anglais: https://docs.opnsense.org/manual/how-tos/nat_reflection.html

279

French - Français / Re: Redirection de ports sur opnsense

« on: October 07, 2023, 06:34:46 pm »

Bonjour,

la redirection n'est pas correcte.

Essaiez une redirection comme ça:

Source = Any
Source Ports = Any 
( Normalement, la source est inconnu. )

Destination = WAN address
Destination ports = 7777, ....

Redirect target IP = IP de votre serveur physique / virtuel / interne
Redirect target port = 7777, ....

280

23.7 Legacy Series / Re: dpinger behaviour after WAN IF down [SOLVED - bug filed]

« on: October 05, 2023, 11:03:37 am »

Problem persists. Bug report here: https://github.com/opnsense/core/issues/6913

281

23.7 Legacy Series / Re: dpinger behaviour after WAN IF down

« on: October 05, 2023, 10:20:48 am »

Tonight the same happened again and - as yesterday - dpinger for IPv6 did not come up again. Incident happened at 2023-10-05T03:10:36.

I will try to reproduce this in an easier way and file a bug.

2023-10-05T03:11:04   Notice   dpinger    MONITOR: ISP_WAN_GWv4 (Addr: xx.xx.148.97 Alarm: down -> none RTT: 0.3 ms RTTd: 0.0 ms Loss: 0.0 %)
2023-10-05T03:11:03   Notice   dpinger    Reloaded gateway watcher configuration on SIGHUP
2023-10-05T03:11:03   Warning   dpinger    send_interval 1000ms  loss_interval 4000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 0ms  loss_alarm 0%  alarm_hold 10000ms  dest_addr xx.xx.148.97  bind_addr xx.xx.148.98  identifier "ISP_WAN_GWv4 "
2023-10-05T03:11:03   Notice   dpinger    Reloaded gateway watcher configuration on SIGHUP
2023-10-05T03:11:03   Warning   dpinger    exiting on signal 15
2023-10-05T03:11:02   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-05T03:11:01   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-05T03:11:00   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-05T03:10:59   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 50
2023-10-05T03:10:58   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-05T03:10:57   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-05T03:10:56   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-05T03:10:55   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-05T03:10:54   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-05T03:10:53   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-05T03:10:52   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-05T03:10:51   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-05T03:10:50   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-05T03:10:49   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-05T03:10:48   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-05T03:10:47   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-05T03:10:46   Notice   dpinger    MONITOR: ISP_WAN_GWv4 (Addr: xx.xx.148.97 Alarm: none -> down RTT: 0.0 ms RTTd: 0.0 ms Loss: 100.0 %)
2023-10-05T03:10:42   Notice   dpinger    Reloaded gateway watcher configuration on SIGHUP
2023-10-05T03:10:42   Warning   dpinger    send_interval 1000ms  loss_interval 4000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 0ms  loss_alarm 0%  alarm_hold 10000ms  dest_addr xx.xx.148.97  bind_addr xx.xx.148.98  identifier "ISP_WAN_GWv4 "
2023-10-05T03:10:42   Notice   dpinger    Reloaded gateway watcher configuration on SIGHUP
2023-10-05T03:10:42   Warning   dpinger    exiting on signal 15
2023-10-05T03:10:42   Warning   dpinger    exiting on signal 15
2023-10-05T03:10:41   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 55
2023-10-05T03:10:41   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-05T03:10:40   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-05T03:10:40   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-05T03:10:39   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-05T03:10:39   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-05T03:10:38   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-05T03:10:38   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-05T03:10:37   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-05T03:10:37   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-05T03:10:36   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 50
2023-10-05T03:10:36   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-04T15:05:37   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 55
2023-10-04T10:01:44   Notice   dpinger    MONITOR: ISP_WAN_GWv6 (Addr: 2a00:xxxx:xxxx:xx::1 Alarm: loss -> none RTT: 0.2 ms RTTd: 0.0 ms Loss: 0.0 %)
2023-10-04T10:01:43   Notice   dpinger    Reloaded gateway watcher configuration on SIGHUP
2023-10-04T10:01:43   Warning   dpinger    send_interval 1000ms  loss_interval 4000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 0ms  loss_alarm 0%  alarm_hold 10000ms  dest_addr 2a00:xxxx:xxxx:xx::1  bind_addr 2a00:xxxx:xxxx:xx::2  identifier "ISP_WAN_GWv6 "

282

23.7 Legacy Series / dpinger behaviour after WAN IF down [SOLVED - bug filed]

« on: October 04, 2023, 12:11:02 pm »

Hi,

I observed some unexpected behaviour in dpinger / OPNsense's handling of dpinger tonight. At least to me it is unexpected, so correct me if I am wrong.

Status:
OPNSense 23.7.5-amd64 on Zotac's ZBOX with 2x 1 GBits Realteak NICs and os-realteak-re installed. Works stable for more than 4 years. WAN on re0 (no VLAN) is directly connected to a Mikrotik router provided from the ISP, so I don't have access to it.

Event:
Due to a reboot of the mikrotik there was an IF DOWN/UP at 04:19:16 - 04:19-26 and again at 04:19:45 - 04:19:49.

Observation:
1. OPNSense detected IF events and reacted accordingly. See system.log below.
2. DPinger noticed that it failed and was restarted twice. When I checked the system this morning at 10:00 I saw that dpinger for IPv6 was down - so was the gateway as shown in OPNSense's dashboard. I triggered a start of dpinger for the IPv6 gateway on the dashboard and it started successfully. The gateway became online and IPv6 was working again.

My expectation:
I would have expected dpinger for IPv6 to resume to normal operation after the incident and not to remain in STOPPED state.

Is this really intended behaviour or do I have to adjust some options for gateway monitoring?


gateways.log for the affected time:

2023-10-04T10:01:43   Warning   dpinger    send_interval 1000ms  loss_interval 4000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 0ms  loss_alarm 0%  alarm_hold 10000ms  dest_addr 2a00:xxxx:xxxx:xx::1  bind_addr 2a00:xxxx:xxxx:xx::2  identifier "ISP_WAN_GWv6 "
2023-10-04T04:19:50   Warning   dpinger    send_interval 1000ms  loss_interval 4000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 0ms  loss_alarm 0%  alarm_hold 10000ms  dest_addr xx.xx.148.97  bind_addr xx.xx.148.98  identifier "ISP_WAN_GWv4 "
2023-10-04T04:19:50   Warning   dpinger    exiting on signal 15
2023-10-04T04:19:49   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:48   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:47   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:46   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:45   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:44   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:43   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:42   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:41   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:40   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:39   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:38   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:37   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:36   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:35   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:34   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:33   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:32   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 64
2023-10-04T04:19:27   Warning   dpinger    send_interval 1000ms  loss_interval 4000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 0ms  loss_alarm 0%  alarm_hold 10000ms  dest_addr xx.xx.148.97  bind_addr xx.xx.148.98  identifier "ISP_WAN_GWv4 "
2023-10-04T04:19:27   Warning   dpinger    exiting on signal 15
2023-10-04T04:19:26   Warning   dpinger    exiting on signal 15
2023-10-04T04:19:26   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 55
2023-10-04T04:19:25   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:25   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-04T04:19:24   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:24   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-04T04:19:23   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:23   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-04T04:19:22   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:22   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-04T04:19:21   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:21   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-04T04:19:20   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:20   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-04T04:19:19   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:19   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-04T04:19:18   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:18   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-10-04T04:19:17   Warning   dpinger    ISP_WAN_GWv4 xx.xx.148.97: sendto error: 65
2023-10-04T04:19:17   Warning   dpinger    ISP_WAN_GWv6 2a00:xxxx:xxxx:xx::1: sendto error: 50
2023-09-28T08:56:32   Warning   dpinger    send_interval 1000ms  loss_interval 4000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 0ms  loss_alarm 0%  alarm_hold 10000ms  dest_addr xx.xx.148.97  bind_addr xx.xx.148.98  identifier "ISP_WAN_GWv4 "
2023-09-28T08:56:32   Warning   dpinger    send_interval 1000ms  loss_interval 4000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 0ms  loss_alarm 0%  alarm_hold 10000ms  dest_addr 2a00:xxxx:xxxx:xx::1  bind_addr 2a00:xxxx:xxxx:xx::2  identifier "ISP_WAN_GWv6 "


system.log for the affected time

2023-10-04T04:20:15   Warning   opnsense    /usr/local/etc/rc.linkup: warning: ignoring missing default tunable request: debug.pfftpproxy
2023-10-04T04:20:14   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure dns (execute task : unbound_configure_do())
2023-10-04T04:20:14   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure dns (execute task : dnsmasq_configure_do())
2023-10-04T04:20:14   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure dns ()
2023-10-04T04:19:50   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure dhcp (execute task : dhcpd_dhcp_configure())
2023-10-04T04:19:50   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure dhcp ()
2023-10-04T04:19:50   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure ipsec (execute task : ipsec_configure_do(,wan))
2023-10-04T04:19:50   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure ipsec (,wan)
2023-10-04T04:19:50   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure monitor (execute task : dpinger_configure_do(,ISP_WAN_GWv4))
2023-10-04T04:19:50   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure monitor (,ISP_WAN_GWv4)
2023-10-04T04:19:50   Warning   opnsense    /usr/local/etc/rc.linkup: The required ISP_WAN_GWv6 IPv6 interface address could not be found, skipping.
2023-10-04T04:19:50   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure monitor (execute task : dpinger_configure_do(,ISP_WAN_GWv6))
2023-10-04T04:19:50   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure monitor (,ISP_WAN_GWv6)
2023-10-04T04:19:50   Notice   opnsense    /usr/local/etc/rc.linkup: ROUTING: keeping inet6 default route to 2a00:xxxx:xxxx:xx::1
2023-10-04T04:19:50   Notice   opnsense    /usr/local/etc/rc.linkup: ROUTING: configuring inet6 default gateway on wan
2023-10-04T04:19:50   Notice   opnsense    /usr/local/etc/rc.linkup: ROUTING: setting inet default route to xx.xx.148.97
2023-10-04T04:19:50   Notice   opnsense    /usr/local/etc/rc.linkup: ROUTING: configuring inet default gateway on wan
2023-10-04T04:19:49   Notice   opnsense    /usr/local/etc/rc.linkup: ROUTING: entering configure using 'wan'
2023-10-04T04:19:49   Notice   opnsense    /usr/local/etc/rc.linkup: DEVD: Ethernet attached event for wan(re0)
2023-10-04T04:19:49   Notice   kernel    <6>re0: link state changed to UP
2023-10-04T04:19:46   Notice   opnsense    /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for wan(re0)
2023-10-04T04:19:45   Notice   kernel    <6>re0: link state changed to DOWN
2023-10-04T04:19:32   Warning   opnsense    /usr/local/etc/rc.linkup: warning: ignoring missing default tunable request: debug.pfftpproxy
2023-10-04T04:19:32   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure dns (execute task : unbound_configure_do())
2023-10-04T04:19:32   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure dns (execute task : dnsmasq_configure_do())
2023-10-04T04:19:32   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure dns ()
2023-10-04T04:19:27   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure dhcp (execute task : dhcpd_dhcp_configure())
2023-10-04T04:19:27   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure dhcp ()
2023-10-04T04:19:27   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure ipsec (execute task : ipsec_configure_do(,wan))
2023-10-04T04:19:27   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure ipsec (,wan)
2023-10-04T04:19:27   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure monitor (execute task : dpinger_configure_do(,ISP_WAN_GWv4))
2023-10-04T04:19:27   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure monitor (,ISP_WAN_GWv4)
2023-10-04T04:19:27   Warning   opnsense    /usr/local/etc/rc.linkup: The required ISP_WAN_GWv6 IPv6 interface address could not be found, skipping.
2023-10-04T04:19:26   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure monitor (execute task : dpinger_configure_do(,ISP_WAN_GWv6))
2023-10-04T04:19:26   Notice   opnsense    /usr/local/etc/rc.linkup: plugins_configure monitor (,ISP_WAN_GWv6)
2023-10-04T04:19:26   Notice   opnsense    /usr/local/etc/rc.linkup: ROUTING: keeping inet6 default route to 2a00:xxxx:xxxx:xx::1
2023-10-04T04:19:26   Notice   opnsense    /usr/local/etc/rc.linkup: ROUTING: configuring inet6 default gateway on wan
2023-10-04T04:19:26   Notice   opnsense    /usr/local/etc/rc.linkup: ROUTING: setting inet default route to xx.xx.148.97
2023-10-04T04:19:26   Notice   opnsense    /usr/local/etc/rc.linkup: ROUTING: configuring inet default gateway on wan
2023-10-04T04:19:26   Notice   opnsense    /usr/local/etc/rc.linkup: ROUTING: entering configure using 'wan'
2023-10-04T04:19:26   Notice   opnsense    /usr/local/etc/rc.linkup: DEVD: Ethernet attached event for wan(re0)
2023-10-04T04:19:26   Notice   kernel    <6>re0: link state changed to UP
2023-10-04T04:19:17   Notice   opnsense    /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for wan(re0)
2023-10-04T04:19:16   Notice   kernel    <6>re0: link state changed to DOWN

283

German - Deutsch / Re: Externe Domain als Portweiterleitung auch von Intern als Domain erreichen

« on: October 03, 2023, 11:41:51 am »

Alternativ, DNS für die Domain überschreiben, das intern die interne IP aufgelöst wird.

Geht in unbound, Stichwort host override
https://docs.opnsense.org/manual/unbound.html

284

23.7 Legacy Series / Re: New setup - WIP and need help

« on: October 01, 2023, 01:48:02 pm »

Hi,

I am sorry for the poor performance of your setup. It is hard to say what goes wrong here.

In order to continue research I'd check configuration of LAN IF to match DHCP server config on LAN an check that an IP is reliably assigned to a connecting device. If that doesn't work, check cabling, jacks, NICs or configure speed manually. This can be done on Interfaces -> [LAN]

Interface diagnostics and DHCP log could give more insight in case.

Done achieving that repeat the same for WAN. But not as dhcp server. Configure client instead, switch off dhcp server for WAN!

USB is not known to be the most reliable. Sometimes, power configuration can be tricky. Iirc someone mentioned to switch off powerD to get USB to work stable.

Just done thoughts.

285

23.7 Legacy Series / Re: New setup - WIP and need help

« on: September 30, 2023, 09:36:37 am »

Hi,

I see a lot of randomness here and yes, realtek may or may not work. E.g.: Experienced breaking pppoe on realtek before whenever I started bulk operations like downloading more than 10MB sized files.

However, my actual setup runs fine with two realteks.

Anyway what happens if you manually configure the networking to 1000BaseT (on the 2,5) or even 100Base-T. Seems as if something is having trouble working continuously without errors.

I would also simplify the setup to a very simple one: LAN Client connected to OPNsense. Do dhcp and webgui work fine now?