On Wed, Jan 21, 2004 at 04:46:37PM -0800, Bill Moseley wrote:
> So the question is, in a setup like the above what's the best way to get
> in and sniff the packets?
My $0.02 is: 2 ethernet cards, 2 cross-wire TP cables, one decent Debian
installation turned into a router:
[Brother] <-> :eth0:
Friend has a Brother Fax/Printer thingy. It has an ethernet port and it
has this "Internet Fax" setup (which is not really a fax) where you type
in someone's email address, scan some documents and it emails an image
(tiff format). It's basically a mail client.
Here's the problem: He has a pppoe
Hmmm, 'ipchains -L' or 'ipchains -L -v' could be useful
here. If the i/o chains filter or accept packets that
could be (part of) the problem you're a step closer to
the solution.
I use ipchains sometimes to block/accept packets to see
what will happen in some circumstances.
I'm very curious what
While tracking down network problems of any kind, it's quite handy
to take a snapshot of the networking parameters so you can look at
it after the event. I have a bash function which is currently:
/bin/uname -a
/sbin/ifconfig
/sbin/route -n
/usr/sbin/arp -n -a
/bin/netstat -n -
4 matches
Mail list logo
