OK. Where do I find out about groups? and where is CHANGES_AND_HINTS.TXT?

"Changes and hints" and a lot of other good documentation is in the root directory of the install disk, or on the slackware ftp servers if you don't have your install disk to hand.

I have the install disk to hand...thanks. I'll read on.

I still have no idea how to establish the connection to the Internet via the modem such that Firefox within KDE recognizes it. I'm using ppp-go to make the connection, however, even console apps, like BitchX don't seem to find it.

Any suggestions?

Well, I appear to be flying solo on this one.

I'm wondering if there isn't an issue with the ppp daemon. It would appear, based upon viewing bootlog, that it is not being loaded. Is there any way to determine if it has been loaded, and if not, how to ensure it is loaded at boot time. What is the method to load the daemon after boot?

ppp-on and ppp-off (and others) control that unless you set up on-demand dialing. You can use 'ping'(ping google.com) to find out if a good connection is being made. Do not mix KDE ppp tools with your use of pppsetup or ispetup or neither will work.
Do you have firewall running?

I think that you should be using KPPP to do this. It really is easier, although I do recall that it can be intimidating.
Excuse me if this is out of date, but I am referring to an old box running Slackware 11.0, so things may have changed a little.
As the root user, start a KDE session and then start KPPP.
Hit "Configure..."
On the "Modems" tab do "New" ( or "Edit" your existing setup).
On the "Device" tab enter a Name e.g. Hayes, Modem device /dev/modem, Flow control Hardware [CRTSCTS], Line termination CR, Connection speed 115200 ( or maximum that your serial port supports), check Use lock file and set Modem timeout to 60 sec.
On the "Modem" tab, check Wait for dial tone before dialling, set Busy wait to 0 sec and Modem volume to mid range. Now hit "Modem Commands". As you have a Hayes modem, then the default Hayes commands should be OK, but for initial setup, set the Pre-init delay, Post-init delay and Dialing speed to maximum. You can cut these back later to shorten the connect time, but at this time you want to be sure that you can get things to work. Hit OK when done, and you will return to the "Modem" tab. Now hit "Query modem". This should connect to your modem. If it does not, then open a shell window, and type 'ls -l /dev/modem'. This should be a symlink to /dev/ttyS0. If it is not, then create it with 'ln -s /dev/ttyS1 /dev/modem' and try "Query modem" again. To this point all that has happened is to set up communication between the computer and the modem via the serial connection. You should now be able to hit "Terminal..." and type command such as ATZ that will be sent to the modem and you should get a response OK.

To actually connect to the internet, you will need to set up your account information from your ISP under the "Accounts" tab in KPPP. On the "Dial" tab you name your connection, enter the dialup phone number, set your Authentication type (often PAP), get KPPP to store your password ( or leave this clear iuntil you are happy that all is OK), set Callback type to None and do NOT Customize pppd Arguments.
On the "IP" tab, set Dynamic IP address if your ISP uses DHCP (like the vast majority).
On the "Gateway" tab, set the Configuration to Default gateway and check Assign the default route to this gateway.
On the "DNS" tab, check Automatic if your ISP uses DHCP. Alternatively you can set Manual and provide DNS server addresses if you want to set these.

This should be all that is required to set up a basic dialup connection using KPPP.

I have no idea re firewall, and no clue as to where it might be nor how to find it.

Secondly, if I wanted to try out the two different techniques, what files are created that would conflict? I notice when I run ispsetup that it deletes resolv.conf in /etc. Apparently that file is created when netconfig is run. And in regard running netconfig, it suggests settup up loopback if dialup is going to be used. The result then is that resolv.conf has merely the host name of my PC, which apparently can be anything, and further has zero effect on anything.

In my explorations, I finally discovered Midnight Commander. It would have been of immense assistance had anyone mentioned this fine tool. It is the equivalent of the old Qfiler program for MS-DOS and the current Total Commander for MS Windows.

At this juncture, I am intimately familiar with most aspects of Kppp and related. The problem is not with the setup, nor with dialing, nor with the modem connecting. It does so. It is that after the connection, nothing happens. The graph available, as well as TX and RX lights on the modem indicate transmit only with no receive. This has been the problem from the outset.

Secondarily, and a question still not answered is if I use ispsetup to create the files required to make the connection, then do ppp-on, the connection is made, however, I'm in CLI mode. If I then startx and initiate KDE, no software within KDE recognizes the connection. How do I make the software within KDE recognize the connection? Note, that even if I can accomplish that, I suspect I will get the same results as noted, namely that there will be no traffic.

OK- You say that you can get a connection with the hardware. Perhaps there is a networking problem that is stopping packets entering your system.
What is the output of 'ifconfig'? You should have a ppp0 interface.
Can you ping your ISPs DNS server addresses?
Are you running a firewall? Perhaps there is an issue with firewall rules.
Perhaps there is a routing problem. What is the output of 'route'?

First. Since I got no response in re what files are created by ispsetup versus Kppp configure that causes both apparently to be non-functional, my only recourse was to re-install Slackware from scratch. Following that, I installed the ispsetup script and ran that. Interestingly, at the end of that script was the statement to in order to make the dialup connection to use yawmppp in Amigo. Uh, right.

Regardless, I did startx/KDE, opened a terminal window and ran ispsetup then ppp-go. That script logged the following:
Next I ran ifconfig which produced the following:
a ping with a count of 5 sent to the remote IP yielded
a ping with a count of 5 sent to the primary DNS yielded the same

The following was received from the route command:
Two major questions remain. How do I determine if there is a firewall and how do I determine if it is running?

Secondly, how do I get applications within KDE to recognize the dialup connection if I don't use Kppp to establish the connection?

'iptables -L' plus other appropriate options will list any firewall rules currently in use.
If you have done a fresh install, then I suspect that you do not a firewall running.

The applications wanting internet access should find the 'ppp0' interface.

This concerns me a little, especially as your ping packets also show a 100% loss.
Some receive and transmit errors can occur, but this seems to be too many. This may be a hardware problem, yet you say that this all works without any problem with Windows. Puzzling.
If you connect from Windows, what is the output of 'ipconfig' and 'route -print'?

One other thing, you refer to "ispsetup". Have you tried "pppsetup"?

I'll check it, however, I suspect you are correct.


That's what I assumed, however, so far, none seem to find it, those being Firefox and Konqueror.


Indeed...and this has been the problem from the outset. I know there are means to determine what operating system someone is using...I'm wondering if my ISP has some sort of a block on against Linux systems, or if there is some rather clandestine communications that Windows Op Sys' have. The ISP is Yahoo accessed via AT&T.

Here's the results of the Windows 2000 Pro queries:

and of course the results of the ping to the primary DSN indicates an active connection the only variation from 5 pings being the time of the exchange.

"route -print" showed a lot of data, however, the IP addr 12.73.96.166 was repeated througout. I could copy it if it would help, but I suspect not.



In a prior post in this thread a member suggested I use a script he created based upon pppsetup which apparently would deal more properly with dynamic assignments. Originally I used pppsetup, however, from the outset, the problem has remained the same.

Have you tried lowering the baud rate? Perhaps you need to lower the baud rate in your linux setup. I note that you mention connect speeds of 24 or 26.4 kbps in your original post.

Baud rate is set identically to the set in W2K...115,200, and I have set it lower to experiment. The results are the same...transmit, no receive, and as well, none of the applications within KDE recognize the connection.

At this point I would pull out the multimeter and check my cable. What you are describing is the symptoms of a system that is not receiving the signals on the DCD line.
From http://www.linux.com/base/ldp/howto/...odem-dumb.html