OK, this is good!
Let's take the whole situation a step at a time, and do a little more research along the way, working towards a reasonably automated way for you to accomplish the above. I', just going to throw out a few questions here and suggestions, in no praticular order:
1) The modprobe command you are using for the ipaq module: Do you need to re-do that every time you stop/restart your network? Or do you mean, every time you restart the computer? If it's upon restarting the computer, then it should be rather simple. Now, I didn't see anywhere earlier in the thread what distro you are using, so for the time being I'll give general ideas about how to do that (we're working on the assumption that your kernel is not auto-probing the kernel module for whatever reason):
--One way is in an rc.local or similar init script which gets run after the machine has booted and entered multi-user mode (init 3/4/5 or whatever). On my slackware OS, I would use /etc/rc.d/rc.local.
--Another way is configuring the module in modules.conf or modprobe.conf (depending on your system) which is used sometime during late boot using the init script rc.modules (same idea as above basically) where you tell the kernel that when a particular device is discovered, insert 'this' module.
--The options you are giving the module, you can put into a little text file in /etc/modprobe.d called 'ipaq' and inside this 'ipaq' file you would put:
Code:
alias wlan0 ipaq
options ipaq vendor=0x0bb4 product=0x0b03
just like that. Note: this alone *might* even make the kernel auto-probe the module automatically as soon as the NIC is discovered, though I realize that the NIC cannot actually *be* brought up without the module inserted. What the line means is: "When you (the kernel) discover a wlan0 device, insert the ipaq module with these options."
ALSO NOTE: If your connection is not called
wlan0, then adjust as required (i.e.
eth0, or whatever it is called). Between this file, and the modules.conf file, with any luck it will get auto-modprobed (though other users reading this, please clarify/correct me if I am missing/mis-explaining exactly how to use the modules.conf file as I do not actually use it myself).
Now, the nameserver issue:
Once you connect (even before you log in) have a look into /etc/ppp or if you are dialing out as non-root, look in ~/.ppp/ and see if there is a freshly created resolv.conf file which appears as soon as the connection is made. If it's there, great. If not, go ahead and log-in to the connection, and check again to see that the resolv.conf file has appeared there. pppd created the file automatically, so it should appear.
There are a couple ways to automate the process of getting resolv.conf updated automatically, as well as the login process itself (I should say that the other way 'round-- i.e., ways to get login to be automated, and THEN get resolv.conf updated automatically):
Locate the file /etc/ppp/chap-secrets or pap-secrets depending on whether you use pap or chap method to log into the ISP. Inside this file is where you put your login-name and password in plain text. My chap-secrets file looks like:
Code:
# Secrets for authentication using CHAP
# client server secret IP addresses
"my-user-name@ns.sympatico.ca" * "Password"
So that takes care of your login info. Now, look into the /etc/ppp/options file. This is the stuff that tells ppp what to do once connected. Particularly relevant options (all of which I have uncomment in my own file) are:
asyncmap 0
noauth
crtscts
modem
noipdefault
mru 1500
mtu 1500
passive
debug
proxyarp
So please read the options file for well commented descriptions of the functions of these options, and adjust your own options file to suit your needs. Do enable the 'debug' option for now at least, as it does provide very useful information as the dialer is dialing and connecting to the ISP. the 'passive' and 'auth/noauth' options you may need to play with.
OK, so for the time being, I would like to know: If you can get the options file set up correctly, and also if you would create the /etc/modprobe.d/ipaq file as described, and test a bit.
First: see if the ipaq module gets inserted automatically when you boot the machine and/or then start the network?
Second: can you dial up your ISP and does ppp login automatically?
Third: Where/when does the resolv.conf appear, and does it automatically get copied over to /etc/resolv.conf? If not copied automatically, but it DOES appear, then we will need to do something about that, maybe a little script that does your dialing (calls wvdial, logs in etc..) and then copies/updates the resolv.conf file. THEN, after all this, if for whatever reason (which hopefully you won't need) we can have the script stop & restart the network, if you must have this happen for the connection to actually come to life.
I realize that the above post is probably rather convoluted & disorderly, but I think I have covered the basics of what needs to happen to get your connection working somewhat by itself when you dial out.
Keep us posted about what's going on, and if you need further help or clarification, you know where we're at.
OH--- What distro IS this you are using?
Sasha
I don't know what 'tethering' is, nor what a 'HTC Mogul' is. Whatever gave you this idea?
ppp options
