Linux-Networking Digest #964
Linux-Networking Digest #964, Volume #11 Wed, 21 Jul 99 14:13:37 EDT
Contents:
Re: Why are there so many slow modem issues? Solution !!! (for me anyways) (bill
davidsen)
Re: Samba-PC can't be seen (bill davidsen)
Re: pppd message: Recieve serial link not clean ("Morris Maynard")
Re: Firewall to protect servers (bill davidsen)
Re: Limit Access By Time or Date (bill davidsen)
Re: PPP connection doesn't work (Clifford Kite)
Re: pppd crashing my kernel (Clifford Kite)
Re: exporting files systems via NFS? (bill davidsen)
Re: Samba PC doesn't show up on Win-Box (bill davidsen)
Re: High Speed Serial Cards. (bill davidsen)
PPP Session takes Memory ("Darrin")
Re: [RH5.2] modem is not responding (Clifford Kite)
Re: dynamic IP = ? (bill davidsen)
Re: samba and windows network - incompatible namespaces? (Ben Blish)
Re: (2 NIC)RTFM no good, please help (Thomas S. Urban)
PPP Peculiar Packet problem ("Morris Maynard")
From: [EMAIL PROTECTED] (bill davidsen)
Subject: Re: Why are there so many slow modem issues? Solution !!! (for me anyways)
Date: 21 Jul 1999 16:20:49 GMT
In article <[EMAIL PROTECTED]>,
Jason Koloseike <[EMAIL PROTECTED]> wrote:
| Last night I went back to me pre-kppp ppp scripts that I
| had used with Redhat 5.1, and to my surprise, they worked!
|
| After some tracking, I was able to narrow it down to one
| parameter: "baud rate".
|
| pppd expects a "baud rate" parameter. Since kppp wasn't
| passing it by default, ppp fixed itself to a slow
| transfer rate, even though the serial port had
| been set to a higher speed (38400, 11520, etc.)
|
| Hope this helps with your issues.
|
| PS. Even thou I downgraded to pppd 2.3.5-2, this is still
| an issue with pppd 2.3.7. But I would term this as a
| kppp bug. I downgraded to 2.3.5 so that I could connect
| to a CHAP authenticated site. 2.3.7 was only allowing
| me to connect to a scripted ISP site.
I'm not having problems with 2.3.8, and I connect to various sites for
support reasons. CHAP, PAP and MSCHAP all seem to work. I do notice that
my logs now show "chap MD5" on some sites, but since they work I don't
worry overly about it.
I roll my own scripts in /etc/ppp/peers, and always include hardware
flow control, baud rate, etc.
--
bill davidsen <[EMAIL PROTECTED]> CTO, TMR Associates, Inc
The Internet is not the fountain of youth, but some days it feels like
the fountain of immaturity.
--
From: [EMAIL PROTECTED] (bill davidsen)
Subject: Re: Samba-PC can't be seen
Date: 21 Jul 1999 17:05:33 GMT
In article <[EMAIL PROTECTED]>,
VBF-Ratingen GmbH <[EMAIL PROTECTED]> wrote:
| I can access the WIndows-PCs, but in the net-neighbourhood under Win the
| Samba-PC isn't there.. :-(
|
| Any Ideas???
Try mounting samba shares directly from a DOS command line. If it works
it's a name service problem, needs something in nmbd.
--
bill davidsen <[EMAIL PROTECTED]> CTO, TMR Associates, Inc
The Internet is not the fountain of youth, but some days it feels like
the fountain of immaturity.
--
From: "Morris Maynard" <[EMAIL PROTECTED]>
Subject: Re: pppd message: Recieve serial link not clean
Date: Mon, 19 Jul 1999 12:58:39 -0400
It is unusual for an ISP to allow login via the old login: password:
sequence these days. User authentication is usually done by using much more
secure binary protocol. Use netcfg in X-windows and get rid of all
Send/Expect strings, and just enter your user name and password in the CHAP
settings.
This is typical of the problems caused by the seriously outdated
documentation provided for Linux services like PPPD in the HOWTOs.
Clifford Kite wrote in message
news:7mvd8k$[EMAIL PROTECTED]...
> Mark Bennett ([EMAIL PROTECTED]) wrote:
>
> : I get connected, and all
> : is OK up till (in /var/log/messages)
> : #pppd 2.3.3 started by root, uid 0
> : #Using inerface ppp0
> : #Connect:ppp0 <--> /dev/tty1
> : #LCP:timeout sending Config-Requests
> : #Recieve serial link is not 8-bit clean:
> : #Problem: all had bit 7 set to 0
> : I am at a total loss. When in Windows and useing a terminal program I
> : connect fine and see the "garbage" of TCP/IP starting, but I never get
this
> : far in linux.
>
> : Useing:
> : pppd connect 'chat -v "" ATDT5766774 CONNECT "" ogin: usename word:
> : password' /dev/ttyS2 115200 lock debug crtscts modem defaultroute
>
> It's very likely that the ISP didn't start PPP at it's end and instead is
> presenting a prompt or menu. The chat script isn't doing it's job but
it's
> hard to tell what is actual and what is not from the hand-co
Linux-Networking Digest #964
Linux-Networking Digest #964, Volume #10 Mon, 26 Apr 99 13:14:01 EDT
Contents:
Re: How to log a telnet session ? (Paul Miles)
Re: Squid: http_access deny - can't make it work (Jussi Torhonen)
Re: Linux client, NT server, and callback problems... (James Carlson)
Re: IP Masquerade ([EMAIL PROTECTED])
Re: Is there an inherent problem with the 3c509(isa)? (Mark)
Re: 7E1-connection before PPP-initialization (James Carlson)
IPChains loses its settings (Yves Van de Weyer)
How to install two of Pccom8 unde Linux (Alexei Kakhno)
Where is H.323 Server? ("David Seaman")
Re: Drivers for 100Mbps Ethernet Cards (Rod Smith)
How to log a telnet session ? ("Francois-Xavier LEBLOND")
Re: sendmail behind firewall (Peter Novikov)
Re: options 3c503 io=0x280,0x300,0x330,0x350 xcvr=0,1,0,1 ("William R. Mattil")
Re: SIOCADDRT: Invalid argument (Kelvin Tsang)
Routing over two interfaces? (Gerald Brandt)
Re: Bandwidth Watcher/Monitor Help/Info Needed (Holger von Ameln)
Configuring PPP on linux ([EMAIL PROTECTED])
Re: FTP as root (TurkBear)
Need help setting up a remote X-term. ("Matthew B. Kennedy")
From: [EMAIL PROTECTED] (Paul Miles)
Crossposted-To: comp.os.linux,comp.os.linux.admin,comp.os.linux.help,comp.os.linux.misc
Subject: Re: How to log a telnet session ?
Date: 26 Apr 1999 10:58:06 GMT
I've never looked at this, but have a look on your system for ttysnoop
Aparently its some kind of wrapper for telnet that logs everything.
Paul
Francois-Xavier LEBLOND ([EMAIL PROTECTED]) wrote:
: Hello,
: I want to log automatically in a file all my telnet sessions. Somebody has
: told me to look in /etc/syslog.conf, but for the moment I've just manage to
: log authentification messsages, and not the complete work I've done in my
: sessions ...
: Thanks
: FX
--
Paul
Final Year CompSci o__
University of Kent _.>/)_"A fish with a mission"
http://stue1ae.ukc.ac.uk (_) \(_)
--
From: Jussi Torhonen <[EMAIL PROTECTED]>
Subject: Re: Squid: http_access deny - can't make it work
Date: Mon, 26 Apr 1999 13:56:28 +0300
On Mon, 26 Apr 1999, sven vahar wrote:
> acl ban1 dstdomain www.badsite1.foo
> acl ban2 dstdomain www.badsite2.foo
>
> followed by:
>
> http_access deny ban1
> http_access deny ban2
Be sure to declare those 'http_access deny' rules before the follwing:
### Allow everything else
http_access allow all
BTW, you could create a banned site list file instead of editing
squid.conf all the time:
acl BANNED "/etc/squid.banned"
http_access deny BANNED
http_access allow all
Jussi
--
===
Jussi Torhonen # E-mail: [EMAIL PROTECTED]
Tietosavo Oyj# Corporate website: http://www.tietosavo.fi
P.O.Box 1582 # Personal homepage: http://www.iki.fi/jt
FIN-70461 KUOPIO # Tel: +358-17-193231 GSM +358-50-5946209
FINLAND # Fax: +358-17-19335573's de OH7DC
--
From: James Carlson <[EMAIL PROTECTED]>
Crossposted-To: comp.protocols.ppp
Subject: Re: Linux client, NT server, and callback problems...
Date: 26 Apr 1999 06:51:49 -0400
[EMAIL PROTECTED] writes:
> I get the following in the logs (with 'kdebug 7' set) repeated several times -
> email me privately if ppp logs make a lot of sense to you and I can send
> more details...
Ok.
> Apr 25 16:07:18 pukeko kernel: ppp0 released
> Apr 25 16:07:18 pukeko kernel: ppp0: ccp closed
> Apr 25 16:07:55 pukeko kernel: ppp: frame with bad fcs, length = 10
> Apr 25 16:07:55 pukeko kernel: ppp: bad frame, count = 10
> Apr 25 16:07:55 pukeko kernel: FF C0 00 21 C2 23 80 63 ...!.#.c
> Apr 25 16:07:55 pukeko kernel: F1 6D .m
>
> ...
Those are massively garbled LCP frames. They should look like this:
FF 03 C0 21 ...
The FCS is "bad" because the frame itself is highly corrupt.
> Thanks for any help - only reference I've found to the 'bad fcs' messages
> indicate that it's usually when the NT server's trying to send me plain text
> at the start of the call, but that doesn't look the case from the
> logs.
Correct. At a guess, at least the ACCM is set incorrectly here. It's
possible that there are also modem-related problems. The inserted NUL
byte (00) is most worrisome.
> There's no default route added to my routing table at this point, so I guess
> ppp's still trying to form the link.
Until IPCP comes up, you'll see no routing done.
> my scripts are as follows:
The scripts *look* ok ...
--
James Carlson, Software Archit
Linux-Networking Digest #964
Linux-Networking Digest #964, Volume #9 Fri, 22 Jan 99 00:13:31 EST
Contents:
Scheduled PPP? (Bruce Barnett)
Re: Why Does Linux Networking Suck So Badly ? ("Mark Vandersteen")
Botting diskless SPARCstation off redhat5.2 unsuccessfull...please help
("p.wojcieszak")
Re: Cable Modem problems (Buster_Bear)
Re: IP Masq & Civ 2 MPE (Dan Kegel)
Re: 3Com 3c509b, not working under RH 5.2 (Dan Kegel)
Re: Connect without hub (Wolfgang Kleinhappl)
Re: Extraction of IP address ("Rob Lauer")
TCP/IP help (Ziae)
Re: diald help. (Vincent Zweije)
Re: Multiple 3c509 ("Kyle Bowerman")
FTP files not visible (Ron Thompson)
Re: RedHat Linux 5.1 & Ethernet 3c509 NIC ("Kyle Bowerman")
Re: Transmit time out (David Kirkpatrick)
From: Bruce Barnett <[EMAIL PROTECTED]>
Crossposted-To: linux.dev.ppp
Subject: Scheduled PPP?
Date: 22 Jan 1999 02:50:10 GMT
I have a PPP link set up to disconnect when idle for 10 minutes.
However, it immediately reconnects. How is this decision made?
I want to scheule a connection ABOUT once an hour, that disconnects when
idle. The PPP docs suggest DIP, while anothe document suggests diald.
The PPP people don't want to talk about either, so I have to figure
out how to integrate the packages. It seems a shame, because PPP
ALMOST does what I want it to do.
The setup scripts are convoluted. Can someone give me a pointer on how
to accomplish the task? Or how the scripts are organized?
The README file does a very poor job of explaining the dozens of script
files used.
If I could put a DELAY between the shutdone and the startup, I'd
solve most of my problem. But this isn't documented as far as I can
tell.
Can anyone help?
--
From: "Mark Vandersteen" <[EMAIL PROTECTED]>
Subject: Re: Why Does Linux Networking Suck So Badly ?
Date: Fri, 22 Jan 1999 13:31:42 +1030
Your answers is plain and simple "DONT USE IT", go back to windoze, stop
rubbishing something you know nothing about.
If you take time to actually learn how to do something insead of using
something without reading the instructions like 99% of people in todays
world then you might actually benefit from it.
Keep your rubbish in the windows newsgroup thanks :)
>>From: [EMAIL PROTECTED] (j)
>> The sheer number of messages posted here - usually half going
>> unanswered - tells the tale ... Linux networking sucks.
>> Now you can take your Winders, add in file-sharing in just a
>> couple of minutes, bring up your Winders workstations and
>> locate and link in within just another few minutes. Easy.
>> Quick. Relatively painless. Not the Linux way ...
>> Now you may try to defend Linux by saying that it has more
>> "flexibility" - but quite frankly we could do with a lot
>> less "flexibility" and a lot more simplicity. I'll bet
>> that 95% of users just want to tie into a local NT server
>> or use Linux AS a file/print server for Winders PCs.
>> I think that "flexibility" is just an excuse - a euphamism
>> for "a bunch of really unsophisticated little utilities
>> written with no real plan in mind by people with a fetish
>> for cryptic poorly-documented command-line parameters and
>> well-hidden config files". As is, Linux is a user-UNfriendly
>> mirror of MSDOS - and that goes double for "connectivity" issues.
>> Want cheap PC networking & connectivity ? One "L" word comes
>> to mind and it's NOT "Linux" - try "LanTastic" instead.
>> Now Linux IS relatively compact and fast and DOES get past
>> some of the old buggaboos inherent to DOS-derived systems,
>> but Linux just isn't "ripe" yet. It needs DUN boxes and
>> "Network" panels which HELP you with things and show all
>> the pertinent options and conflicts right there.
>> Someone could make a LOT of money if they could put together
>> a turn-key Linux-based file/print server package which could
>> autoconfigure most things and be really easy and helpful on
>> the rest. Something you take out of the box and 20 minutes
>> later you have a good working server. You can do that with
>> Winders, but not with Linux unless you apparently have put
>> in a tremendous number of obsessive hours.
>> Now you thought I was just gonna flame ... nope. I've been
>> relatively polite and realistic here. There are MANY issues
>> to address, MANY refinements to be made before Linux becomes
>> a really good option for administrators of small/medium networks.
>> As much as I dislike Winders, it's a positive relief to boo
