The 2x4 IS the cheaper option. That could be your fiber bundle.
1 Like
Did you set the IP manually? If so check if you have a default route via the router with ip -6 r l on all VMs. You can also manually define a /128 route (and a /64 on the routers side, don’t forget about the route back 
)if the router isnt on the same subnet. You just need to set the default route to it.
2 Likes
I skimmed the thread, and re: power.
I’ve seen somewhere that for power redundancy, people would
- Put the redundant PSUs in the servers on separate UPSes
- Put the two UPSes on separate AC phases
This way a single UPS failure or losing a single power phase doesn’t take you down.
This would probably be a great time to do it.
Edit:
For stress testing a Yocto build is actually quite nice. I’m just pushing stuff I know, but depending on the build phase it actually stresses most part of the system quite nicely. Networking least of all, but you get a lot of CPU and IO stress. Also uses a lot of memory, although it’s not particularly stressful there.
2 Likes
I’m currently stumped by this IPv6 issue. For whatever reason Proxmox allows IPv6 traffic between guest and host, but not between guest and guest, even though they are on the same host.
I have posted a thread over on the Proxmox forums if anyone might have some ideas.
Have you ran a pcap to confirm the packets are/aren’t arriving or are somehow being filtered by the guest?
1 Like
Did you try disabling the firewall on their interfaces and then test it? Might be the firewall config blocking ipv6.
1 Like
Ok, I figured it out. There are some subtle differences in how IPv4 and IPv6 routing works that I got caught up on.
In short, what I was trying to do was arbitrarily split up subnets without a router in the middle. I needed a router in the middle. The difficult part was figuring out how to properly route things, but I think I have things handled now.
TLDR: Native IPv6 works now, its all dual-stack.
That all said, here’s an idea to bounce off you fine folks. Could I get a show of hands (or likes or whatever) of who would be interested in a small VM for science? If there are a few folks interested I would be happy to set something up.
Something like 2-core 2-gb ram 16gb HDD and one IPv6 address. Nothing fancy. No IPv4 because $$$.
1 Like
I’m interested in a 1 core, 256 MB of RAM, probably 1 or 2 GB storage and an ipv6 address. I wonder if I can set wireguard on that and if I can route all ipv4 traffic through wg on an ipv6 tunnel. I see no reason why that wouldn’t be possible.
My current router running Alpine runs at 101 M, most of it being cached, actual used is 42 MB, so I should get around just fine with those specs. As long as you also have an ipv4 NAT, then sure, I’d be glad to help test it.
I put together A Google form for anyone who wants to play with things. @ThatGuyB.
I’m happy to be flexible too. If you need IPv4 NAT, a custom ISO, or something else simple, that can easily be provided.
I’m not really looking to benchmark anything for hard numbers (old hardware, cut me some slack), but a general “how does it feel” would be great feedback.
1 Like
You’re located in the US, right? I would probably like to fuck around a little, although I don’t have any use for it, but being on a different continent is a no-go here.
2 Likes
Spent some time at the shop yesterday. The goal was to reset the firmware on the new UCS switch.
Took far longer than necessary due to a misprint in a Cisco PDF. It was saying I needed to push ctrl+one, which must have been a misprint. The actual combo was ctrl+L. Thanks Cisco.
I did manage to reset the device, so now I just need to set it up. I’m looking forward to my router have a 10G uplink.
Don’t mind the mounting solution. Do as I say not as I do.
In other news, I’m having some trouble with my IPv6 tunnel. It keeps closing due to inactivity and only seems to wake up if internal traffic wakes it up, so external traffic won’t necessarily make it in. Still troubleshooting on this front.
3 Likes
Have you seen smokeping before? It can perform as both latency monitoring and impromptu keepalive daemon. Though I only end up checking it once every few months.
2 Likes
I am finally getting around to the customer-facing interface. It’s not pretty yet, but I have some boilerplate I am working with which should hopefully help move things along.
I am crossing my fingers that it will be fairly straightforward to get functionality to create/view/delete services from this control panel.
No, but that looks like a fun piece of software. I will have to play with it. In the meantime I just set up a CRON job to ping google every minute, I’ll see if that does the trick.
2 Likes
1 Like
If you ever need another generator, I strongly recommend a self-starting generator along with an automatic transfer switch. It means you have hours instead of minutes to get to the DC before your UPS’s die.
1 Like
You can also get generators that are piped directly in your natural gas in the building so your fuel supply is practically unlimited.
3 Likes
Someday. In the meantime I’m looking at ways to automate doing a clean shutdown when battery power runs low. Currently the UPS units estimate a 10-minute runtime, but I’d only count on half that.
Besides, the difference between “generator” and “no generator” is a solid first step.
That’s brilliant. Why have fuel sitting around going bad when it can just be piped straight in?
1 Like
According to uptime robot, the IPv6 tunnel seems to be stable now. I suppose it just needed traffic to be kept open.
2 Likes
That’s the worst part of the second hand market, things can potentially break a few weeks or months after the purchase. Although you may be able to find cheap replacement parts for some devices.
1 Like