Thanks for being patient, it's very much appreciated!
1 -= Adjusted the host name on the Router. I saw no change.. I was expecting to see the name appear in the network connections instead of 'network 5'.
2 -= Yes, I am on the top port of the modem.
3 -= Now that you mention it, while slow at 100mbps, the other router DID disconnect me quite often (before it outright broke). And when it wasn't me, it was the other devices plugged in. dd-WRT, when rebooted, actually stabilizes everything, (and works at 1gbps).
For the tests:
4 -= Disabling the other NICs didn't change anything. It had me wondering if it could have been the same subnet mask of 255.255.255.0 but with both offline the issue still occured.
5 -= During the ping session, the outgoing log was dropping tons of random IPs with the other system turned on (once windows had started. Didn't even need to log in!). The dropped IPs were from both systems seemingly at random too.
Note that rebooting the dd-wrt router solves all that while both systems are up.
6 -= Checking the status, I noticed that when both or one of the two system's names were present, the issue occurred. However when I reboot dd-WRT, the names become asterisks (*) and the connection is actually working. Not sure what all of that means yet.
EDIT: Things seem to work when neither system appear in the "DHCP Clients" Of Status / LAN, if that helps.
EDIT 2: I tested starting the other system first and then my own system. I suspected the problem would happen there too and I confirm that the moment a second system connects, the first system online is disconnected.
There's a couple of things I want to test now, too. I'll let you know if anything.
6 -= Checking the status, I noticed that when both or one of the two system's names were present, the issue occurred. However when I reboot dd-WRT, the names become asterisks (*) and the connection is actually working. Not sure what all of that means yet.
EDIT: Things seem to work when neither system appear in the "DHCP Clients" Of Status / LAN, if that helps.
EDIT 2: I tested starting the other system first and then my own system. I suspected the problem would happen there too and I confirm that the moment a second system connects, the first system online is disconnected.
There's a couple of things I want to test now, too. I'll let you know if anything.
The asterisks just mean that the router does not now the hostname of the system.
I am wondering if it has something to do with DNS... are you able to type in any ip addresses when the systems drop?
6 -= Checking the status, I noticed that when both or one of the two system's names were present, the issue occurred. However when I reboot dd-WRT, the names become asterisks (*) and the connection is actually working. Not sure what all of that means yet.
EDIT: Things seem to work when neither system appear in the "DHCP Clients" Of Status / LAN, if that helps.
EDIT 2: I tested starting the other system first and then my own system. I suspected the problem would happen there too and I confirm that the moment a second system connects, the first system online is disconnected.
There's a couple of things I want to test now, too. I'll let you know if anything.
The asterisks just mean that the router does not now the hostname of the system.
I am wondering if it has something to do with DNS... are you able to type in any ip addresses when the systems drop?
I haven't tried any specific IP addresses other than the DD-WRT router's.
Whenever one of the systems take over the internet connection, the router is still accessible whereas websites are not until I reboot the router, usually from the 'services' tab and then clicking 'reboot router'. I don't physically reboot the system using the power button.
The names of the systems is the default-assigned windows one... the only special character is the dash "-".
I tried adding an NIC to the system to remove the switch from the equation and dd-WRT saw my system as a NEW system! Prompting me to get a 24-hour trial.
If I make upgrades to the system, do I need to buy a new licence? Would the new (second) NIC be active only once activated? (The NIC was detected, but my system would not connect to the router through it!)
Yes. Once the public VGA version worked fast and well (disregarding the current disconnections), I bought a full version to enable WiFi.
My build is fairly recent: DD-WRT v3.0-r55052 std (02/02/24)
I haven't tried upgrading from there yet as, right now, I suspect it would lose its license from upgrading again and I DO NOT want to do a full reinstall at the moment.
Not sure how this has gone unnoticed, but in your screen shots, you don't have any DNS configured in the DHCP section of the Basic Setup tab. You need to have at least one there. This is what hands out the DNS servers to the clients via DHCP. Try putting 8.8.8.8 into Static DNS 1 and put 1.1.1.1 into Static DNS 2 and see if that fixes it. _________________ Linksys EA8500 (Internet Gateway, AP/VAP) - DD-WRT r53562
Features in use: WDS-AP, Multiple VLANs, Samba, WireGuard, Entware: mqtt, mlocate
Wireless 5ghz only
Netgear R7800 (WDS-AP, WAP, VAP) - DD-WRT r55779
Features in use: multiple VLANs over single trunk port
Linksys EA8500 WDS Station x2 - DD-WRT r55799
Netgear R6400v2 WAP, VAP 2.4ghz only w/VLANs over single trunk port. DD-WRT r55779
OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.
Joined: 16 Jun 2006 Posts: 152 Location: Germany, BW
Posted: Mon Feb 26, 2024 10:28 Post subject:
With WAN-Port doing DHCP he is using the ISP settings:
Gateway 198.91.168.97
IPv4 DNS 0 209.197.128.2
IPv4 DNS 1 209.197.128.5
QMachforr:
But its worth a test, lets put in other external DNS.
On WAN setting activate "Ignore WAN DNS", in DHCP setting put in 1.1.1.1, 9.9.9.9, 208.67.222.222
I prefer not to use 8.8.8.8 or 8.8.4.4 as Google has enough Data from us.
I saw you were testing with a ping to 1.1.1.1 from a PC. Try either telnetting or ssh'ing into your router and run the ping from there. This will tell you if the router is losing connection or the LAN is using connection. _________________ Linksys EA8500 (Internet Gateway, AP/VAP) - DD-WRT r53562
Features in use: WDS-AP, Multiple VLANs, Samba, WireGuard, Entware: mqtt, mlocate
Wireless 5ghz only
Netgear R7800 (WDS-AP, WAP, VAP) - DD-WRT r55779
Features in use: multiple VLANs over single trunk port
Linksys EA8500 WDS Station x2 - DD-WRT r55799
Netgear R6400v2 WAP, VAP 2.4ghz only w/VLANs over single trunk port. DD-WRT r55779
OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.
However while I understand the principle, it's beyond my current level of network knowledge to accurately implement. (I know what you mean by telnetting, but I'll be damned if I can use it properly)
I'm not even sure if googling the procedure would have it work to give the intended results you're looking for to diagnose, too.
Think of me as between a noob and a novice in terms of network infrastructure understanding with some spikes of intermediate left and right.
It's actually very easy to do. From your Windows cmd prompt simply type:
Code:
telnet YourRouterIP
Username is always root
Password is your Router's password.
Once logged into your router simply type:
Code:
ping 1.1.1.1
And let it run and see if it stops whenever you are experiencing Internet access issues.
Use CTRL+C to stop the ping process and exit will terminate the connection. _________________ Linksys EA8500 (Internet Gateway, AP/VAP) - DD-WRT r53562
Features in use: WDS-AP, Multiple VLANs, Samba, WireGuard, Entware: mqtt, mlocate
Wireless 5ghz only
Netgear R7800 (WDS-AP, WAP, VAP) - DD-WRT r55779
Features in use: multiple VLANs over single trunk port
Linksys EA8500 WDS Station x2 - DD-WRT r55799
Netgear R6400v2 WAP, VAP 2.4ghz only w/VLANs over single trunk port. DD-WRT r55779
OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.
Joined: 16 Jun 2006 Posts: 152 Location: Germany, BW
Posted: Mon Feb 26, 2024 21:45 Post subject:
You can try the ping from DD-WRT itself, but I don't think this will bring up any new Information.
The second PC powered on kicks out the first running PC from Internet connection.
The second PC then has Internet, the first one not. Rebooting the DD-WRT box while both PCs are running brings back Internet connection also for the first PC.
So it's my understanding that DD-WRT box always has Internet connection.
But for an unknown reason DD-WRT stops routing the packets from 1st PC when 2nd PC connects to the Network.
As it's not because of same IP or MAC I'm out of ideas what the reason could be.
