DreadPotato

joined 1 year ago
[–] DreadPotato@sopuli.xyz 2 points 7 months ago* (last edited 7 months ago) (1 children)

I just swipe left for "back" (android), and I can access everything just fine, it just closes the TOS. Just do that every time I open the app, works like a charm.

[–] DreadPotato@sopuli.xyz 5 points 7 months ago

But then you don't want face-melting lasers.

Now hold on...I can see that being useful too. Two consecutive failed face IDs? BAM!!!* face melting laser on the (probably) unauthorized person trying to access your phone.

[–] DreadPotato@sopuli.xyz 1 points 7 months ago* (last edited 7 months ago)

Because the implication is, that Tesla isn't doing something bad WRT how they designed the stalls? IDK, anything that's not bashing Tesla directly seems to get down voted here, even if it's not actually related specifically to Tesla.

[–] DreadPotato@sopuli.xyz 3 points 7 months ago* (last edited 7 months ago) (2 children)

It is objectively safer to park like that (charging or not). Most parking lot accidents happens as someone leaves the parking spot. The risk of accidents when leaving the parking spot is significantly reduced compared to parking front first.

[–] DreadPotato@sopuli.xyz 7 points 7 months ago (1 children)

It was actually quite well planned out, opening up the network in stages to see that everything worked as intended before a wide rollout. You can even see in the app which chargers are open to other car brands. This mistake is 100% on the driver, the info is easily available to that person.

[–] DreadPotato@sopuli.xyz 13 points 7 months ago* (last edited 7 months ago)

My dad is pretty unhappy with his Mercedes EQS which costs significantly more than the model S, it also had issues with loose interior trim and panel gaps. And despite the fairly high price point its still riddled with shitty plastic interior. It kind of feels like all manufacturers are rushing stuff out the door at the cost of QC.

[–] DreadPotato@sopuli.xyz 1 points 7 months ago (1 children)
[–] DreadPotato@sopuli.xyz 1 points 7 months ago (1 children)

That image is not mine, it's just for reference by the other user to show me where to look

[–] DreadPotato@sopuli.xyz 1 points 7 months ago (3 children)

Nothing, and it just reports 100% packet loss when I terminate the ping command.

[–] DreadPotato@sopuli.xyz 1 points 7 months ago

as far as i can tell from the output, i think my DNS is working?

[–] DreadPotato@sopuli.xyz 1 points 7 months ago

this is the contents of the interfaces file

I don't have anythiung seperated in to different VLANs, and i only use this single subnet. all other devices can ping outbound without issues.

[–] DreadPotato@sopuli.xyz 1 points 7 months ago (5 children)
 

[SOLVED] Turns out I'm just a bigger moron than I thought. The MAC address of my server had accidentally been flagged in my router for black listing.

As the title says, my proxmox host is apparently not able to reach the internet anymore, not sure for how long this has been an issue, I rarely work on the host itself. It can ping other devices on my network just fine, and other devices can ping it. I can also SSH in to it and access the web interface. My VMs are connected to the internet without any issues. I don't need to access the host remotely/outside my home network, this is just for updating it etc.

I can't see the host under active devices in my router though.

I have been trying to figure why, but so far without any luck.

 

I am just getting back my sea legs, but apparently they're pretty shaky because I can't get my ubuntu torrent (no seriously, it is) to download. It never starts downloading and is stuck in "stalled". I've tried a number of things, but even with default settings it isn't starting. I'm using proton VPN on Linux Mint, but even with the VPN disabled it doesn't work.

last time I torrented was probably 15 years ago.

EDIT: i managed to get it working. As expected it was a Qbit config issue. First issue was a port forwarding issue. second one was the interface i connected it to. Apparently the interface named something with "vpn" is not the correct one to bind Qbit to, its a dummy created by the VPN that doesn't work. I had to select one named "tun0". If i just selected the regular physical interface I had IP leaks with the VPN enabled.

view more: next ›