Hi,
I have a home gateway router (hex S) connected to a hap AC to provide wireless network. So far, I’ve been using the hap AC as a dhcp server with a different subnet from the hex S. The problem is, I need the wifi clients to be in the same network as all the other devices due to dlna, wireless printer, etc…
So, I came up with the idea of using the hap AC as a switch:
I removed the dhcp server
I removed the ip-pool addresses previously used by the dhcp server
I enrolled all ports on the bridge (including the wireless ports and the sfp port, which is the one connected to the hex S)
I created a dhcp relay directing all requests to the hex S
Well, it doesn’t work. I can’t get an ip address from the wireless ports, neither from the ethernet ports of the hap AC.
What am I missing?
Thanks.
I removed all filters and the nat masquerade. Tried it with and without the dhcp relay. Still can’t get an ip.
I notice the sfp port in the bridge tab was disabled…
It’s disabled in the bridge, like it wants to keep being a WAN. The connection to the main router keeps working. That’s how I can program the hap AC, since My computer is connected to the hex S through a switch in another room.
Edit: I thought maybe the sfp port “doesn’t like” to be bridged. I disconnected it and routed a cable from the hex S to the eth1 port. Guess who showed up disabled in the bridge…
Can’t see how could there be a loop. Anyway, no ports are disabled. It’s just that the port used as wan in the “quickset menu” pops out of the bridge. That kind of makes sense. But I try not to program anything in the quickset menu, hoping it will not disturb the programming on the webconfig or terminal. Last time I checked, it jumped from AP mode to WISP mode. The thing is, there is no mode in the quickset compatible with using this router as a switch. I’m getting the feeling it’s just not possible…
It’s tempting to always advice that, but the truth is, ROS is quite a complicated thing for those who see it for the first time, especially for “home” users.
So it is either quickset or “i’ll better go and buy something else” for them.
Don’t think it is wise to encourage people to go that road.
What if you don’t use it but you check on it, just to know what your programming is “doing”?
You find some red fields stating that you must write something. You find some working modes that you don’t even know or care about…
In my case you could also find that you lost your 5GHz wifi…
And since that there is no mode in quickset that allows not to nominate a port as WAN, and something will always be written on the “WAN field” and you find that whatever port is written in that field, it pops out of your bridge, you wander if it is really possible to program this thing to be used as a switch…
On my capacs, I use WISP AP mode I think thats what its called.
This is like a default quickset setup that gets one to the point of making minor changes to the config and the one is up and running.
No firewall rules to setup etc.
Simply assign wifi settings and ensure port interfaces are identified.
My cap acs are connected through vlans, so I identify those vlan interfaces appropriately.
(one bridge for all connected devices)
Well, I tried to start from the WISP AP mode bridge. It was such a mess I was ready to give up. Then I decided to pretend there’s no such thing as “quickset”, and finally I got it done. What I was missing from the start, I think, was the disabling of the WAN in the interface list.
