Tiny Core Base > CorePlus

WiFi Cannot Scan

<< < (13/30) > >>

Juanito:

--- Quote from: eltone on January 17, 2014, 11:27:49 PM ---I had to launch the browser and note that the home page timed out, before learning this CLI indexing failed to connect to router.  Also, the IP & dns address'  looks syspicious.

--- End quote ---

I get exactly that sort of output and everything works as expected:
--- Code: ---udhcpc (v1.21.1) started
Sending discover...
Sending select for 192.168.1.111...
Lease of 192.168.1.111 obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 192.168.1.1

--- End code ---


--- Code: ---Now that wicd.tcz has completed the burn-in phase on tc-4.73, it will be installed on tc-5.10 next go-around:
...
Q: Shouldn't it be recompiled first?
--- End code ---
We'll know that once you've tested it  :P

eltone:

--- Quote from: Juanito on January 18, 2014, 02:03:43 AM ---
We'll know that once you've tested it  :P

--- End quote ---

hi,

'wicd.tcz' was just dounloaded into 5.1's /mnt/sdb1/tce/optional directory.

Errors trapped:


--- Code: ---root@box:~# wicd
/usr/local/sbin/wicd: exec: line 3: /usr/local/bin/python: not found
root@box:~# wicd
Traceback (most recent call last):
  File "/usr/local/share/wicd/daemon/wicd-daemon.py", line 46, in <module>
    import gobject
ImportError: No module named gobject
root@box:~#

--- End code ---
Installed python to resolve line 2 glitch and the ImportError is up for grabs . . .
Dependencies are unclear, going this route.
eltone

tinypoodle:

--- Quote from: eltone on January 17, 2014, 11:27:49 PM ---
--- Code: ---tc@box:~$ sudo iwconfig wlan0 essid "eltonenetwork"
tc@box:~$ sudo iwconfig wlan0 key 6789abcdef
tc@box:~$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
Sending select for 192.168.0.64...
Lease of 192.168.0.64 obtained, lease time 86400
deleting routers
SIOCDELRT: No such process
adding dns 192.168.0.1
tc@box:~$

--- End code ---

I had to launch the browser and note that the home page timed out, before learning this CLI indexing failed to connect to router. 

--- End quote ---

Would you not have succeeded to connect to router in the first place, then you could never have gotten above output...
::)


--- Quote ---Also, the IP & dns address'  looks syspicious.

When using wicd, static addresses are used.  I have seen this anomaly with this particular dns address before and suspect that is the problem here.

--- End quote ---

Looks like expected.
If you want a static address, then why exactly do you run udhcpc?

Juanito:

--- Quote from: eltone on January 18, 2014, 10:37:02 PM ---Installed python to resolve line 2 glitch and the ImportError is up for grabs . . .
Dependencies are unclear, going this route.

--- End quote ---

Dependencies are as per wicd.tcz.dep updated for tc-5.x, i.e.:
--- Code: ---pygtk.tcz
dbus-python.tcz
urwid.tcz
wpa_supplicant-dbus.tcz
dhcpcd.tcz
net-tools.tcz
ncurses-utils.tcz
shared-mime-info.tcz
hicolor-icon-theme.tcz
--- End code ---

jlslegalise has just submitted an update for wpa_supplicant-dbus, take care that you do not have wpa_supplicant loaded at the same time as wpa_supplicant-dbus

Edit: wicd seems to work, copied to 5.x repo.

eltone:

--- Quote from: tinypoodle on January 18, 2014, 11:41:54 PM ---
--- Quote from: eltone on January 17, 2014, 11:27:49 PM ---
--- Code: ---tc@box:~$ sudo iwconfig wlan0 essid "eltonenetwork"
tc@box:~$ sudo iwconfig wlan0 key 6789abcdef
tc@box:~$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
Sending select for 192.168.0.64...
Lease of 192.168.0.64 obtained, lease time 86400
deleting routers
SIOCDELRT: No such process
adding dns 192.168.0.1
tc@box:~$

--- End code ---

If you want a static address, then why exactly do you run udhcpc?

--- End quote ---

hi,
I'm sure the dns server address needs to be changed to surf the net.

On a similar problem distro, 'nameserver 192.168.0.1' was changed to 'nameserver 8.8.8.8' to fix!

CFG locaton:


--- Code: ---/etc/resolv.conf


--- End code ---

Q: How can the  TCP nameserver assignment be altered?
eltone
--- End quote ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version