Hi Matthias,
On Thu, 26 Apr 2007 at  8:54 +0200, Quade, Matthias wrote:
> Am Donnerstag, den 26.04.2007, 01:59 +0200 schrieb Waldemar Brodkorb:
> > Hi Matthias,
> > 
> > You subscribed to the diamand support for FreeWRT. You get a answer
> > under 1 hour. Please compare our consulting to other "companys" like
> > Dell or IBM.
> > 
> > On Thu, 26 Apr 2007 at  1:41 +0200, Quade, Matthias wrote:
> > > Hi folkes,
> > > 
> > > I've installed an image from the webbuilder (including the bridge-utils)
> > > and want to solve this problem:
> > > 
> > > WLAN AP                   |               |       Some office computers
> > > 192.168.2.1               |   Thick wall  |       with cable connection 
> > > dhcp-server               |               |       only
> > > with I-net access |               |
> > 
> > Where is the connection between office and AP? I can't see the cable
> > between "thick wall" and ap.
> 
> Hi Waldemar,
> thanks for your fast reply!
> There _is_ no cable connection... I've got an AP (German Telekom, some
> OEM-Stuff, but workes) in the Mainfloor and want to have the WRT in the
> basement to act as an Bridgte to the Telekom AP. From the Computers to
> the WRT are cables. Sorry for that, I didn't point you right.

Then you have two possibilities. Either use WDS or STA (Wireless
client support) in FreeWRT to connect both AP via Wireless. WDS is
not really a standard AFAIK, so it might be more problematic to
setup a WDS link between a FreeWRT and a non-FreeWRT box. Or even
between different models we have not a lot of experience.

So configure your FreeWRT box as WLAN client in sta mode.
 
> > /etc/init.d/S40network restart is a little bit buggy, because it
> > does not remove correctly the existing network configuration. 
> > 
> I recognized it and was also suprised about it.

Then either report a bug or sent a patch :} 
 
> > Please just do "fwcf commit" and reboot, so that the AP has the
> > correct network interfaces. For example eth1 shouldn't have an ip
> > address. 
> > 
> This was also that what I thougt. But if I do fwcf commit and commit
> stupid things... Does the "hard reset" still work under FreeWRT and
> resets the LAN-Ports to 192.168.1.1 ?

Failsafe is the preferred mode to fix the embedded device in such situations. 

bye
        Waldemar
 
-- 
don't open your wrt, free it
http://www.freewrt.org
_______________________________________________
freewrt-users mailing list
freewrt-users@freewrt.org
https://www.freewrt.org/lists/listinfo/freewrt-users

Reply via email to