Internal network setup using a wireless network and repeater

[prowebmonkey]

Hi, we are in an office building and each suite is assigned a wireless internet connection. We have no control over the settings or security with regards to the devices we connect to it, so I wanted to setup and internal network.

I have bought a wireless repeater https://www.amazon.co.uk/gp/product/B0728HH8GZ/ and also a better router https://www.amazon.co.uk/gp/product/B00CEB53MS/ to actually connect our devices to and use the firewall features etc.

My understanding was I could connect the repeater to the existing wireless network using Wireless Repeater Mode. Then connect the router to the repeater with a cable using Lan to WAN to get the internet and setup an internal network.

However so far, anyway I have tried to connect the repeater, results in no internet when I connect to the repeater after the setup. The router did pickup settings from the repeater when on one configuration (WISP) but still no internet.

Does anyone have or know of a guide for doing this kind of thing as I have had to factory reset the repeater about 8 times now, so I am clearly doing it wrong.

Thanks,
David

 

[bill001g]

I would try to set the repeater up as a simple client-bridge device. To run in repeater mode you would need to use WDS and if that is not turned on in the main wifi it will not work correctly.

 

[prowebmonkey]

I would try to set the repeater up as a simple client-bridge device. To run in repeater mode you would need to use WDS and if that is not turned on in the main wifi it will not work correctly.

I thought that is what I was doing with the repeater. I was trying to connect that to the wireless network. And then plugging a cable into it for the second router. It just doesn't seem to work, I am wondering if it is an issue with the device or maybe the building network just doesn't allow it.

David

 

[bill001g]

The key difference generally is the need for WDS. Client-bridge can run without it WDS it acts a single machine much like a real client.

Sometime this is tricky to get configured because these repeater/extender devices have multiple ways to run. Some actually act as a router that takes its wifi from the wireless.

It you can connect a PC directly to the wireless without having to log into a web page or load any special drivers you should be able to get it to work. What you are basically doing is running a wireless nic (ie the repeater) connected to a linux machine (ie the router). If you had used a actual linux machine the main network really has little way to tell if the requests come from the linux machine itself or from another machine connected.

 

[prowebmonkey]

The key difference generally is the need for WDS. Client-bridge can run without it WDS it acts a single machine much like a real client.

Sometime this is tricky to get configured because these repeater/extender devices have multiple ways to run. Some actually act as a router that takes its wifi from the wireless.

It you can connect a PC directly to the wireless without having to log into a web page or load any special drivers you should be able to get it to work. What you are basically doing is running a wireless nic (ie the repeater) connected to a linux machine (ie the router). If you had used a actual linux machine the main network really has little way to tell if the requests come from the linux machine itself or from another machine connected.

Thanks for coming back to me. So basically I can connect my Mac and other laptops/phones to the Office Wifi without any issues. Also if I setup a mobile hotspot on my phone the repeater connects to that without any issues at all. But if I connect the repeater to the office Wifi and then login to it (I did this by connecting the repeater by wire to my PC). The Mac address of the Repeater section shows blank and the status just says Disconnect/Scanning...