Linux-Networking Digest #13, Volume #10 Wed, 27 Jan 99 01:13:46 EST
Contents:
Re: GTE, DSL and Linux (Stephen Carville)
redhat 5.2 and ipfw problems? (Fred Obermann)
Re: long time to log in ([EMAIL PROTECTED])
Re: configuration of eth0 & ifconfig ("John K")
TCP/IP ("Milos Popovic")
TCP/IP 2 ("Milos Popovic")
Re: Mail and DNS servers WARNING ("Stu")
Re: PPP Setup for Uswest.net Dial in (Clayton Haapala)
Re: Running Xterm from another Linux box on the network (Senthil K Narayanas)
Re: Setting up PPP ("Wael Sedky")
Linux TCP/IP stack guidance ([EMAIL PROTECTED])
Cable Modem on Linux (GarDian)
S.O.S.Halflife server via firewall ("pules")
Toshiba Integrated 56kflex modem problem? (N_Tran)
Re: Terminators and thinnet (Dai to)
Linux Firewall (Herbie van Tetering)
long time to log in (Stef)
logging UDP packets ("Willem")
Re: Can not detect D-Link 220 ethernet card (Lawrence Poon)
Re: Track down ping problems with 2 linux machine network. (Gordon Dailey)
Re: ppp help (Minh Giang)
load balancing between two t1s (or cable, or ISDN, etc) ("Tom Smith")
----------------------------------------------------------------------------
Date: Tue, 26 Jan 1999 11:49:22 -0800
From: Stephen Carville <[EMAIL PROTECTED]>
Subject: Re: GTE, DSL and Linux
Ron Forrester wrote:
> Stephen Carville <[EMAIL PROTECTED]> writes:
>
> > I just got off the phone with a GTE rep who told me in no uncertain
> > terms that GTE will not install ADSL if the connected machine runs
> > UNIX, Linux, any MacOS, or Win 3.1. I briefly explained to her that
>
> That's bullshit. I am a GTE DSL customer and I am running Linux.
>
> The ONLY issue there is if you use GTE as an ISP, they want to come out
> and setup your computer, and they require it be running Windows 95 or
> NT 4.0 when they do that.
When I was forwarded from one number to the next I assumed I was still
talking to the Telephone Company. It turns out the salesgirl from hell is
a rep for GTE Internet. The policy i was pissed about was a symptom of
GTE the ISP not GTE the Telco.
I suppose I should have realized this earlier. Since divestiture, the
Telco's have been very adamant about where their responsibility ends and
the customer's begins. The idea that GTE _insisted_ on handling the
software setup implied they consider the demarc to be the hard drive on my
computer! That makes no sense.
I checked the GTE webpage and called some of the participating ISP's and
they told me they don't care what I run as long as I pay my bill each
month. The fellow at California Prime Line ( http://www.cpl.net) even
knew what I was taking about when I said was using Linux.
If anyone is interested, the list of ISP's that offer DSL using GTE is at
http://www.gte.com/dsl/partisp.html
Maybe by starting there you can avoid the sudden rise in blood pressure I
usually experience when confronted by institutional cluelessness.
> Anyway, email me if you can't get it straight, and I will give you
> the number of a woman at GTE who is VERY helpful.
>
> rjf
Thanks to everyone who answered me. Right now, it seems the problems can
be worked out. I can use Linux and get a faster connection. Life is
Good...
--
Stephen Carville
----------------------------------------------------------------------
Civilization, as we know it today, owes it's existence to the engineers.
These are the men who, down the long centuries, have learned to exploit
the properties of matter and the sources of power for the benefit of
mankind.
L. Sprague DeCamp
------------------------------
From: [EMAIL PROTECTED] (Fred Obermann)
Subject: redhat 5.2 and ipfw problems?
Date: 26 Jan 1999 21:33:08 GMT
I have recently set up a box with redhat 5.2,
with the 2.0.36 kernel, to act as a firewall.
I believe from the following entries in the kernel
system map that support for ipfw is built into this
kernel:
00156f40 T check_ipfw_struct
001574b8 T ipfw_input_check
001574dc T ipfw_output_check
00157500 T ipfw_forward_check
00157524 T ipfw_device_event
001da274 D ipfw_ops
001da28c d ipfw_dev_notifier
ipfwadm is version 2.3.0 dated 1996/07/30.
I have 2 Ethernet cards,
one which is hooked up to a LAN, the other to
the Internet via a router (ADSL).
eth0, the nic connected to the router (which is
set up to act merely as bridge) is set up with
a static IP of say '216.36.24.36'.
eth1, is set up with a local network address of
192.168.2.1, and talks to the LAN
I have IPV4 packet forwarding turned on.
The default gateway on the Linux box is set to '216.36.24.254'.
The NT boxes on the lan have their default gateway set
to 192.168.2.1, the internal address of the Linux box.
>From the Linux box I can talk to both the
LAN and the Internet.
>From the LAN, I can talk to the Linux box.
However, I am so far, unable to talk to the Internet
from the LAN.
Even with following simplistic set of rules (as listed
with the ipfwadm command), I can't seem to communicate
with the outside world from within the LAN:
IP firewall input rules, default policy: accept
IP firewall output rules, default policy: accept
IP firewall forward rules, default policy: deny
pkts bytes type prot opt tosa tosx ifname ifaddress source
destination ports
0 0 acc/m all ---- 0xFF 0x00 any any 192.168.2.0/24
anywhere n/a
Is there something obvious that I am missing?
Fred O
please remove the under-bar in [EMAIL PROTECTED] to reply.
--
===========================================================================
Another satisfied Aracnet user who Aracnet internet service
who hasn't edited their .signature Ring +1 503 626.6873 V.34 (33600) 24hrs
,but might if you tell them. >=-)> Browse http://www.aracnet.com for info!
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: long time to log in
Date: 26 Jan 1999 17:13:26 -0600
In article <[EMAIL PROTECTED]>, Stef <[EMAIL PROTECTED]> wrote:
>I conected two computers using ethernet. Both run Debian 2.0. Ones IP
>is 192.168.1.2, the others 192.168.1.3.
>Ping works fine from one machine to the other and vice versa. telnet
>from 192.168.1.3 to 192.168.1.2 also works fine. But when I telnet
>to 192.168.1.3 (even from 192.168.1.3 itself) I get:
>
>Trying 192.168.1.3...
>Connected to 192.168.1.3.
>Escape character is '^]'.
>
>Then nothing happens for some minutes, and finaly I get the login
>prompt. Also rlogin or telnet to ports 80 and 25 exhibits this
>behaviour.
>
>What coudl cause this lag?
>
A search on Deja News http://www.dejanews.com would have no doubt turned
up at least 50 answers to this FAQ. Or perhaps just skimming a few days
worth of articles would have answered it as well.
Your system is doing a DNS lookup and until it fails you get no login.
fix your /etc/hosts file and /etc/host.conf and you should check your
/etc/resolv.conf while you are at it. I would strongly urge you to
get a good book on Unix system admin. It will explain all this in
much greater detail. But the short answer is:
/etc/host.conf
order hosts,bind
tells your system to check your hosts file *first* then your nameserver.
And make damn sure that the host is entered in the host file. Though to
be honest it sounds like your hosts file might be messed up.
Regards
Bill
------------------------------
From: "John K" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,alt.linux,comp,linux.redhat,linux.redhat.misc
Subject: Re: configuration of eth0 & ifconfig
Date: Tue, 26 Jan 1999 23:57:13 -0500
Thanks for your info.
Yes, I got this far. The problem is the Linux machine. The Ethernet card is
not getting a IP number. When I tested the link durring the jumper
installation with both computers connected under DOS, the link worked.
Therefore, the problem is not cables or conflics. The problem is that Linux
is not assigning ant IP number to eth0.
I made this conclusion because when I try to ping the Linux computer to his
own IP (192.168.0.2) Host is unreachable.
So If It can't ping its own IP, Linux is the problem. Any idea how to
assign eth0 a IP?
PS. Wingate provides DCHP.
>6. If U've gotten this far and ur still saying "this aint helping any" then
>ur linux machine is the problem... ur internal ethernet card on linux isnt
>getting a ip-number... isnt installed correctly (but this should of shown
in
>step 3) or something i dont know about.
------------------------------
From: "Milos Popovic" <[EMAIL PROTECTED]>
Subject: TCP/IP
Date: Wed, 27 Jan 1999 00:08:00 -0500
Hi,
I am trying to install TCP/IP on my RedHat Linux 4.01. I have a Rockwell
modem, and an IP account that I regularly use with my Windows 95. Does
somebody know of a good web-site with directions on how to configure your
Linux in order to connect to the internet via ISP.
Thanks,
MILOS POPOVIC
------------------------------
From: "Milos Popovic" <[EMAIL PROTECTED]>
Subject: TCP/IP 2
Date: Wed, 27 Jan 1999 00:09:11 -0500
Hi,
I am trying to install TCP/IP on my RedHat Linux 4.01. I have a Rockwell
modem, and an IP account that I regularly use with my Windows 95. Does
somebody know of a good web-site with directions on how to configure your
Linux in order to connect to the internet via ISP.
Thanks,
MILOS POPOVIC
please e-mail me @
[EMAIL PROTECTED]
------------------------------
From: "Stu" <[EMAIL PROTECTED]>
Subject: Re: Mail and DNS servers WARNING
Date: Tue, 26 Jan 1999 16:35:47 -0500
>DNS, POP3, IMAP4 and SMTP work very very well. We use it without any
>problems at all . Though I invested some time and moneyt in my SENDMAIL
>book.
WARNING: There is a buffer overflow in the imap4 server that ships with
redhat. And there's an existing exploit. I know of two people who got hit
with this. DO NOT USE the imap4 server unless you're sure the buffer
overflow has been fixed in the version you have.
------------------------------
Crossposted-To: mn.online-service
From: [EMAIL PROTECTED] (Clayton Haapala)
Subject: Re: PPP Setup for Uswest.net Dial in
Date: Wed, 27 Jan 1999 04:09:44 GMT
In article <[EMAIL PROTECTED]>,
Jeffrey S. Kline <[EMAIL PROTECTED]> wrote:
>I agree....
>
> GET A REAL ISP and hack off with these ISP wannabe's
>
>Cheers
>Jeff
>
Now, where's the challenge in that? :-)
My main surprise was that it simply didn't work right away, since
it does so easily with every other ISP I've tried. Heck, I've even
set myself up as an ISP after a fashion, but just to my brother for dial-in,
and that was easy, too.
--
Clay Haapala "Woe to he who fears change more than disaster! For
[EMAIL PROTECTED] how can he then avoid disaster?" -- from "the Firebugs"
------------------------------
From: Senthil K Narayanas <[EMAIL PROTECTED]>
Subject: Re: Running Xterm from another Linux box on the network
Date: Wed, 27 Jan 1999 00:29:08 -0500
On Wed, 27 Jan 1999 [EMAIL PROTECTED] wrote:
> In article <78gql6$loa$[EMAIL PROTECTED]>,
> "Mike Drummond" <[EMAIL PROTECTED]> wrote:
> > I am attempting to run Xterm from another Linux box on my home LAN and I am
> > getting some permission problems that I need help solving
> >
> > I log into the other Linux box via Telnet and set up my display as follows
> >
> > export DISPLAY=<IP of this machine>:0
> >
> > I then type
> >
> > xterm &
> >
> > and I get the following error message
> >
> > xlib client is not authorized to connect to server
> > xlib connection refused by server
> >
> > Could someone please explain where I need to go to set up my permissions?
> >
> > I am running S.U.S.E on both boxes
> >
> >
>
> permission stuff should be held in the following files:
>
> o /etc/hosts
> o /etc/hosts.allow
> o /etc/hosts.deny
>
hi,
The above stuff applies to normal remote logins(ftp,rlogin,telnet)
and access to other services lpd,finger etc.
xlib authentication(access to connect to Xserver) is made by
cookie mechanism by having same tokens in .Xauthority file in users
home directories .
normally "mkcookie" or "mkxauth" is used to update tokens in
.Xauthority files.
The second method would be to add hosts to Xserver's access
control list using "xhost" program.(This allows any client started by
any user from the remote host to connect to your Xserver , In a home
network this really doesnt matter)
man pages contain the nitty-gritty of above utilities.
senthil
>
> add something like ALL:ALL to hosts.allow and you should prolly be in
> business.
>
> note: ALL:ALL may not be the best 'cuase it lets everybody in. if you're
> just going to use the one other box substitute the ip addy....
>
>
> a complete idiot,
> Don'r
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>
>
------------------------------
From: "Wael Sedky" <[EMAIL PROTECTED]*>
Crossposted-To: alt.os.linux.slackware,comp.os.linux.setup
Subject: Re: Setting up PPP
Date: Wed, 27 Jan 1999 00:35:47 -0800
Try this link
I am having a similar problem setting up CHAP. The how-to is a little hard
to follow when it comes to CHAP, but I will try X-ISP. It seems like an easy
to use program.
http://linux.tqn.com/msub36.htm
------------------------------
From: [EMAIL PROTECTED]
Subject: Linux TCP/IP stack guidance
Date: 26 Jan 1999 21:39:00 GMT
Hi --
I am beginning work on a network emulation system which requires playing
with messages at the IP stack layer as done by NAT/Masquerading/Firewalls.
I am somewhat familiar with the workings of the BSD protocol stack, but
wanted to ask this: are there any good refs for the linux stack and its
implementation details?
I've look through the khg and the linux/Documentation/networking files, and
I've looked at the source, but wondered if there was a better reference for
the layer handoffs, etc. Thanks for any ptrs, etc. that can be offered.
ben
------------------------------
From: [EMAIL PROTECTED] (GarDian)
Subject: Cable Modem on Linux
Date: Wed, 27 Jan 1999 05:34:09 GMT
Hi,
I am a beginner to Linux.
Currently I am running Red Hat 5.2 and have a cable modem internet
connection. I tried to use DHCP to connect to the net but it doesn't
seem to work. How do I configure the Linux to connect to cable
modem???
Thanks
GarDian
[EMAIL PROTECTED]
------------------------------
From: "pules" <[EMAIL PROTECTED]>
Subject: S.O.S.Halflife server via firewall
Date: Sun, 24 Jan 1999 22:52:22 +0100
I have been reading and trying for weeks now, but I still cant get the
HalfLife dedicated server working via my Linux firewall. i've seen some
games on masq apps which work with ipautofw, and ive tried, but no success.
(There doesn't seem to be any info on ipautofw)
I know the following ports must be opened:
7001tcp, 27005udp, 27010udp, 27015udp, 27016udp, 6000tcp, 6003tcp.
I would be enormously happy with a tip on what to write in my firewall
script to open those properly. I don't care about security on those ports, I
just want to play.
P.S. Please dont refer me to the HOWTO's and such, because thats what ive
been wasting my free time with the last three weeks.
------------------------------
From: N_Tran <[EMAIL PROTECTED]>
Subject: Toshiba Integrated 56kflex modem problem?
Date: Sun, 24 Jan 1999 15:51:40 -0600
I just installed Redhat5.2 on my Toshiba Satellite Pro 490CDT, Everything
went through very smoothly until I tried to install the modem. It doesn't
respond whenI tried to activate it. Does any one know how to solve this
problem??
Thanks in advance.
There is only one happiness in
life, to love and be loved.
-George San-
=====BEGIN PGP SIGNATURE=====
KeyID 1024/948FD6B5
Fingerprint EE C9 E8 AA CB AF 09 61 8C 39 EA 47 A8 6A B8 01
Version: 2.6.2
iQCVAwUBMhyBbQtXkSokWGapAQFZwgQAl6oljDTIflypKJRSXvCfkzwOIK7rU4Uq
t+lkIfnqsLMxH1hgSGxOIUaV2lA7gn6wdesKoDxqv9xpKAU7PpyfpQxZkTdVyGTS
nffv0wz8tRy3YxW2Od1mDf+a3RxfHSF61jPQB0GgvJYovZDg1Abp+0ovSosuQ01k
yldDUV3ofvo=
=j+7P
=====END PGP SIGNATURE=====
------------------------------
From: Dai to <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Terminators and thinnet
Date: Sun, 24 Jan 1999 13:48:51 -0800
"Thin net is the best way to link lots of errors together."
The way thin net works is RG58 cable has an impedance of 50ohms. When
the network signal reaches the end of the cable it wants to reflect back
down the cable .
Putting a terminator with a resistance equal to the impedance of the
cable will cause the resistance at the terminator to theoritically go to
infinite. Thats what keeps the signal from bouncing back down the cable.
Also one of the terminators should be grounded.
Thin net can stand a slightly out of tolerance terminator but it is a
miracle that it works to begin with. A couple other things to look out
for... Running the cable over with office chairs will mash it and change
the impedance. Also the impedance of the cable can change with age.
Wayne
Boris Statnikov wrote:
> I have an RG58 A/U Coaxial and attempted to use 75ohm (as opposed to
> 50) terminators. Now I can't guarantee that I've set up my ethernet
> cards correctly to work with base2 instead of baseT, but everything
> worked as baseT before and I did change the cards' bios settings. I
> suspect terminators, but can 25 ohm difference really do it?
>
> Boris
>
> --
> Too many cooks spoil the brouhaha.
>
> "Bored Of The Rings", The Harvard Lampoon
>
>
------------------------------
From: Herbie van Tetering <[EMAIL PROTECTED]>
Subject: Linux Firewall
Date: Tue, 26 Jan 1999 21:22:50 +0000
Hello,
I need some advice on configuring a firewall for a linux box. I am
currently using a RedHat and Slackware distribution, I am interested in
configuring a firewall for linux in general, not for a specific
distribution. Does anybody have a list on most commonly used firewalls
and/or programs that implement them?
---
If Intel had designed human beings, it would have put in a bit that made
them revert back to chimpanzee mode, most of the brain disabled, no
speech, eats mostly bananas, etc.
- A.S. Tanenbaum, Structured Computer
Organisation
------------------------------
From: Stef <[EMAIL PROTECTED]>
Subject: long time to log in
Date: 24 Jan 1999 23:34:12 +0100
I conected two computers using ethernet. Both run Debian 2.0. Ones IP
is 192.168.1.2, the others 192.168.1.3.
Ping works fine from one machine to the other and vice versa. telnet
from 192.168.1.3 to 192.168.1.2 also works fine. But when I telnet
to 192.168.1.3 (even from 192.168.1.3 itself) I get:
Trying 192.168.1.3...
Connected to 192.168.1.3.
Escape character is '^]'.
Then nothing happens for some minutes, and finaly I get the login
prompt. Also rlogin or telnet to ports 80 and 25 exhibits this
behaviour.
What coudl cause this lag?
Stef
--
WebMaster D-WERK
UNIX and Windows NT administration, SOS-ETH
ETH Zurich
[EMAIL PROTECTED] http://hoes.li
------------------------------
From: "Willem" <[EMAIL PROTECTED]>
Subject: logging UDP packets
Date: Sun, 24 Jan 1999 23:37:38 +0100
Since I'd like to know the protocol of a Windows client program running on
our intranet, I'm looking for a program or docs about sniffing/logging udp
packets. I am not that experienced with C to code my own, and the ethernet
snif programs I've found so far only log tcp packets. Could anyone help me?
Thanks so much,
Willem
PS Any perl examples or docs are also greatly appreciated!
------------------------------
From: Lawrence Poon <[EMAIL PROTECTED]>
Subject: Re: Can not detect D-Link 220 ethernet card
Date: Tue, 26 Jan 1999 22:55:48 -0700
Hi Snows,
I use D-link 220 ethernet cards in my RH Linux Box and they work fine.
Try to boot up your system with Dos and run a setup program ,
available from www.dlink.com, and make sure the setup program could
detech your NIC and no resource conflicts with other devices.
I don't think Linux could detect your D-Link 220 if they have resource
conflicts.
Hope it may help.
Lawrence Poon
Snows wrote:
> I installed red hat in my pc (opps newbie again). Everthing was fine
> except the networkcard. It couldnot detect my D-Link 220 ethernet
> card. I read through the Ethernet-HOW-TO and Kernel-HOW-TO, then tried
> to go through the instruction and recompile my own kernel. But I even
> could not run "make" in /usr/src/linux directory. The error mesg says
> "not target".
> Could someone give me some clues?
>
> Thanx.
------------------------------
Date: Wed, 27 Jan 1999 00:06:54 -0500
From: Gordon Dailey <[EMAIL PROTECTED]>
Subject: Re: Track down ping problems with 2 linux machine network.
I'm no expert and I'm really pretty new at this. I'm currently doing the
same thing you are and learning about linux networking in the process.
However, I may some ideas.
First, make sure both network cards actually work. Im my case I was using
Intel cards and I had a diagnostic program to verify that each card was
okay. Obviously, if one of the cards is bad, things will not work.
Second, make sure that your cabling is sound. I had the same problem you
had: When I first connected my machines, I couldn't ping one from the other
regardless of which machine I pinged from. I knew the cards were fine and
each machine was seeing its own card, that left the cabling to investigate.
I am using thinnet--coax with BNC connectors--which requires tee connectors
and terminators at each end of the cable. I had good quality cable (which
you may want to verify) and I had used the proper tee connectors and
terminators. However, the terminators were taken out of the spare parts bin
such that they were questionable. I got some more and swapped out the ones
I had. Lo and behold, everything worked fine! So, it turned out that the
problem was just that one of the terminators I had was bad.
I hope this helps.
--Gordon
Darren Ford wrote:
> I still need help tracking down ping problems between my two machines.
> Let me give you some out put and some background and see if you can
> help.
>
> Here is route output:
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.0.0 * 255.255.255.0 U 0 0 1
> eth0
> 127.0.0.0 * 255.0.0.0 U 0
> 0 2 lo
>
> Here is ifconfig output: (using netgear 300Tx NIC and de4x5 driver, I've
> tried netgear's tulip driver too and similar results)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
> UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
> RX packets:79 errors:0 dropped:0 overruns:0
> TX packets:79 errors:0 dropped:0 overruns:0
>
> eth0 Link encap:Ethernet HWaddr 00:40:05:41:98:37
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0
> TX packets:0 errors:6 dropped:0 overruns:0
> Interrupt:10 Base address:0x6200
>
> Here is arp output: (ford2 is my other malfunctioning machine)
>
> Address HWtype HWaddress Flags Mask Iface
> ford2
> (incomplete) eth0
>
> Here is /etc/hosts: (I did have 127.0.0.1 localhost
> localhost.localdomain in there)
>
> 192.168.0.2 ford2 ford2.killnt.net
> 192.168.0.1 ford1 ford1.killnt.net
>
> The other machine has identical output except it's IP is 192.168.0.2.
>
> Why, if I don't even have the other machine connected, does ping just
> give this and sit there and why does the local loopback device packet
> count go up?
>
> PING 192.168.0.2 (192.168.0.2) 56 data bytes:
------------------------------
From: Minh Giang <[EMAIL PROTECTED]>
Subject: Re: ppp help
Date: Sun, 24 Jan 1999 17:44:42 -0500
first of all, I put the debug option in /etc/ppp/option and dial....there's no
file in /var/log/debug...
What do I need to put in /etc/syslog.conf to write to this file?
This is what I got in /var/log/messages by putting kdebug 1 in
/etc/ppp/options
Jan 24 16:41:22 localhost pppd[610]: pppd 2.3.5 started by root, uid 0
Jan 24 16:41:22 localhost pppd[610]: Serial connection established.
Jan 24 16:42:33 localhost kernel: pp_tty_ioctl: set flags to 10000
Jan 24 16:42:33 localhost kernel: pp_tty_ioctl: set flags to 10000
Jan 24 16:42:33 localhost kernel: pp_tty_ioctl: set xasyncmap
Jan 24 16:42:33 localhost kernel: pp_tty_ioctl: set xmit asynmap ffffffff
Jan 24 16:42:33 localhost kernel: pp_tty_ioctl: set flags to 1000
Jan 24 16:42:33 localhost kernel: pp_tty_ioctl: set mru to 5dc
Jan 24 16:42:33 localhost kernel: pp_tty_ioctl: set rcv asyncmap ffffffff
Jan 24 16:42:33 localhost kernel: pp_tty_ioctl: set flags to 10000
Jan 24 16:41:22 localhost pppd[610]: Using interface ppp0
Jan 24 16:41:22 localhost pppd[610]: Connect: ppp0 <--> /dev/modem
Jan 24 16:41:22 localhost pppd[610]: LCP: timeout sending Confing-Request
Jan 24 16:42:33 localhost kernel: ppp: channel ppp0 closing.
Jan 24 16:41:22 localhost pppd[610]: Hangup (SIGHUP)
Jan 24 16:41:22 localhost pppd[610]: Modem hangup
Jan 24 16:41:22 localhost pppd[610]: Connection terminated.
Jan 24 16:41:22 localhost pppd[610]: Exit.
Clifford Kite wrote:
> Minh Giang ([EMAIL PROTECTED]) wrote:
>
> : I'm having trouble connect to our ISP using RedHat 5.2 Linux using
> : pppd.
> : here are my setup:
>
> : # /etc/resolv.conf
> : search fast.net
> : nameserver 198.69.204.2
> : nameserver 198.69.204.7
>
> : #/etc/ppp/options
> : connect /etc/ppp/ppp-on-dialer
> : 115200
> : crtscts
> : asyncmap 0
> : defaultroute
> : modem
> : lock
> : noipdefault
>
> To use PAP you need the pppd option "user myusername" or "name myusername"
> where myusername is the one in pap-secrets.
>
> : #/etc/ppp/ppp-on-dialer
> : #!/bin/sh
> : exec chat -V
> : TIMEOUT 10 \
> : ABORT "\nBUSY\R" \
> : ABORT "\nNO ANSWER\r" \
> : ABORT "\nNO CARRIER\r" \
> : ABORT "\nNO DIAL TONE\r" \
> : ABORT "\nRING\r\n\r\n\RING\r" \
> : '' AT \
> : TIMEOUT 35 \
> : OK ATDT9540300 \
> : CONNECT ''
>
> Try replacing the CONNECT '' with CONNECT '\c' . This prevents a carriage
> return from being sent - often the source of trouble.
>
> : #/etc/ppp/pap-secrets
> : myusername * my_password
>
> : my message log:
>
> : .....localhost pppd[536]: pppd 2.3.5 started by root, uid 0
> : .....localhost ifup-ppp: pppd started for ppp0 on /dev/modem at 115200
> : .....localhost pppd[536]: Serial connection established
> : .....localhost pppd[536]: Using interface ppp0
> : .....localhost pppd[536]: LCP: timeout sending Config-Requests
> : .....localhost pppd[536]: Connection terminated
> : .....localhost pppd[536]: Exit.
>
> If neither suggestion above works for you, then you may need to look in
> /var/log/debug for ppp negotiation messages for a clue. Add the pppd
> option "debug" to get meaningful messages.
>
> An after-thought: you don't show the timestamps for the messages here.
> If the connection process seems extra long, then a misconfigured IRQ
> is a possibility.
>
> --
> Clifford Kite <[EMAIL PROTECTED]> Not a guru. (tm)
> /* Governments should be changed like diapers - often and for the
> * same reason. */
------------------------------
From: "Tom Smith" <[EMAIL PROTECTED]>
Subject: load balancing between two t1s (or cable, or ISDN, etc)
Date: Sun, 24 Jan 1999 18:03:00 -0500
There are two T1s (or cable, or ISDN, whatever) going to the same upstream
provider. The routers themselves are not balanced.
How would you make the linux machine balance connections between the two
routers?
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.networking) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Networking Digest
******************************
