Can you setup Wifi with a static ip address?

[gerald_clark]

Core is not a boot and run distro.
It is a toolkit.
wifi.sh is ONE of the tools.
Others have been mentioned already.

You need to learn how to use the tools.
Iwconfig and wpa_supplicant are thoroughly documented on the internet.  Simple instructions are in the .info files.

[beerstein]

again - did you try to use a static IP address inside the routers range. ?
I am using piCore here on a RaspberryPi and I have it set up DHCP and its address from thr router is 192.168.0.5. Using the Control Panel I changed the yes  from"use DCHP Broadcast?" to NO and inserted the 192.168.0.5 here plus the Gateway and the Broadcast. The Nameservers are still there from the DHCP and I have left them untouched.
Then I rebooted with the static address and the RP was connected using static IP.

[tinypoodle]

Static configuration is very rarely used with wifi by latter's very nature; e.g. with any network which you do not administrate, you could not know the range of allowed addresses.
Personally I always run udhcpc (or any other dhcp client) explicitely after having associated and possibly authenticated first, so I can't imagine any obstacle to a static configuration instead.

[bmarkus]

again - did you try to use a static IP address inside the routers range. ?
I am using piCore here on a RaspberryPi and I have it set up DHCP and its address from thr router is 192.168.0.5. Using the Control Panel I changed the yes  from"use DCHP Broadcast?" to NO and inserted the 192.168.0.5 here plus the Gateway and the Broadcast. The Nameservers are still there from the DHCP and I have left them untouched.
Then I rebooted with the static address and the RP was connected using static IP.

Do not uses static address within the DHCP address range. There is a release time in the DHCP server to assign same IP to a MAC within this period which cab be few days tipycally but after that this address will be reassign to another MAC. So be prepared for IP conflict later when router will use 192.168.0.5 for another device.

If you need a fix address, you can set up your DHCP server to assign a specificic IP to a MAC instead of choosing one from the pool. In this case you can use TC as ususally and manage IP centrally.

[tinypoodle]

again - did you try to use a static IP address inside the routers range. ?
I am using piCore here on a RaspberryPi and I have it set up DHCP and its address from thr router is 192.168.0.5. Using the Control Panel I changed the yes  from"use DCHP Broadcast?" to NO and inserted the 192.168.0.5 here plus the Gateway and the Broadcast. The Nameservers are still there from the DHCP and I have left them untouched.
Then I rebooted with the static address and the RP was connected using static IP.

Arbitrary use of a static IP without having excluded that it may be within range of dynamic address pool is reckless and could get you in trouble with any netadmin.

[Trace]

The DHCP in my hardware router is off .....

The address I am using is the same one that I use from the same laptop when I am trying different distro's on it.

This static ip address works fine with this laptop and router with : windows, BT5, puppy, etc.

It does not work with tc and slitaz and these both seem to have the same problem of udhcpc always being invoked and so by the process of trial and error and the harware always being the same it is not the address that is at fault.

slitaz also uses wpa_supplicant and wpa_gui for setup and even with that seems impossible to use without udhcpc always starting which is why I am trying to find a working example from someone who has done it.

I get the feeling noone here has actually ever done this?

[gerald_clark]

Once you have the interface associated with your access point, just use ifconfig to assign an IP address.

[Trace]

Yes I can do that but can't connect without using wifi.sh to enter  wpa-psk key which starts udhcpc and so fails to connect.

I am writing this using the same static ip and hardware right now from vista and can reboot and do the same from puppy and various other distro's using the same address.

So it seems it's udhcpc that is the problem and noone knows how to stop it running.

[gerald_clark]

You do NOT need to run wifi.sh
Research iwconfig and wpa_supplicant.

[bmarkus]

So it seems it's udhcpc that is the problem and noone knows how to stop it running.

You can kill udhcpc with kill command. For process number look around in /var/run

You can disable it with nodhcp boot code, see

http://tinycorelinux.net/faq.html#bootcodes

[Trace]

I have already set these bootcodes and other combinations as suggested on the 1st page. I have tried various different pkill udhcpc commands.
and have tried wpa_supplicant in slitaz which seems to have the same unstoppable udhcpc.

If it's simple please can someone give me an example script or instructions instead of just suggesting solutions for different stages of connecting via wifi.

I know it's probably right in front of me but I'm so lost in it now I'm confused.

[tinypoodle]

wifi.sh is subject to GPL, if you insist on using a tool that does not meet your needs, you are free to modify it to your liking.

Core is a toolkit, and it is the users responsibility which tools to choose and how to use them.

The only automatic invocation of udhcpc could occur when omitting boot code "nodhcp" as a default which may be convenient for some users (it's not convenient for me, but I don't feel that interferes with my freedom a simple mechanism to deactivate it is provided).

[tinypoodle]

If it's simple please can someone give me an example script or instructions instead of just suggesting solutions for different stages of connecting via wifi.

I know it's probably right in front of me but I'm so lost in it now I'm confused.

http://wiki.tinycorelinux.net/wiki:setting_up_wifi_at_boot?s[]=wpa&s[]=supplicant

[Trace]

Those instructions are for connecting at boot using udhcpc.

I don't have a problem connecting using udhcpc.

I do have nodhcp as a default boot code as I said on page 1.

If there is no simple answer, there is no simple answer ..... I'm surprised that I seem to be the only person to want to do this.

[gerald_clark]

You may be happier running Ubuntu or some other boot and run distro.
You do NOT need to use dhcp, and your repeated complaints about it demonstrate
that you are not bothering to learn the tools you have been pointed to.
You need to establish an association with your access point.
For WEP use iwconfig.
For WPA use wpa_supplicant.
Once associated, use ifconfig to assign the IP address.