Tiny Core Base > CorePlus
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:
--- Quote from: beerstein on January 30, 2014, 01:51:31 PM ---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.
--- End quote ---
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:
--- Quote from: beerstein on January 30, 2014, 01:51:31 PM ---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.
--- End quote ---
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version