Re: Problems setting up DNS, gateway und subnetmask!



In message <slrndr5qsd.9c.ibuprofin@xxxxxxxxxxxxxxxxx>
ibuprofin@xxxxxxxxxxxxxxxxxxxxxx (Moe Trin) wrote:

> On Wed, 28 Dec 2005, in the Usenet newsgroup comp.os.linux.setup, in article
> <43b1d7dc$0$3797$9b4e6d93@xxxxxxxxxxxxxxxxxxxxxxxxxx>, Tamer Higazi wrote:
>
> >I have received from my ISP an IP, DNS, Subnetmask and the DNS
> >Serverentries to add to my ubuntu linux machine

I *think* what you have is the information for connecting your machine via a
modem. You appear however to be using a router.

The interpretation, if my guess is correct is as follows:

On the WAN (ADSL or whatever) side of your router are two addresses -
81.10.53.21, and 81.10.53.22. One of these is your router's IP address for
the WAN interface, and the other is the remote end of the link. You don't
need to worry about these if your router is connecting.

On the LAN side of your router, i.e. the wiring between the router and your
machine, you are using the private network 10.0.0.x. For this to work your
machine needs to have an address in the 10.0.0.<1-254> range. The router is
10.0.0.138, so don't use that for your machine.

(For this network, the "official" subnet mask is 255.0.0.0, giving addresses
from 10.0.0.1 to 10.255.255.254. However you need to use the mask that is
set on the router, which may be different. Addresses below 10.0.0.254 will
work with any likely mask, provided the mask you set on your machine does
match that on the router.)

You may well find that the router is also the DNS server and DHCP server,
which simplifies things quite a lot.

I can't help you with the routing commands - I'm new to Linux myself.

>
> The information is wrong.
>
> >iface eth0 inet static
> >address 81.10.53.22
> >netmask 255.255.255.252
>
> Looking at RFC1878, that mask says there are four IP addresses on this
> segment:
>
> 81.10.53.20 "Network" address - probably not usable for a host
> 81.10.53.21
> 81.10.53.22
> 81.10.53.23 "Broadcast" address - not usable
>
> >gateway 10.0.0.138
>
> And how does one reach that address? It is not one of the four addresses
> noted above.
>
> >My File /etc/hosts:
>
> Generally, it is a good idea to list the IP address of "this" host, so it
> can boot properly if the name server is not reachable.
>
> >If I enter the command route:
>
> Yes
>
> >sudo route add default gateway 10.0.0.138 eth0
> >
> >I receive this errormessage:
> >SIOCADDRT: Das Netzwerk ist nicht erreichbar (Network unreachable)
>
> Yes - because you can not reach 10.0.0.138 from 81.10.53.20/28. The
> gateway MUST be on the "local" interface (which _probably_ means it
> is 81.10.53.21).
>
> Old guy

--
Alan Adams, from Northamptonshire
alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.nckc.org.uk/
.



Relevant Pages

  • Re: Cannot connect to RWW from home PC
    ... eth0 172.26.0.1/16 Extra none ... That would be the address you need a DNS record for. ... One question - if I reset the Thomson Router will that clear all the ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... No 10.0.0.138 is the address used to log onto Thomson's router to make the ... On the DNS question I can add an MX record in the DNS area of GoDaddy's ... eth0 172.26.0.1/16 Extra none ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... NIC, you need to specify an external DNS server for DNS, instead of the ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... You say "And in the router you need to forward to your external nic IP" ... You say "You need the domain hoster to setup a DNS record that will be ... We have rerun CEICW sort of hoping it would sort out the router but no ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Even a single-NIC configuration should have ONLY the LAN IP of the server as ... Then you can run the CEICW or use the DNS console to enter ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)