sbc@wucs1.wustl.edu (Steve B Cousins) (11/04/88)
Here's a problem that's driving me crazy (I'm about to throw cap and kip out the window). Any comments, criticisms, or even flames are welcome at this point. The ip numbers that I put in my /etc/atalkatab file get subtly modified when they are used by the kbox to broadcast. For example, if I put 128.252.118.0 in atalkatab, our ethernet monitor says that the kbox is trying to broadcast to 128.253.117.0. Is this a known bug? Some background: We have a very simple setup: one kbox-3, two unix hosts, and three mac-II's. We're a class B ethernet site, and the only relevant ip numbers are 128.252.118.3 -- erl -- a microvax II 128.252.122.25 -- ibc3 -- a sun 4 128.252.116.1 -- the kbox The mac-II's have statically assigned ip addresses 128.252.116.2 (and .3 and .4). We have NCSA Telnet 2.2 working, papif working, and would be very happy if we could just get aufs working. I posted once before about my problems getting aufs working, and the general concensus was that I must have something wrong with a broadcast address. The setup files we're using are ibc3:/etc/atalk.local # mynet mynode myzone 55.122 25 MIG # bridgenet bridgenode bridgeIP 55.116 1 128.252.116.1 erl:/etc/atalk.local # mynet mynode myzone 55.118 3 MIG # bridgenet bridgenode bridgeIP 55.116 1 128.252.116.1 erl:/etc/atalkatab (instructions deleted) 55.118 N2 128.252.118.0 MIG #MIR, appletalk-in-IP 55.122 N2 128.252.122.0 MIG #IBC, appletalk-in-IP 55.116 N2 128.252.116.0 MIG #MIG, appletalk-in-IP 56.1 KC 128.252.116.1 MIG #MIG, localtalk I128.252.116.255 I128.252.123.12 #ipbroad ipname I128.252.122.25 I128.252.122.25 #ipdebug ipfile L0 L0 L0 L0 S0 S200 #ipother atnetet ddprangestart LX0 S3 S3 #flags ipstatic ipdynamic S56.1 S55.116 #atneta atnete As you can see, we use the address of the subnet that the kbox is on as the broadcast (ipbroad) destination. From what I can tell, on a broadcast, the kbox gets the broadcast and should redirect it to both the MIR subnet and the IBC subnet (is this how broadcast should work?). What comes out of the kbox, according to the net monitor, are packets destined for 128.253.117.255 (not 128.252.118.255) and for 128.253.121.255 (not 128.252.122.255). This is verified, in that if I remove either line from the atalkatab and reboot the kbox, broadcasts only get repeated to the (corrupted) address corresponding to the one left in the table. Am I doing something wrong? Should this be this difficult? Any comments on the entries in the above tables are greatly appreciated. Thanks in advance. Steve Cousins sbc@wucs1.wustl.edu Research Associate 314-362-6968 (Not networking guy)