Flint 2 won't connect to the modem

Routers
22

So is static IP my only option here? Does the router not work for Verizon USA?

23

Without further information about what kind of DHCP is used here itā€™s rather impossible to help. Something is odd, but I canā€™t tell you what it is.

Maybe you should check it with your ISP.

24

Or contact your ISP for login and password for Pppoe.

25

Cable modems donā€™t have PPPoE - they often use MAC-based DHCP auth.
Thatā€™s why I am curious if the DHCP works well.

@freshgouda You could try to clone the WAN MAC of the old router.

1 Like
26

@freshgouda did you manage to fix this?

I know someone who is facing the same issue with Arris Surfboard S33 v2 and Flint 2.

27

okay, in my friendā€™s case, they had a laptop connected to one Ethernet port in the modem and router connected to the second Ethernet port in the modem.

The ISP does not support connection over both Ethernet ports in the modem. So, just connect modemā€™s one Ethernet port with the router and disconnecting the laptop solved the problem.

Thank you.

28

I just had a very similar issue with my Flint 2.

Now my Flint 2 is a few layers back in the home lab network. So It's WAN port is connected to a network who's gateway is just another OpenWRT router. The DHCP on that network is done via a raspberry pi(pi-hole).

That network has been rock solid and efficiently hands out DHCP addresses to all sorts of devices from servers to iot bits and bobs. There are about 30 physical devices on that network. So I'm not at all suspicious of it.

So I've done very basic testing of the Flint 2. As in it still has that new router smell.

I just can get it to grab a DHCP from this network. I have yet to try it on other networks. I'll likely try tether next.

Now I was able to give it a static IP and that works just fine.

I'd like to understand why it won't grab the DHCP address from the Pi-hole on that network? I'm also interested to know if this is going to be an issue when I move it up the stack of networks. Ultimately ending up in slot right behind the fiber modem. If it can't grab DHCP then I've got a big issue.

29

You will need to read the dhcp logs of your RPi and maybe use Wireshark to see what is going on.

I doubt troubleshooting without this is possible.

1 Like