i just ran netconfig cause, well i dont know why, i just wanted to.

anyways i typed "*myname*pc" for the name, and i typed a number of different things for the domain name, and i selected the option that says that dial-up users should use this, i selected that.

anyways iv configed it a number of different ways but i still cant use my dialup connection, even after doing ppp-on.

does anyone know how i can get back to where i can conect to the internet? its really annoying to have to boot into windows to use the net

(PS. be descriptive, i dont want to have to reboot AGAIN to ask a trivial question)

Uhm... I can't tell from your post whether you had it working at one time, or you never had it working at all?

What kind of modem do you have, etc?

-Shade

i had a conexant HSF winmodem, and i downloaded their trial driver and it worked. up untill today i could browse the internet with mozilla or lynx using my modem (i intialized the modem by typing as root "ppp-on" and i closed the connection with "ppp-off)

now that i have done netconfig, "ppp-on" will still do its thing and i can hear the modem dialing up, it even gives me the message saying i connected. but now that i have done "netconfig" none of my programs that require a internet connection will work, they always say stuf like "host not found" or "page not found"


one idea i had is if someone could tell me the name of the file that netconfig changes i could just search my slack CD for that file in its defaut state (or if that doesnt work, i could ask some slack user who hasnt done netconfig to e-mail it to me)

or if someone knows how to fix this problem and they could tell me, that would be helpfull.

In slack 9.1 the is a file /etc/rc.d/rc.inet1.conf. This is new to slack-9.1. The settings are written to this file and are read as variables when /etc/rc.d/rc.inet1 is run at boot.

You can delete your entries but if you have only run netconfig once you should have your original config file in there named rc.inet1.conf~. If this file is there than you can delete or rename the current one then rename the back up as rc.inet1.conf.

Alternatively you can try running netconfig again. You can enter the hostname and domain name if you like but the only other thing you need to worry about setting up is loopback which you will need for the internet connection. Can't remember but it may be that for a nameserver you might want to put in your isp's domain name and then your isp's primary dns.

If all you want is a dialup connection and you use kde, the simplest way to get yourself on the net is by using kppp. It's easy to configure and you can run it as a normal user.

I don't know about your winmodem driver but I roll my own with the ltmodem package. During the install of my winmodem modules a /dev/modem is created and linked to /dev/ttyLT0. In kppp setup I nominate /dev/modem.

Keep that in mind because you'll have to know how your drivers interface and it maybe that they too create a link via /dev/modem. You can query the modem in kppp's setup and know right away if you can connect to it. If not it's probably a permission problem. Come back and maybe I or someone else can help.

Even with a dialup connection, you should not be going online as root!

I use ppp-on and ppp-off from clients on a home network to start/stop dialups. You can suid those scripts and I think possible you may need to change permissions on you dialup scriptin /etc/ppp as well. Did it two weeks ago but don't have my notes handy.