I hope you don't mind very naiive questions about bridging, but this
is all very new to me and I'm wondering if I am heading in a wrong
direction for what I want to do.
We have a 486 machine on our network which currently hosts our
intranet server (khttpd) and is also our printer server. I have
recently added an adhoc wireless network interface and I'd like a
transparent binding of the two networks to allow unrestricted network
traffic in both directions (using IP Forwarding would restrict traffic
back out to the wireless nodes).
Is this possible with the bridging tools?
My reading of the Bridging HOWTO suggests that the bridge machine
vanishes from the network, ie, I'd no longer have any access to that
machine as an intranet server or printer server, but then again,
assigning an IP to the bridge suggests that it might work.
I've read the Network and Ethernet HOWTOs, but have to confess that I
really don't understand the fine details of networking. What has me
especially confused is setting all interface net addrs to 0, and then
(optionally) giving the bridge a new IP. Where I'm not clear is on
the choice of IP for that bridge.
1) is the bridge IP on a new subnet? ie, if I am bridging
192.168.70.0 and 192.168.10.0, does that mean the bridge
itself should not be either 10 or 70?
My guess is that it might be possible to have the bridge on
the ethernet subnet, on the 70.0 network. Would this mean it
would be accessible to the ethernet side (for HTTP, ssh &c)?
If this is true, then how do the wireless nodes see this IP?
(default gateway?)
if the bridge is on a new subnet, how do I set the routing
tables on other machines to recognize this as the gateway to
the other network?
do I perhaps misunderstand "subnet" and need to assign an IP
within 70.0 and then assign the wireless network as some IP
range under the 70.0 network?
2) if my wireless beacon is now this new IP, can I still do
dhcrelay from the server across to the wireless network?
3) would our intranet be accessible from both sides? If
Do _all_ other stations in the ethernet network will need
routing tables to include this new subnet as the gateway to
the other (ie wireless) network and vice versa?
I follow the Bridging HOWTO so far as running brctl to create bridges,
but I don't think I really understand how the bridge is used.
For example, if I route through the gateway for the alternate subnet,
does this mean I can access any of those machines by their respective
IP?
If I am on the wireless network and request an internet address, will
the packets follow the default route to the bridge and from there
follow the default route to our internet gateway on the 70.0 subnet?
If you know any good references for rank beginner tutorials, please
send them along.
Again, my apologies for the naiive questions; if you have an
opportunity to reply, your help will be greatly appreciated.
--
Gary Lawrence Murphy <[EMAIL PROTECTED]> TeleDynamics Communications Inc
Business Innovations Through Open Source Systems: http://www.teledyn.com
"Computers are useless. They can only give you answers."(Pablo Picasso)
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge
