morris@WINDOM.UCAR.EDU (Don Morris) (04/22/89)
Suppose I want to put a Proten box between, amoung other things, two subnets on the same net (the subnet is defined by the 3rd byte): 128.1.1 | Proteon | -------------------------------- 128.1.2 | | | bridge bridge bridge | | | 128.1.3 128.1.4 128.1.5 Is it possible to configure the Proteon to route traffic to subnets 3, 4, and 5 out the 128.1.2 interface? Thanks for any help on this. -- Don --
jnc@proteon.com (J. Noel Chiappa) (04/22/89)
Hi, didn't you get a reply to this when you asked Proteon Customer Service? Noel
swb@DAINICHI.TN.CORNELL.EDU (Scott Brim) (04/22/89)
Don, I'm not sure exactly what the question is. P4x00s can have
multiple IP addresses per interface, so yours will route to
128.1.{2,3,4,5} all on one interface (and even forward packets for
dumb hosts). Is that all you're after?
Scottmac@proteon.com (Michael A. Curtis) (04/22/89)
Don,
Try just adding interfaces 128.1.3 [345] to the ethernet in
question.
Mike C.mead@UHURA.CC.ROCHESTER.EDU (Ted Mead) (04/24/89)
Mike, What happens, in terms of routing updates and other broadcast traffic, when an interface has multiple subnet address and the network is not completely subnetted as is the case with bridge connected "subnets"? Will the routing updates be sent, redundantly to each bridge connected network? If the hosts were actually configured to understand subnets (3 bytes netmask), then I guess you would need the redundant routing updates - one for each subnet. If the hosts were not subnetted and the router interfaces was configured with a local-wire broadcast, would the hosts have to process duplicate routing updates from each interface. In other words, does each "virtual" address send out routing updates? I apologize if the questions aren't completely clear. It is the result of a lack of understanding, on my part, on how the router acts when an interface is configured with multiple IP addresses on a non-subnetted bridge connected network. Another thing I don't understand is why I have to use a local wire broadcast for each of these virtual interfaces when the hosts on the bridge connected segments are not subnetted. In summary, 1) How do you configure the router when the hosts on the bridge connected segments are not configured to understand subnets? 2) How do you configure the router when the hosts on the bridge connecte segments are configued to understand subnets? 3) What form of the broadcast address do you use in both cases (local or network wire)? 4) Will redundant routing updates be sent out from each interface? Thanks, Ted P.S. Glad your back!
tvm@proteon.com (Tom Miceli) (04/24/89)
Don, You may route traffic on the "number 2" subnet interface by assigning mulitiple IP addresses to that interface on the P4200 (i.e. that physical interface can have addresses 128.1.2.x, 128.1.3.x and 128.1.4.x). This way the router will forward traffic on those subnets. Also, remember to add these subnets in IP Config. Tom Miceli
tvm@proteon.com (Tom Miceli) (04/25/89)
Subject: Config. Question We have supported multiple IP addresses per interface since the first introduction of the p4200 product. This is done using the "IP CONFIG> add address" command. You can also select which ones will have RIP packets sent out them, whether to send net and/or subnet routes, etc. Each address even has it's own configuration of broadcast address. There is enormous flexibility in configuring multiple addresses. In particular, you would only want to send network RIP routes out the side of the router on 128.1.[2,3,4,5], since these machines presumably do not know that they are subnetted. Presumably this would be sent from the 128.1.1.x address. You would also want to enable proxy ARP, since the hosts out on 128.1.[3,4,5] don't know about the subnetting. (In older versions of the software, the first IP address was the "primary" address. This changed in Release 7.4 to allow full configuration, back in the fall of 1987.)
medin@NSIPO.NASA.GOV ("Milo S. Medin", NASA ARC NSI Project Office) (04/25/89)
Tom, the current release doesn't not support having multiple IP addresses per subnet however. That is, if you want to have 3 seperate IP addresses per subnet, and not 3 subnet interfaces per interface, you can't do it with the current release. I think this may be what Don was asking about... Please correct me if I'm wrong... Thanks, Milo
tvm@proteon.com (Tom Miceli) (04/25/89)
Milo, Below is a "reprint" of the original message that Don sent. I interpret the question as assigning DIFFERENT subnet addresses to the same physical interface, which is possible. If he means assigning the SAME subnet number to different interfaces then that can't be done (according to the spec). i.e. you can't have 128.1.1.x on one interface and 128.1.1.y on another. Maybe Don can clarify. TVM ------------------------------------------------------------------------------- Subject: Config. Question Suppose I want to put a Proten box between, amoung other things, two subnets on the same net (the subnet is defined by the 3rd byte): 128.1.1 | Proteon | -------------------------------- 128.1.2 | | | bridge bridge bridge | | | 128.1.3 128.1.4 128.1.5 Is it possible to configure the Proteon to route traffic to subnets 3, 4, and 5 out the 128.1.2 interface? Thanks for any help on this. -- Don --
morris@WINDOM.UCAR.EDU (Don Morris) (04/26/89)
Tom is correct. I want to assign different subnet numbers to the same interface. It appears that Proteon can handle this situation from the many replies I have received (many thanks to you who have responded). -- Don --