thats right. With one ethernet plug, you need to have 3 cards. 2 in the
computer that actually is connected to the plug. one card for the pplug
and one card for communications with thte other computer. ofcourse the
other computer must have another card. No special software is needed.
read networkin
Alec wrote:
How does one connect two computers to the internet throught one ethernet
socket? Does one of them have to have two ethernet cards and run special
software?
Technically, one socket would not do the job. But to your querstion:
One computer acts as a gateway. One interface is connec
First you need to find out if that card is supported. If it is then
find out which driver you need. Then you compile that driver into you
kernel or as a module. Someone may know which card your talking about
and tell you which driver you need, if it is supported. If not there
are a couple place
You might want to check /usr/doc/sysvinit/examples/network (from the sysvinit
package).
>
> Just transferred over from Red Hat 6.1 to Debian 2.1. My NIC card worked
> fine in Red Hat and appears to work okay in Debian _if_ I issue an
>
> ifconfig eth0
>
> command. Naturally, though, I'd like t
heya, paul
have a look in /etc/init.d/network
from
da bobstopper
-Original Message
Just transferred over from Red Hat 6.1 to Debian 2.1. My NIC card worked
fine in Red Hat and appears to work okay in Debian _if_ I issue an
ifconfig eth0
command. N
> Just transferred over from Red Hat 6.1 to Debian 2.1. My NIC card worked
> fine in Red Hat and appears to work okay in Debian _if_ I issue an
> ifconfig eth0
This is typically done in the script /etc/init.d/network That script is
generated at install when you answer the questions about your
when i want to change network settings to take effect everytime it boots i
edit /etc/init.d/network
hope you enjoy debian, ive played with a few rh boxes and they about drove
me mad.
nate
On Mon, 10 Jan 2000, Paul M. Foster wrote:
paulf >
paulf >Just transferred over from Red Hat 6.1 to Debian
You can put:
ifconfig eth0 netmask
into /etc/init.d/network .
You will probably also have to add your "route" line in there as well.
On Mon, 10 Jan 2000, Paul M. Foster wrote:
>
> Just transferred over from Red Hat 6.1 to Debian 2.1. My NIC card worked
> fine in Red Hat and appears to wor
At 10:55 AM 7/12/1998 +0800, you wrote:
>Could be. Routing is not that hard, but it depends a bit on what kernel
>you are using. 2.1.x is easier than earlier kernels.
I'm using 2.0.29 is that a problem?
For a very good debugging tool use tcpdump. You will see both incoming
>and outgoing packets
Everthing looks good. ARP packets are most likely what you're seeing on your
hub. Can
you check out your NT machine's configuration?
Tomt wrote:
> Heres my previous message
> ___
> Hi Everyone,
>
> I've managed to get tcp/ip network
> Hi Everyone,
>
> I've managed to get tcp/ip networking up and running on my Debian machine.
> I have my 3com 3x509 configured to ip address 192.168.0.1, I have one other
> machine on my local network(for now) and it is ip 192.168.0.2.
>
> How can I get my debian machine to see(ping) the othe
"G. Kapetanios" <[EMAIL PROTECTED]> writes:
> beacause of high network load and nothing to do with hardware. However I
> now get it not only in tty8 where syslog messages appear but in my working
> console . As a matter of fact while I write this message through telenet
> to my mail sever I get th
12 matches
Mail list logo
