Hacker Newsnew | past | comments | ask | show | jobs | submit | realloc's commentslogin

I built something similar for a personal project (though not using the FUSE API) with Samba running locally. Samba has a VFS API which isn’t terrible complicated and lets you accomplish mostly the same thing: https://wiki.samba.org/index.php/Writing_a_Samba_VFS_Module

The only problem I ran into was not being able to bind to 127.0.0.1:445, or connect to a different port, on Windows. I ended up writing a small pcap program that would look for packets going out to some other ip and replay them back at localhost on the port samba was running on, so Windows thought it was connecting to a remote machine. It was a ridiculous solution and I’m sure there’s a better way, but it worked for what I needed.


Very interesting DARPA is looking into in a modern version! I always thought, if nothing else, ekranoplan look incredible and somewhat other-worldly. Thankfully the DARPA project renderings don’t seem less weird.

Recently a Lun-class ekranoplan was stranded during a towing operation which left it open to urban explorers who took some photos, including of the inside: https://www.rferl.org/a/photographer-sneaks-inside-the-legen...


The C in ECMP stands for “cost”, which is usually calculated as the number of hops or intermediate nodes to the destination. If you were to use link speed as the “cost”, links of unequal speed wouldn’t be equal cost anymore. You can certainly use ECMP over links of different speeds, but as you said bandwidth doesn’t scale for a single connection, so any TCP connections that end up on the slower link perform at the speed of the slower link and it’s difficult to figure out why.

This is intentional: TCP treats packets received out-of-order as representative of an overloaded network. There’s generally a guarantee that packets sent in-order over a single link will be received in that order, but no such guarantee exists for packets sent through two completely independent links/networks. You need something on the receiving end (either at the destination or at the point where the separate paths converge) that will coalesce and re-order packets, such as an MPTCP or PPP implementation.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: