![]() |
![]() |
Articles / TULARC / PC info / Amiga / Amiga Networking / | ![]() |
|
![]() |
||||
![]() |
![]() |
|||
![]() |
![]() |
|||
![]() |
||||
|
|
||||
![]() |
![]() |
|||
![]() |
60 How do I configure a machine which has both an Amiga Link and an ethernetconnection so that machines on either network can see each other? |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
![]() |
||
![]() |
||
![]() |
![]() |
![]() |
![]() |
||
|
|
||
![]() |
||
![]() |
![]() |
![]() |
![]() |
||
![]() |
||
This article is from the Amiga Networking FAQ, by Richard Norman with numerous contributions by others.
Given machines A, B, and C with node B having both Amiga Link and Ethernet card
(Quicknet) as shown below, and all running Envoy.
A <=== Alink ===> B <=== Ethernet ===> C
In order for node A to access node C or vice versa use the following configuration
scheme: (IP addresses for example only!)
node A node B node C
IP-Address: 244.1.a.a 244.1.b1.b1 244.1.c.c
244.2.b2.b2
Subnet Mask: 255.255.0.0 255.255.0.0 255.255.0.0
255.255.0.0
Use Realm: yes yes yes
Realm-Serv: NO yes yes
Realm-Name: NET NET NET
Serv-Addr: 244.1.b1.b1 244.1.b1.b1 244.2.b2.b2
Def GateWay: 244.1.b1.b1 ------ 244.2.b2.b2
Loc Realms: ------ NET 244.1.0.0 -------
Loc Realms: NET 244.2.0.0
Rem Realms: ------ ------ ------
where b1.b1, and a.a are the AmigaLink hardware addresses. i.e. the last two bytes
of the IP address MUST match the hardware address on the AmigaLink interfaces.
On the ethernet interfaces, however, b2.b2 and c.c can be anything since Envoy
supports ARP on ethernet.
NOTE: the IP addresses are for example ONLY! Unless you manage all the nodes
concerned you must coordinate the IP addresses with your network administrator or
provider.
This example basically creates two TCP/IP domains: 244.1 and 244.2 Each domain can
have multiple nodes. Node B serves as the gateway between the two domains. If you
were to set up additional gateways to other domains, you would use the route
command on each node that you wished to enable communications to the new domain.
The route command merely tells TCP/IP which gateway or router to use for data
that is to be sent to a particular domain thus providing a more direct path, and
avoiding sending unnecessary traffic to other parts of the network.
The gateway provides access to other parts of a network that would not otherwise
be directly accessible. A router is dedicated to keeping track of routes to
various domains. On large networks your default gateway will often point to a
router thus negating the need to maintain route commands on each node.
For further discussion of domains and beginner info on the Internet you should
refer to ZEN
AMosaic(AM)
---------------------------------------
NOTE: for more info on Mosaic check out Amosaic-FAQ
 
Continue to:
amiga, pc, hardware, sotware, networking
![]() |
|
|