r00ty

Humans? I knew it! Even when it was the bears, I knew it was them!

Killing for your government: Government will track you down, kick your door in and throw you in prison for refusing to.

Fixed thar for you :P

So between 0 and 20. 😛

Pretty sure mine was 16399753. But, not logged in for probably 15 or more years, so could be wrong.

No idea whatsoever about the password :P

Well good news. Because ipv6 has a thing called privacy extensions which has been switched on by default on every device I’ve used.

That generates random ipv6 addresses (which are regularly rotated) that are used for outgoing connections. Your router should block incoming connections to those ips but the os will too. The proper permanent ip address isn’t used for outgoing connections and the address space allocated to each user makes a brute force scan more prohibitive than scanning the whole Ipv4 Internet.

So I’m going to say that using routable ipv6 addresses with privacy extensions is more secure than a single Ipv4 Nat address with dnat.

Weird. Ipv6 and YouTube stats for nerds shows between 140mbit and 600mbit depending on what’s being watched and the time of day.

Is it possible your isp has problems with their ipv6 setup?

IPv6 overheads should only have a marginal impact on max speeds.

I think people’s experience with PLE will always be subjective. In the old flat we were in, where I needed it. It would drop connection all the time, it was unusable.

But I’ve had them run totally fine in other places. Noisy power supplies that aren’t even in your place can cause problems. Any kind of impulse noise (bad contacts on an old style thermostat for example) and all kinds of other things can and will interfere with it.

Wifi is always a compromise too. But, I guess if wiring direct is not an option, the OP needs to choose their compromise.

Aha, glad to hear it.

OK, one possibility I can think of. At some point, files may have been created where there is currently a mount point which is hiding folders that are still there, on the root partition.

You can remount just the root partition elsewhere by doing something like

mkdir /mnt/rootonly
mount -o bind / /mnt/rootonly

Then use du or similar to see if the numbers more closely resemble the values seen in df. I’m not sure if that graphical tool you used that views the filesystem can see those files hidden this way. So, it’s probably worth checking just to rule it out.

Anyway, if you see bigger numbers in /mnt/rootonly, then check the mount points (like /mnt/rootonly/home and /mnt/rootonly/boot/efi). They should be empty, if not those are likely files/folders that are being hidden by the mounts.

When finished you can unmount the bound folder with

umount /mnt/rootonly

Just an idea that might be worth checking.

Most smaller instances will let you make a new community.

Getting people to subscribe, that’s your problem.

I think it’s more twitter slang. Sure it can be applied elsewhere. But I’ve mostly heard it used regarding twitter posts.

I think we should qualify the question. I think I’d like to hear a reason for society as a whole to exist that is reasoned and has a firm basis in logic and has no emotive or circular reference.

Because I cannot see the point of it (and I’ve been accused of being a pessimist, depressed and worse for expressing this opinion). So, I would really like to hear an actual reason for us all to be here.

No! Those trickle-down economics they told us about will be kicking in any time now! I’m certain!

Yeah, but they’re not. That’s the modern world. But also even if it was a web server there’s usually ways to advertise the IP for the app to connect to. I’ve seen other stuff do that. So getting an IP is easy. Once the app knows the IP and if you really want to allow connections from outside to your IOT devices (I wouldn’t) it could remember the IP and allow that.

You really don’t need to give a fixed IP to everything. I think I’ve given 1 or 2 things fixed IPv6 IPs. Everything else is fine with what it assigns itself.

Only if you’re a masochist.

Hah. But to be fair, ATM did have a specific use that it worked great for. That is the move to digital voice circuits. The small fixed cell size and built in QoS meant that if you had a fixed line size you could fit X voice channels, and they would all be extremely low latency and share the bandwidth fairly. You didn’t need to buffer beyond one cell of data and you didn’t need to include overhead beyond the cell headers.

ATM was designed to handle the “future” or digital network needs. But, the immediate use was about voice frames and that likely dictated a lot of the design I’d expect.

You should only assign static ipv6 to servers, in theory you could just define a host id and use a prefix too. But, most people at home really aren’t running enough servers to make that worthwhile. Everything else should just pick up new addresses fine using ND.

Per 100g is quite normal across Europe too (because you can kinda treat the values like a percentage or at least compare to any other product). We usually in the UK have per 100g and either per serving size or package size.

I think this really comes down to whether the employee was IT (and to an extent part of the network team). If so, I’d say there’s a lot of questions to be answered here. If not, there’s also a lot of questions to be answered but not from that employee :P

I think in 99% of use cases, upgrading isn’t a problem. Most of the time new SQL versions are backward compatible. I’ve never personally had a problem upgrading a database for a product that expects an older version.

They do have compatibility modes too, but those only go back so far too.

But, I think companies with their production databases for perhaps older complex systems are likely very weary of upgrading their working database. This is most likely where this situation comes from. Imagine being the person responsible for IT, that upgraded the DB server and database to the latest version. Everything seemed to be working fine. Then accounts run their year-end process, it falls over and now there are months of data in the newer version that won’t work properly. It’d be an absolute pain to get things working again.

Much safer to leave that SQL 2005 server doing what it does best. :P