Quote:
Originally Posted by zerospinboson
it might be better if you give the iliad an ip like from 0.2 and the pc 0.1, as that's what windows wants from you when you set up internet connection sharing..  |
Sure. I didn't have Windows connection sharing in mind when I started working on it (I wanted to use adhoc for ssh/scp to the iliad). But you are right, a more sensible choice of addresses makes it suitable also for that. However, when you enable connection sharing, windows acts as dhcp server and assigns itself a static address (192.68.0.1). This setup is inverted to what I have assumed for v0.1 (dhcp server on iliad and client on windows). In order to cope with both scenarios v0.2 keeps starting a dhcp server while statically assigning 192.68.0.2 to the iliad (with 192.168.0.1 as gw and dns server). Recap:
Windows connection sharing enabled
PC address: 192.168.0.1
iLiad address: 192.168.0.2
Windows connection sharing disabled
PC address: 192.168.0.3*
iLiad address: 192.168.0.2
* More precisely dynamically assigned in the range 192.168.0.3-192.168.0.254
In v0.2 I should have fixed WEP which, I realized, was broken in v0.1. I didn't catch that right away because Windows silently downgraded to an open connection and I overlooked the fact that the lock symbol was gone.
Quote:
Originally Posted by zerospinboson
Although i'm guessing this doesn't work in combination with the iDS downloader yet?
|
Right. It doesn't work with "iDS downloader" and it won't. For that I need to directly patch wireless.sh. Doable if people are interested but definitely a different approach.
/Michele/