What network identifier to use???

What network identifier to use???

Post by Will Muldre » Wed, 25 Aug 1999 04:00:00



I've just connected by two linux machines together, recompiled kernel
many times to install hardware, and am now trying to get a tiny network
going.  I connect to the internet via a dial up using pppd.  I can
telnet between my two machines - but so far I've just used some
arbitrary network identifier

My question is, what network address should I use for my machines - the
x.x.x.mymachine bit...?  Does it matter if there's another network out
there with the same address?  I know you have to register domain names,
but what about IP addresses?

Forgive me if I'm being an idiot - I'm quite pleased I've got this far!!

Will Muldrew

 
 
 

What network identifier to use???

Post by Robert_Glove » Wed, 25 Aug 1999 04:00:00


There are blocks of addresses reserved for private networks (RFC
1918).

Class A private networks
10.n.n.n

Class B private networks
172.16.n.n
through
172.31.n.n

Class C Private networks
192.168.n.n

You can use private network addresses any way you want (sort of).  By
design, these addresses cannot travel across the internet -- that
keeps them "private".  Any self-respecting internet router will refuse
to forward packets to/from these addresses.  That means that you
should never see a private address in one of those ranges unless
perhaps your ISP uses one of them.  In that case your mail server,
news server, etc. might be visible to you as a private address.  If
your ISP uses a private address range, then avoid using that yourself.

You might ask: How do I get on the internet when I have a private
address?  The answer is simple: it is the interface (network card,
modem PPP connection, etc.) that has an IP address, not the computer.
Computers can and do have more than one interface.  So your computer
can simultanesously have a private address of 192.168.88.8 and a
public IP address of 204.205.206.207.

When you dial up you are temporarily assigned a globally valid IP
address for the duration of your session.  It gets re-assigned to the
next caller when you hang up (or get hung up on).


>I've just connected by two linux machines together, recompiled kernel
>many times to install hardware, and am now trying to get a tiny
network
>going.  I connect to the internet via a dial up using pppd.  I can
>telnet between my two machines - but so far I've just used some
>arbitrary network identifier

>My question is, what network address should I use for my machines -
the
>x.x.x.mymachine bit...?  Does it matter if there's another network
out
>there with the same address?  I know you have to register domain
names,
>but what about IP addresses?

>Forgive me if I'm being an idiot - I'm quite pleased I've got this
far!!

>Will Muldrew


 
 
 

1. Extracting identifiers using sed

Hi,

I've been trying solve a problem using with sed without success, I can
do it in perl but I'm wondering if its practical in sed.  I have a C
file from which I would like to extract all the identifiers beginning
with ID_.  For example, the output on the following input:

        if (ID_XYZ == ID_FOO) {
                zap(ID_PAQ);
                ID_PQ(ID_RS);
        } else {
                j = ID_UUQ;

would be:

ID_XYZ
ID_FOO
ID_PAQ
ID_PQ
IU_RS
ID_UUQ

I can't see how one would accomplish this using the s/// command without
using another utility to break the lines up into a token per line.

BTW, here is the perl:

while (<>) {


        }

Regards,

Niall

2. Pseudo-tty

3. Using dhcp-client-identifier to get fixed IP address

4. Weird path error in ftptool 4.6

5. Linux as network printer identifier for Windows users

6. sn3200 ethernet card driver

7. Iproute2 problem across networks using NAT and 2 internal networks

8. struct in_addr

9. using network boot to install RedHat using Anaconda

10. Network to Network IPSec VPN using RHEL/CentOS: separate VPN Router and LAN Gateway

11. Does AIX support Combine 2 network adaptor to form a single network interface using single IP

12. Using Linux to Identify Network Printers for Windows Machines on Same Network

13. Wireless networking using VPN to access home network