Hi folks, i have a bridge, with 2 vlans (20, 30). I have a dhcp running on each vlan, which is serving the vlan tags to a unifi ap.
Some devices seem to be able to acquire an ip, but most cannot. I have read countless posts about this issue here on the forums, but none solutions found.
I tried disabling rstp, setting admin mac, etc. Nothing works. I’m on the latest stable routeros on RB750gr3
why do you have arp=proxy-arp set on two ether interfaces? This setting messes with ARP (and DHCP involves ARP) … while I see point in setting it on ether2 (VPN uses same subnet addresses) I don’t see point in setting it on ether3.
membership in /interface bridge vlan is incomplete, ether3 and ether4 should be set as untagged members of corresponding VLANs. Well, it’s true that ROS seems to handle tgat automatically, but never the less …
if you don’t have a particular reason to have it enabled, disable /interface detect-internet feature … it can mess things royally.
Concur besides missing items MKX noted on bridge vlans, my concerns focus on the FW rules.
WHERE are the input chain rules?? The default rules keep your router safe, its not secure at the moment and should not be connected to the internet.
The order of rules could be improved, fast track in the forward chain should be the first rule I believe.
Then there are really confusing rules, if you have to use ! twice in a rule, something aint efficient and SO hard to read.
The use of ! often backfires as well as unintended items get dropped.
Keep it simple readable and lean.
???
add action=accept chain=input protocol=icmp
{forward chain} add action=accept chain=forward comment=“Established, Related”
connection-state=established,related add action=fasttrack-connection chain=forward comment=FastTrack
connection-state=established,related
add action=drop chain=forward comment=“Drop invalid” connection-state=invalid
{rules above are standard/good, - below suggest remove}
+++++++++++++++++++++++++++++++
log=yes log-prefix=invalid
**add action=drop chain=forward comment=
“Drop tries to reach not public addresses from LAN” dst-address-list=
not_in_internet in-interface=ether2 log=yes log-prefix=!public_from_LAN
out-interface=!ether2
add action=drop chain=forward comment=
“Drop incoming packets that are not NATted” connection-nat-state=!dstnat
connection-state=new in-interface=ether1 log=yes log-prefix=!NAT
add action=drop chain=forward comment=
“Drop incoming from internet which is not public IP” in-interface=ether1
log=yes log-prefix=!public src-address-list=not_in_internet
add action=drop chain=forward comment=
“Drop packets from LAN that do not have LAN IP” in-interface=ether2 log=yes
log-prefix=LAN!LAN src-address=!192.168.1.0/24**_
Replace ALL of the above noise with
add (any rules where you want subnets or vlans to be able to access the internet)
add (any rules if you want any internal traffic allowed, for example users on vlanxx to be able to use printer on vlanyy)
add action=accept chain=forward comment=“Allow Port Forwarding”
connection-state=new connection-nat-state=dstnat in-interface-list=WAN
chain=forward action=drop comment='drop all else"
OKAY the DST NAT Rules are a bit funky… or confusing.
Is your WANIP dynamic or static/fixed?? The third rule is incomplete…
IF STATIC IP (assuming wanip=192.168.0.100)
/ip firewall nat
add action=src-nat chain=srcnat to-addresses=192.168.0.100
add action=dst-nat chain=dstnat comment=“Web Server” dst-address=192.168.0.100
dst-port=8008" protocol=tcp to-addresses=192.168.1.101
add action=dst-nat chain=dstnat comment=SNMP" dst-adress=192.168.0.100
dst-port=8161 protocol=udp to-address=??? to-ports=161 ( I am copying and assuming port translation 8161 to 161, if its just a typo (no port translation) then drop to ports)
No, i am not yet using a managed switch. So basically,
ether1 = WAN
ether2 = Corporate LAN
ether3 = serve as VLAN trunk to Managed switch trunk (but for now, testing vlan tags on unifi ap)
I am evaluating vlan on gb750gr3 cpu usage. Want to make sure it wont crash after it goes live.
Am I interpreting correctly that VLANs are set up on the UniFi AP, so the AP is tagging outgoing traffic? If so, then ether3 and ether4 need to be added as tagged members in the bridge VLAN table.
Try adding the ether3 and ether4 as tagged then. What’s likely happening is that the DHCP replies aren’t tagged on egress, so they aren’t making it back to the AP clients. The PVID setting for the bridge port only assigns the PVID on untagged inbound packets. /interface bridge vlan is the bridge’s VLAN table similar to a VLAN table on a managed switch. Fyi, if you want to use proxy-arp, you’ll need to set it on the VLAN interfaces themselves in /interface vlan. ARP can be completely disabled on ether3 and ether4 if everything coming in is tagged. Once you have everything working, you’ll see all ARP entries related to ether3 and ether4 showing vlan20 and vlan30 as the associated interface with replies coming from the MAC associated with those interfaces, and the bridge hosts table will track the physical port and VLAN associated with each MAC address.