Messages

1

22.1 Legacy Series / Re: MultiWAN: Access explicity to network of WAN2

« on: April 27, 2022, 10:23:38 am »

Hi everybody.

So no idea yet? I've set up 2 routes:

• 192.168.178.1/24 to WAN
• 192.168.188.1/24 to WAN2

But still only one of both Gateway is accesible so the route setting didn't help.

Really nobody with an idea? Or is this a missing feature of OPNSense?

Best regards
Floh

2

22.1 Legacy Series / MultiWAN: Access explicity to network of WAN2

« on: March 04, 2022, 10:51:57 am »

Hello I just set up MultiWAN Group with WAN as Tier1 and WAN2 as Tier2 and defined monitoring for both interfaces. I also changed the Gateway to MultiWAN Group for the rule for LAN.

I'm still online, and everything is fine (over WAN). Currently WAN2 is not online yet (its new and a technician is on the way here, to set up the phone line). Well, I'd like to access the Router of WAN2, so I can setup it from LAN network. OPNsense is able to ping the router connected at WAN2.

But I'm routed to WAN instead to WAN2 from LAN. I found out this with the help of traceroute:

Code: [Select]

traceroute 192.168.188.1
traceroute to 192.168.188.1 (192.168.188.1), 64 hops max, 52 byte packets
 1  opnsense (192.168.100.1)  0.792 ms  0.165 ms  0.153 ms
 2  fritz.box (192.168.178.1)  1.336 ms  0.727 ms  1.388 msThere you see, the traceroute went to 192.168.178.1 which is WAN.
WAN = 192.168.178.1/24
WAN2 = 192.168.188.1/24

I'd expect, if I use destination address which is in network range of WAN2, then opensense would route to WAN2 no matter if the gateway of WAN2 is down.

Best regards
Floh

3

21.7 Legacy Series / openVPN: Route not being added/pushed

« on: August 23, 2021, 01:48:27 am »

Hello I'm almost there. I did setup openVPN on server and exported the ovpn file and imported this on client machine. So far so good.

Unfortunately the route is not set if the connection is estabilished. If I add the route manually on the client side as following...

Code: [Select]

ip route add 192.168.100.0/24 via 10.0.100.1... then I can access the remote machines. So what am I missing?

I did make sure to enter the IPv4 Local Network:


Best regards
Floh

4

21.7 Legacy Series / Re: Tunables: vfs.zfs.trim 0 doesn't work

« on: August 16, 2021, 12:16:04 pm »

Stupid me...

WRONG:

Code: [Select]

vfs.zfs.trim 0
Correct:

Code: [Select]

vfs.zfs.trim.enabled 0
Now it's working as expected.

cu Floh

5

21.7 Legacy Series / Tunables: vfs.zfs.trim 0 doesn't work

« on: August 16, 2021, 12:04:28 pm »

Hello, I need to turn of trim because the ssd doesn't support TRIM. *sigh*

I added an entry in tuneables:
vfs.zfs.trim 0

But it didn't affect and trim is still enabled and I get errors:

Code: [Select]

ahcich0: Timeout on slot 30 port 0
ahcich0: is 00000000 cs 00000000 ss 40000000 rs 40000000 tfd 50 serr 00000000 cmd 0000c817
(ada0:ahcich0:0:0:0): SEND_FPDMA_QUEUED DATA SET MANAGEMENT. ACB: 64 01 00 00 00 40 00 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: Command timeout
(ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain
ahcich0: Timeout on slot 15 port 0
ahcich0: is 00000000 cs 00000000 ss 00008000 rs 00008000 tfd 40 serr 00000000 cmd 0000cf17
(ada0:ahcich0:0:0:0): SEND_FPDMA_QUEUED DATA SET MANAGEMENT. ACB: 64 01 00 00 00 40 00 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: Command timeout
(ada0:ahcich0:0:0:0): Retrying command, 2 more tries remain
ahcich0: Timeout on slot 22 port 0
ahcich0: is 00000000 cs 00000000 ss 00400000 rs 00400000 tfd 40 serr 00000000 cmd 0000d617
(ada0:ahcich0:0:0:0): SEND_FPDMA_QUEUED DATA SET MANAGEMENT. ACB: 64 01 00 00 00 40 00 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: Command timeout
(ada0:ahcich0:0:0:0): Retrying command, 1 more tries remain
ahcich0: Timeout on slot 29 port 0
ahcich0: is 00000000 cs 00000000 ss 20000000 rs 20000000 tfd 40 serr 00000000 cmd 0000dd17
(ada0:ahcich0:0:0:0): SEND_FPDMA_QUEUED DATA SET MANAGEMENT. ACB: 64 01 00 00 00 40 00 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: Command timeout
(ada0:ahcich0:0:0:0): Retrying command, 0 more tries remain
ahcich0: Timeout on slot 4 port 0
ahcich0: is 00000000 cs 00000000 ss 00000010 rs 00000010 tfd 40 serr 00000000 cmd 0000c417
(ada0:ahcich0:0:0:0): SEND_FPDMA_QUEUED DATA SET MANAGEMENT. ACB: 64 01 00 00 00 40 00 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: Command timeout
(ada0:ahcich0:0:0:0): Error 5, Retries exhausted
I doublechecked:

Code: [Select]

root@OPNsense:~ # sysctl vfs.zfs.trim
vfs.zfs.trim.max_interval: 1
vfs.zfs.trim.timeout: 30
vfs.zfs.trim.txg_delay: 32
vfs.zfs.trim.enabled: 1

Code: [Select]

root@OPNsense:~ # grep trim /boot/loader.conf
vfs.zfs.trim="0"
Hm, whats wrong here?

Best regards
Floh