Ed's Big Plans

I’ve found that the implementation of NAT (network address translation, also called internet connection sharing [ICS] (OSX) and network bridging (Windows)) on Tin is pretty decent. The most common use of NAT from a laptop is to convert the laptop into a software wireless router: the laptop is connected to an actual router via wire, and transmits the network wirelessly. I needed to do the reverse: to receive a wireless signal and then share the address with a desktop that doesn’t have a wireless interface.

This succeeded until the wireless connection was inexplicably irresolvable in that dialing to any IP address from either the desktop or Tin resulted in server timeouts. This happened over and over and usually required about ten minutes after each failure and reconnection to the wireless router.

I’ve read a bit more, and I’m really no closer to figuring out why this happened but have a few hypotheses. First, it could be that the NAT implementation isn’t as bullet proof as I had hoped; second, it could be that the router some how doesn’t like what I’m doing; and third, my ISP may see the set up as somehow disruptive to other clients and thus had disconnected me.