In my current network setup, I have a Cisco RVS4000 router that feeds into a 48 port ethernet switch and a Ubiquiti PicoStation M2 wireless access point.
I want the Cisco router to act as a DHCP server for the whole network. I am unsure how I should setup the Ubiquiti PicoStation M2...
The 2 options which seem relevant are Network Mode and Wireless Mode.
The options for Network Mode are:
Bridge
Router
SOHO Router
The options for Wireless Mode are:
Station
Station WDS
Access Point
Access Point WDS
From what I've read and what I want... I'd go for Bridge and Access Point?
Yes, Bridge and Access Point are the correct settings for extending your existing network onto wireless "media". the other options would create a second network.
The easiest way:
Connection in this order: Router -> Switch -> PicoStation
Set the PicoStation in "Access Point" Mode.
If you do it this way the clients that connect the Access Point (PicoStation) will retrieve an DHCP Adresse from the Router. The wireless clients are in the same subnet as the clients connected to the switch.
If you want to divide the "normal" clients from the wireless clients you set the PicoStation to Router Mode.
Access Point transmission media wireless, antena.
Bridge if transmission media like cable
the recommended option is router if you set DHCP
but in wireless i'm not sure about best option
Related
so the setup I've got:
Main Router which receives the internet connection and is my primary WIFI network: 192.168.1.0/24
Secondary Router which I've connected via the following method to create a separate LAN: 10.3.3.0/24. Main Router's LAN port --> Secondary Router's WAN port.
I've got this setup fine and can get internet from the Secondary Router's LAN, no problem.
My question is: Is it normal behavior to be able to ping a device connected to the main router from the secondary router?
I would like to isolate devices on each LAN so that devices connected to the separate LAN's can't communicate and wondering if I'm able to achieve this using 2 consumer grade routers?
Cheers!
This is normal behavior because the secondary router knows that IPs in the 192.168.1.0/24 subnet should be forwarded to its WAN port, so it can access hosts connected to that network.
Sadly, you usually can't create 2 segregated subnets with 2 consumer-grade routers, as these only have 2 network interfaces (one for WAN and one for the built-in switch).
I also do not recommend doing this, as double NAT can have unexpected side effects. If you really want to separate devices on your local network, looking into VLANs is a better way. You can use your existing router but will need a compatible switch.
If your routers support vlan management you should use separate vlans for both subnets. Otherwise you cant devide your networks.
I am building a home office network.
Due to physical limitation of my environment, I have setup my Wifi network under two routers in two different rooms.
DSL <------> Router 1 (Room 1) < ---- RJ45 192.168.1.105 --> Router 2 (Room 2)
Following is the current setting for bother Router
Router 1
IP: 192.168.1.1
DHCP Range: 192.168.1.0 - 192.168.1.255
Facilities connected:
DSL Wall point - Connected to internet (NBN).
Printer
Smart TV
Mobile
Other Desktop
Router 2
IP: 192.168.2.1
DHCP Range: 192.168.2.0 - 192.168.2.255
Facilities connected:
Laptop
Smart TV
Mobile
Gateway: 192.168.1.1
I can connect to internet from Router 2. However, I am not able to use Router 2 to access to the Smart TV and Printer that is connected to Router 1 .
Both routers does NOT support Access Point Mode. Therefore, they are connected Via RJ45 Ethernet.
Anyone have any idea on how to fix it?
Thanks in advance!
The problem is because that router uses NAT/NAPT for the lack of IP address and the protection of internal network. Normally, we use four types like Full Cone NAT, Restricted NAT, Port Restricted NAT and Symmetric NAT. They have different features, but they have a common feature: none of connection can be established from the outer side.
That means you can connect to outer side from inside, and then establish a connection, then the bidirection communication can work well. But if you firstly want to handshake from the outer side, it will fail.
So, here is something we called NAT traversal or NAT pounch hole to make some specifi internal IP/port can be connect from outside.
For your circumstances, the easiest way is to try upnp or nat-pmp if your router supports them. If not, it's relatively hard for you to simply connect them. Maybe you can try STUN/TURN/ICE, but I think you will not like them cause it's relatively hard.
Recently I have followed this link to setup a wireless router into an access point in my home.
Our current network components are as follows:
Main router (192.168.1.1): a Sercomm router configured by the ISP, with DHCP enabled for address 192.168.1.30 onwards.
AP router (192.168.1.2): a TP-Link WD8970 router on the bridge mode, with WDS turned on (on the same SSID, mode and channel as the main router) and DHCP turned off. However, this AP is configured to broadcast a different SSID to indicate a different storey.
Devices (182.168.1.xx): desktop or mobile clients that could connect to both SSIDs.
(click here for the topology image)
The problem is that:
Most of the time, devices connected to AP router's SSID is given 169.254.x.x IP addresses and could not reach the internet
Devices that is configured with a dynamic IP and connected to the main router's SSID could reach only devices connected to the main router's SSID
Devices that is configured with a static IP and connected to AP router's SSID could reach both routers (the main router at 192.168.1.1 and the AP router at 192.168.1.2, respectively)
DHCP packets are not forwarded from the main router (192.168.1.1) to the AP router (192.168.1.2), while other types of packets could flow through
How would you advice on configuring this home network differently, to make it more stable and usable?
I had the same issues in past days. I fixed checking the flag "DHCP RELAY". As soon as I checked it all went fine. All devices connected to the wireless router have received the IP address form DHCP server.
https://www.tp-link.com/us/support/faq/1630/ (the real configuration page on Archer D7 is slightly different form what stated in the link).
This was my network: I have a small usb powered 4G modem/router connected to internet. I wanted to share the internet with several devices located far from the 4G modem/router, so I decided to extend the coverage by means a TP-LINK Archer D7 ADSL modem/router used as Wifi access point. I connected the 4G modem to AP through WDS. The pc's and printers connected to Archer D7 (AP) were fine, security camera, smartphones etc.. no IP from DHCP. After the setting DHCP RELAY everything went fine.
Most of the time, devices connected to AP router's SSID is given 169.254.x.x IP addresses and could not reach the internet
This issue has to do with the WDS connection and poor connection from the AP to the main router. As a wifi expert (ok, expired CWNA) it's never a good idea to use WiFi extenders or WDS in your case. It increases interference, adds an extra hope, and rarely helps. While it's easy to think of these as a signal booster the wifi network protocol isn't setup for these types of connections. Only some commercial APs with parabolic antennas can truly benefit from wifi extenders.
Test with a cable connected from the main router to the AP and use the interfaces instead of wifi. It's possible you have DHCP issues with your wifi issue so first test with static IPs.
If this works then you should leave the cable in place. Understandably this isn't always possible so replacing your main router with a quality wifi router would be my 2nd choice. Sorry I don't know any good consumer grade APs but they are out there.
My ISP changed their network configuration and now my home setup is not working anymore. I had one Asus router which features like QoS and parental control, my physical network consists of UTP, powerlan and wifi.
In the new setup I'm required to run a new router (functionally crippled) to handle IPTV and telephone, but I would still like to run all my LAN traffic through my Asus for the additional functionality it provides. Not a problem I thought, until it turned out that the IPTV units are required to be connected directly to the new router. Which means all other systems using the powerlan (a.o. a Wifi Access Point) also bypass the Asus. Parental control is useless.
Is there anyway I can setup the new router to only function as a gateway, and let everything go though the Asus?
This setup did not work: internet <-> [extern IP] newrouter [192.168.2.254] <-> [192.168.2.253] Asus [192.168.2.1] <-> LAN [192.168.2.100-199]
The new router has 254 as its LAN IP
The Asus has a static WAN ip of 253, and its LAN IP to 1 (with 254 as the gateway).
DHCP hands out IP configs with 1 as the gateway
Theoretically this means any LAN device getting an IP will send to the Asus on IP 1, it forwards that via 253 to the new router at 254, which pushes it out to the internet.
But alas. Any suggestions if this can be made to work?
I cannot change the subnet on the new router, it is blocked to 255.255.255.0.
I do want wat to run switches everywhere to setup a VLAN.
You could just use a different subnet for your asus router.
e.g. use the 192.168.2.1 address for your asus router and configure DHCP to hand out IPs of that network (192.168.2.x). Then configure your new Router to have the IP 192.168.1.1.
Now add a static route from your asus router to your new router and the other way round. That way every device in the 192.168.2.x network has to go through your asus router.
Of course that does only work if you can configure routes on your new router.
I come from DD-WRT, but I'm really liking OpenWRT and will probably make the switch on all my routers. Anyway, I'm actually struggling to get a simple Client WiFi setup going. Here's what I'm going for:
Internet --- Foreign AP ---(wifi)--- My OpenWRT Router ---(ethernet switch)------ My OpenWRT LAN
I am able to connect to the Internet via the Foreign AP with my DD-WRT router (identical model and revision). I guess what's confusing me the most about OpenWRT is the eth0 interface, or perhaps a lack of understanding what DD-WRT does with eth0 in Client WiFi mode. As with a Linux desktop/laptop, I assume eth0 is the WAN port on a router, and in Client WiFi mode, is disabled and the routing table is rewritted so eth0 is replaced with wlan0/ath0. Is this correct?
Anyway, my steps on OpenWRT (with luci) are as follows: connect computer to router via ethernet, go to WiFi page and click Scan on wlan0 interface, choose the foreign AP, assign to default WAN firewall group, verify connection/IP Address with foreign AP. At this point I am able to ping 8.8.8.8, but I cannot reach webpages or connect with, say, Spotify.
I took a look at the answer here: Luci (openwrt) wifi bridge client - how to configure? which isn't exactly what I want (this one is for a bridged repeater/client), but it looks like I am doing everything correctly for just the client functionality. I shouldn't have to bridge any interfaces, right?
So all one should have to do is:
Go to interfaces and click Scan on one of the WiFi radios (2.4 or 5GHz)
Select the host WiFi network
And it just works. Why is that not written down anywhere on the Internet? Now it is, I suppose...
I am not able to get this to work with my 5GHz radio (which works for Client mode on DD-WRT), so it may be a kernel (or some other) issue with this particular build of OpenWRT.