On 2007/01/21 19:01, stan wrote: > On Sun, Jan 21, 2007 at 11:16:26PM +0000, Stuart Henderson wrote: > > > ifconfig bridge0 create > > > ifconfig gif0 create > > > ifconfig gif0 tunnel x.x.176.33 x.x.176.37 > > > ifconfig gif0 up > > > brconfig bridge0 up
that all looks ok. > > > But when I try to do "brconfig learn bridge0" I get a message about the > > > interface not being configured. Looks like it is though: > > > > If you're typing exactly that, you are trying to use the command > > 'bridge0' on the bridge interface called 'learn'. i.e. 'brconfig learn bridge0' is incorrect. perhaps you mean 'brconfig bridge0 learn <some_interface>' but that's unnecessary, 'learn' is the default. > > > ifconfig snippet follows > > > > 'brconfig' will tell you more than ifconfig. It defaults to learning anyway. ifconfig only gives you basic interface information. brconfig (maybe 'brconfig -a' depending on how recent your OS is) gives you more information about the bridge (which MAC addresses are seen on each side etc). > In addition to this I need for the Windows machines to be able to mount > shares. If I understand that part of it correctly, it's a non routable (sub > IP) protocol. So I need for the Non IP Ethernet frames to be bridged > between the 2 locations , right? generally it's all TCP/IP with Windows file shares. the main problem is with network browsing, which is often easier to configure with a flat L2 network rather than a routed network, as you have setup with the gif tunnel and bridging. consider the ipsec'd gif bridge as some type of ethernet connection between the sites. (if the term 'bridge' is unfamiliar, it basically just means a 2-port switch). machines on both sides of the bridge should be configured with IP addresses in the *same* subnet, and with the bridge in place you should be able to connect between them. if this is how you've set things up and it isn't working, you'll need to describe the setup in more detail and what things aren't working. (alternatively, it may be an option to remove the bridge and just use a routed setup, if network browsing is unimportant it's easy enough to either mount by IP address or by name with an lmhosts entry; cross- subnet windows file sharing is a bit far off topic here, you'll find some things about it in samba docs but it's a bit fiddly)
