querubin@uhccux.uhcc.Hawaii.Edu (Antonio Querubin) (07/25/90)
We're running the Fusion Network System package on a VAX with two ethernet boards and are attempting to make it act as a router between our subnet and the campus backbone. Can anyone experienced in setting up FNS help us out? One ethernet board has an IP address of 128.171.1.99 and attaches to the campus backbone. The other board is 128.171.11.2 and we have only one PC running KA9Q on that side of the net. (Other hosts on that side of the net are running DECnet/LAT). We want to pass packets through the VAX. Here's the contents of our net.db file: name:exists:state:route:hops:delay:maxpkt:options:comment veva0:1:nrc$veva0:[ETHER]AA0004009A60::2000::DEVICE=XQB0:DELQA-VAXS3600-2 veva0:1:nrc$veva0:[INET]128.171.1.99::2000::GWY: UHNET veva1:1:nrc$veva1:[ETHER]AA0004009A60::2000::DEVICE=XQA0:DELQA-VAXS3600-1 veva1:1:nrc$veva1:[INET]128.171.11.2::2000::GWY;SUBNET=255.255.255.0: Physics subnet veva0:1:nrc$veva0:[INET]->128.171.1.100::2000:::ZEUS IS THE ROUTER On our VAX we can ping both boards and any machine on either side of the VAX. We can even ping off-campus through our router 128.171.1.100. On our PC which has an IP address of 128.171.11.16 we can ping 128.171.11.2 but cannot ping 128.171.1.99 nor anything else on that side of the VAX. While I can force a route in KA9Q to the VAX via a 'route add', the VAX just gobbles up the packets and doesn't seem to do anything with them as far as we can tell. It seems that if FNS is smart enough to know which board to use to ping a particular address it ought to know how to pass packets it receives to the right side of the network. Are we missing something here and doing something wrong or is FNS just brain-dead when it comes to routing? We have the latest version of the FNS package. Any help would be appreciated. Thanks! Antonio Querubin, Jr. querubin@uhccux.uhcc.hawaii.edu antonio_querubin-manoa@uhplato (BITNET)
almquist@JESSICA.STANFORD.EDU ("Philip Almquist") (07/27/90)
Antonio, > It seems that if FNS is smart enough to know which board to use to ping a > particular address it ought to know how to pass packets it receives to the > right side of the network. Are we missing something here and doing something > wrong or is FNS just brain-dead when it comes to routing? I have never used the Fusion software, but I did observe that nothing in the command file you included looked like a command telling Fusion that it was permitted to act as a router. To quote from RFC-1122: The host software MUST NOT automatically move into gateway mode if the host has more than one interface, as the operator of the machine may neither want to provide that service nor be competent to do so. Philip