Messages

1

General Discussion / Re: Opnsense not booting. Filesystem dirty

« on: July 05, 2023, 04:57:29 pm »

Took a few days to find time. Installed fresh and loaded backup.

System now works as expected. Got stuck during search for updates again, remembered I read somewhere to change setting to prefer ipv4 over ipv6. This resolved the updating problem as well

Thanks for your support

Gesendet von meinem ONEPLUS A6013 mit Tapatalk

2

General Discussion / Re: Opnsense not booting. Filesystem dirty

« on: July 02, 2023, 12:36:13 pm »

I have googled, yes. I have backups, yes

I tried resetting to factory defaults by moving config.xml to config.bak but this does not fix the filesystem error

Maybe there's still a way to fix the filesystem. If not, I'll format and reinstall

Gesendet von meinem ONEPLUS A6013 mit Tapatalk

3

General Discussion / Opnsense not booting. Filesystem dirty

« on: July 02, 2023, 12:19:59 pm »

My Opnsense froze during an update and does not boot properly since.

Fsck in read only shows dirty filesystem, but cannot repair due to expansion failing, see screenshot

Any help appreciated, I am at slightly above beginner level. Thank you for your consideration

Gesendet von meinem ONEPLUS A6013 mit Tapatalk

4

22.7 Legacy Series / Re: [SOLVED] Unable to access second upstream router GUI and network

« on: October 21, 2022, 02:10:08 pm »

yes, both are accessible. Added a route for both networks so I can access both in any case

5

22.7 Legacy Series / Re: [SOLVED] Unable to access second upstream router GUI and network

« on: October 21, 2022, 01:43:47 pm »

Solution: I had an outgoing allow all rule on my WAN1 interface. After deleting it access worked

Thank you for your support

6

22.7 Legacy Series / Re: Unable to access second upstream router GUI and network

« on: October 21, 2022, 01:40:02 pm »

A traceroute from my PC to the WAN_LTE router hops to the LAN interface on OPNsense and then times out

7

22.7 Legacy Series / Re: Unable to access second upstream router GUI and network

« on: October 21, 2022, 01:36:23 pm »

Yes, the Fritzbox is accessible. What's not accessible is the second WAN_LTE

8

22.7 Legacy Series / Re: Unable to access second upstream router GUI and network

« on: October 21, 2022, 01:22:19 pm »

These are screenshots for my settings at LAN0/Rules, gateways and rules. I cannot acess the net of the second WAN even when the standard WAN is deactivated, so it is the standard gateway in that condition.

9

22.7 Legacy Series / [SOLVED] Unable to access second upstream router GUI and network

« on: October 21, 2022, 12:56:37 pm »

[Solution: I had an outgoing allow all rule on my WAN1 interface. After deleting it access worked]

Background: I have set up OPNsense in my homelab to learn how it works and become familiar with the settings.

It is set up behind my ISP cable router on WAN0. WAN0 gets an IP address via DHCP from the upstream cable router. From a PC connected to LAN0 I can access the WAN0 net, the internet as well as the cable router's web GUI.

Now here is my problem: I connected a second upstream router (LTE) to WAN1 which shall ultimately act as a failover for when my primary cable connection drops out. But for now all I want is to access the second router's web GUI. WAN1 is set exactly like WAN0 and gets an IP address via DHCP from the LTE router on a different net (see below). There are no conflicts in the IP addresses as far as I can tell. Accessing the web GUI is not possible. OPNsense shows that the WAN1 interface receives an IP from the DHCP server (DHCP server address is identical to the one I am trying to access)

Here is what I tried and what failed so far:

- I created rules to allow all in all out for WAN1 and LAN0

- I set WAN1 as gateway with a higher priority than WAN0 (lower number=higher priority).

- I disabled WAN0 completely

WAN0 net: 192.168.178.0/24. DHCP at 192.168.178.1. Internet and WAN0 net devices accessible
WAN1 net: 192.168.1.0/24. DHCP at 192.168.1.1. WAN1 devices not accessible
LAN0 net: 10.10.0.0/24. Device from where I am trying to access is at 10.10.0.100