"Thomas" == Thomas H George writes:
Thomas> I need basic references to get started. The problem: My
Thomas> daughter's company has instructed her to install DSL to
Thomas> facilitate working from home when she is on-call. She is
Thomas> a system manager for a complex Tandem
ober 22, 2002 11:53 AM
Subject: Re: Networking Help for an Absolute Beginner Please
> Well, I'm not a networking guy myself, but I'd recommend looking at the
> Linux Network Administrator's Guide
> (http://sunsite.ualberta.ca/Linux/LDP/LDP/nag2/index.html) for
> starters. I wo
Personally,
I would go and get a Linksys or one of the other inexpensive DSL/Cable
routers. They are easy to install and provide a limited amount of firewall
capabilities.
Just my .02c
Barry deFreese
NTS Technology Services Manager
Nike Team Sports
(949)-616-4005
[EMAIL PROTECTED]
"Technology
Title: RE: Networking Help for an Absolute Beginner Please
You need to set up a little gateway for your home, use debian and iptables, make sure to install debian with kernel 2.4 to use iptables.
This will let you share your internet connection with all your pc at home.
You can take an old
Well, I'm not a networking guy myself, but I'd recommend looking at the
Linux Network Administrator's Guide
(http://sunsite.ualberta.ca/Linux/LDP/LDP/nag2/index.html) for
starters. I would imagine that has most of what you're going to need
(maybe a little too much?).
As far as hardware goes,
In article <[EMAIL PROTECTED]>,
Antony Burrows <[EMAIL PROTECTED]> writes:
[snip]
> etc etc And I dont have a clue. can anyone tell me what I need to do to
> my linux box and my win95 box to get them talking! or at least point me
> in the right direction of the HOWTOS that tell the slow on
I pulled everything out of my machine but the video card and the nic and
the nic still wouldn't work. Usually I wouldn't have asked the mailing
list about such a simple thing, but this has me baffled. Do you, or
anyone else, know of anything else to try to get my nic working correctly?
On Sun, Jul 04, 1999 at 06:50:48PM -0500, Robert Rati wrote
> On Sun, 4 Jul 1999, John Pearson wrote:
>
> >[snip]
> > A quick look at the kernel source shows some LinkSys cards use the Tulip
> > driver (likely not yours, as I thought these were all PCI cards) and some
> > use the Lance driver; ha
On Sun, 4 Jul 1999, John Pearson wrote:
> On Sat, Jul 03, 1999 at 04:52:14PM -0500, Robert Rati wrote
> > On Sat, 3 Jul 1999, John Pearson wrote:
> > >[snip]
> > > Your NIC driver is sending stuff to your NIC and expects to receive an
> > > interrupt down the track (probably to say that it has fin
On Sat, Jul 03, 1999 at 04:52:14PM -0500, Robert Rati wrote
> On Sat, 3 Jul 1999, John Pearson wrote:
> >[snip]
> > Your NIC driver is sending stuff to your NIC and expects to receive an
> > interrupt down the track (probably to say that it has finished), but the
> > interrupt never arrives.
> >
>
On Sat, 3 Jul 1999, John Pearson wrote:
> On Fri, Jul 02, 1999 at 08:41:47PM -0500, Robert Rati wrote
> > The message in /var/log/syslog said this:
> > Jul 2 20:27:08 Obereon kernel: eth0: Tx timed out, lost interrupt?
> > TSR=0x1, ISR=0x2, t=3500.
> > Jul 2 20:27:18 Obereon kernel: eth0: Tx tim
On Fri, Jul 02, 1999 at 08:41:47PM -0500, Robert Rati wrote
> The message in /var/log/syslog said this:
> Jul 2 20:27:08 Obereon kernel: eth0: Tx timed out, lost interrupt?
> TSR=0x1, ISR=0x2, t=3500.
> Jul 2 20:27:18 Obereon kernel: eth0: Tx timed out, lost interrupt?
> TSR=0x1, ISR=0x2, t=1000.
Robert Rati [EMAIL PROTECTED] wrote:
> The message in /var/log/syslog said this:
> Jul 2 20:27:08 Obereon kernel: eth0: Tx timed out, lost interrupt?
> TSR=0x1, ISR=0x2, t=3500.
> Jul 2 20:27:18 Obereon kernel: eth0: Tx timed out, lost interrupt?
> TSR=0x1, ISR=0x2, t=1000.
> Jul 2 20:27:28 Ober
The message in /var/log/syslog said this:
Jul 2 20:27:08 Obereon kernel: eth0: Tx timed out, lost interrupt?
TSR=0x1, ISR=0x2, t=3500.
Jul 2 20:27:18 Obereon kernel: eth0: Tx timed out, lost interrupt?
TSR=0x1, ISR=0x2, t=1000.
Jul 2 20:27:28 Obereon kernel: eth0: Tx timed out, lost interrupt?
T
Robert:
I see 22 transmit errors on the eth0 interface. Check /var/log/syslog
(or /var/log/kern.log) for a description of the errors. I'm running one
of the 2.0.x kernels, so I can't be much help with problems specific to
your kernel. The files in /usr/src/linux/Documentation/ have some-
times
15 matches
Mail list logo
