-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Quaylar
Sent: Wednesday, January 17, 2001 5:15 PM
To: [EMAIL PROTECTED]
Subject: [newbie] local unix-win microlan
hiho,
im trying to set up a unix-win microlan (how it is called in the
mandrakeuser.org-guide) and i´ve followed the steps as described in the
guide at mentioned adress:
unix side :
ethernet card is recognized
eth0 modules are loaded without probs
local ip adress configured by ifconfig to 192.168.0.1
route add -net 192.168.0.0 eth0 ..... set
win and unix machine entries in the /etc/hosts file
win2k side
properties for local connection : TCP/IP : 192.168.0.2 netmask
255.255.255.0 (unix side too)
set DNS of my isp and entered the unix box as gateway
so far everything seems to be ok......but i cant ping the
machines.......neither win from unix nor unix from win.....always reaches a
timeout, has somebody a point regarding this i might have missed ?
---
Being able to ping your machines across the LAN is the first important step.
This establishes that your LAN cards are correctly configured and that your
wiring is ok.
Assuming for the moment that your lan cards are correctly configured, look
again at your wiring.
Since you are using CO-AX, you -MUST- have a BNC plug at each end of the
cable and then a "T" connector.
I.E.
[=-|--------------|-=]
| |
Computer
The "[=" represents the terminator at each end.
While the -|- represents the "T" connector.
Also, I know this sounds funny, but it's true. If your cable is TOO short,
some lan cards see the unusually low resistance as an "open" connection and
shut down their transmitters.
Make sure your cable is at least 15 feet in overall length. You could add
another segment if it is too short.
Put an Ohm meter across the center ping to the shield with the cable
unplugged from the computers and you should get 1/2 the value of each
terminator's resistance.
If not you have a short or a wiring problem.
BTW: Twisted pair Ethernets are far easier to debug since the hubs normally
have lights to tell you if everything is hooked up properly.
You must start off by being able to ping the different machines...
---
Re: Proxy & Masq
Proxy and Masq are different, though in some confusing ways very similar.
With Proxy servers, the user's application "logs" into the PROXY server as a
user and submits a request to the internet. The PROXY then transmits the
request back to the client.
With proxy servers, you applications must directly support PROXY usage. Many
programs do not!
--
With MASQ, each machine believes that it is "on" the internet. That is that
it has it's very own internet connection via the Linux box, which acts as a
gateway.
What really happens, though, is that they client machine is set up to have a
"private" ip address. This private address creates packets which are not
permitted to be sent out via the internet. The internet would actually
disregard them!
Instead the packets arrive at the "gateway" (Linux box). Linux strips off
information from the packets and "repackages" them with it's own VALID IP
address, and sends them up to the internet.
When the response comes back in, Linux does the opposite.
Linux can do this VERY quickly. As far as your other computers are
concerned, they all have connections to the internet.
As far as Linux is concerned, it is "routing" masq'd packets to the
internet.
As far as your ISP is concerned, your Linux box is a very busy machine, but
you only have ONE internet connected computer.
Thus Linux is a great way to fool your ISP into believing that you only have
one machine "on" the internet.
For the most part the ISP doesn't care, since they are only supporting one
computer connection. Everyone is happy, since you pay less!
-JMS
[EMAIL PROTECTED]
---
furthermore i´d have a question regarding the difference between ip
masq/proxy/micro lan:
ip masq howto tells me that if one uses ip masq the server would NOT act as
a proxy and the clients would be DIRECTLY connected to the internet through
the server, although for the external network all clients would have the ip
of the server.
so how is this meant ?......what is the difference to the proxy server then
?
and can i also do connection sharing without masq but only the "win/unix
microlan" ?
would be glad if somebody can bring some light into this, cause i´d really
like to "understand" what i´m doing ;)
regards,
--quay
------------------------------
-Quaylar-
Icq# 30932448
[EMAIL PROTECTED]
<! Knowledge is power >
