home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip
- From: proyse@peeras.demon.co.uk (Phil Royse)
- Path: sparky!uunet!pipex!demon!peeras.demon.co.uk!proyse
- Subject: Routing IP over X25
- Distribution: world
- References: <1992Dec11.123440.17671@medusa.prime.com>
- Organization: Peer Association
- Lines: 42
- Date: Wed, 16 Dec 1992 18:34:46 +0000
- Message-ID: <724530886snx@peeras.demon.co.uk>
- Sender: usenet@demon.co.uk
-
-
- In article <1992Dec11.123440.17671@medusa.prime.com> davidh@CIS.Prime.COM writes:
-
- >route add net yy.yy.2.0 yy.yy.1.1 1
- >
- >to which route says "network is unreachable". This is because the kernel
- >routing code states that the router must be on the SAME network as your
- >interface.
-
-
- Hhmmm.. dunno about that last comment...
-
- Dave,
-
- Unless I've misread your explanation, I think the problem lies in your
- calling the third host yy.yy.2.0 Because if it is on a separate subnet
- from yy.yy.1.1 then its interface must have a different network address.
- In your set up I think you're violating IP addressing rules..(?)
-
- If this is the case, you will need to define the output port of the second
- host yy.yz.1.1 and the input port of the third (last) host yy.yz.1.2
-
- I.e. if the second and third hosts are joined by a subnetwork, then they
- must have a common subnet number (yy.yz).
-
- It's easy to forget that in routing the IP address defines the interface
- of a router or host, not the actual router. I.e. a host acting as a router
- must have one address for each interface it supports... and the network
- number part (in your case the first two octets, as you're Class B).
-
- I hope this helps.
-
- Forgive me if I've given you duff info.
-
- Regards,
-
-
-
- Phil Royse Comms Consultant | member: The Peer Association
- TUDOR HOUSE | (OSI & GOSIP specialists)
- 12 Woodside Road, Purley
- Surrey CR8 4LN (UK) Tel: (+44) 81 645-9868
-