Re: SuSE home network

From: Martin Blume (mblume_at_socha.net)
Date: 11/23/03 

Date: Sun, 23 Nov 2003 15:01:59 +0100

"Carl" <phleum_nospam@chello.se> schrieb
> I'm completely lost!
>
> I have four computers (two SuSE 9.0, one SuSE 8.2, and one Win
> 2000) connected to a cable modem. The internet provider allows
> up to four internet connections via dhcp.
ok.

>
> Now, I would like to access all computers from within the same
> network, but I cannot figure out how to do it.
>From your ISP's network or from your own internal network?
As I understand your setup, you have:

---Internet----
    +
    ISP
     +---------+other clients
     |
     your cable modem
       |
       + Win2000
       + SuSE9 (1)
       + SuSE9 (2)
       + SuSE8.2

I have instead :
      |
      | (setup as above)
      |
      my cable modem
      |
      my router/firewall
      |
      + W2k
      + SuSE 8.2
      + diverse other stuff

The advantages are:
- I am on my internal network (192.268.1.x) to which nobody has
access but me (provided that my router/firewall is safe)
- I can hook up as many computers as I like, but only is visible
from the outside (the router)

My router is a hw router, no a dedicated pc. You can also have one
of your computers doing the routing / firewalling.

> I've read different manuals and looked up
> the basics of TCP/IP, NIS, NFS, etc in several Linux books.
>
> This doesn't help, I'm stuck!
>
> Does anyone know about a simple step-by-step manual (from the
> basic HW-stuff to the more intricate procedure of setting IP-
> adresses, defining gateways, routing tables, and the
> configuration of NIS/NFS servers/clients).
>
Where's the problem?
1.) First you have to configure your network hardware. Start up
Yast, select network devices, network card, let Yast detect your
card, configure it, either with automatic address (DHCP), this would
be the case of directly hooking up your pcs to the cable modem. In
the case of a router between pcs and cable modem, you can set up for
DHCP or manual ip addresses. In the case of a manual ip address,
choose one in the range of e.g. 192.168.0.x with a netmask of
255.255.255.0.

After this step, you can check, that the command ifconfig (given as
root user) gives you an output for eth0, such as:

smail:/home/mblume # ifconfig
eth0 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:ff
          inet addr:192.168.1.24 Bcast:192.168.0.255
                    Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1400 Metric:1
           [...]

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1
           [...]

2.) Configure routing with yast also in the same screen. Here you
have to enter the address given by your ISP or the address of your
router/firewall. If you setup W2k to get the address by DHCP from
your ISP, you'll this address and also the addresse(s) for name
resolution (see below).

After this step, you can check that :
# ping 195.135.220.3
PING Turing.suse.de (195.135.220.3) 56(84) bytes of data.
64 bytes from Turing.suse.de (195.135.220.3): icmp_seq=1 ttl=244
     time=84.6 ms
...
works.

3.) Configure DNS (Domain Name Resolution). This is the sw that
resolves human-readable names like www.suse.de into addresses that
computers understand like 195.135.220.3. Start up YaST and select
Network Services, select DNS and Hostname, then enter the addresses
given to you by your ISP into addresses for nameserver 1, 2 and
possibly 3. If you selected DHCP in step 2, you can also get these
adddresses automatically.

After this step, you can check that :
# ping www.suse.de
PING Turing.suse.de (195.135.220.3) 56(84) bytes of data.
64 bytes from Turing.suse.de (195.135.220.3): icmp_seq=1 ttl=244
     time=84.6 ms
...
works.

This should bring you up and running. I hope not to have too many
errors in explaining.

If you have any questions, come back and ask here.

HTH
Martin

PS: My thanks and apologies to SuSE that their server is always a
guinea pig for my tests and explanations.

Relevant Pages

  • RE: [Full-Disclosure] Calcuating Loss
    ... The Internet is just that, ... Each network is owned by someone. ... > What we need is something that you have to log into or your DHCP is revoked immediately. ... > So again it is anonymity that causes most of the grief. ...
    (Full-Disclosure)
  • Re: F9 DOS attack
    ... you could simply force the cable modem to reset ... vulnerable to attack from the internet. ... "I'm not getting a DHCP address from you, ...
    (Fedora)
  • Re: How to get my 2 ethernet cards to work
    ... If you have a cable modem that connects to an ethernet ... which connects to the internet. ... that with the almighty Linux, known to be a network OS, how could it ... > deeply wrong here and I need to fix it before taking a single step ...
    (comp.os.linux.networking)
  • RE: [Full-Disclosure] Calcuating Loss
    ... The Internet is just that, ... Each network is owned by someone. ... > What we need is something that you have to log into or your DHCP is revoked immediately. ... > So again it is anonymity that causes most of the grief. ...
    (Full-Disclosure)
  • Re: Multiple IP Schemes for Different Buildings
    ... The linksys on your first network stays as it is, ... DHCP broadcast is on the local subnet only, ... router to forward internet traffic to your firewall. ... If each server has it's own DHCP server then I don't need to worry ...
    (microsoft.public.windows.server.general)