(E-Mail Removed) (Dodger) wrote news:d3d53d9d.0404301331.3a03709
@posting.google.com:
> Ping between the Ws works in this setup, but seemingly no tcp traffic
> (no Windows network browsing, no ftp from W2 to W1, for example.
Windows network browsing is a bit special. It uses broadcasting and so is
naturaly limited to each network. To "windowsaly" browse between two
network you may use different methods (a WINS server, a domain browser, a
samba server to send browse list to the other network).
No FTP is not a good sign. Could you give more information :
- ifconfig -a output
- netstat -rn output
- iptables -L output
> Again, access from all Ws to the net works fine, all Ws can ping GW
> and have access to a Samba share on GW as well. However, with the
> bridge up, there now is NO traffic at all between the left and the
> right side of the network - not even ping between W1 and W2 works.
> How can I get this to work? I was told that creating a bridge was the
> best way to get rid of the subnet separation and enable traffic
> between the eth1 and wlan0. What am I doing wrong?
Well, a bridge means that the two networks are the same network. It as if
there is no more GW between the W1 and W2. The GW is becoming
"invisible".
And so, you have to map your Ws host address/mask in the same network,
that is the bridge network. For managemebt purpose the "invisible" has
often an ip (it's a visible invisible bridge).
The advantage of the bride is that any broadcast packet is propagate on
the both "network" (there is only 1 tcp/ip network) and so Windows
browsing is fully supporting. However it means that you GW will
retransmeet many packet.
Regards