Tried a lot of things, but my Hex does not get an automatic IP from my ISP (Tweak in NL over KPN the fiber network). The configuration is from the default QuickSet to keep it simple. The DHCP client on ether1 shows “Searching…”.
Things I tried:
Cloned MAC and WAN IP settings from a working router (static IP): works
Installed OpenWRT on the Hex: works out of the box
Connected both the WAN cable and the Hex to a managed Layer 2 switch (TP-Link TL-SG108PE): works
Tried a TP-Link Archer C7 v2: doesn’t work with factory firmware but does work with DD-WRT installed
What happens is that the client does get connected to the WiFi network, but sometimes the wireless interface does not go to the “up” state. So the DHCP client does not get an address.
It will remain stuck in that condition until the WiFi connection is interrupted for some reason.
This is on RB951G-2HnD devices, so old wireless code.
Which version of ROS do you run on that Hex ?
There have been some recent bug fixes related to DHCP context, might be worthwhile to upgrade to latest stable version in ROS7 chain.
(Hex runs just fine on ROS7, mine does already for several years).
I’m not near the router now, I will return home on Monday. But the default config is not touched, just using QuickSet (which works when I connect to WAN through a L2 switch as mentioned before).
You could add a vlan interface to ether1 with a vlan of 34,
Make the new vlan interface a wan (Interfaces interface list)
(leave ether1 as a wan)
move the dhcp client that is on ether1 to the new vlan
Thanks. I have an Internet Only subscription, which does not use VLAN tagging. I have tried using the VLAN tags anyway, but no luck.
From their support page (translated):
Internet Only
The connection is untagged (so no VLANs).
Use the WAN port of your own router to connect our media converter.
Use DHCP to obtain an IP address.
Latest RouterOS version (7.10) shows the same behavior btw.
It may be that your ISP has somehow “remembered” the MAC address of the other router and refuses to assign an IP address until the lease for that other MAC has timed out (as a way to prevent that you can get 2 IP addresses on your line).
I have done some experimenting with this (see 1st post), and that does not seem to be the case. It looks like some router OSes (like factory TP-Link and Mikrotik RouterOS) have a different DHCP Client implementation which causes my issue. Or some kind of blacklist at the ISP side. I just don’t get a DHCP reply for my requests.
Currently I’m using a TP-Link C7 with DD-WRT without issues. If I connect my laptop (with a different MAC address obviously) directly to the media converter, that works fine as well (I get a DHCP lease instantly). And OpenWRT on the Hex works as well.
Try changing the Hostname/Identity of the router.
Maybe they block devices named Mikrotik (due to some issues in the past with poorly configured devices)
Looking at the Mikrotik dhcp client page, it says it requests a few options.
But none of those listed are the CAPWAP-Server or the Vendor-Specific Options which are also requested.
Maybe your ISP’s DHCP server doesn’t like one of these, unfortunately you can’t change them.
Also the vendor-specific option request is sent, but it doesn’t send a Vendor Class Identifier so presumably the DHCP server is supposed to guess what vendor-specific option it wants??
Maybe you could attempt to get your openwrt client to send these additional options and see if it causes the dhcp to break and if so, That might be useful to send to Mikrotik Support. (And maybe also to your ISP)
Perhaps easier. You could ask your ISP tech support and see if they can give you any insight into what is currently happening.
I also called Tweak support, and they said everything looked fine at their side and that they could see my DHCP requests. Maybe good to know: in my area, Tweak ISP uses the KPN fiber network. No support for end users from that party though.
I will try the OpenWRT-with-additional-client-settings route.