Quote:
Originally Posted by thetechnobear
a) "iwconfig wlan0 essid "myssid""
myssid should have been substituted with your network name
e.g.
iwconfig wlan0 essid myhomewifilan
|
I know, that's what I did. I just didn't see the point in writing my ssid's name in this topic. But of course, I substituted it.
Quote:
Originally Posted by thetechnobear
b) "192.164.1.104 is the static DNS I attributed to the iLiad "
i assume this is a typo, and you mean is a static IP , and that you mean that you have assigned to the iLiad within the router setup
im also slightly confused as you said this was assigned to the iLiad wired mac address, which as dirk said is different to eth0.
|
Of course, my mistake. I meant static IP, not DNS. And it's 192.168.1.104, not 192.164.1.104 (typo).
And it's assigned to the wired mac address, right.
Quote:
Originally Posted by thetechnobear
what seems odd here, is that wlan is using dhcp, and assigned 104, yet you said you 'reserved' this for static ip on ethernet
|
Maybe that's were the problem lies ?
Quote:
Originally Posted by thetechnobear
btw, the wlan may still not have worked if you had eth0 plugged in, due to routing not being set up, but that was not really aim - it was more to see if dhcp was connecting you to network which it appeared to.
|
eth0 was not plugged in. I tested the iLiad without it being plugged anywhere (not to the router, not to the compuer either)
Quote:
Originally Posted by thetechnobear
btw2, on my router i can list which clients are connected to it, and iliad will show up, and also shows ip router assigned to it (even if it disconnects afterwards)
|
I can't do that with mine (it's stupid, I know), but I tried with a third party app, and iLiad didn't show up. Of course, when it was connected to the wired ethernet and working successfully, it showed up.
Quote:
Originally Posted by thetechnobear
anyways as i said at start, the ifconfig output looks very promising, and suggests the following:
i) your iliad is connecting to router/wifi ok
ii) its ok with dhcp
so i think problems could be:
a) ip conflict (however usually this works, just gives 'bad' performance, any only applies if eth0 is also plugged in)
as mentioned above, think its worth checking
i) on your router, what MAC address have you assiged to 104?
ii) you could try explicity assign an IP address to MAC of wlan0
iii) and/or check that your router is assigning (automatic) wifi addresses from a different range to wired AND that its outside the range you have assigned static addresses to
e.g i usually use 192.168.0.1 - 192.168.0.50 for static/reservered up, and 192.168.0.100 - 110 for the 'wifi pool'
b) routing setup - DNS and default gateway
ps. the annoying thing about the default scripts, is if they detect any errors, they bring the whole interface down again, hence why you had to type the steps manually  |
a) I never tried to connect with the wifi when wired ethernet was plugged in, in order to avoid conflicts.
I'll try to manually assign a MAC address.
BTW, router gives out dynamic addresses that are outside the range defined for static IP adresses. And two days ago, I tried again with another computer, which connected wirelessly without any problem, and got it's dynamic IP address immediatly (which was outside the range assigned to static IP addresses)
b) The thing is (quite funny) that iLiad cannot connect to the router, even with wired etherned, if I click the automatic configuration. I have to enter all the values manually, and give it a static IP address. Dynamic IP doesn't work, not only with wifi, but also with wired ethernet. However, it works with another router, gets a dynamic IP address, so apparently, the problem really comes from my router. Maybe one day I'll buy a new one, but I kinda like mine, works flawlessly for ports, games, apps, etc., and before the present problem with iLiad, I never had any trouble with it.
Anyway, thank you, to all of you, really, for trying to help me. I think the easy solution for me would be to be able to have a script to connect to the wifi with a static IP address, I hope it will be possible with next firmware release, and I hope I won't have to wait something like a year
