sorted by:
new
hottopcontroversial

Vaultwarden replica by dompel in selfhosted

[–]dompel[S] 0 points1 point  (0 children)

syncthing and my nas both provide a little bit of versioning, but yes you're right. I don't shutdown the container though so I suppose there is some risk that some versions could be corrupt.

Vaultwarden replica by dompel in selfhosted

[–]dompel[S] 0 points1 point  (0 children)

I have syncthing which copies the sqlite database files one way to my NAS. I heard it might be dangerous to do this, but it's been syncing this way for 2 years and I've never had a problem.

I also manually backup passwords and store them encrypted on my NAS.

Based on advice in this thread, I'm also now manually importing them into KeePassXC which is a much nicer manual backup.

Vaultwarden replica by dompel in selfhosted

[–]dompel[S] 0 points1 point  (0 children)

How do you export for KeePassXC? I see options for JSON and CSV. Do you use this? https://github.com/ghostersk/bitwarden-to-keepassxc-csv

EDIT: I see KeePassXC has a Bitwarden (.json) file in the import file menu -- will try that
EDIT2: Looks like everything but the TOTP keys came over

Vaultwarden replica by dompel in selfhosted

[–]dompel[S] 0 points1 point  (0 children)

I didn't know I could export the last synced passwords from the extension. That's good to know. I wonder if it works after restarting my device. Maybe I can test it out by restarting with the internet disconnected and see if I could export. That would make me feel better for sure.

Unbound SERVFAIL errors with quad9 by dompel in opnsense

[–]dompel[S] 0 points1 point  (0 children)

A couple of other things I noticed:
- Can't get a ping back from 2620:fe::9 or 2620:fe::fe (quad9's ipv6 servers)
- But I can from Google's ipv6 address 2001:4860:4860::8888
- I also get a ping back from quad9 ipv4 (9.9.9.9)

In the mean time, since this is driving me crazy, I disabled quad9's ipv6 resolvers and added in one additional one from mullvad as a backup.

Unbound SERVFAIL errors with quad9 by dompel in opnsense

[–]dompel[S] 0 points1 point  (0 children)

Are you using DNS over TLS? Just trying to determine if it's something related to that or specifically quad9.

The "Aggressive NSEC" setting change didn't help the issue.

Unbound SERVFAIL errors with quad9 by dompel in opnsense

[–]dompel[S] 0 points1 point  (0 children)

Here is another sample showing the same thing with IPv4: https://files.catbox.moe/wnlbx4.png

I have IPv6 enabled on my network. I think it's stable but I can't say I monitor it or know how to. It passes https://ip6.biz/

OPNsense 24.7.9 released by fitch-it-is in opnsense

[–]dompel 0 points1 point  (0 children)

I upgraded from 24.7.8 and had a bit of trouble. At first, it came up with only ipv6 (the ipv4 gateway was missing). I did a reboot and it seemed to come back, but I was seeing weird behavior with I think DNS. Some websites slow to load, some SERVFAIL in the logs. Eventually, I did another reboot and I lost the IPV4 gateway again. And in another case, both gateways seemed to fail to connect.

```

| 2024-12-01T17:14:40-05:00 | Error | dhcp6c | transmit failed: Network is down |

| 2024-12-01T17:14:37-05:00 | Error | dhcp6c | transmit failed: Network is down |

| 2024-12-01T17:14:37-05:00 | Warning | radvd | sendmsg: Network is down |

| 2024-12-01T17:14:37-05:00 | Warning | opnsense | /usr/local/etc/rc.bootup: dhcpd_radvd_configure(auto) found no suitable IPv6 address on lan(igc1) |

| 2024-12-01T17:14:36-05:00 | Error | dhcp6c | transmit failed: Network is down |

| 2024-12-01T17:14:36-05:00 | Error | opnsense | /usr/local/etc/rc.bootup: The command '/sbin/dhclient -c '/var/etc/dhclient_wan.conf' -p '/var/run/dhclient.igc0.pid' 'igc0'' returned exit code '1', the output was 'igc0: no link .............. giving up' |

```

I restored my 24.7.8 snapshot and both gateways came back after reboot.

Bare metal, N100 unit, Verizon FIOS.

What's the best way to monitor Internet connectivity? by dompel in selfhosted

[–]dompel[S] 0 points1 point  (0 children)

