William Shu wrote:
Hi,
I have 3 issues related with using my wireless router, and
making sure changes take effect at boot time.
ISSUE 1: Obtaining DHCP from router
My wireless router can be used if my machine (an hp pavillion
5000 series laptop) is given a fixed IP address. For this to
happen, the ipW3945d service (driver) has to be activated so
that the wireless connection is associated with the eth1
interface. (From the HOWTO's this is done so that sofware that
can change certain wireless connectivity parameters into
unlawful values cannot be tampered with by a user, which is an
FCC legal requirement) eth0 is associated with the wired network
interface.
My router may issue DHCP IP addresses, but I cannot use the
wireless connection because I would need the issued IP address
to configure the eth1 interface needed for the connection!
Unfortunately, the router cannot issue both fixed and DHCP IP
addresses at the same time! Furthermore, the accepted address
range set for the router need not be known by the user, who need
not have root/admin access.
QUESTION: How can I configure my eth1 interface so that it can
get a DHCP IP address from the router?
What brand/model of wireless router? I failed to get a dlink working,
though I've had n problems with Apple's airports or a linksys.
I don't use the builtin dhcp server, but I do use dhcp.
ISSUE 2: Adding configuration start-up commands at boot time
The following are actually more of linux boot-related questions:
I used /sbin/chkconfig to start the ipw3945d service at boot
time. However, the initialisation commands
# /sbin/iwconfig eth1 essid "doit1wlan" channel 6 rate auto
txpower auto
I would not specify the channel on a client.
# /sbin/iwconfig eth1 key open s:xxxxx
what's that work "open?" "key" is supposed to be followed immediately
by the key.
# /sbin/ifconfig eth1 up 192.168.110
which are used to configure the device are lost.
QUESTION: How should I save these commands so that they are
automatically executed at time? (.bashrc does not seem right!)
If you use RH's configuration tools, it should all work. The
information's stored in /etc/sysconfig/network-scripts and it's possible
to edit the files with a little vim, but I prefer to see something to
work on.
ISSUE 3: Controlling Services across sessions
Sometimes, when my laptop runs out of power and shuts down, the
subsequent reboot restart or resume some of the programs
(processes) that were running before. This does not happen when
I shutdown the system. I have deleted the processes from the
current session services, but they still re-appear on subsequent
boots. (such processes seem to be hvve unusual names, id's or
directory paths appended/prepended to them). I think at one time
in the distant past, pm-hibernate or pm-suspend had been called.
If the system hibernates, then it should resume to the same state it was
in before. By definition.
QUESTION 1: How can I turn this on or off -- at my discretion?
I have in the past had success setting my choices in KDE>
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
