HN user

jonathonlui

72 karma
Posts0
Comments13
View on HN
No posts found.

Some mobile phone providers check the packet TTL to limit tethering.

Network packets commonly have start with default TTL values of 64, 128, or 255. Each hop in the network subtracts 1.

When phone connects direct to carrier (cell tower, I assume) the carrier will see TTL of 64.

A laptop tethered to a phone introduces a hop so laptop-to-phone TTL is 64, phone-to-carrier TTL is 63.

Carriers can then limit bandwidth if network packet that don't have a common TTL.

For `iptables` look at `--ttl-inc 1` (to add back the 1 so 63 => 64) or `--ttl-set 64`.

Alternatively, you set the tethered devices to use a TTL of 65, e.g. linux/mac `sysctl -w net.inet.ip.ttl=65`

Not a pro, but the handful of times a month I solder, the Pinecil has been great. It can use TS100 tips so easy to get different tips.

It packs easily away in a plastic shoebox with my soldering accessories and consumables along with whatever project I'm currently working on.

After issues using various (cheap) USB 1Gbps ethernet adapters and an Intel MBP, I ended up getting one that uses a RTL8156B and seems ok. These are 2.5Gb adapters that use NCM driver so shouldn't cause high CPU.

I don't have 2.5Gb network equipment but have tested with iperf between and get around like 900 Mbps and no high CPU, unlike noticeable CPU usage with the cheap 1Gbps USB adapters that use ECM drivers

See also https://gist.github.com/MadLittleMods/3005bb13f7e7178e1eaa9f...

If you can wire the 2 AP via a LAN, then this is how I've used cheap consumer wifi APs which are usually combo AP+router devices:

The first AP is connecting to internet gateway through its WAN port. This AP does the networking stuff like DHCP, NAT, etc.

The other wifi APs are configured to be AP-only, i.e. disable DHCP. Use same wifi SSID and auth settings as the first AP. Then connect the APs using their LAN ports.

Client devices should now connect to the AP with the best signal.

But if the client is already connected to an AP and a better-signal AP is available, many clients won't automatically connect to the better AP. This is because the client don't know that the other AP is the same network. So if you move around you may need to trigger the client to disconnect and reconnect.

This can be solved with APs that have a "mesh" feature which can instruct connected clients to reconnect to a better AP in the same network using https://en.wikipedia.org/wiki/IEEE_802.11k-2008 but AFAIK mesh systems from different manufacturers aren't interoperable.

I use the Feitian Multipass that I bought from Amazon before Titan Keys were available. I had connected to my Google account using my iphone.

This morning I received the "Update on your Titan Security Key" email from Google. I was able submit the $0 order for replacement using the Google replacement link.

So seems like Google can't tell different between the Feitian Multipass and their version.