AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Gargoyle block wireless to wired client11/24/2023 I have rebooted the devices several times, but will try manually disable/enable the dhcp service.Īs a workaround I have configured a split scope for VLAN2 on the CRS and RB951. So basic VLAN tagging seems to be working i.e. When I connect a client to the RB951 on the guest SSID and give the client a static IP in the 172.20.22.0/24 range, the client can connect properly. I have not configured any L2 security/firewalling e.g. But I have confirmed the problem when connecting the two devices directly The connection between the two Mikrotik devices is over devolo powerline. at some point in the past it did work with this configuration. when I set up DHCP Server for VLAN 2 on the RB951 and connect to the guest SSID on the CRS however: packet sniffer on RB951 shows DHCP request leaving the router, but no DHCP reply/offer is being received packet sniffer on the CRS shows that the DHCP reply/offer is sent out on the correct VLAN to the correct MAC dhcp logs on the CRS show that the DHCP request is received and an IP from the correct pool is offered to the client WiFi Clients connected to the RB951 "guest" SSID do NOT receive IPs from the CRS at all WiFi Clients connected to the RB951 SSID "unknown" receive IPs from 172.20.20.0/24 WiFi Clients connected to the CRS SSID "guest" receive IPs from 172.20.22.0/24 WiFi Clients connected to the CRS SSID "unknown" receive IPs from 172.20.20.0/24 Network 172.20.22.0/24 is my guest network tagged with VLAN 2, coupled with an SSID named "guest".Ī DHCP Server running on the CRS should serve both VLANs with IP addresses, but there is a problem with DHCP für VLAN2 (guest): Network 172.20.20.0/24 is my primary network on an untagged VLAN, coupled with an SSID named "unknown". Problem receiving DHCP addresses over a VLAN using latest RouterOS v6.38.1. Heres the description nonetheless.maybe some of my findings are helpful: I have a similar problem, which I was about to post before I came across this thread. ROS-6.38.1 on Accesspoint and ROS-6.37.3 on the router is the highest version pair that works with my configuration. I also tried different versions on the access point but the version here doesn't seem to matter. Also reset the AP configuration (System/Reset configuration) in case something was misconfigured - same resultsĪbove configuration worked for some years now.ĭowngrading to 6.37 and step-by-step upgrading to 6.37.1, 6.37.2, 6.37.3 and at least 6.38 i discovered that until 6.37.3 everything works fine. Router RB1200 - Netgear Switch GS108 - Accesspoint RB433.ĭHCP server running on router (without problems and configuration changes for years now).īridge1 configured with member port wlan1 and eth1, Wireless clients can register to the AP but don't get any IP. Router continuously reports: "dhcp1 offering lease 192.168.2.252 for without success" for the DHCP client on the AP. However, the windows clients connected to the router over the same external switch get IPs assigned. Wireless clients on an access point (RB433 - no matter if 6.37.x or 6.38) do not get any DHCP address from the router 6.38 or higher) and even not a dhcp client on the AP gets an address. Just discovered a strange problem with the DHCP server running at RouterOS 6.38.x preventing another Mikrotik Accesspoint and wireless clients from geting an IP address and rendering them inoperable.
0 Comments
Read More
Leave a Reply. |