Linux-Networking Digest #916, Volume #9 Sun, 17 Jan 99 21:13:54 EST
Contents:
Re: Help! Multiple ethernet config problems ([EMAIL PROTECTED])
Re: AutoPPP and pppd server (David Efflandt)
Re: dns will not work properly (J. Scott Berg)
Re: traceroute is using the wrong interface (Benjohn007)
Re: Help with Firewall FWTK2.0 on REDHAT 5.1 ("Mike")
Authentication w/PAP??? ([EMAIL PROTECTED])
FTP woes (Michael Schwager)
HELP: IBM ISA Token Ring 16/4 ("John P. Arnold")
traceroute is using the wrong interface ([EMAIL PROTECTED])
Network Video Broadcast (not conference) Available? (Patrick Shomo)
Re: Ethernet card recommendation--urgent (Neil Zanella)
HTTP and POP3 problems using IP masquerading (David J. Mellor)
Re: Machine denys telnet and FTP (Luca Filipozzi)
Red Hat 5.0 : usernet hangs (Neil Zanella)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Help! Multiple ethernet config problems
Date: Mon, 18 Jan 1999 00:57:27 GMT
Well, after a bit more tweaking of io and irq values I decided to try
accessing the interfaces via the network from another computer. The
interface that couldn't be pinged locally worked from the outside for some
reason. I don't know why it works but everything is up and running as a
firewall.
John
In article <77tmhd$75s$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> I am trying to setup a 486/50 computer with multiple ethernet cards to be
> used as a firewall and am having all kinds of trouble getting both cards to
> work at the same time. The cards in question are a (ISA) 3Com 3C509B and a
> Linksys Ether16 using the 3c509 and ne modules respectively. I have
> configured both to non-pnp via their Dos utilities and configured a kernel
> with modular drivers as well.
>
> The problem is that even though both cards appear to be initialized at boot
> and will show up as active via an ifconfig command, I can only ever ping one
> of the cards at once (from the box that they are installed in). Via
> Linuxconf, I have setup the adapters with the io and irq information and have
> introduced the parameters via lilo as an append statement also. Given that
> either one card or the other can be pinged when I change the io and irq for
> the card I am suspecting that it is a resource configuration issue. The
> problem is that there are, obviously, a huge number of io and irq
> combinations and I would like to try a better method than trial and error to
> find the right combination.
>
> The last combination I tried was eth0 at io 0x320, irq 5 and eth1 at io 0x340
> irq 10. Other unsuccessfull combinations have included 0x210, irq 10 and
> 0x300, irq 5.
>
> If anyone could offer any advice I would really appreciate it. I've spent a
> ridiculous amount of time trying to find a solution! :-)
>
> John
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED] (David Efflandt)
Crossposted-To:
alt.uu.comp.os.linux.questions,alt.os.linux.dial-up,comp.os.linux.setup,comp.os.linux.misc,alt.comp.linux.isp
Subject: Re: AutoPPP and pppd server
Date: 18 Jan 1999 01:12:39 GMT
Reply-To: [EMAIL PROTECTED]
On 16 Jan 1999 22:11:27 GMT, Alan Baker <[EMAIL PROTECTED]> wrote:
>I've installed Redhat 5.1 for use as a small dialup PPP server. Dialout
>PPP works fine, but inbound /AutoPPP/ calls will not stay connected. A
>Win95/Win98 caller can connect and log in, but immediately gets the
>dreaded "cannot negotiate a set of protocols" message. An OS/2 dialer
>gets similar results without the message.
The problem is that the mgetty example uses '+pap' and 'man pppd' is
unclear on what a peer is. Your computer is attempting to authenticate
the other computer (hostname) instead of the user. Since there is no
pap-secret for that computer, (and Win isn't likely to answer it anyway)
it fails. Remove the '+pap' and the 'auth' and 'login' options
will still authenticate the user (instead of the host).
>On the dialer side, TCP/IP is the only protocol requested. On the Linux
>side, mgetty takes the call and PAP validates the user successfully, but
>then the caller drops the session almost immediately. The Linux box is a
>standalone, not networked to anything else currently.
What makes you think that pap is successful?
>/var/logs/messages isn't very revealing even with debug and kdebug 7. How
>can I determine what's going on here and why the negotiation fails?
Unfortunately RedHat does not set up any file for detailed debug info to
go (like Slackware does), so it vaporizes unless you set something up
yourself in /etc/syslog.conf. This would likely reveal why your
authentication is NOT successful (hostname instead of username).
This had me stumped for awhile, especially since my username and one of my
machines have the same name. I did not realize the Windows was refusing
to authenticate itself.
--
David Efflandt [EMAIL PROTECTED]
http://www.xnet.com/~efflandt/
------------------------------
From: [EMAIL PROTECTED] (J. Scott Berg)
Subject: Re: dns will not work properly
Date: 17 Jan 1999 19:02:33 GMT
In article <OnWhslcQ#[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote:
>jc:~# cat /var/named/pz/127.0.0
>
>
> @ IN SOA jc.plum.org. (
> 1 ; Serial
> 8H ; Refresh
> 2H ; Retry
> 1W ; Expire
> 1D) ; Minimum TTL
> NS jc.plum.org
> 1 PTR localhost.
Your syntax in this file is wrong.
@ IN SOA jc.plum.org. userid.jc.plum.org. (
1 ; Serial
8H ; Refresh
2H ; Retry
1W ; Expire
1D) ; Minimum TTL
NS jc.plum.org.
1 PTR localhost.
Note the additional entry on the first line before the open
parenthesis. It's of course irrelevant in this case what form that
entry takes; in the more general case, it means the email address of
the person responsible is <[EMAIL PROTECTED]>.
Secondly, note that extra period after the address on the NS line.
I'm not entirely clear on what's going on with the root.hints file.
-Scott Berg
------------------------------
From: [EMAIL PROTECTED] (Benjohn007)
Subject: Re: traceroute is using the wrong interface
Date: 18 Jan 1999 01:18:20 GMT
traceroute --help should give u the different interface options you can choose
from
------------------------------
From: "Mike" <[EMAIL PROTECTED]>
Subject: Re: Help with Firewall FWTK2.0 on REDHAT 5.1
Date: Sun, 17 Jan 1999 16:00:52 -0500
Nevermind.... I didn't RTFM in the makefile.config where it tells to add
the -l crypt for linux. I don't really need x-gw, so I am configuring now!
Mike wrote in message ...
>I am having problems compiling firewall tool kit 2.0 on redhat 5.1, kernel
>2.0.34. For one it says I am missing intrinsic.o from the X11 grouping to
>get x-gw to compile. Also, adding in the auth portion at compile (make),
>gets errors in resolving crypt for pass.o. How do I fix this???
>
>
>Any help is appreciated,
>
>Mike
>[EMAIL PROTECTED] & [EMAIL PROTECTED]
>
>
>
------------------------------
From: [EMAIL PROTECTED]
Subject: Authentication w/PAP???
Date: Sun, 17 Jan 1999 16:20:34 GMT
Hello, all
How in Sam's Hill do I authenticate myself with PAP?
I've been hearing alot about this, and it sounds like my situation.
I get a 'username:' prompt, followed by 'password:', and then get
dumped into 'annex:'
If I type ppp, it starts ppp, sending lcp, but disconnects after
awhile, whereas if I start pppd also, it disconnects immediately..
My sysadmin **thinks** they use PAP.
I've heard the bit about switching to PAP after 'CONNNECT' from the
modem, but what then? How do I switch?
(pap-secrets file is setup properly, but nothing else I suspect)
Please help a newbie (how many times have we heard that on this board??)
Forest, [EMAIL PROTECTED]
>>Linux is .... Microsoft just isn't.<<
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: Michael Schwager <[EMAIL PROTECTED]>
Subject: FTP woes
Date: Sun, 17 Jan 1999 18:25:43 -0800
Problem: reinstallation of rh5.1 using known-good kernel, I can't ftp
from my windows machine. ACtually, it's like this
d:> ftp 10.10.10.10
Connected to 10.10.10.10
and then it just sits there. I can ftp to localhost from the linux
machine itself. What settings do I need to fix? (this did not happen
the first time I installed rh5.1.
thanks
ms
------------------------------
From: "John P. Arnold" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.hardware
Subject: HELP: IBM ISA Token Ring 16/4
Date: Sun, 17 Jan 1999 19:33:59 -0600
I installed an IBM ISA Token Ring 16/4 card on my Compaq Deskpro
running the 2.0.36 kernel. When properly connected I haven't had any
problems talking to the network. The device driver I'm using is the
ibmtr.c
(version 1.3.57) that comes with the 2.0.36. My problem is that when
I'm not physically connected to the network my machine hangs during
the bootup procedure. Specifically, it hangs at rc.inet1. More
specifically,
I believe it hangs at the ifconfig command.
According to the Token Ring mini-HOWTO, I can avoid error messages,
when not connected to the network, by using a Token Ring loopback
connector. Does this apply also to my problem?
If a loopback connector is necessary, what is the pinage so I can build
one?
Is there an updated driver for my kernel version that would avoid this
problem all together?
Thanks in advance for any help...
------------------------------
From: [EMAIL PROTECTED]
Subject: traceroute is using the wrong interface
Date: Sun, 17 Jan 1999 19:51:01 GMT
I am running Redhat 5.2 as a SMB and DHCP server for some Win95 clients. I am
now trying to connect to the internet using PPP.
I have three network interfaces when ppp is connected: lo, eth0, ppp0.
I have tested both ping and http to both ip addresses and domain names, and
both appear to use the correct interface(ppp0).
But now when I attempt a traceroute, it says it has found multiple interfaces
and is going to use eth0 (which is the wrong one).
How can I get it to choose the correct interface???
Some useful information may be that in order to get win95 to work I had to do
the following command:
route add -host 255.255.255.255 dev eth0
Can you please help!
Brendan
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: Patrick Shomo <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x,comp.os.linux.misc
Subject: Network Video Broadcast (not conference) Available?
Date: Sun, 17 Jan 1999 21:09:22 +0000
I'm hoping someone out there can comment on my issue...
My goal is to take an analog signal and broadcast it to a client. I
bought a Hauppage WinTv card (using bttv driver and xawtv) to begin
testing and it works fine. I can display the xawtv window
elsewhere(using X11), but the frame rate slows to a lurch (this is due
to the fact that the Hauppage card overlays images direct to the local
frame buffer/video card's memory).
I'd like to get full frame rate (or at least close) meaning ~30fps on a
100TX, 100FX or even ATM network. Bandwidth should not be an issue.
I've checked out vic and other mbone tools for Linux, but they seem to
all take advantage of the Quickcam for Video Conferencing. The nv tool
looks like a winner (can operate in recvOnly mode for the client), but
again everything is based around the QuickCam.
THE QUESTION:
Does anybody know how to get nv (or other such tools) to pick up an
analog signal through a TV card and broadcast it to clients? If there is
another card I should try, then please let me know...
Thanks,
Pat
------------------------------
From: Neil Zanella <[EMAIL PROTECTED]>
Crossposted-To:
linux.redhat.install,comp.os.linux.hardware,redhat.networking.general,iu.linux
Subject: Re: Ethernet card recommendation--urgent
Date: Sun, 17 Jan 1999 17:55:12 -0330
I reccomend an EtherFast 10/100 LAN Card by Linksys.
It uses the tulip.c driver that comes with kernel 2.0.36 .
You can also download the driver from their website.
The card works very well on my system.
Neil
On Mon, 11 Jan 1999, Jan Stifter wrote:
> [...]
> Shane Bearham wrote:
> >
> > "Larry Herzog Jr." wrote:
> >
> > Nothing like a good old WD8013 series card....never fails me
> > even performs admirably, it's programable or jumpered &
> > around here I can pick them up for $3-$5 each at swap meets
> >
> > Shane ()
>
> I can recommend the Fast EtherRx PCI 10/100TX card of Kingston.
> just turn on the DEC-Tulip option in the kernel and it works perfect...
>
>
> jan
>
> ---------------------------------------------------------------------
> | Jan Stifter email: [EMAIL PROTECTED] |
> | web: www.htl-bw.ch/~ia95stif |
> | meet me: telnet://freechess.org:5000 (nick: nunc) |
> ---------------------------------------------------------------------
>
>
------------------------------
From: [EMAIL PROTECTED] (David J. Mellor)
Subject: HTTP and POP3 problems using IP masquerading
Date: Sun, 17 Jan 1999 12:10:23 -0800
I am using a PC running RedHat Linux 5.2 to act as a router and DNS server
and to provide internet access to two other machines on a local network,
one running Windows 98 and the other running MacOS 7.6.1. I have set up IP
masquerading and use diald 0.16-5 to automatically bring up a PPP
connection whenever any of the machines needs to connect to the internet.
Basically, the system is working almost perfectly for web access, newsgroup
reading and sending email from the non-Linux machines, but I am having a
couple of problems which I just cannot solve and am wondering if anybody
can shed any light on them.
The first problem is that there are certain web sites which are
inaccessible when using IP masquerading. One example is
http://www.movielink.com which sends a few HTTP packets when a first try to
access it via IP masquerading, but then no more packets come in and the
browser just displays a blank page and eventually times out. If I connect
the modem directly to the Windows 98 machine, and use dial-up networking to
connect to the site, then the site is displayed with no problems. The other
problem I am having is in retrieving email from my ISP's POP3 server via IP
masquerading. Using Eudora 4.1 on the Windows 98 machine the program will
download the first of several messages very slowly (looking at the lights
on the modem and using diald-top and ifconfig, packets are being received
by the modem at the rate of about one per minute), and then eventually time
out with the following error messages:
Closing the connection, [07:04:31 PM]
Error writing to network. Cause: connection reset by remote side (10054)
9 message(s) left to download, [07:04:31 PM]
There has been an error transferring your mail.
I said: DELE 1 and then the POP server said: ERR POP idle time out
This behaviour always occurs while I am using IP masquerading, but if I
connect the modem to the Windows 98 machine and switch over to using
dial-up networking on that machine, then the messages are downloaded
immediately with no delays.
I suspect that I have misconfigured the router in some way, but after
having read all of the relevant HOWTOs that I could think of I am still at
a loss to explain this behaviour. I would like to know if anyone else has
experienced the same, and if so were they able to fix it. The configuration
of the machine being used as the router is as follows:
Pentium II 300 MHz
128 Mb memory.
8.4 GB disk (all filesystems have plenty of free space)
3COM 905B 100/10 Base-T ethernet card (for connecting to the local network)
US Robotics Sportster 56K (for connecting to the ISP, Netcom)
The internal network is a class C network, with network address 192.168.0.0
and network mask 255.255.255.0. The three machines have IP addresses:
192.168.0.1 - Linux
192.168.0.2 - Windows 98
192.168.0.3 - MacOS
and the Windows and Macintosh machines have the Linux machine's IP address
set as their default gateway and as their DNS server.
IP forwarding is enabled in /etc/sysconfig/networking, and the IP
masquerading entries are in /etc/rd.c/rc.local, and are as follows:
/sbin/depmod -a
/sbin/modprobe ip_masq_ftp.o
/sbin/modprobe ip_masq_vdolive.o
/sbin/modprobe ip_masq_raudio.o
/sbin/ipfwadm -F -p deny
/sbin/ipfwadm -F -a m -S 192.168.0.0/24 -D 0.0.0.0/0
/usr/sbin/diald
The versions of the sofware I am using are:
Linux - 2.0.36 (the kernel which came with RedHat 5.2)
ipfwadm - 2.3.0-6
diald - 0.16-5
ppp - 2.3.5-1
net-tools - 1.46-1
My diald setup is as follows:
/etc/diald.conf
===============
mode ppp
fifo /etc/diald/diald.ctl
connect /etc/diald/connect
device /dev/ttyS0
speed 115200
modem
lock
crtscts
mtu 576
mru 576
local 192.168.1.1
remote 192.168.1.2
dynamic
defaultroute
include /etc/diald/filters
/etc/diald/connect
==================
#!/bin/sh
# Copyright (c) 1996, Eric .
#
# This script is intended to give an example of a connection script that
# uses the "message" facility of diald to communicate progress through
# the dialing process to a diald monitoring program such as dctrl or
diald-top.
# It also reports progress to the system logs. This can be useful if you
# are seeing failed attempts to connect and you want to know when and why
# they are failing.
#
# This script requires the use of chat-1.9 or greater for full
# functionality. It should work with older versions of chat,
# but it will not be able to report the reason for a connection failure.
# Configuration parameters
# The initialization string for your modem
MODEM_INIT='AT&F1E1Q0V1&C1&D2S0=0S7=60S19=0M1&M4&K1&H1&R2&I0B0X4'
# The phone number to dial
PHONE_NUMBER="5321000"
# The chat sequence to recognize that the remote system
# is asking for your user name.
USER_CHAT_SEQ="ogin:--ogin:"
# The string to send in response to the request for your user name.
USER_NAME=<MY USER NAME>
# The chat sequence to recognize that the remote system
# is asking for your password.
PASSWD_CHAT_SEQ="assword:"
# The string to send in response to the request for your password.
PASSWORD=<MY PASSWORD>
# The prompt the remote system will give once you are logged in
# If you do not define this then the script will assume that
# there is no command to be issued to start up the remote protocol.
#PROMPT="annex:"
# The command to issue to start up the remote protocol
#PROTOCOL_START="ppp"
# The string to wait for to see that the protocol on the remote
# end started OK. If this is empty then no check will be performed.
#START_ACK="Switching to PPP."
# Pass a message on to diald and the system logs.
function message () {
[ $FIFO ] && echo "message $*" >$FIFO
logger -p local2.info -t connect "$*"
}
# Initialize the modem. Usually this just resets it.
message "Initializing Modem"
/usr/sbin/chat TIMEOUT 5 "" "\rAT" OK ATH0 OK "$MODEM_INIT" TIMEOUT 45 OK
""
if [ $? != 0 ]; then
message "Failed to initialize modem"
exit 1
fi
# Dial the remote system.
message "Dialing system"
/usr/sbin/chat \
TIMEOUT 45 \
ABORT "NO CARRIER" \
ABORT BUSY \
ABORT "NO DIALTONE" \
ABORT ERROR \
ABORT "RINGING\r\nRINGING" \
"" ATDT$PHONE_NUMBER \
CONNECT ""
case $? in
0) message Connected;;
1) message "Chat Error"; exit 1;;
2) message "Chat Script Error"; exit 1;;
3) message "Chat Timeout"; exit 1;;
4) message "No Carrier"; exit 1;;
5) message "Busy"; exit 1;;
6) message "No DialTone"; exit 1;;
7) message "Modem Error"; exit 1;;
*)
esac
# We're connected try to log in.
message "Logging in"
/usr/sbin/chat \
TIMEOUT 5 \
$USER_CHAT_SEQ $USER_NAME \
TIMEOUT 45 \
$PASSWD_CHAT_SEQ $PASSWORD
if [ $? != 0 ]; then
message "Failed to log in"
exit 1
fi
# We logged in, try to start up the protocol (provided that the
# user has specified how to do this)
if [ $PROMPT ]; then
message "Starting Comm Protocol"
/usr/sbin/chat TIMEOUT 15 $PROMPT $PROTOCOL_START
if [ $? != 0 ]; then
message "Prompt not received"
exit 1
fi
fi
if [ $START_ACK ]; then
/usr/sbin/chat TIMEOUT 15 $START_ACK ""
if [ $? != 0 ]; then
message "Failed to start Protocol"
exit 1
fi
fi
# Success!
message "Protocol started"
/etc/diald/filters
==================
# This is a pretty complicated set of filter rules.
# (These are the rules I use myself.)
#
# I've divided the rules up into four sections.
# TCP packets, UDP packets, ICMP packets and a general catch all rule
# at the end.
#------------------------------------------------------------------------------
# Rules for TCP packets.
#------------------------------------------------------------------------------
# General comments on the rule set:
#
# In general we would like to treat only data on a TCP link as significant
# for timeouts. Therefore, we try to ignore packets with no data.
# Since the shortest possible set of headers in a TCP/IP packet is 40
bytes.
# Any packet with length 40 must have no data riding in it.
# We may miss some empty packets this way (optional routing information
# and other extras may be present in the IP header), but we should get
# most of them. Note that we don't want to filter out packets with
# tcp.live clear, since we use them later to speedup disconnects
# on some TCP links.
#
# We also want to make sure WWW packets live even if the TCP socket
# is shut down. We do this because WWW doesn't keep connections open
# once the data has been transferred, and it would be annoying to have the
link
# keep bouncing up and down every time you get a document.
#
# Outside of WWW the most common use of TCP is for long lived connections,
# that once they are gone mean we no longer need the network connection.
# We don't necessarily want to wait 10 minutes for the connection
# to go down when we don't have any telnet's or rlogin's running,
# so we want to speed up the timeout on TCP connections that have
# shutdown. We do this by catching packets that do not have the live flag
set.
# --- start of rule set proper ---
# When initiating a connection we only give the link 15 seconds initially.
# The idea here is to deal with possibility that the network on the
opposite
# end of the connection is unreachable. In this case you don't really
# want to give the link 10 minutes up time. With the rule below
# we only give the link 15 seconds initially. If the network is reachable
# then we will normally get a response that actually contains some
# data within 15 seconds. If this causes problems because you have a slow
# response time at some site you want to regularly access, you can either
# increase the timeout or remove this rule.
accept tcp 15 tcp.syn
# Keep named xfers from holding the link up
ignore tcp tcp.dest=tcp.domain
ignore tcp tcp.source=tcp.domain
# (Ack! SCO telnet starts by sending empty SYNs and only opens the
# connection if it gets a response. Sheesh..)
accept tcp 5 ip.tot_len=40,tcp.syn
# keep empty packets from holding the link up (other than empty SYN
packets)
ignore tcp ip.tot_len=40,tcp.live
# make sure http transfers hold the link for 2 minutes, even after they
end.
# NOTE: Your /etc/services may not define the tcp service www, in which
# case you should comment out the following two lines or get a more
# up to date /etc/services file. See the FAQ for information on obtaining
# a new /etc/services file.
accept tcp 900 tcp.dest=tcp.www
accept tcp 900 tcp.source=tcp.www
# Once the link is no longer live, we try to shut down the connection
# quickly. Note that if the link is already down, a state change
# will not bring it back up.
keepup tcp 5 !tcp.live
ignore tcp !tcp.live
# an ftp-data or ftp connection can be expected to show reasonably frequent
# traffic.
accept tcp 120 tcp.dest=tcp.ftp
accept tcp 120 tcp.source=tcp.ftp
#NOTE: ftp-data is not defined in the /etc/services file provided with
# the latest versions of NETKIT, so I've got this commented out here.
# If you want to define it add the following line to your /etc/services:
#ftp-data 20/tcp
# and uncomment the following two rules.
accept tcp 120 tcp.dest=tcp.ftp-data
accept tcp 120 tcp.source=tcp.ftp-data
# If we don't catch it above, give the link 1 minute up time.
accept tcp 60 any
# Rules for UDP packets
#
# We time out domain requests right away, we just want them to bring
# the link up, not keep it around for very long.
# This is because the network will usually come up on a call
# from the resolver library (unless you have all your commonly
# used addresses in /etc/hosts, in which case you will discover
# other problems.)
# Note that you should not make the timeout shorter than the time you
# might expect your DNS server to take to respond. Otherwise
# when the initial link gets established there might be a delay
# greater than this between the initial series of packets before
# any packets that keep the link up longer pass over the link.
# Don't bring the link up for rwho.
ignore udp udp.dest=udp.who
ignore udp udp.source=udp.who
# Don't bring the link up for RIP.
ignore udp udp.dest=udp.route
ignore udp udp.source=udp.route
# Don't bring the link up for NTP or timed.
ignore udp udp.dest=udp.ntp
ignore udp udp.source=udp.ntp
ignore udp udp.dest=udp.timed
ignore udp udp.source=udp.timed
# Don't bring up on domain name requests between two running nameds.
ignore udp udp.dest=udp.domain,udp.source=udp.domain
# Bring up the network whenever we make a domain request from someplace
# other than named.
accept udp 30 udp.dest=udp.domain
accept udp 30 udp.source=udp.domain
# Do the same for netbios-ns broadcasts
# NOTE: your /etc/services file may not define the netbios-ns service
# in which case you should comment out the next three lines.
ignore udp udp.source=udp.netbios-ns,udp.dest=udp.netbios-ns
accept udp 30 udp.dest=udp.netbios-ns
accept udp 30 udp.source=udp.netbios-ns
# keep routed and gated transfers from holding the link up
ignore udp tcp.dest=udp.route
ignore udp tcp.source=udp.route
# Anything else gest 2 minutes.
accept udp 120 any
# Catch any packets that we didn't catch above and give the connection
# 30 seconds of live time.
accept any 30 any
/etc/ppp/options
================
asyncmap 0
For email replies my address is dmellor at ix dot netcom dot com
------------------------------
From: [EMAIL PROTECTED] (Luca Filipozzi)
Subject: Re: Machine denys telnet and FTP
Date: Sun, 17 Jan 1999 17:54:30 -0800
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] says...
> >> I am using Redhat 5.2 with a 3c509 card. The system is online. However,
> >> when I try to telnet or ftp to it, it finds the host, but keeps denying my
> >> connection
> >> and closes the telnet window. What could be wrong? Thanx.
> >>
> >Chech your /etc/hosts.allow and /etc/hosts.deny files.
> >--
> >Luca Filipozzi <[EMAIL PROTECTED]>
> >
>
> I did...hosts.deny is empty, and hosts.allow sez
> ALL: ALL....any other suggestions?
>
Is there an entry for telnet in /etc/inetd.conf?
telnet stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.telnetd
--
Luca Filipozzi <[EMAIL PROTECTED]>
------------------------------
From: Neil Zanella <[EMAIL PROTECTED]>
Subject: Red Hat 5.0 : usernet hangs
Date: Sun, 17 Jan 1999 18:05:45 -0330
Hello,
Has anyone been experiencing trouble with Red Hat 5.0's usernet
utility. On my machine the application works but fails when it comes
to deactivating the interface ppp0 (at which stage the interface just
freezes).
Any help or agreement that I am experiencing a bug is appreciated,
Thanks,
Neil
------------------------------
** 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
******************************
