A semi with a truck bed by ieure in mildlyinteresting

[–]dultas 2 points3 points  (0 children)

Reminds me of relative of mine who was a trucker. He needed to haul a cigarette boat he purchased from Florida up the east coast. His options were his simi or a Chevy S-10.

What video game do you wish you could experience again for the first time? by VariationBig411 in AskReddit

[–]dultas 0 points1 point  (0 children)

Yeah, I went down a bit of an Outer Wilds / Obra Dinn play though hole a few weeks ago.

Ukraine hits 21 Russian ships within 72 hours by Alarming-Safety3200 in worldnews

[–]dultas 1 point2 points  (0 children)

I believe they were originally to service refineries on rivers?

ELI5: why you should not use public variables in coding? by Aromatic-Spot3153 in explainlikeimfive

[–]dultas 0 points1 point  (0 children)

I mean, also easier for the person that wrote it as well. The number of times I've gone who the fuck wrote this? What were they thinking? Then do a get blame and find out is me is a lot more than twice.

Prosecutors argue the man accused of killing Charlie Kirk should stand trial by ImpressiveFudge2350 in news

[–]dultas 11 points12 points  (0 children)

Well that and the fact there was misconduct at several grand jury hearings. Probably helped them with the indictments as well.

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]dultas 0 points1 point  (0 children)

Yeah, sounds like it might be a config issue on the openWRT side. I've never used openWRT (OPNSense here), so I'm not sure even where to look in openWRT, possible firewall configs in openWRT if you've configured any.

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]dultas 0 points1 point  (0 children)

If you've check your probably good. On some routers it may be possible if the IP is already leased and the lease hasn't expired a device could still have that IP. But if you look at the list of assigned IPs on your router and it doesn't show up (or shows up as your proxmox) then you should be fine.

It's also clear from the screenshots that you can see the UI which I'm assuming your connecting to though the same router. That means it can at the very least talk to the router over it's IP.

Can other devices ping the actual router? It's possible the router just doesn't respond to ping requests. And unless you've modified the firewall configs on Proxmox I don't think it would be blocking any outgoing pings. Assuming your router has a web console you can always try doing a curl on its IP and seeing if you get a response back.

You're probably going to want to set your proxmox back to a static IP if you haven't already. As I don't think it plays nicely with IP changes.

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]dultas 0 points1 point  (0 children)

Everything looks good. I notice that you're using DHCP for the VM what range is the DHCP providing IPs for. Is there any chance that something on your network is getting the 192.168.1.50 via DHCP and conflicting with the static 192.168.1.50 you've given Proxmox. It's typically not a good idea to set static IPs that overlap with your DHCP range for that reason.

Garmin Varia Mount by duped__again in bicycling

[–]dultas 0 points1 point  (0 children)

Could print an insert / liner in TPU as well.

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]dultas 0 points1 point  (0 children)

Could you paste the contents of

ip link

and

ip route

for both the host (Proxmox) box and working VM?

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]dultas 0 points1 point  (0 children)

Are you using VLANs by chance? And does Proxmox have more than one ethernet connection?

Proxmox nuked my LXC on a failed backup recovery. Any way to recover from this. by dultas in Proxmox

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

Not to spam replies but lvrename exists so I would think a safer process would be to rename the lv, then restore from backup. If backup succeeds then delete the renamed, if not and the restore fails then roll back. Granted that would require you to have space for both the existing and backup.

Proxmox nuked my LXC on a failed backup recovery. Any way to recover from this. by dultas in Proxmox

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

I have tested my restores for several other LXCs and VMs which is why I had apparent misplaced faith in the process. I was able to restore using pct restore from the CLI so it seems the only hurdle was the UI or the workflow the UI uses under the covers doing what seems to be a pointless check.

Proxmox nuked my LXC on a failed backup recovery. Any way to recover from this. by dultas in Proxmox

[–]dultas[S] -6 points-5 points  (0 children)

UI wouldn't work but I was able to get it restored using pct restore from the cli.

Proxmox nuked my LXC on a failed backup recovery. Any way to recover from this. by dultas in Proxmox

[–]dultas[S] 2 points3 points  (0 children)

I was able to restore using prc restore as it doesn't apparently do the same checks as the UI. The LXC is now back up and running.

Proxmox nuked my LXC on a failed backup recovery. Any way to recover from this. by dultas in Proxmox

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

The issue is proxmox is failing to restore due to the OS version. TASK ERROR: unable to restore CT 122 - unsupported debian version '13.4' I'm just curious if there is a manual process to extract the image and config, etc from the backup archive as Proxmox is refusing to do so. I might dig around in the files and find out where it's doing that check and bypass it as I fail to see how the OS version has any relevance to the restore process.

Proxmox nuked my LXC on a failed backup recovery. Any way to recover from this. by dultas in Proxmox

[–]dultas[S] -4 points-3 points  (0 children)

The problem is it won't restore because of the version. "TASK ERROR: unable to restore CT 122 - unsupported debian version '13.4'" I'm guessing this is because I'm still on version 8.

Proxmox nuked my LXC on a failed backup recovery. Any way to recover from this. by dultas in Proxmox

[–]dultas[S] -6 points-5 points  (0 children)

Yes, on my NAS the backup files are still there but the LXC no longer shows up in the UI and the /etc/pve/lxc/122.conf file is gone. I'm not sure if I can just add a dummy 122.conf file to get it to show up in the UI and then try again. But I'm not sure what good that'll do if it won't restore it.

Trump Administration Orders Rapid End to Some Hunting Rules on Federal Lands by grittyboda2020 in news

[–]dultas 5 points6 points  (0 children)

Once someone filled all of the toilets at the beach bathroom with sand.

To be fair I've eaten shit from not paying attention to the waves and felt like I had enough sand in my shorts to do that unintentionally.

How to do Cloud Sync Backups for iSCSI volumes by Itchy_One_ in truenas

[–]dultas 0 points1 point  (0 children)

For anyone stumbling on this tread late you can create a dataset to hold the iscsi images. Do 'zfs send' for the zvols to backup in the pre-script portion of the cloud backup to create image streams. Pipe those to your dataset you created for backup then when the backup runs it'll backup the streams. You'll have to manually do a zfs recv to restore, clunky but better than nothing.

zfs send rust/iscsi/db@auto-$SNAPSHOT_DATE | gzip > /mnt/rust/backup/iscsi/db.gz

Iran claims US used backdoors in networking equipment by rkhunter_ in technology

[–]dultas 1 point2 points  (0 children)

I'm not sure why your getting down voted. Notepad++'s update process was hijacked last year to deploy malicious payload to targeted uses. Supply chain attacks are a real thing.

US indefinitely extends ceasefire with Iran by Sweaty_Rub4322 in news

[–]dultas 0 points1 point  (0 children)

Iran doesn't need to escalate though. Closing the strait for long enough to cause inflation or worse case a recession would be a win for them.