I don't see why it's not going to work in your case.
The only thing which is not going to work are protocols apart from IP. The most common problem is DHCP, which is solved by installing DHCP relay.
[EMAIL PROTECTED] wrote:
Does this mean it won't work at all right now? What about using Bering's Bridge stuff?
--Pat
On Mon, 16 Dec 2002, Marty Buchaus wrote:
I've brought this up before to Vlad, I'm not sure if he's working on a solution (if one is possible) to bridge layer 2 info with parpbridge. This is by the way, why you cannont get ip info. Since you need to have an ip for parpbridge to add the route via iproute2.Marty Buchaus CTO Dabuke Internet Services (ASI / BigSky) RedHatCertifiedEngineer # 807101943103186 ICQ - 10579998 AIM - snuffychi-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED]
Sent: Sunday, December 15, 2002 8:07 PM
To: [EMAIL PROTECTED]
Subject: [leaf-user] WISP and Bridging
Hey all,
I'm not sure if what I'm doing is going to work the way I envision it.
I have an Off The Shelf AP, a WISP box, several wireless connection and several wired connections
Here's my proposed network
Internet -- AP ~~~~~ Wireless ~~~~~ WISP -- Wired
|
Wired
I have the WISP box joining the SSID as a Managed Node, and it can ping the AP. However, any wired clients behind the WISP can't get an IP address from the AP.
I'm not sure if I've configured the Bridging the right way or if my whole idea is hosed.
Basically, I want the two wired segments and wireless segment to be one whole segment
Interfaces wlan0 and eth0 are loading properly.
Here's my if.config file.
DEFAULT_GW="192.168.2.1"
IFACES="wlan0 eth0"
eth0_IPADDR="192.168.0.4/24"
wlan0_IPADDR="192.168.2.3/24"
ENABLE_PARP_BRIDGING="yes"
Thanks for any help.
--Pat
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/
--------------------------------------------------------------
----------
leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
--
Best Regards,
Vladimir
Systems Engineer (RHCE)
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
