Hex-S Router No IP

RouterOS General
1

Good afternoon

I have configured a Hex-S router for one of our remote sites and sent it to site for one of our guys to install. They installed the router. It is currently connected to a BT router on eth1 with a switch connected on eth2. it is set to 10.124.1.1 and set to give IP’s in the range 10.124.1.2-10.124.1.254. This is working as it should.

BT have since been in and fitted a new fibre route, Cisco 4321. Site have disconnected the Hex-S from the BT router and plugged it into the GE 0/0/1 port on the Cisco router via Cat5 but the Hex-S is failing to pick up an IP address.

I have had one of our guys on site connect his laptop to the Cisco router via the GE 0/0/1 port and he gets an IP address. This is a 169 address but he gets internet access. The gateway address is an IPv6 address, FE80…

If I connect the Hex-S back up to the Cisco router, it still refuses to get an IP address. I’ve tried setting a static IP for the eth1 but I can’t add the IPv6 address in the gateway.

Would anyone have any ideas how I can get this connected and working?

We had fibre installed in another depot and used a Ubiquiti EdgeRouter x4 and had no issues, it just worked straight away.

Thanks

Alex

2

If by “169 address” you mean 169.254.x.x, it’s what some devices automatically assign when they don’t get any other address from DHCP. RouterOS doesn’t do that, so it would explain why it ends up with no address. And it suggests that there’s really no DHCP server.

As for working internet access, and with fe80… gateway, it’s possible if it’s IPv6-only (possibly with NAT64 at upstream router), because IPv4 and IPv6 don’t mix. RouterOS doesn’t automatically get IPv6 from RA, it can be enabled, but it would be just single address for router itself, it would be useless for devices behind it. You can try to add DHCPv6 client and get prefix, that would help, but all connected devices would have to use IPv6, no more 10.124.1.x.

3

That, or they didn’t enable the DHCP client feature, or it’s bound to the wrong port/bridge.