jorhett
Occasional Visitor
I've been seeing a problem for a couple of years now where every 30 seconds or so I get tossed to the screen that says
> You cannot login unless logout another user first.
Since I'm always the only one logged in, I hit Back and continue on my business. Since I don't login often, and not for long, I've been putting up with this. It's been going on since at least the shift to 386 and continued with 387 and also with 388. So tonight I started debugging it.
I followed advice here and used these commands to clear all the values prior to logging in before a set of tests:
> nvram unset login_ip_str
> nvram unset login_timestamp
> nvram unset login_ip
Tests have confirmed that it doesn't matter if I use the dns name or the IP address, it only matters which protocol is being used. If I change the DNS name to only return an A record, or go directly to the IPv4 address, this problem disappears. If I go to the IPv6 address, or go to the exact same DNS name (after clearing dns cache of course) that returns an AAAA record then exactly 30 seconds after login I get redirected to the "logout another user" page.
Before anyone says "only use IPv4" -- that's not plausible for me. I work on dual stack services all day. IP traffic entering/leaving my house has been over 50% for a decade, and it's nearing 98% these days. In fact, I only have IPv4 on one local segment and I want to leave disable that and leave it on only for Guest network... and you can't login to admin from a Guest network.
> You cannot login unless logout another user first.
Since I'm always the only one logged in, I hit Back and continue on my business. Since I don't login often, and not for long, I've been putting up with this. It's been going on since at least the shift to 386 and continued with 387 and also with 388. So tonight I started debugging it.
I followed advice here and used these commands to clear all the values prior to logging in before a set of tests:
> nvram unset login_ip_str
> nvram unset login_timestamp
> nvram unset login_ip
Tests have confirmed that it doesn't matter if I use the dns name or the IP address, it only matters which protocol is being used. If I change the DNS name to only return an A record, or go directly to the IPv4 address, this problem disappears. If I go to the IPv6 address, or go to the exact same DNS name (after clearing dns cache of course) that returns an AAAA record then exactly 30 seconds after login I get redirected to the "logout another user" page.
Before anyone says "only use IPv4" -- that's not plausible for me. I work on dual stack services all day. IP traffic entering/leaving my house has been over 50% for a decade, and it's nearing 98% these days. In fact, I only have IPv4 on one local segment and I want to leave disable that and leave it on only for Guest network... and you can't login to admin from a Guest network.