Linux-Networking Digest #137, Volume #10 Sun, 7 Feb 99 09:14:01 EST
Contents:
Re: newbie: ping ok --no telnet ftp (Jianmang Li)
Re: ipforwarding / masquarading ([EMAIL PROTECTED])
Re: PPP hangs after lots of data (Nathan Kurz)
HylaFAX server receive problem (Sebastian Luhr)
Re: newbie: ping ok --no telnet ftp ("Pedro Ferreira")
Re: ipforwarding / masquarading ("TiM")
Problems with addtosmbpass/password-encryption of Win98 (Yves Schlegel)
3c905B compiled module wanted (dbp)
Re: DOS & WIndows to Linux (Eckardt Augenstein)
newbie: lose default gateway info on reboot (Thomas Miller)
Re: mail - "we do not relay" error ("Pedro Ferreira")
Re: IP masquerading ("Pedro Ferreira")
----------------------------------------------------------------------------
From: Jianmang Li <[EMAIL PROTECTED]>
Subject: Re: newbie: ping ok --no telnet ftp
Date: Sun, 07 Feb 1999 13:04:10 +0100
[EMAIL PROTECTED] wrote:
> This is probably an easy question, but I've been driving myself nuts trying to
> figure it out, with no luck.
>
> I am running Red Hat 5.1 in a small home lan with some windows machines (98 &
> NT4). TCP/IP seems to be working fine, since I can ping all the way around,
> my problem is that in trying to telnet or FTP from a win machine to linux my
> login is refused. After reading some other posts I tried to telnet to
> localhost, and had the same result. In all cases I tried logging in as both
It sound to me that your telnet server daemon is not started. Check the
/etc/services file see if the telnet services is blocked.
>
> root, and another user, neither worked. Additionally (or probably because
> of) I can't get SAMBA to work right. the command smbclient -L larry will
> list the C drive as an available resource, but smbclient \\larry\c comes
> back with a menu- type list. I also am not seeing my linux box (curley) in a
> network neighborhood window. Please Help!!! It' must be something simple,
> but I'm just not seeing it.
>
> Thanks in Advance.
>
> Dennis
>
> PS: I will also post any responses e-mailed to me in case someone else is in
> the same boat.
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: ipforwarding / masquarading
Date: Sun, 07 Feb 1999 12:03:44 GMT
> Well, the HP site worked fine for me. I'm masqing a DSL connection
> with 192.168.x.x addresses behind it. I browsed with Netscape 4.0?
> running on a linux box behind the firewall box. I don't run any local
> DNS services and use standatd 10BaseT abd 10Base2 connections.
>
Thanks for checking that Greg.
Could someone running Win95 as the browser check it for me?
(I've had one other person confirm the same problem so far)
Cheers,
Steve.
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED] (Nathan Kurz)
Subject: Re: PPP hangs after lots of data
Crossposted-To: comp.protocols.ppp
Date: Thu, 04 Feb 1999 02:54:07 GMT
I have experienced what seems to be the same problem. PPP would
connect fine, would work fine for a 1-10 minutes, and then would hang.
I am also running Linux on a notebook. If I recall correctly, I had
the same problems with all possible combinations of:
Thinkpad 560 with Pentium 133
Megahertz CC/XJEM3336 Ethernet/Modem
24 Megs and 40 Megs of RAM
Linux 2.0.34 and Linux 2.0.35
pppd 2.2.0 and pppd 2.3.5
It seemed like the problems would often occur whenever the machine
began to swap. On the other hand, this wasn't always be the case.
With more memory, the problem seemed to occur less often. Using
'irqtune' may have helped slightly, but certainly did not solve the
problem. The amount of time the problem took to appear correlated
strongly with the amount of data being transferred. I did not
perceive a difference between sending and receiving data.
I think I tried every single ppp option and none made the problem
better. lcp-echo-failure would serve to automatically take down the
connection, but failed miserably in conjuction with persist (but I
think this is a separate bug). Telling my modem not to use
compression prolonged the onset of the problem, but I think that was
because less data was being transferred. As such, I do not believe
that the problem is related to packet size or protocol.
Judging by 'route -n', there appeared to be no routing problems -- at
least on the local end. Viewed with 'ifconfig', the ppp0 interface
appeared normal. As stated, 'tcpdump -i ppp0' would show a gradual
stoppage of packets, apparently due to windows being filled.
<possibly-faulty-recollection>I did not notice that any replies were
received, though, 'ping' or otherwise. According to 'pppstats -w 1',
no packets were being sent or received.</possibly-faulty-recollection>
Running gdb on the pppd-2.3.5 process (recompiled with debugging
information) would show that pppd was stuck in a select() that was
called from wait_input(timeleft(&timo)) at main.c line 524.
'timeleft' would evaluate to zero, implying that the wait_input would
wait forever. <possibly-faulty-recollection>If I forced the select to
return, pppd would try to take down the connection. Interestingly, it
would hang again before it died, somewhere in disestablish_ppp(). If
I attached and detached with gdb (doing nothing else) it would then
die gracefully.</possibly-faulty-recollection>
I've travelled a lot with this machine, and have never had a similar
problem with any other ISP. I do not believe that other users have
this problem with this ISP. But after trying everything I could think
of, I recently I solved the problem by changing ISP's. Since then my
connection has not hung once. But if I can help anyone solve this
problem by reconnecting to the former ISP, I'm sure that I can
recreate the problem at will.
Hope this helps someone,
--nate
[EMAIL PROTECTED]
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Chris Croughton) writes:
>Hi!
>
>I have a problem which I think is something to do with pppd. I can dial
>out fine, I connect to my ISP fine, names resolve OK, and I can start
>doing stuff. Looking at the web, using FTP, ping, telnet, everything
>works.
>
>However, after a while (and particularly when I'm sending a lot of data,
>rather than receiving it) the connection seems to hang. Not hang UP, the
>phone line is still in use and the modems are still talking to each other,
>but nothing gets sent.
>
>It seems to be related to packet size as well, and posibly protocol. The
>first thing to stop are TCP connections (FTP especially), and ping will
>keep on running and getting replies. Then ping stops getting replies
>after a while as well.
>
>I've run it with tcpdump looking at ppp0, and what seems to happen is that
>the incoming replies stop (for the TCP packets) first, then the outgoing
>TCP packets stop (presumably because the window is blocked), then ping
>replies (ICMP echo reply) stop, and finally ping (ICMP echo) packets
>aren't even sent. At this point, the only thing to do is drop the line
>and try again. Using ps, pppd is still there and running, and ppp0 is
>still present doing ifconfig.
>
>Note that during all this my local Ethernet is working fine, so it's not
>TCP/IP in general that has the problem. Nor is it a routing problem,
>route -n gives the same output throughout.
>
>System details:
>
> Pentium 233, 48Mb RAM (notebook machine)
> PCMCIA modem card, 33k6 using Cirrus Logic modem chipset
> Linux kernel 2.0.34, Debian 2.0 distribution
> pppd 2.3.5, installed as binaries from the Debian CD
>
>Connecting using wvdial, pup/pdown or chat, same problem whatever the
>method.
>
>If you want further information, traces, logs etc. let me know. Or if
>there are some commands I haven't found to look at the state of software
>queues or whatever.
>
>I haven't seen anything about this sort of problem anywhere (the problems
>usually seem to be initial connection or dropped lines, not failures in
>between). If anyone has seen this sort of thing before, any ideas are
>welcome...
>
>Note: this is crossposted to comp.protocols.ppp and to
>comp.os.linux.networking, because it could be either a pppd problem or a
>Linux specific one. If you change it to reply to only one of them, please
>keep the subject as c.o.l.n is too busy for my system to handle all the
>traffic and I'm filtering on the subject. Or if you put it to some other
>newsgroup as more relevant, please mail me and let me know so I can add
>it...
>
>Thanks,
> Chris C
>
------------------------------
From: Sebastian Luhr <[EMAIL PROTECTED]>
Crossposted-To: aus.computers.linux
Subject: HylaFAX server receive problem
Date: Sun, 07 Feb 1999 17:59:58 +0800
G'day.
I've got a "interesting" problem with the hylafax server when receiving
faxes.
I haven't been able to find other posts on this, or any references to it in
the FAQ.
Basically - sending faxes is ok. Receiving faxes *appears* to be fine
according to hylafax. Result though is that after about 60 lines, the
rest of the fax is discarded.
After discarding, an "OK" error code is returned.
According to the session trace, all 220 or so lines of the fax were
received. (At 7.7lines / mm ..)
---Begin session trace---
Feb 08 15:00:54.28: [16202]: SESSION BEGIN 00000031 [phone number]
Feb 08 15:00:54.28: [16202]: <-- [4:ATA\r]
Feb 08 15:00:56.12: [16202]: --> [3:FAX]
Feb 08 15:00:56.12: [16202]: MODEM set baud rate: 19200 baud (flow control
unchanged)
Feb 08 15:00:56.12: [16202]: MODEM set baud rate: 19200 baud, input flow
XON/XOFF, output flow
XON/XOFF
Feb 08 15:00:56.12: [16202]: ANSWER: FAX CONNECTION
Feb 08 15:00:56.12: [16202]: STATE CHANGE: ANSWERING -> RECEIVING
Feb 08 15:00:56.12: [16202]: MODEM input buffering enabled
Feb 08 15:00:56.12: [16202]: RECV FAX: begin
Feb 08 15:01:03.74: [16202]: --> [5:��^�]
Feb 08 15:01:03.74: [16202]: --> [29:+FTSI: " 08 (number)"]
Feb 08 15:01:03.74: [16202]: REMOTE TSI "08 (number)"
Feb 08 15:01:04.06: [16202]: --> [22:+FDCS: 1,3,0,2,0,0,0,0]
Feb 08 15:01:04.06: [16202]: REMOTE wants 9600 bit/s
Feb 08 15:01:04.06: [16202]: REMOTE wants page width 1728 pixels in 215 mm
Feb 08 15:01:04.06: [16202]: REMOTE wants unlimited page length
Feb 08 15:01:04.06: [16202]: REMOTE wants 7.7 line/mm
Feb 08 15:01:04.06: [16202]: REMOTE wants 1-D MR
Feb 08 15:01:04.17: [16202]: --> [2:OK]
Feb 08 15:01:04.17: [16202]: <-- [7:AT+FDR\r]
Feb 08 15:01:05.69: [16202]: --> [5:+FCFR]
Feb 08 15:01:07.72: [16202]: --> [22:+FDCS: 1,3,0,2,0,0,0,0]
Feb 08 15:01:07.72: [16202]: REMOTE wants 9600 bit/s
Feb 08 15:01:07.72: [16202]: REMOTE wants page width 1728 pixels in 215 mm
Feb 08 15:01:07.72: [16202]: REMOTE wants unlimited page length
Feb 08 15:01:07.72: [16202]: REMOTE wants 7.7 line/mm
Feb 08 15:01:07.72: [16202]: REMOTE wants 1-D MR
Feb 08 15:01:07.72: [16202]: --> [7:CONNECT]
Feb 08 15:01:07.72: [16202]: RECV: begin page
Feb 08 15:01:07.72: [16202]: MODEM set XON/XOFF/FLUSH: input ignored, output
generated
Feb 08 15:01:07.72: [16202]: RECV: send trigger 021
Feb 08 15:01:07.72: [16202]: <-- data [1]
Feb 08 15:02:10.95: [16202]: RECV: 226 total lines, 0 bad lines, 0
consecutive bad lines
Feb 08 15:02:10.97: [16202]: MODEM set XON/XOFF/DRAIN: input interpreted,
output disabled
Feb 08 15:02:10.97: [16202]: --> [17:+FPTS: 1,2219,0,0]
Feb 08 15:02:14.31: [16202]: --> [7:+FET: 2]
Feb 08 15:02:14.31: [16202]: RECV recv EOP (no more pages or documents)
Feb 08 15:02:14.43: [16202]: --> [2:OK]
Feb 08 15:02:14.43: [16202]: RECV send MCF (message confirmation)
Feb 08 15:02:14.43: [16202]: RECV FAX (00000031): from 08 (number), page 1
in 1:10, INF, 7.7
line/mm, 1-D MR
Feb 08 15:02:14.43: [16202]: RECV FAX (00000031): recvq/fax00019.tif from 08
(number), route to <unspecified>, 1 pages in 1:18
Feb 08 15:02:14.45: [16202]: <-- [7:AT+FDR\r]
Feb 08 15:02:17.23: [16202]: --> [8:+FHNG: 0]
Feb 08 15:02:17.23: [16202]: REMOTE HANGUP: Normal and proper end of
connection (code 0)
Feb 08 15:02:17.23: [16202]: RECV FAX: bin/faxrcvd "recvq/fax00019.tif"
"ttyS0" "00000031" ""
Feb 08 15:02:19.06: [16202]: RECV FAX: end
Feb 08 15:02:19.06: [16202]: SESSION END
And the result as e-mail:
=======================================================================
recvq/fax00019.tif (ftp://vfd:4559/recvq/fax00019.tif):
Sender: 08 (number)
Pages: 1
Quality: Fine
Page: 1728 by 29
Received: 1999:02:08 15:01:07
TimeToRecv: 1:06
SignalRate: 9600 bit/s
DataFormat: 1-D MR
ReceivedOn: ttyS0
CommID: c00000031 (ftp://vfd:4559/log/c00000031)
======================================================================
So, 226 lines are received, at 7.7 lines /mm = 29 printed lines.
I've tried using rtscts, disabling AT+FDIS which I thought might be
the problem since the modem is a class 2 and the documentation states
that a squishing and cutting of images may occur if it's used.
I've tried different data compression schemes - still the same problem.
So far I've spent a solid 24 hours playing with this and would really
appreciate hints and advice from people who may have had a similar problem.
The modem is a Netcomm Roadster II 56k.
If anyone wants to see some of the received faxes and their session trace,
feel free to ask ;)
I'm sure it's just some minor thing which I've overlooked.
=)
------------------------------
From: "Pedro Ferreira" <[EMAIL PROTECTED]>
Subject: Re: newbie: ping ok --no telnet ftp
Date: Sun, 7 Feb 1999 12:40:08 -0000
>I am running Red Hat 5.1 in a small home lan with some windows machines (98
&
>NT4). TCP/IP seems to be working fine, since I can ping all the way around,
Do you ping the address or the IP?
Make shure you have all the IP's + hosts names in \windows\hosts and this
file is the same as the linux /etc/hosts...
>my problem is that in trying to telnet or FTP from a win machine to linux
my
>login is refused. After reading some other posts I tried to telnet to
You need to be more specific on this... do you have a login prompt in
telnet? If not maybe the telnetd daemon is dead. Did you configure any
firewall (ipfwadm) rules? If you have a prompt check out hosts.allow and
hosts.deny or /etc/.rhosts or ~/.rhosts (this last two are dangerous to use
for security reasons...)
As for SAMBA, I think it's the best communications software ever made. If
you read the FAQ's and HOW TO's you'll have no problem...
------------------------------
From: "TiM" <[EMAIL PROTECTED]>
Subject: Re: ipforwarding / masquarading
Date: Sun, 07 Feb 1999 13:12:09 GMT
Yes... both HP and xoom sites are up and functional
[EMAIL PROTECTED] wrote in message <79jveu$om2$[EMAIL PROTECTED]>...
> > Well, the HP site worked fine for me. I'm masqing a DSL connection
>> with 192.168.x.x addresses behind it. I browsed with Netscape 4.0?
>> running on a linux box behind the firewall box. I don't run any local
>> DNS services and use standatd 10BaseT abd 10Base2 connections.
>>
>
>Thanks for checking that Greg.
>
>Could someone running Win95 as the browser check it for me?
>(I've had one other person confirm the same problem so far)
>
>Cheers,
>
>Steve.
>
>-----------== Posted via Deja News, The Discussion Network ==----------
>http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: Yves Schlegel <[EMAIL PROTECTED]>
Subject: Problems with addtosmbpass/password-encryption of Win98
Date: Sun, 07 Feb 1999 13:11:52 +0100
Hello everyone,
I'm new to LINUX and I faced some problems installing Samba 1.9.18p. I'm
using the German S.u.S.E. 6.0 distribution with kernel 2.0.36. How the
hell can I add my UNIX-users to the smbpasswd file? I tried addtosmbpass
but it always started but never finished. Can someone give me the
correct syntax for addtosmbpass? The example in the man-page I really
can't understand.
I think that is the reason for my problems establishing connections from
Win98 to Samba with other than anonymous logins.
Thanks a lot,
Yves
------------------------------
From: dbp <[EMAIL PROTECTED]>
Subject: 3c905B compiled module wanted
Date: Wed, 03 Feb 1999 00:50:54 +0800
After detail checking of vortex site and newsgroup, I think I need to
compile the 3c905B source code (3c59x.c) in order to make the
NIC works. But I fail to compile the source code after followed its
guide and the links to compiled module in vortex are broken.
Can anyone kindly send me the compiled 3c59x.o module? Thank you!
------------------------------
From: Eckardt Augenstein <[EMAIL PROTECTED]>
Subject: Re: DOS & WIndows to Linux
Date: Sun, 07 Feb 1999 01:00:42 +0100
Martin Cleaver wrote:
> I am preparing to start moving some of my home network over to Linux. I have
> three windows machines and want at least two of them to run RedHat., In the
> meantime I also had a DOS machine (486) with a BBS and had tried to install
> MS networking with an NE2000 card, but never manahed to get it to work. The
> machine has a 500 MB harddisk and B/W Hercules card (now that's old) but no
> CD-ROM, so I want to get it on the network as a trial for the rest and to
> learn a little about Linux.
> I have managed to install Monkey Linux from 5 floppies, and wonder if this
> is the way. I shall have to start from scratch (I don't even know how to
> edit a text file in Linux :-(. I would like to use Monkey (or another mini)
> to connect the 486 to my Windows TCP/IP network so I can progress from there
> (then I will have access to cable Internet and a CD-ROM at least, as well as
> all the software waiting on my network machines...
>
> Is Monkey a good choice, or is maybe a cludgier choice better: just get the
> TCP/IP running. Is there a newbie's guide to something so simple? (All the
> HOWTOs I read assume I know how to edit a Linux text file...)
>
> Rgds
>
> Martin
I don�t know those small-size-distributions at all so i can�t tell. but you
should get along with any other distrib. as well. suse linux (www.suse.com)
e.g. provides boot disks with install-options via network.
i recently installed a full linux (without X i.e. graphical user interface) on
a i386 /850MB/NE2000 comp. this way, it�s slow but works fine. 486 shure is
fine for a lot of puroses, e.g. routing, small local servers ...
For learning first steps in setting up linux i took the suse-linux handbook
(german version, in my case. i think red hat should come with a good
documentation too). they don�t explain the world to you but just what you need
to know to get started. The great advantage is that if you take the the
distribution and the book from one company you can rely on specific information
about paths and config files/scripts. Otherwise you may go mad in the beginning
not knowing which things to find where to do what ...
good luck, eckardt
PS: for text editing don�t take vi. its behavior may seem weird to windoze
users. if you can afford the disk space install (x)emacs . ;~)
------------------------------
From: Thomas Miller <[EMAIL PROTECTED]>
Subject: newbie: lose default gateway info on reboot
Date: Wed, 03 Feb 1999 21:21:33 -0700
Hello,
I used
route add default gw <router address>
and it worked just fine. Then I rebooted the system (mkLinux on
PowerMac 6100 ) and now I have to do it again.
I'm sure there's a config file I can edit.
is it /etc/config.routes ????
thanks
------------------------------
From: "Pedro Ferreira" <[EMAIL PROTECTED]>
Subject: Re: mail - "we do not relay" error
Date: Sun, 7 Feb 1999 12:54:09 -0000
>What does "we do not relay" from a mail recipient mean?
This means that the mail server you are connecting does not recognize your
IP as a client IP... You configure this in /etc/mail/, files ip_allow,
name_allow, relay_allow.
This as nothing to do with DNS...
To configure sendmail don't try to edit sendmail.cf by hand... Use m4 macro
compiler and a simple configuration to start with... read all about it in
the HOW TO's!
------------------------------
From: "Pedro Ferreira" <[EMAIL PROTECTED]>
Subject: Re: IP masquerading
Date: Sun, 7 Feb 1999 13:35:23 -0000
>
>ipfwadm -F -p deny
>ipfwadm -F -a m -S 192.168.2.2/22 -D 0.0.0.0/0
>
this is wrong...
you give this command with network address, not host address.
Also the mask is important. a mask of /22 means that you have 22 bits set,
so you are using a network mask of 255.255.255.252, witch is not very
common...!
If you want a mask of 255.255.255.0 you have to use /24
Also check out the IP's and netmask's of all hosts. They must be all in the
same network, in this case 192.168.2.0 with mask 255.255.255.0, that is, all
the addresses must be in 192.168.2.2 to 192.168.2.253
(normaly you reserve IP's ending with .1 or .254 to routers and the like,
don't use .127)
so the command is something like:
ipfwadm -F -a m -S 192.168.2.0/24 -D 0.0.0.0/0
This will connect all hosts in network 192.168.2 to the outside
Read the NET3 HOW TO... www.linux.org
------------------------------
** 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
******************************
