Linux-Networking Digest #246, Volume #12 Mon, 16 Aug 99 16:13:36 EDT
Contents:
Re: Need help masquerading PPTP VPN with IPChains (Johan Welsch)
can't talk to a SUN machine ? (Theodor Cranendonk)
Re: gdm murdered mysteriously ([EMAIL PROTECTED])
Re: Seeing my linux in windows (Ville Nummela)
Re: delaying eth1 initialization ("A Chawla")
Networking problems ([EMAIL PROTECTED])
Re: Newbie 3c589 Red Hat PCMCIA question ("Tris Thorne (LTH)")
Re: Newbie and Ethernet Card (Richard Petty)
diald - Dialing at bad times (John Crider)
Great networktroubleshooting resource! (Othmar Kyas)
PPP logon delay (Luc Willems)
LINUX & NETWORK LAYERS (Martin Birtel)
DIGI Classicboard/8 LINUX Drivers are there any?? ("Stathis Grigoriadis")
Re: TIME_WAIT with TCP socket ([EMAIL PROTECTED])
Setting up a Network ("Joshua Mitnick")
Automating dial up links (Ivan Berg)
Re: Possible to use PPTP on Win98 with Linux firewall Marquerading? (Kenneth P
Kennedy)
help with ipfw (Gregory Geller)
Re: Multi homed Linux as router between MS domains ("Andrey Smirnov")
Looking for Modem Port Scanner/Sniffer Program ("Young4ert")
----------------------------------------------------------------------------
From: Johan Welsch <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.security
Subject: Re: Need help masquerading PPTP VPN with IPChains
Date: Mon, 16 Aug 1999 18:41:10 +0200
As I understood your problem, you may wish to do the following :
192.168.1.2 ---> 216.181.87.4 ---> 209.183.196.1
NT LINUX FIREWALL VPN SERVER
I've already done such masquerading over VPN with an entire Linux system
and VPN 1.0.5 for Linux.
The Linux Firewall must be the VPN client
then your NT station use it as its gateway (as usual)
but U must add a special route on your VPN client to your VPN server
using the SL interface created by VPN, and an other one on your VPN
server back to your local area 192.168.1.2 :
NT : IP 192.168.1.2, Gateway 216.181.87.4
LINUX FIREWALL
SL0 interface : 10.1.1.1
add a route to 10.1.1.2 through SL0
VPN SERVER
add a route to 192.168.1.2 through SL0
Be careful with your firewall chains. Try first with an opened firewall
good luck
yoyo
------------------------------
From: Theodor Cranendonk <[EMAIL PROTECTED]>
Subject: can't talk to a SUN machine ?
Date: Mon, 16 Aug 1999 18:35:29 +0200
Does anybody know if there is a talk deamon for
linux that allows one to talk to a sun machine. Or are there
any other options ?
I keep getting: [Checking for invitation on caller's machine]
but nothing else.
thanks
+------------------------------------+
| Theodor Cranendonk |
| E-Mail: [EMAIL PROTECTED] |
+------------------------------------+
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: gdm murdered mysteriously
Date: Mon, 16 Aug 1999 17:11:08 GMT
you might want to delete gdm.pid in /var/run directory.
In article <[EMAIL PROTECTED]>,
Gunendra Patil <[EMAIL PROTECTED]> wrote:
> Hi,
> I also got the same problem when I messed up with IRQ's. When I
copiled
> my kernel with sound capabilities I gave IRQ 12 ( which is used for
> mouse, at least in my system) and I got the same problem...
> You may wish go look at the /var/log/messages to check whether you
have
> any similar problem. You may wish to use rescue disk to boot up to see
> this.
>
> All the best !!
>
> Frank v Waveren wrote:
> > Anything in the logs?
> >
> > In article <[EMAIL PROTECTED]>,
> > Marek <[EMAIL PROTECTED]> writes:
> > > According to /var/run/gdm.pid, gdm was already running (656) but
seems
> > > to have been murdered mysteriously
> > >
> > > I got this message I can not run X ...any idea what to do with
this??
> > >
> > > Marek
> > >
> >
> > --
> >
> > Frank v Waveren
> > [EMAIL PROTECTED]
> > ICQ# 10074100
>
> ------------------ Posted via CNET Linux Help ------------------
> http://www.searchlinux.com
>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: [EMAIL PROTECTED] (Ville Nummela)
Subject: Re: Seeing my linux in windows
Date: 16 Aug 1999 14:10:55 GMT
On Mon, 16 Aug 1999 09:21:52 -0400, jake <[EMAIL PROTECTED]> wrote:
>Hello:
> I am trying to use samba to connect to my linux machine thru windows.
>I can use smbclient fine to connect to from my linux machine to a
>windows machine, but i am having trouble going from the windows machine
>to my linux box. My linux box doesn't even show up in the network
>neighborhood and when i try and type in \\linux\share it always asks
>for a password. I have no idea what this password would be, i've tried
>roots, made a user with the same name as my windows one... Any help is
>appreciated.
It depends on the way you have configured your samba. You really should
look at the documentation (there are several files to read, everything
about security and passwords).
--
| IRC naturae alienum est! Periculosum est! Delendum est! |
------------------------------
From: "A Chawla" <[EMAIL PROTECTED]>
Subject: Re: delaying eth1 initialization
Date: Mon, 16 Aug 1999 16:55:06 GMT
Thanks,
I actually had /etc/conf.modules set up as:
alias eth0 ne
alias eth1 ne
options ne io=0x300, 0x320 irq=3,5
I decided to also change lilo.conf to include after the 'image=' stuff:
append="ether=3,0x300,eth0 ether=5,0x320,eth1"
This got things working. Thanks again,
Anoop
Steve Cowles wrote in message ...
> Try adding
>an alias to the file /etc/conf.modules (see below) so that it will load the
>driver (prior to the network stack being brought up). Which by the way, is
>why you are getting your "delaying eth1 initialization" message.
>
>In your case, you will probably have to add some additional information
>(like irq/io address) to this file to tell the kernel which card is eth0,
>eth1. On my system (RH60) there is a file in the /boot directory called
>module.info that has some good infoformation on what that particular
>driver/module is expecting for directives placed in the conf.modules file.
>ie How to specifiy irq/baseio per driver. Since I'm using two different
>drivers, I did not have to specifiy the irq/baseio stuff.
>
>> I cannot seem to get a second card recognized which is a ISA NE2000
>> compatible with a realtek8019 chipset. My first card is also an ne2000
>> compatible D-Link card.
>>
>>
>> I upgraded to the 2.2.11 kernel (and also had to change to ISC's dhcp
>> client). But the DHCP address is really only for eth0.
>>
>> cards are configured as follows:
>> eth0 interrupt=3, io=0x300
>> eth1 interrupt=5, io=0x320
>>
>> I previously tried interrupt=9 and 0x280 but same problem. I did check
>that
>> there are no io conflicts.
>>
>> On bootup I get:
>>
>> NE*000 ethercard probe at 0x300: xx xx xx xx xx xx
>> eth0: NE2000 found at 0x300, using IRQ 3.
>>
>> But no mention of eth1.
>>
>> then later I get
>>
>> "Delaying eth1 initialization"
>>
------------------------------
From: [EMAIL PROTECTED]
Subject: Networking problems
Date: Mon, 16 Aug 1999 16:48:15 GMT
Help!!!
I've install Linux 6.0 on an HP Pavilion. Everything went perfectly.
I used a 3c509 NIC and "ifconfig" tells me both "lo" and "eth0" are up
and running.
But I can't seem to ping out of or into this machine. When I ping to
another machine, "netstat -i" shows that there are 25 TRX-OK but 0
RV-OK.
Thanks very much in advance.
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: "Tris Thorne (LTH)" <[EMAIL PROTECTED]>
Crossposted-To: redhat.hardware.arch.intel,redhat.networking.general
Subject: Re: Newbie 3c589 Red Hat PCMCIA question
Date: 16 Aug 1999 17:04:14 GMT
If you have the 3c589_cs.o file handy, just load it as a module after
booting.
#insmod /lib...../modules/...whatever/3c589_cs.o
I think you have to bring up the interface then with ifconfig -i <devname>
up
or if you want it to do it at boot, read the howto about conf.mod file.
Good luck!
Tris
Bob Festa <[EMAIL PROTECTED]> wrote in article
<[EMAIL PROTECTED]>...
> Great forum here. Installed RH 6.0 on a Dell inpiron laptop. My ethernet
> card (3c589) was not one of the module choices. During the networking
> install section, how do I point to the 3c589_cs.o driver for the module
> thats in another directory?
>
> Failing that, how do I link the driver after installation. Linux Conf
does
> not have the 3c589 module listed as a choice either? I can 'locate
> 3c589_cs.o', and copy it to the module directory but I dont know how to
> have the install script 'see' it.
>
> Thanks
>
> Bob
>
> ------------------ Posted via CNET Linux Help ------------------
> http://www.searchlinux.com
>
------------------------------
From: [EMAIL PROTECTED] (Richard Petty)
Subject: Re: Newbie and Ethernet Card
Date: Mon, 16 Aug 1999 17:55:56 GMT
In article <[EMAIL PROTECTED]>, Charles van Trappen
<[EMAIL PROTECTED]> wrote:
>This could be any of the following causes I think:
>- you misconfigured the IO, IRQ stuff for the card (check under Win98
>which resources it is using - under Control Panel|System check "Network
>adapters", select your NIC and click the properties button - check the
>"Resources" tab, which gives you the IO range and IRQ);
>- another ethernet module was loaded: check your /var/adm/messages file
>for messages like
>
>Aug 12 23:18:25 router kernel: eth0: 3c509 at 0x300 tag 1, BNC port,
>address 00 60 8c 96 ea 78, IRQ 5.
>Aug 12 23:18:25 router kernel: 3c509.c:1.16 2/3/98
>[EMAIL PROTECTED]
>Aug 12 23:18:25 router kernel: eth0: Setting Rx mode to 1 addresses.
>
>The main thing to look for is basically "eth0".
So what tools exist IN LINUX to check on IRQ matters?
Does everyone have to boot Window to configure a Linux box?
--Richard
PS: I've to two NICs -- neither one are recognized.
--
Spam deterent: Remove the "bogus" part for a correct address.
------------------------------
From: John Crider <[EMAIL PROTECTED]>
Subject: diald - Dialing at bad times
Date: Mon, 16 Aug 1999 13:48:54 -0400
I am running diald v 0.99 on Slackware 4.0. Using netwatch and netstat
on my Linux box I have seen that netbios (from Win98) is firing a
request that diald is trying to resolve by dialing my ISP. When I
change diald.conf to ignore these UDP packets, I can then do NO name
resolution.
The problem I have I think is well documented as a problem (I have seen
allusions to it all over). The only solution I have seen is getting my
own DNS running on my Linux box. Is this true?
Can anyone tell me if I have any options from the windoze side to turn
these blips off? Is there some more specific UDP packet I can ignore?
I looked for FAQs to answer this question, but the only one I found (at
the diald website) said that they didn't know what to do about this
situation. Please help!
--
The basic needs of sentient beings can be expressed
in four categories: Food, Shelter, Intellectual Stimulation and
dimly lit places in which to gather and consume things their
mothers told them not to. -Some smart person
------------------------------
From: Othmar Kyas <[EMAIL PROTECTED]>
Subject: Great networktroubleshooting resource!
Date: Mon, 16 Aug 1999 20:42:25 +0200
Try out
www.networktroubleshooting.com -
it is the best and most dedicated troubleshooting site for LAN WAN and
ATM on the Internet. Hundreds of problem symptoms and their typical
causes. If you provide new symptoms and causes you receive a free copy
of the Fault-Navigator software.
Regards
Othmar
------------------------------
From: Luc Willems <[EMAIL PROTECTED]>
Subject: PPP logon delay
Date: Mon, 16 Aug 1999 20:47:16 +0200
I have a linux server (kernel version 2.2.7 ) running as a dial in
server voor PPP connections.
When i login with a WIN95/98 client i've noticed that there is a delay
between the point that you are logged in , according to the linux server
, and the point windows wil tel you you are connected. I 've seen 1 case
where it took about 1 minute before the windows send a message that it
was connected. In this time you can make a netwerk connection with the
server.
In "normal" conditions , this time is about 10 to 15 seconds.
Does anybody now if this is a problem of WIN95/98 or the PPP Deamon and
how i can change this behavior
Luc Willems
------------------------------
From: Martin Birtel <[EMAIL PROTECTED]>
Subject: LINUX & NETWORK LAYERS
Date: Mon, 16 Aug 1999 20:48:40 +0200
Hi!
I want to send and receive single ethernet packets.
I think i have to access other lower network layers of linux and i don=B4=
t
know how.
is there some kind of overview of the linux-network layers and how to
access them with c++/c???
thanx for any help
Martin
------------------------------
From: "Stathis Grigoriadis" <[EMAIL PROTECTED]>
Subject: DIGI Classicboard/8 LINUX Drivers are there any??
Date: Mon, 16 Aug 1999 21:14:03 +0300
Do you know abou any linux driver for the Multiserial DIGI Classicboard/8
??? ISA Card ???
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.unix.programmer,comp.protocols.tcp-ip
Subject: Re: TIME_WAIT with TCP socket
Date: Mon, 16 Aug 1999 18:51:22 GMT
> Actually most stacks use the BSD time-wait hack (sanctioned by
RFC1122).
> When a new connection attempt with a sequence number after the last
> sequence number used by the old connection occurs the time-wait is
dropped
> early and the connection request is processed.
I've always been under the impression that the chances of successfully
taking that path were rather slim.
rick jones
--
these opinions are mine, all mine; HP might not
want them anyway... :)
feel free to email, or post, but please do not do
both...
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: "Joshua Mitnick" <[EMAIL PROTECTED]>
Subject: Setting up a Network
Date: Sun, 15 Aug 1999 16:17:52 GMT
I just finished installing RedHat 6.0. My first question is: When I
installed for my LAN (Cable Modem) I didn't know all of the information.
How do I find out my Domain name, Default Gateway, Primary Nameserver and
all those things from Windows98? (Domain name is not in the winipcfg, so I
need to find out some info that's not there) Anyway, if I were to reinstall
and have all of the information to set up the network correctly, would the
cable modem be working? (ie. be able to just click on netscape or something
and automatically goto webpages without having to connect to an ISP or
anything) Thank you.
[EMAIL PROTECTED]
------------------------------
From: Ivan Berg <[EMAIL PROTECTED]>
Subject: Automating dial up links
Date: Sat, 14 Aug 1999 21:20:51 -0600
Anybody know of a program that will automate dial up links when they are
needed, dial on demand sort of deal and disconnect when needed. I have
tried diald and cannot seem to get it to work properly. Any suggestion
for different program or help with diald?? Thanks
Here is my diald problem:
I have read the FAQ and still have this problem:
Diald works great until after I connect for the first time, it then
shuts down the connection after rules have been met, the problem is it
immediately brings it up again after it shuts it down. In other words,
the second I get it up, it's going to keep going up.
tcpdump shows these RIP routing packets when no activity is presented
from the user:
207.0.103.15.route > 207.0.103.111.route: rip-resp 1: 207.0.103.0(1)
207.0.103.111 > 207.0.103.15: icmp: 207.0.103.111 udp port route
unreachable [tos 0xc0]
This is repeated over and over again every 30 seconds(default time for
RIP updates)
It seems I should be ignoring the RIP updates by defaults, I think the
ICMP replies is what is bringing it up.
I tried to fix it in the standard.filter but it doesn't seem to be
working.
Here is my standary.filter, any help would be appreciated. Thanks
# 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
signficant
# 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 transfered, 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 neccessarily 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 120 tcp.dest=tcp.www
accept tcp 120 tcp.source=tcp.www
# SSL connections are usually for secure http so treat them like http.
# NOTE: Your /etc/services may not define the tcp service ssl, 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.
keepup tcp 120 tcp.dest=tcp.ssl
keepup tcp 120 tcp.source=tcp.ssl
# 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 10 minutes up time.
accept tcp 400 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.
#Added by IMB to keep ICMP from bring connection up
ignore icmp any
ignore udp any
# 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 gets 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 10 any
------------------------------
From: Kenneth P Kennedy <[EMAIL PROTECTED]>
Subject: Re: Possible to use PPTP on Win98 with Linux firewall Marquerading?
Date: Mon, 16 Aug 1999 10:08:30 -0600
Actually, this is only talking about what the Win95/98 box can do. In
otherwards, you can't use a Win95/98 box to do IP forwarding. What is done
with the actual ip streams is uneffected.
-ken-
"You're one of those condescending Unix computer users!"
"Here's a nickel, kid. Get yourself a better computer" - Dilbert.
On Mon, 16 Aug 1999, Peter Hacksel wrote:
> From:
>
> ftp://ftp.rubyriver.com/pub/jhardin/masquerade/ip_masq_vpn.html
>
> "Note for W'95/'98 VPN client users: sorry, but the W'95/'98 IP stack does
> not support IP forwarding (can we say "Brain Dead"?) or more than one
> simultaneous PPTP session. Every W'95/'98 system will have to establish its
> own connection to the VPN server."
>
> Can I interpret this correctly as saying that I cannot use Win98 as a PPTP
> client (behind my Linux firewall) to connect to a PPTP server (outside my
> firewall). Does my Win98 box need to know its traffic is being forwarded?
>
> Thanks,
>
> Peter
>
>
>
>
------------------------------
From: Gregory Geller <[EMAIL PROTECTED]>
Subject: help with ipfw
Date: Mon, 16 Aug 1999 15:07:25 -0400
Reply-To: [EMAIL PROTECTED]
I'm trying to get ipfw to log packets going out of our internal network
so I can keep track of students downloading warez and porn. I have been
able to get such a log using ipfwadm, but I can't seem to get it to
resolve the destination IP address, which would make things a lot
easier.
Any ideas? The man page was no help on this issue.
Thanks,
Gregory Geller
Savannah College of Art and Design
------------------------------
From: "Andrey Smirnov" <[EMAIL PROTECTED]>
Subject: Re: Multi homed Linux as router between MS domains
Date: Mon, 16 Aug 1999 12:45:59 -0700
Do you use WINS on your network?
Nuno Jonet <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]...
> Hi all
>
> My company has two subnets, 192.168.20.0 and 192.168.10.0 .
> Each of them is a Win NT domain. Both servers at each segment are
multihomed
> and are serving as gateways. Because of the way MS networking works, each
> subnet can't see the other, only the other subnet's server, and even then
> it's really slow.
>
> For this reason, I thought of putting Red Hat Linux 5.2 with 2 NICs to
serve
> as a router between the segments.
> All went well, except for when I tried to browse the network. Although I
can
> ping both subnets from the Linux box, and ping any host from any other
> subnet from any machine, the MS browsing thing isn't happenning. Now I
> can't see any machine across subnets...
>
> Since ping is working, I suppose the gateways were correctly configured.
> It almost feels like the Netbios packet is being striped when it passes
> through the Linux box.
>
> Am I missing something ???
> Samba was automatically installed. Could it interfere ?
>
> Any help is most welcome !!!
>
> Thanks in advance
> Nuno
>
>
------------------------------
From: "Young4ert" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Looking for Modem Port Scanner/Sniffer Program
Date: Mon, 16 Aug 1999 19:37:22 -0400
Can anyone tell me where I can find a program that can sniff the traffic on
a modem or serial port?
--
[EMAIL PROTECTED]
PS. Please remove 4 from the reply address should you decide to reply.
------------------------------
** 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
******************************
