Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Linux OS.: Technical questions -- Ignore unavailable to you. Want to Upgrade?

To: g_m10 who wrote (171)	2/18/1999 4:32:00 PM
From: Gerald Walls	Respond to of 484

Have to admit that gossips about Linux being ready for the desktop prime time are slightly exaggerated. They're Wild Fabrications, also known as Damn Lies. Today I tried to get connected using linuxconf for setup. Nice programm, but doesn't have TCP/IP in it. To the best of my ability setup PPP, but didn't get any signs of life. Gave a call to my ISP. The answer was: 1. For Linux they need to setup something on their server 2. They don't support Linux 3. He will email to his boss, and the boss will email me within 48 hours about what can be done. It isn't very difficult, just confusing. Read the how-tos. They got me through it. They were probably installed onto your Linux system or you can get to them through linux.org or directly at linux-howto.com Here's a couple that will be immediately useful: PPP: linux-howto.com TCP/IP: linux-howto.com As far as what the ISP told you, they're full of sh\|t: 1) Total BS. They do not know and do not care what OS you use. They care about a PPP connection and TCP/IP. 2) From 1, the only sense this makes is that they don't have an installation program to set up the TCP/IP numbers for you, or that they don't have a pretty "internet desktop." 3) Don't hold your breath waiting for an intelligent answer.

To: g_m10 who wrote (171)	2/18/1999 9:59:00 PM
From: Mitch Blevins	Read Replies (2) \| Respond to of 484

Today I tried to get connected using linuxconf for setup. Nice programm, but doesn't have TCP/IP in it. To the best of my ability setup PPP, but didn't get any signs of life. Gave a call to my ISP. The answer was: 1. For Linux they need to setup something on their server 2. They don't support Linux 3. He will email to his boss, and the boss will email me within 48 hours about what can be done. The lack of TCP/IP was a kind of surprise. I always thought it came from Unix world. As stated before, your ISP is full of shit. You do not have to rely on them for special setup, and TCP/IP is fully present in your system. You just may be missing an option from whichever setup program you are using (I'm not familiar with linuxconf). Take things one step at a time. First, make sure your modem actually works and can dial out. Use minicom. Find your chatscript (/etc/ppp/chat?) and look at it. This controls the modem dialing and possibly handles the Login:, Password: challenge/response stuff. Find your ppp options file (/etc/ppp/options?). This controls the options of pppd. pppd is the program that takes control of the connection after the chatscript exits. An important option is the 'debug' option because it can allow you to spy on what is happening to help debug the process. See the man page for details. Try connecting using the RH supplied script (/etc/ppp/ip-up?). You can look in /var/log/messages or /var/log/ppp or similar for messages from the pppd. Read about the different types of authentication methods in the HOWTOs given in the previous message, or the man page for pppd. You have 3 different kinds of authentication: 1) Clear text 2) PAP 3) CHAP Clear text authentication is controlled in the chat script, with a challenge/response that will listen for something like "login:" and then send the appropriate username. Similar for "password:". PAP and CHAP work basically the same as each other. You must then fill out the /etc/ppp/chap-secrets or /etc/ppp/pap-secrets file as specified in the man page. Also, you must add an entry for username in the /etc/ppp/options file. There is a variation of CHAP made by Microsoft called MS-CHAP. This is supported, but last I checked you needed to recompile pppd to support it. (This may have since changed). Maybe this is what your ISP was talking about? Sometimes you can ask your ISP which of these methods of authentication they use... but sometimes the tech guy has no clue. To find out, you can snoop on the connection (remember the 'debug' option) and see if the "login:" challenge is being sent. If so, you probably have a clear text auth and don't need PAP or CHAP setup. If you don't have clear text... luckily you can set up to work with either chap or pap at the same time. Just fill out both the pap-secrets and chap-secrets files. You will need to remove any clear text lines used in your chatscripts. Hope this helps a little... -Mitch

To: g_m10 who wrote (171)	2/19/1999 4:52:00 AM
From: E. Charters	Respond to of 484

Don't worry. TCP/IP is part of Linux. Your ISP does not need to support Linux. You have to set up networking on your system sometimes. this is done with netconfig. You set it up with a phony host name and for local loop. It's a bit tricky. Then you set up DIP or chat scripts for dial in. It works. I will show you how its done when I get a free mo. EC<:-}

To: g_m10 who wrote (171)	2/19/1999 6:40:00 PM
From: Marcelo Magnasco	Read Replies (1) \| Respond to of 484

Today I tried to get connected using linuxconf for setup. Nice programm, but doesn't have TCP/IP in it. To the best of my ability setup PPP, but didn't get any signs of life. Gave a call to my ISP. The answer was: 1. For Linux they need to setup something on their server 2. They don't support Linux 3. He will email to his boss, and the boss will email me within 48 hours about what can be done. The lack of TCP/IP was a kind of surprise. I always thought it came from Unix world. Errr, what do you mean it doesn't have tcp/ip? It's part of the kernel, there is no way to take tcp/ip OUT of linux: it's not an option. Furthermore, if your ISP offers PPP, then ppp is ppp is ppp, has nothing whatsoever to do with Windows or Linux. Of course you can get connected. The problem with setting up a ppp connection to an isp is that the server may reply strange things. Happened to me. What you do is the following: use control-panel , go to the network thingie, say you want a brand new ppp (or you want to edit the one you have), and then be sure to check on DEBUG THE CONNECTION. That way, whenever you try to connect (your modem does go piii paa paaa, right?) the full log will be written on /var/log/messages . You will see what you get from the ISP and what your script was expecting. In my case, I was expecting "login:" and was getting "UserId:", and there was also an issue of the script expecting "CONNECT 28800" from the modem and the modem replying "CONNECT 192600" (ha!! I wish!). Other option is to connect by hand using cu, taking note of what you see, and then take it from there. The script in question is somewhere on /usr/sysconf/network-scripts/chat or something like that. PPP setup is definitely not ready for prime time. However, let me assure you that you CAN get connected, and wish you best of lucks. Or, even better, try again and ask again. Best, m