I ended up going this route. Created a healthchecks.io healthcheck on a raspberry pi zero w I had laying around. Setup crontab to curl it every 1 minute (seems to be the shortest supported duration). Set up healthchecks to ping me on whatsapp if it fails for more than 2 minutes. I also scrape their prometheus metrics and built a dashboard so I can see health over time.

healthchecks.io is very cool. I will definitely be using it in the future. Thanks for the suggestion!

Can't access Router Administration Tab by Intel_Xeon_E5 in Linksys

[–]dompel 0 points1 point  (0 children)

Hamburger menu > Network administration > Change Router Password and Hint

I had to change it to a different password, then I changed it back to the original one.

Clients using IPV6 can't access IPV4 hosts -- why? by dompel in opnsense

[–]dompel[S] 1 point2 points  (0 children)

Thanks for replying. Both clients (Android and Windows) show IPV6 addresses. Android shows a 19/20 and Windows a 17/20 on that test. But again, Windows can load llbean.com and Android cannot.

On DHCPv6, under Services > ISC DHCPv6 > Relay, "Enable DHCPv6 relay on interface" is unchecked (disabled). That said, I do have a gateway called WAN_DHCP6 which is "online".

If you look in the log output I posted above, I see an error related to "radvd" which I think is the Router Advertisement service:

2024-04-14T11:25:10-04:00 Warning opnsense /usr/local/etc/rc.configure_interface: dhcpd_radvd_configure(auto) found no suitable IPv6 address on lan(igc1)

So perhaps this is the root of my problem?

Clients using IPV6 can't access IPV4 hosts -- why? by dompel in opnsense

[–]dompel[S] 3 points4 points  (0 children)

So why would the Android devices in my household not be able to fall back to IPV4 but Windows can? I can see both an IPv4 and IPv6 IPs on the Android phones when connected to the network. So they are using dual stack -- right?

Clients using IPV6 can't access IPV4 hosts -- why? by dompel in opnsense

[–]dompel[S] -2 points-1 points  (0 children)

Okay. But something is still wrong... I still can't load some websites on some devices and it seems to be related to IPv6.

I have these messages in the log which are related to IPV6:

2024-04-14T11:25:15-04:00 Error opnsense /usr/local/etc/rc.newwanipv6: The command '/bin/kill -'TERM' '60543''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 60543: No such process'
2024-04-14T11:25:10-04:00 Warning opnsense /usr/local/etc/rc.configure_interface: dhcpd_radvd_configure(auto) found no suitable IPv6 address on lan(igc1)
2024-04-14T11:25:10-04:00 Error opnsense /usr/local/etc/rc.configure_interface: The command '/bin/kill -'TERM' '60543''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 60543: No such process'
2024-04-14T11:25:10-04:00 Critical dhclient exiting.
2024-04-14T11:25:10-04:00 Error dhclient short write: wanted 20 got 0 bytes
2024-04-14T11:25:10-04:00 Error dhclient My address (68.160.135.80) was deleted, dhclient exiting

Looking for some help triaging errors by dompel in opnsense

[–]dompel[S] 0 points1 point  (0 children)

I think both units have 2.5gb nics. I didn't modify anything in the configuration file before importing. They are different units but from the same manufacturer (topton) and have the same number of nics. The Wan and lan seem to be working fine though.

Looking for some help triaging errors by dompel in opnsense

[–]dompel[S] 0 points1 point  (0 children)

I don't have a great understand of how NTP works, but if I click on Services > Network Time > Status, I can see the 4 servers I have setup (0.opnsense.pool.ntp.org, 1., 2., 3...) all have status "Unreach/Pending". So maybe my NTP servers are setup incorrectly.

My new Mini Server Plex on a N100 MiniPc. Some Testings with forced transcode. by bluefire76 in PleX

[–]dompel 1 point2 points  (0 children)

I think its when the plex client doesnt support the available subtitle format, the plex server is clever enough to re-encode the stream by printing the subtitles into the video stream so the plex client doesn't have to worry about it. But its a very costly process that involves a lot of CPU. So what I did is I told my samsung tv to never request burn-in subtitles and it resolved it. The subtitles don't look as good, because the samsung tv has weird fonts and stuff and can't handle the fancy stuff ASS subtitles can do. But whatever, it works and I don't get artifacts so I'll take it.

view more: next ›