Marc Chamberlin wrote:
So, my feeling about the man page for ifcfg-bridge is that it is very abbreviated and requires a deep understanding of the openSuSE network setup model which I don't have. Worse, the man page for ifcfg-bridge refers to a non-existent website - http://linux-net.osdl.org/index.php.Bridge for further information, and there is nothing that I can find in the openSuSE documentation wiki's that describe how to set up openvpn either. How about this:
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-security/cha.se...
I don't think I used this when I set up my openvpn some six years ago, but that document appears to be quite comprehensive. Thanks Pers for your reply, but no, I have to disagree, this document is not comprehensive. I have read this document and it does NOT describe how to set up a bridged interface at all. It simply assumes you have
On 11/26/2012 11:19 PM, Per Jessen wrote: these interfaces already set up, there is not a single line describing how to configure the ifcfg files for tun, tap, or br interfaces either manually or through YaST.
Additionally, using YaST to set up my bridge interface - br0 - has brought up a new bit of confusion. If I check my eth1 interface as being one of the devices that I want bridge, I get a popup error telling me "At least one selected device is already configured. Adapt the configuration for bridge (IP address 0.0.0.0/32)?" and I have no option but to let it do so. Right.
And when I do, the IP address I had and want statically assigned to eth1 (in my case 192.168.10.100) gets removed and replaced with 0.0.0.0/32. You have to assign your static address to the bridge interface instead.
OK, I can accept this and thanks for the info. But my confusion remains, how does the bridge interface (br0) KNOW about the connection between my tap0 and eth1 interfaces. Setting up the tap0 interface, via YaST, seems to be straightforward (though there is nothing to specify an association between it an an ethernet (eth) or bridged device nor did I expect there to be), but my experiments with setting up the bridge, using YaST, do not enlighten me. If I select both interfaces, tap0 and eth1, as the devices to be bridged, which YaST seems to allow in its GUI, it does NOT set the BRIDGE_PORTS variable, in the ifcfg-br0 configuration file, to both ports/devices. (ya gotta love all this naming inconsistencies!) It ONLY sets it to tap0 and if I bring the YaST network card setup back up and edit the br0 interface it indeed ONLY shows the tap0 device as being bridged, despite the fact that I had originally selected both the tap0 and eth1 devices for bridging. In other words, from examples I have seen about bridge interfaces (not related to openvpn usage), and from what YaST is doing, it appears that the bridge interface can only know about one device to bridge. (That doesn't make a lot of intuitive sense to me, bridging something seems to mean, at least to me, that I am connecting two things together! In this case a tap interface and an eth interface) So if I can only set one interface) as the device to be bridge, how will openvpn KNOW to use what tap/bridge/eth interface combo, (since I can give them any name I like, and worse what if there are multiple ones) to use? In other words, how is the tap interface to be correlated to which bridged interface and to which ethernet (ethx) interface? The openvpn startup scripts, supplied by the openvpn package, make this all explicit, but Lars is telling me that these are no longer used in openSuSE. I don't have the code behind YaST to study, (nor should that be necessary and probably would not help either) and without a description of the openSuSE model on how to configure the ifcfg files, I am lost... SO either I am still missing something (documentation elsewhere?), or perhaps there is a bug in YaST and it is not setting up a bridge interface properly? Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org