• 2 Posts
  • 54 Comments
Joined 2 years ago
cake
Cake day: June 9th, 2023

help-circle
  • Then you’d be surprised when you calculate the numbers!

    A Falcon 9 delivers 13100kg to LEO and has 395,700kg propellant in 1st stage and 92,670kg in 2nd stage. Propellant in both is LOX/RP-1. RP-1 is basically long chains of CH2, so together they burn as:

    3 O2 (3x32) + 2 CH2 (2x14) -> 2 CO2 (2x44) + 2 H2O (2x18)
    

    Which is 2*44/(2*44+2*18) = 71% CO2. Meaning each launch makes (395700+92670)*.71 = 347 tons CO2 or 347/13.1 = 26.5 tons of CO2 per ton to orbit. A lot of it is burned in space, but I’m guessing the exhaust gases don’t reach escape velocity so they all end up in the atmosphere anyway.

    As for how much a compute satellite weighs, there is a wider range of possibilities, since they don’t exist yet. This is China launching a test version of one, but it’s not yet an artifact optimized for compute per watt per kilogram that we’d imagine a supercomputer to be.

    I like to imagine something like a gaming PC strapped to a portable solar panel, a true cubesat :). On online shopping I currently see a fancy gaming PC at 12.7kg with 650W, and a 600W solar panel at 12.5kg. Strap them together with duct tape, and it’s 1000/(12.7+12.5)*600 = 24kW of compute power per ton to orbit.

    Something more real life is the ISS support truss. STS-119 delivered and installed S6 truss on the ISS. The 14,088kg payload included solar panels, batteries, and truss superstructure, supplying last 25% of station’s power, or 30kW. Say, double that to strap server-grade hardware and cooling on it. That’s 1000*30/(2*14088) = 1.1kW of compute per ton to orbit. A 500kg 1kW server is overkilling it, but we are being conservative here.

    In my past post I’ve calculated that fossil fuel electricity on Earth makes 296g CO2 per 1 kilowatthour (using gas turbine at 60% efficiency burning 891kJ/mol methane into 1 mol CO2: 1kJ/s * 3600s / 0.6 eff / (891kJ/mol) * 44g/mol = 296g, as is the case where I live).

    The CO2 payback time for a ton of duct taped gamer PC is 1000kg * 26.5kg CO2/kg / ( 24kW * 0.296kg/kW/hour) / (24*365) = 0.43 years. The CO2 payback time for a steel truss monstrosity is `1000kg * 26.5kg/kg / (1.1kW * 0.296kg/kW/hour) / (24*365) = 9.3 years.

    Hey, I was pretty close!







  • PostUp = ip route add 100.64.0.0/10 dev tailscale0
    

    Looks like you need to stick this line in the tailscale service file, since it’s the only time that the existence of the tailscale0 device is guaranteed. If you don’t want to modify the service file inside the package, could you write your own systemd service file and include the tailscale service as a prerequisite?

    Also make sure that when you start the VPN first and then tailscale, you don’t get a double tunnel situation where tailscale goes out through the VPN (unless that’s what you wanted).


  • The exact script would depend on the use case; you’d use commands something like this:

    mkdir -p /etc/netns/VPN
    sh -c 'echo nameserver 1.1.1.1 > /etc/netns/VPN/resolv.conf'
    ip netns add VPN
    ip link add tun1 type wireguard
    ip link set tun1 netns VPN
    

    Because the wireguard device was created in the default namespace, it will “magically” remember its birthplace, even after you move its mouth (the tun1 device) to a separate namespace. The envelope VPN packets will keep going in/out in the default namespace.

    ip netns exec VPN wg setconf tun1 /etc/wireguard/vpn.conf
    ip netns exec VPN wg set tun1 private-key /etc/wireguard/vpn-key.private
    ip -n VPN addr add 192.my.peer.ip/32 dev tun1
    

    Get the wireguard config file from the VPN website, both mullvad and OVPN have a wizard to generate them. Your assigned private network ip is in the config file. Also get and save your device key.

    ip -n VPN link set tun1 mtu 1420
    ip -n VPN link set tun1 up
    ip -n VPN route add default dev tun1
    ip netns exec VPN su myuser -c 'firefox --no-remote'
    

    Now all firefox (and only that firefox) traffic will go through the tunnel. Firefox has its own DNS, if you run another app it will use 1.1.1.1.

    I actually do the reverse of this - I create a namespace ETH and move my eth0 device in there and attach dhcpcd to it. Then I create the wireguard tun1 device inside ETH namespace, and move tun1 to the default namespace. Then any software I run can only use the tunnel, because the ethernet device doesn’t even exist there. This keeps the routing table simple and avoids a whole class of issues and potential deanonymization exploits with the split routing table used in traditional single-namespace VPN configurations.



  • TauZero@mander.xyztoPrivacy@lemmy.mlVPN's recommendations?
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    1 month ago

    OVPN is a 1-to-1 feature clone of mullvad (wireguard, multiple device keys, crypto payments/cash in the mail, no usernames/emails, etc.) AND has port forwarding. Switched to them when mullvad sadly closed their ports, no problems since. Can’t live without port forwarding.




  • IMHO if you don’t have a globally-reachable address or forwarded port, you are not really a participant of the internet, you are just a receptacle xD

    One service I never see mentioned is OVPN. They have a 1-to-1 feature parity with mullvad and were an easy drop-in replacement when mullvad closed their ports:

    • wireguard
    • port forwarding
    • no usernames/emails/registration, only account numbers
    • crypto payments/cash in the mail
    • same price as mullvad
    • multiple device keys
    • multihop
    • no bandwidth limits
    • setup guides
    • status dashboard

    I used mullvad for years, sad to see them go, and all my scripts basically worked without any change other than the server addresses/public keys. Only downside is they don’t have as many users so not as many servers. I wish more people would join up so I get more IPs to choose from :D



  • TauZero@mander.xyztoxkcd@lemmy.worldxkcd #2948: Electric vs Gas
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    2
    ·
    1 year ago

    I was apprehensive about EVs but the first time I rode in one I immediately fell in love with it. I get carsick easily, and the super-smooth ride without the chug-chug-chug of an internal combustion engine made the experience surprisingly much more pleasant for me. I do not use a car, but if I had to buy one, I don’t think I could ever stomach an ICE again knowing that this alternative is available.









OSZAR »