A/UX 2.0.1: Internet Forwarder Bug


I'm trying to get an Internet forwarder running under A/UX 2.0.1. I have configured several systems the same way, with no luck. I've tried using a Macintosh IIfx, a Macintosh IIci and a Macintosh IIx, each with 2 rev K EtherTalk cards. The other systems on the networks include a Macintosh IIx on each network and a Decstation 2100 and a MacBlitz card on the 192.33.20 network.

Here are the procedures I've been using in my attempts to bring up the forwarder:

1) Install the cards into the system.

2) Do a newconfig nfs and answer "n" to the YP client prompt.

3) Configure IP & broadcast addresses & netmasks for each card
so /etc/NETADDRS file look like:

0 192.33.20.1 192.33.20.255 255.255.255.0
1 134.69.50.1 134.69.50.255 255.255.255.0

4) Set up my /etc/hosts file to include hosts on both sides of the
router as follows:

0x7F.0x00.0x00.0x01 loop lo loo localhost
192.33.20.1 jabberwock #ae0 host reference
134.69.50.1 jabberwock1 #ae1 host reference
192.33.20.2 manticore
134.69.50.4 fredsys
192.33.20.200 dextra # decstation 2100
192.33.20.201 blitzoid # macblitz 50/8

5) Restart the system and verify that the following daemons
are running:

/etc/portmap
/etc/inted
/etc/in.routed
/etc/nfsd 4 (4 of these)
/etc/biod 4 (4 of these)
/etc/rpc.lockd
/etc/rpc.statd

6) From system "manticore", which has an Internet address of
192.33.20.2, a broadcast address of 192.33.20.255 and a netmask of
255.255.255.0, I can ping jabberwock successfully on both sides
(192.33.20.1 and 134.69.50.1). Additionally, I can rlogin to both sides
of jabberwock (the /etc/hosts file contains EXACTLY the same info as
jabberwock's) using "rlogin jabberwock" and "rlogin jabberwock1".

7) From system "fredsys", that has an Internet address of 134.69.50.4,
a broadcast address of 134.69.50.255, and a netmask of 255.255.255.0, I
can access both sides of jabberwock the same as I could from manticore.
Again, the /etc/hosts file is identical to jabberwock's.

8) Neither ping nor Telnet nor rlogin is successful from manticore to
?redsys or vice versa. The /etc/hosts files are the same on all three
?f these machines. All of the addresses match up as they should.

9) Verify the cables and terminations; check the interfaces
with an ifconfig ae0 on all three machines and an ifconfig ae1 on
jabberwock. All addresses and interfaces show up as they should, but
to no avail.

10) At this point, I can't Telnet, ftp, ping or rlogin to fredsys from
any system on the 192.33.20 network except jabberwock.

11) From jabberwock, I can ping all of the other systems on both nets.
I can rlogin, etc. all of the other systems. I just can't cross the
barrier from one net to the other.

Any suggestions?


With the above configuration, we have been able to reproduce your problem. On an A/UX 2.0.1 Internet forwarder/router, the host "manticore" on network 192.33.20 CAN'T talk to the host "fredsys" on network 134.69 via A/UX 2.0.1 Internet forwarder host "jabberwock".

With the same configuration, but with the Internet forwarder/router (jabberwock) running A/UX 2.0, the problem goes away.  Hosts ("manticore" and "fredsys" in this case for example) on different networks via A/UX 2.0 router CAN talk to each other.
Published Date: Feb 18, 2012