Bitcoin-qt peer connection issues

[coinz4dayz]

So a bit of background info. I was originally running a full node with bitcoin-qt with no issues. I was averaging about 40 connections with a maximum of 80 from what I can recall. Well my old router/gateway was dropping it's internet connection and needed to be rest almost daily. I decided to replace it but I'm a noob and screwed up and only bought a router. I didnt want to buy a modem so I'm using the old router/gateway with dmz enabled and set the new router as the host. I also forwarded port 8333 on the new router.

It fixed the dropping internet issue but now I can only get a maximum of 14 connections with the lowest being 9. I know hardly anything about networking so I have no idea where to even begin solving this. I did check my node with

https://getaddr.bitnodes.io/#join-the-network

And it came back with a green check mark so I guess it's okay? Can anyone shed any light on what's going on? Thanks.

Edit: I also have DHCP enabled on both routers which I don't think is right. Maybe that has something to do with it?

[deepceleron]

When you port forward, you must specify the IP address of the internal computer running Bitcoin. If you are using DHCP, this does not guarantee that the internal computers will always receive the same IP addresses. You should set up a DHCP fixed lease in your router for the particular computer's MAC address, or manually configure the IP address on the machine itself.

Only one device should should be a DHCP server for your local network, and there should only be one layer of network address translation (your router's external interface should get a real internet address from the modem or network it is connected to).

[coinz4dayz]

Thanks so much for replying it really helped. After trying to mess around with the DHCP settings to no avail I think I'm just going to buy a dedicated modem so I don't have two routers interfacing with each other.

Posted From bitcointalk.org Android App

[Dare]

Did your public IP address change when you added the other router? If so, it may take a while for your node's information to get passed around the network again. If it is a DHCP issue, getting a dedicated modem won't necessarily help, as the computer running bitcoind still needs to have a static IP with the correct port forwarded to it.