I'm somewhat new to this forum;
I recently purchased a set of the wireless wire cubes (CubeG-5ac60adpair)
When I went to go and plug everything in and get it configured, I came across some oddities that I'm unsure how to resolve.
I currently have an RB4011 as my main router. (I am excluding the other bits of my network that are unimportant to this, ie, my one cap ac, and two rb260gsp switches)
I have my network set up to be 192.168.88.0/23 - with the built-in dhcp server;
When setting up the cubes, I plugged them in, the master into the rb4011l, and secondary just plugged it in in another room and vaguely pointed them at each other.
I was able to get into them through Winbox, I gave it the default configs, and update the hostnames & removed the default ip addresses (because I already have 192.168.88.2 & 3 used in my network)
When I enabled the ipv4 dhcp client on the devices, they got an IP properly assigned, but they did not get any routes or gateway information.
I don't have anything special in my network, just a simple subnet, no VLANs, no weird or non-standard routes, nothing crazy.
Other devices on my network (phones, laptops, IOT devices, etc) are able to connect to their relevant access points and get dhcp info just fine.
But I'm stuck on why the cubes aren't getting route information nor gateway information. They get everything else, such as the dns server, and their own IP address, but there's no gateway, and the default route that's added is weird. I'm not sure how to explain it.
The two form a wireless bond out of the box, which is nice, but I'm just stuck on why dhcp isn't appearing to work properly.
Am I supposed to not enable DHCP on these devices? I tried resetting them a few times, no change in terms of dhcp.
Or, has anybody seen anything like this before?
I've put some console output below, the first block from the rb4011 showing the dhcp server info, second block from the cube, third from my cap ac.
Secondary question, I've already emailed the supplier I purchased these from - so this is lower priority, but my second Cube has something rattling around inside of it, seems like something broke off inside the cube somehow, has anybody seen this happen before? Like I said, I submitted a ticket to the supplier about it, I'm hoping this is just a one-off thing. But figured I'd drop it in here just in case..
Thank you in advance for any input that can be provided.
If I've left something out, or more info about a certain aspect is needed, let me know and I'll grab it.
dhcp-server info
Code: Select all
[noodle@ndl-router] /ip/dhcp-server> print value-list
name: defconf
interface: bridge
lease-time: 1d
address-pool: default-dhcp
add-arp: yes
authoritative: yes
always-broadcast: yes
use-radius: no
lease-script: {...snip...}
[noodle@ndl-router] /ip/dhcp-server/network> print value-list
;;; defconf
address: 192.168.88.0/23
gateway: 192.168.88.1
netmask: 23
dns-server: 192.168.88.9
wins-server:
ntp-server: 192.168.88.1
caps-manager: 192.168.88.1
domain: home.example.com
dhcp-option: wpad
[noodle@ndl-router] /ip/dhcp-server/option> print value-list
name: wpad
domain-search
code: 252
From the "main" wireless cube:
Code: Select all
[noodle@ww-cube-house] /ip/dhcp-client> print value-list
interface: bridge
add-default-route: yes
default-route-distance: 1
use-peer-dns: yes
use-peer-ntp: yes
dhcp-options: hostname,clientid
status: bound
address: 198.168.88.15
dhcp-server: 192.168.88.1
primary-dns: 192.168.88.1
secondary-dns: 75.75.75.75
primary-ntp: 192.168.88.1
expires-after: 6d23h59m29s
[noodle@ww-cube-house] /ip/route> print value-list
dst-address: 192.168.88.1/32
routing-table: main
gateway: bridge
immediate-gw: bridge
distance: 0
scope: 10
suppress-hw-offload: no
local-address: 198.168.88.15%bridge
This is the output from my cAP AC:
Code: Select all
[noodle@ndl-wap] /ip/dhcp-client> print value-list
;;; defconf
interface: bridge
add-default-route: yes
default-route-distance: 1
use-peer-dns: yes
use-peer-ntp: yes
dhcp-options: hostname,clientid
status: bound
address: 192.168.88.5/23
gateway: 192.168.88.1
dhcp-server: 192.168.88.1
primary-dns: 192.168.88.9
primary-ntp: 192.168.88.1
caps-managers: 192.168.88.1
expires-after: 51w3d20h12m8s
[noodle@ndl-wap] /ip/route> print value-list
dst-address: 0.0.0.0/0 192.168.88.0/23
routing-table: main main
pref-src:
gateway: 192.168.88.1 bridge
immediate-gw: 192.168.88.1%bridge bridge
distance: 1 0
scope: 30 10
target-scope: 10
vrf-interface: bridge
suppress-hw-offload: no no
local-address: 192.168.88.5%bridge
20210901 Edit: I plugged the devices into my RB4011 again yesterday, and I found that they both got their proper DHCP configs this time. Not sure exactly what happened, as I've not changed anything between the debugging and initial creation of this post, and yesterday's test.
But I'm going to mark this up to gremlins & gamma ray bitflips from the Sun. Changing the topic title to add resolved.