[rbridge] Developing a hybrid router/bridge.
alper.yegin at samsung.com
Fri May 14 17:17:22 PDT 2004
Mobile node (the host) and the foreign agent (mobile node's first-hop
router) rely on parsing the L2 header on the IP packets sent between the
two, in order to learn the L2 address of the other, rather than using
If you are setting the L2 source address on the original L2 header to X,
this causes problem.
Am I missing something?
> -----Original Message-----
> From: rbridge-bounces at postel.org [mailto:rbridge-bounces at postel.org]
> Behalf Of Radia Perlman
> Sent: Friday, May 14, 2004 5:06 PM
> To: Developing a hybrid router/bridge.
> Subject: Re: [rbridge] Developing a hybrid router/bridge.
> I'm confused. I don't see what that text from mobileIP has to do with
> this proposal.
> I think my proposal has nothing to do with ARP. I'm just proposing
> something that
> would make it impossible for an IP packet that had been forwarded
> the campus
> by one RBridge to be accidentally re-sent over the campus by another
> one. I was
> marking a data packet in a way that would be (hopefully) ignored by
> IP nodes,
> both v4 and v6, and IP routers as well.
> The suggestion is that a packet that has been handled by an RBridge on
> this virtual subnet
> have a dummy layer 2 source address. Other RBridges, would notice the
> layer 2
> source address and not ever forward such a packet across the same
> virtual subnet.
> I thought it would work, and I asked Erik Nordmark whether in all
> IP nodes
> ignore the layer 2 source address on received packets and he said yes.
> I could imagine uses of the layer 2 source address. An obvious
> use for it is
> to refresh an ARP cache. DECnet certainly did that sort of thing. It's
> not inconceivable
> that some IP implementation might do that even though it's not
> in any spec.
> But from asking around, nobody has told of a case in which this would
> a problem.
> So hopefully, Alper, you just misunderstood my suggestion.
> Alper Yegin wrote:
> >>How about having a specific, constant MAC address, say "X", that
> >>"transmitted by an RBridge".
> >>When an RBridge decapsulates an IP packet onto the destination LAN,
> >>can set the source
> >>address in the layer 2 header to be X. The rule will be that an
> >>is not allowed to forward a packet that has layer 2 source
> >This would break RFC3344:
> > While the mobile node is away from home, it MUST NOT transmit any
> > broadcast ARP Request or ARP Reply messages. Finally, while the
> > mobile node is away from home, it MUST NOT reply to ARP Requests
> > which the target IP address is its own home address, unless the
> > Request is unicast by a foreign agent with which the mobile node
> > attempting to register or a foreign agent with which the mobile
> > has an unexpired registration. In the latter case, the mobile
> > MUST use a unicast ARP Reply to respond to the foreign agent.
> > that if the mobile node is using a co-located care-of address and
> > receives an ARP Request in which the target IP address is this
> > of address, then the mobile node SHOULD reply to this ARP Request.
> > Note also that, when transmitting a Registration Request on a
> > network, a mobile node may discover the link-layer address of a
> > foreign agent by storing the address as it is received from the
> > Advertisement from that foreign agent, but not by transmitting a
> > broadcast ARP Request message.
> >But I'm not sure who deserves the blame :)
> >rbridge mailing list
> >rbridge at postel.org
> rbridge mailing list
> rbridge at postel.org
More information about the rbridge