2013-04-25 - Re: [GRASE-Hotspot] using a repeater
Header Data
From: “Pollington, Glyn” <Gl***n@hp.com>
Message Hash: a02fc3e93669a53d86a11f27515dd21909f8154bdaea8f17c691f336d809d9c8
Message ID: <99DF9CFBA2E2D947A37658DFB2AE72BB50E9090C@G4W3292.americas.hpqcorp.net>
Reply To: <!&!AAAAAAAAAAAYAAAAAAAAAMUqYtei4rhBqhEf7CX3SubigAAAEAAAAKTnjaST00JJoqwnipPbZm8BAAAAAA==@winkelmaenner.com>
UTC Datetime: 2013-04-25 08:40:43 UTC
Raw Date: Thu, 25 Apr 2013 15:40:43 +0000
Raw message
As far as I can tell I got an repeater to work OK - although the system will be going back on site tomorrow so that will prove it.
I was already using a TP Link access point, configured with a static address 10.1.0.253. So I bought another one just the same and followed the instructions for enabling a repeater - basically from the AP GUI it would scan the available networks then I just selected my existing hotspot. It could be done manually with just the SSID and the MAC of the AP. I did set the IP of the repeater to 10.1.0.252 just so I could connect it to the existing lan to manage in future.
Once working I tested it by taking the new ap to the garage and watched the signal strength go down on my iPad, then turned on the repeater and after 30 secs full signal strength and I could walk out of range of the original AP.
I think the trick is getting the hardware to play together which is why I used identical devices.
From: Lars Winkelmann [mailto:la***s@winkelmaenner.com]
Sent: 18 April 2013 09:17
To: 'GRASE Hotspot General Discussions'
Subject: Re: [GRASE-Hotspot] using a repeater
Hi Tim,
i use a WRT54GL with DD-WRT (AP mode, no encryption, IP: 10.1.0.2 / 255.255.255.0, GW+DNS 10.1.0.1, DHCP of and forward to 10.1.0.1) directly connected to squid.
Client WLAN connection to the WRT54GL works fine.
The repeater is an edimax EW-7438RPn (IP: 10.1.0.8 / 255.255.255.0, GW: 10.1.0.1)
http://www.edimax.us/html/english/products/EW-7438RPn.htm
the repeater is connected to wrt54gl and I got a dhcp lease from grase server.
I cannot ping the grase server and got timeout.
Lars
Von: Timothy White [mailto:ti***8@gmail.com]
Gesendet: Mittwoch, 17. April 2013 21:56
An: GRASE Hotspot
Betreff: Re: [GRASE-Hotspot] using a repeater
Hi Lars
Firstly, what equipment are you using?
Currently your access points and repeaters must only be doing Layer 2 routing. Layer 3 should be left to the hotspot. This means you shouldn't need DHCP relays, and your access points and repeaters IP's shouldn't be on the grase network (mostly for security, but also so they don't interfer with a client). They should be setup as "ethernet bridges", with all Layer 3 (IP addresses and such) handled by grase.
The best way to think of it, is they should be setup transparently like an ethernet switch. You don't know how many ethernet switches are between you and a server, just how many routers. If you can tell how many wireless devices are between you and the server (due to IP routing instead of Ethernet routing) then they are setup wrong.
Let us know what model equipment you have, and the settings in them.
Tim
On 15/04/2013 5:18 PM, "Lars Winkelmann" <la***s@winkelmaenner.com<mailto:la***s@winkelmaenner.com>> wrote:
I´m testing grase since some weeks and all works fine.
I´ve found some help for the squid logging problem in the mailing list but now i´ve a problem to connect a repeater.
This is my configuration:
Grase Server:
- IP 10.1.0.1 / 255.255.255.0
- DHCPStart 10
- DHCPend 250
WRT54GL AccessPoint-1
- IP 10.1.0.2 / 255.255.255.0
- GW / DNS: 10.1.0.1
- DHCP forwarder: 10.1.0.1
- no encryption
WRT54GL AccessPoint-2:
- IP 10.1.0.3 / 255.255.255.0
- GW / DNS: 10.1.0.1
- DHCP forwarder: 10.1.0.1
- no encryption
Now I want to connect a repeater to AccessPoint-2.
Repeater-1:
- 10.1.0.8 / 255.255.255.0
- GW: 10.1.0.1
- no encryption
Repeater-1 is connected to AccessPoint-2, dhcp works fine, but I can´t reach the grase server / internet
If I ping the grase server 10.1.0.1 I get a timeout. Ping to Accesspoint-1 and Accesspoint-2 works fine.
Please give me a hint what i´m doing wrong.
Thx
Lars
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Grase-hotspot mailing list
Gr***t@lists.sourceforge.net<mailto:Gr***t@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/grase-hotspot
Thread
-
Return to April 2013
- Return to “Drazen <dr***a@radez.hr>”
- Return to ““Pollington, Glyn” <Gl***n@hp.com>”
- Return to “Lars Winkelmann <la***s@winkelmaenner.com>”
-
Return to “Timothy White <ti***8@gmail.com>”
- 2013-04-15 (Mon, 15 Apr 2013 09:18:18 +0200) - [GRASE-Hotspot] using a repeater - Lars Winkelmann <la***s@winkelmaenner.com>
- 2013-04-15 (Mon, 15 Apr 2013 09:30:22 +0200) - Re: [GRASE-Hotspot] using a repeater - Drazen <dr***a@radez.hr>
- 2013-04-17 (Thu, 18 Apr 2013 05:55:34 +1000) - Re: [GRASE-Hotspot] using a repeater - Timothy White <ti***8@gmail.com>
- 2013-04-18 (Thu, 18 Apr 2013 10:16:50 +0200) - Re: [GRASE-Hotspot] using a repeater - Lars Winkelmann <la***s@winkelmaenner.com>
- 2013-04-25 (Thu, 25 Apr 2013 15:40:43 +0000) - Re: [GRASE-Hotspot] using a repeater - “Pollington, Glyn” <Gl***n@hp.com>
- 2013-04-18 (Thu, 18 Apr 2013 10:16:50 +0200) - Re: [GRASE-Hotspot] using a repeater - Lars Winkelmann <la***s@winkelmaenner.com>