Posted: Fri May 17, 2019 18:58 Post subject: Private network in apartment building
Hi all,
I've been using dd-wrt for some time now on my own private internet connections. However, I'm moving to a building that has a a main router and a switch on every floor. I would really like my own wired and wifi network to have more control over my devices. This feels like a challenge and I could use some tips on where to start.
It is set up and works like this:
( | and - are wired connections)
Code:
Main Router (192.168.1.xxx / 255.255.255.0)
|
|
1st floor Switch
|
|
2nd floor Switch
|
|
3rd floor Switch----computer (gets IP by DHCP from main router)
|
|
4th floor Switch
So I would like to create my own private network (subnet ?) behind the main router and have control IP addresses etc.
I'm kinda lost on which mode to use. I have a wired connection between the primary and secondary (DD-WRT) router and I would like private wired and wifi connections on the secondary router.
Important note: I don't have access to the primary router
Could someone give me a hint on this ?
Thanks in advance !
The owner insisted that I use an access point like this:
He was talking about security concerns. Saying that when using some other setup a whole floor could be blocked.
Could he be talking about something like this ?:
Quote:
As an example, some colleges still allow students to have their own wireless access points (WAPs). They require that the WAPs not hand out private IP addresses (like routers with DHCP/NAT) because it makes it difficult to track down which client is causing problems (eg. virus infections, worms, etc.)
And are these assumptions correct when using egc's solution?
- My secondary router gets a WAN IP 192.168.1.xxx
- I can use DCHP to give my devices 192.168.55.xxx IP's
- All traffic to the primary router seems to be coming from 192.168.1.xxx
- Computers on the primary router (192.168.1.xxx) cannot see/acces my devices behind my secondary router (192.168.55.xxx)
Joined: 18 Mar 2014 Posts: 12837 Location: Netherlands
Posted: Sat May 18, 2019 18:27 Post subject:
TheGuyCalledBob wrote:
Really ? Ok Thnx/dankjewel!
I do have some additional questions though.
And are these assumptions correct when using egc's solution?
- My secondary router gets a WAN IP 192.168.1.xxx
- I can use DCHP to give my devices 192.168.55.xxx IP's
- All traffic to the primary router seems to be coming from 192.168.1.xxx
- Computers on the primary router (192.168.1.xxx) cannot see/acces my devices behind my secondary router (192.168.55.xxx)
Thanks in advance
Spot on, so make sure you set a strong WPA2 /AES password, because anybody who knows or acquires it use your IP address and you will be blamed.
Joined: 04 Aug 2018 Posts: 1446 Location: Appalachian mountains, USA
Posted: Sat May 18, 2019 18:43 Post subject:
Looks to me like you are good, but there are some here (e.g. egc) who know way better than I.
I think the big issue is when you have two DHCP servers on two devices both handing out addresses in the same IP space like 192.168.1.X. You've worked around that by having your router work with the space 192.168.55.Y, so you should be good. I've done the same with several setups with absolutely no problems. _________________ 2x Netgear XR500 and 3x Linksys WRT1900ACSv2 on 53544: VLANs, VAPs, NAS, station mode, OpenVPN client (AirVPN), wireguard server (AirVPN port forward) and clients (AzireVPN, AirVPN, private), 3 DNSCrypt providers via VPN.