![]() However I have a feeling that's not possible? I'm willing so sacrifice the Gargoyle Bandwidth monitoring if I need to.Ĭould anyone maybe share their view/ideas/tips/insights what might be the best way for me to puersuit? (with the given hardware). I can live with the second DHCP server on the Gargoyle but no with all wireless clients accessing my BRIDGE clients - only a few selected. The Gargoyle's network address is 192.168.3.1 and the wireless clients are ergo in the same subnet.īandwith monitoring on the Gargoyle works now but now I can't use pfSense's DHCP (different subnet WIFIAP and Gargoyle's clients) and my firewall rule with ALIAS (IPs) is not working anymore because all traffic coming into the WIFIAP interface now are routed as IP 192.168.1.201 (Gargoyle's WAN IP). What I have now is, the Gargoyle WAN port is defined as static/wired IP (192.168.1.201), same subnet as pfSense's BRIDGE and is plugged into WIFIAP (OPT1). ![]() I had most of that working but some access between the networks (LAN and WIFIAP) didn't work out and I couldn't figure out what it was.Īlso the bandwidth monitoring on the Gargoyle doesn't work when not making use of its WAN port (before Gargoyle was connected from one of the internal switches LAN ports to WIFIAP (OPT1) on ALU). (All other allowed WLAN clients have static DHCP IPs) Gargoyle Guest WLAN clients should have no access to BRIDGE/LAN network devices.pfSense makes DHCP for all LAN/wireless clients on the Gargoyle.Gargoyle router plugged into pfSense OPT1, subnet 192.168.3.0/24.I've been fiddling around for a while now but couldn't achieve my ideal configuration….hence a lack of network knowledge. The Gargoyle router is only there as Access Point with 3 different WLANs. Set the same settings for the SSID, network mode, and the wireless channel as per the primary router. This way, the router will be able to connect to the Ethernet-only device and will connect wirelessly to the other router or the modem. Gargoyle 1.9.1: Access Point with Wireless Clients To connect a wired device to the internet, choose the option ‘Client Bridge’ from the wireless mode dropdown. By disabling legacy 802.11b rates ( option legacy_rates '0') you can at least force the use of 6Mbps or more on the WiFi multicast packets, and this opens up more airtime for other uses.ALU Interfaces: LAN, WAN, WIFIAP, BRIDGE (LAN > WAN) On the other hand, if someone on WiFi requests the group, it will still flood the multicast there, and some people have reported problems with certain devices such as android phones and with ipv6 when igmp_snooping is enabled (requires further debugging to identify if there is really a problem or not). This will cause the bridge to forward only on bridge ports that have requested to receive the particular multicast group. There are two possible fixes for this, one is to enable multicast snooping: option igmp_snooping '1' under the appropriate /etc/config/network settings for the bridge. This can completely use up the WiFi airtime with even fairly light multicast streaming. If you have “enabled legacy 802.11b rates” on your WiFi (Advanced settings checkbox in LuCI under the WiFi settings, or option legacy_rates '1' in /etc/config/wireless file) then 1Mbps is the rate that will be used. On WiFi the slowest modulation available is used for multicast packets (so that everyone can hear them). ![]() This means all network interfaces connected to a bridge (such as a WiFi SSID and ethernet VLAN) will receive multicast packets as if they were broadcast packets. ![]() By default on bridged interfaces on OpenWrt (at least tested in 18.x series) multicast snooping is turned off. For example PS3, xbox, TVs and stereos use DLNA to detect, communicate with and stream audio/video over the network. ![]() DLNA and UPnP clients and printer or SMB discovery protocols on LANs tend to work by using multicast packets. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |