Ok i understand, but if i know right rdomains are not only separated in L3 but in L2 too.
See this paper: http://www.openbsd.org/papers/f2k9-vrf/ It is possible to use overlapped IP network and it has independent ARP table. In pf or route? documenation i cant find (for the present) any section about routing packet between rdomains. But in my opinion your idea is useful among other things interconnect two rdomain in L2 . Some imaginary example commands (inspired from freebsd epair): ifconfig vwire create it creates two sub interface vwire0a and vwire0b (create a virtual crossover cable) and after that ifconfig vwire0a rdomain 1 ifconfig vwire0b rdomain 2 ifconfig vwire0a 1.1.1.1/24 up ifconfig vwire0b 1.1.1.2/24 up and ping -V1 1.1.1.2 works Sorry for the noise thx Csszep 2009/12/25 Rolf Sommerhalder <rolf.sommerhal...@alumni.ethz.ch>: > On Fri, Dec 25, 2009 at 2:37 PM, Csaba Szip <css...@gmail.com> wrote: >> OpenBSD has some network virtualization (not yet fully ready?) stuff >> in the tree called rdomain. I reading the current documentation, but i >> dont find any solution to interconnect two rdomain. I create two >> vether interface in different rdomain and switched them, but it doesnt >> work. So that would be nice if this vwire (or similar) device will be >> provided and coexist with rdomain. > > Hello Csszep, what you need to "glue" rdomains together is _routing_ > (combined eventually with some firewalling by pf) which operates at > network layer-3 level, based on IP addresses etc. in IP packet > headers. > > The purpose of vwire however is to establish a connection between two > bridges which may have ether(4), other pseudo-device such as tunX, and > real physical interfaces as members. Thus vwire "glues" together two > bridges which become like a large virtual switch with the member > interfaces being switch ports. Note that the bridge and the > interconnecting vwire operate at link layer-2 exclusively, e.g. we > consider _switching_ which looks only at MAC addresses of Ethernet > frames. > > Thus, vwire will not even (need to) be aware of the protocols used by > the payload which these switched Ethernet frames encapsulate. vwire > will essentially just be bi-directional pipes which transport bits > between two bridges. In order to make things interesting, these pipes > might introduce some distortion into those bit streams, like loosing > occasionally some bits, delay them, etc. > > vwire will be a link layer-2 device, much like a UTP cables with some > "bumps" in it. It will not know anything about IP nor routing network > layer-3. > > Regards, > Rolf
