Can you setup Wifi with a static ip address?

[Trace]

Hello all,

I have been trying to setup wifi in the latest coreplus to work with a static ip address?

I have tried everything (all the different scripts for bootlocal.sh etc.) I can find and udhcpc still runs.

Been at this for a couple of days now, I'm sure I am missing something really simple.

Can anyone help or point me in the right direction, is anyone else using tiny core with wifi and a static ip address?

[gerald_clark]

Boot with the nodhcp option.
Then you can ifconfig a static address.

[Trace]

I've tried that and udhcpc always runs, I've tried so many different things now that I'm sure I'm missing something right in front of me.

Can you please detail how exactly you would go about it.

[tinypoodle]

udhcpc is not expected to run automatically with boot code "nodhcp".
I suggest you boot with "nodhcp norestore" to exclude you have any scripts laying around somewhere and try to set an IP manually.

Code: [Select]

sudo ifconfig interface address

[beerstein]

Hi Trace:
Is your TCL system hooked via WIFI to a router which is set up using  DHCP?
If yes, this router assigns an IP address to your system. If you have a static IP address on your system the router can not see it.

I think - but I am not sure - First set up your TCL system using DHCP (automatic address assignment) then check which IP your system has been assigned  to. (using ifconfig)  It will be an address inside the routers address range. Make a note of it and assign this address as a static address to your TCL system. Then check if the  router still sees your system. Please let me know if it worked.

[tinypoodle]

If you have a static IP address on your system the router can not see it.

How so?

[Juanito]

First set up your TCL system using DHCP (automatic address assignment) then check which IP your system has been assigned  to. (using ifconfig)  It will be an address inside the routers address range. Make a note of it and assign this address as a static address to your TCL system.

I'm no expert, but I thought it was good practise to set a static ip address outside of the dhcp address range?

[tinypoodle]

I'm no expert, but I thought it was good practise to set a static ip address outside of the dhcp address range?

Absolutely

[Trace]

OK .... here's some more facts:

Coreplus is installed on USB flashdrive from a latest version live CD.

nodhcp was chosen as one of the permanent boot options during install and is still there.

My hardware router has it's integrated DHCP turned off (we have multiple Xbox's here and have to use static addresses for each to avoid confusion).

Everything here laptop's, phone's, tablet's etc. are all set with individual static addresses and work with no problems.

What I am looking for is a way to setup my latest coreplus to automatically connect after booting with a static ip address.

From the way everybody is talking it seems like it should be really simple but for me no matter what I try when I try to connect and enter my tkip password .... it always starts UDHCPC and broadcasts for a lease .... which of course it never gets because DHCP is turned off in my hardware router.

I've tried different ways using nodhcp bootcode etc. and all the scripts and instructions I could find e.g.:

pkill udhcpc
ifconfig wlan0 (static address) netmask 255.255.255.0 up
route add default gw (gateway address)
echo "nameserver 8.8.8.8" > /etc/resolv.conf

and putting that in bootlocal.sh.

No matter what I try ... when I click on the wifi icon and enter my network and tkip key ..... UDHCPC always runs ?

I'll try the "nodhcp norestore"    and   "sudo ifconfig interface address"   but this seems very similar to what I've tried before.

Are you guys using static addresses over wifi?

[gerald_clark]

Don't run wifi.sh.

[Trace]

Aha... yes wifi.sh seems to be the problem .... always runs udhcpc.

Can you tell me how to do it without using wifi.sh?

And how to setup and execute my settings (inc. password etc.) to connect automatically when booting?

[tinypoodle]

WEP or WPA?

[Trace]

wpa-tkip   ......... essid and password.

[tinypoodle]

You shouldn't be concerned at all about "to connect automatically when booting" before you have managed manually, and then you can script.
All the idea about "norestore" was that no scripts are run.

Look into wpa_supplicant and optionally wpa_gui or wpa_cli, they are all well documented; there is nothing specific to Core to it, with exception from bootlocal.sh for automatization purposes.

[Trace]

Yes I tried the norestore instructions as well but dhcpc still ran and I don't know how to connect without using wifi.sh

Ok .... yes I'll look into that but I've already spent about 3 days researching.

I was hoping there was just a simple way of doing it ... it only takes seconds in Puppy and others.

Is nobody here using tc with a static address over wifi?

I really like the philosophy of tc but static ip is essential for me and this just seems like a huge amount of work.

This and slitaz are the only distro's I have problems with static ip's in and they both use UDHCPC.
 
Am I the only person wanting to do this?