On 1/21/07, stan <[EMAIL PROTECTED]> 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
> >
> > 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'.
>
> > ifconfig snippet follows
>
> 'brconfig' will tell you more than ifconfig. It defaults to learning anyway.
>
Maybe I'm confused here. Let me explain what I am trying to do. I have to
locations at location A I have a subnet of 192.168.1.0/24 at location B I
have a subnet of 192.168.20/24. Presently I am able to ping from
192.168.1.100 to 192.168.2.100, thus the IP layer is working.
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?
You might be confused. Access to Windows shares uses SMB (or more
recently CIFS) protcols coupled with NetBIOS name query & RPC calls,
all of which are routable. Otherwise you wouldn't be able to connect
to a file server on a different subnet than your client (common in all
networks except for the smallest.)
At any rate, all of the above is most certainly IP-based.
DS
