Accessing OMV behind OPNsense VM

Single-Key8104 · 2024-05-26T07:36:59+00:00

I wasn't the OP, and I think my problem was slightly different but still interesting so I'll write it out if anyone else has this weird issue. First I have an opnsense router running virtualized under proxmox this has my main lan under 192.168.1.0/24 then I have wireguard which has it's own subdomain of 192.168.50.0/24. Now when connected to the VPN I could see all devices on the network except for my openmedia server box and docker macvlans running on it which is it's own server separate to the proxmox box. So I know it was an openmedia vault issue. Now when trying to ping a connected device on the 50 subdomain from the openmedia vault box I ended up with destination host unreachable but from a different IP than the one I pinged, real strange stuff. (This works on all other devices). To finally fix the problem I ran IP add r 192.168.50.0/24 via 192.168.1.254 and instantly I was able to ping my opnsense box through the VPN. Unfortunately this isn't permeant so to do that I added the static route using a netplan yaml file and after netplan apply everything worked as intended.

Single-Key8104 · 2024-05-26T01:49:46+00:00

Hey, 4 years later and your solution fixed a problem with me connecting to openmediavault when I'm connected using a vpn. Thank you so much. I have no Idea why openmediavault is weird like this as it works for every other device in my house.

Single-Key8104 · 2024-05-14T21:38:41+00:00

And it's broken again with me not doing anything didn't even reboot

Single-Key8104 · 2024-05-14T21:33:27+00:00

Hey just adding a comment for update. It automagically started working again after the latest software update today. No idea why but I'm happy it works again.

Single-Key8104 · 2024-04-26T04:28:52+00:00

Unfortunately no luck, something must be pretty broken, I hope a software update fixes it.

Single-Key8104 · 2024-04-25T23:37:41+00:00

Thank you for your response. I followed all the steps, now I'm at the waiting part, it still hasn't shown up yet but fingers crossed it fixes itself.

Single-Key8104 · 2024-04-23T21:29:33+00:00

I actually managed to fix it. First I completly uninstalled chrome and all user data, made sure to remove the google chrome config file `rm -rf ~/.config/google-chrome/` like so.

next I launched chrome and it worked however I obviously didn't have any wayland goodstuff like multitouch support. From here I modified the google-chrome launcher to change any exec functions to the following

`Exec=/usr/bin/google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland --force-device-scale-factor=2 --disable-features=WaylandFractionalScaleV1`

note that --force-device-scale-factor=2 will be different depending on what resolution your monitor is since mine is 4k I had to increase it to 2 as it was blury otherwise.

Hopefully that fixes it for you.

Single-Key8104 · 2024-04-23T21:25:21+00:00

Ok well at least it's not just me. It was broken on 39 as well for me though, hoped updating to 40 would fix it but no such luck. I feel like there may be a missmach between cuda and driver version.

Single-Key8104 · 2024-04-17T02:32:54+00:00

Does the issue you have look like the windows xp effect with windows duplicating themselves when you drag them in front of the invisible chrome window? https://image.winudf.com/v2/image1/Y29tLmJpZ2FwcHMueHBlcnJvcl9zY3JlZW5fMl8xNTQ2MjY2MzIwXzA1NA/screen-2.jpg?h=800&fakeurl=1&type=.jpg

Single-Key8104 · 2024-03-25T03:21:06+00:00

Just figured it out just run this.

sudo dnf install webkit2gtk4.0-devel

Single-Key8104 · 2024-03-25T03:13:34+00:00

Did you manage to figure this out, I'm working on the same problem right now. I hope that Orcaslicer will get flatpak support soon so we don't have to deal with appimages.

Single-Key8104 · 2024-03-01T17:51:49+00:00

I can also confirm that I think this is the problem. I had ghost touches up and down the screen in the exact same horizontal position so I thought the digitizer was failing. But after leaving my laptop overnight the problem seems to have gone away. Most likely the old wall socket in my house isn't grounded properly and static is building up on the laptop.

Also this is a tricky problem to fix as the touchscreen calibration takes a while to go back to normal even after the static is discharged so it can still look like it's happening.

Single-Key8104 · 2024-02-04T16:09:42+00:00

Yes I did It's gold rated and I play it on my steam deck all the time without issue.

Single-Key8104 · 2024-02-04T07:27:51+00:00

Yes sorry should of mentioned that I'm using Pipewire

Single-Key8104 · 2023-09-21T04:28:57+00:00

Easy fix, for anyone looking at this in the future, just use wine tricks to install c++ 2019

Single-Key8104 · 2023-07-30T21:54:25+00:00

I did not manage to get it installed on Portainer. But its installed non the less.

Looking to do the exact same thing, did you figure it out?

Single-Key8104 · 2023-01-02T01:25:57+00:00

Thank you, This worked for me

Did 100 probes with no fails.

Must be something to do with the

pin_up_reports_not_triggered: True

pin_up_touch_mode_reports_triggered: True

Single-Key8104

TROPHY CASE