Addendum to my longish blog about my router.
I used to think that changing any setting would invalidate the certificate (the one that lets you log in without dire warnings about being unsafe.)
NOW I know that just Rebooting the router, or shutting off power and then turning it back on, messes with the certificate on the router; now the router certificate and the PC certificate don't like each other,
I used to think that changing any setting would invalidate the certificate (the one that lets you log in without dire warnings about being unsafe.)
NOW I know that just Rebooting the router, or shutting off power and then turning it back on, messes with the certificate on the router; now the router certificate and the PC certificate don't like each other,
and I must generate a different computer certificate.
So...What? This is worse than the old firmware version, 37031 (I'm using 37038)
Then it gets real complicated.
If I knew how, I could create a certificate and upload it to the router, and use the router to send a certificate to my PC.
Generally speaking, I need a router certificate that doesn't change, despite reboots and settings.
If I knew how, I could create a certificate and upload it to the router, and use the router to send a certificate to my PC.
Generally speaking, I need a router certificate that doesn't change, despite reboots and settings.
The guys making the User interface (for guys like me) ignore the user interface, preferring line commands. That's my only explanation for why this happens more than a year after the router was released.
I won't have a valid certificate because they've invalidated it?
What is a CRL?
The most basic router instructions are lost on me anyway; shades of high school math classes.
OK a brief look at this train-of-thought:
One way to get a certificate (for WAN access??) is to use DDNS.
I don't want WAN access, although I'm sure you-all have worked around it.
One way to get a certificate (for WAN access??) is to use DDNS.
I don't want WAN access, although I'm sure you-all have worked around it.
But I *did* briefly want to look at my local-area-network,
specifically, the address-assignment page ("DHCP".)
I'm rewriting this sentence...Lan Gateway vs Wan Gateway (I'm glad I'm not in speech class making a presentation)
My primary router in a Lan is the gateway, um, which makes the modem (which is a router) My primary router, but it's not,
My primary router in a Lan is the gateway, um, which makes the modem (which is a router) My primary router, but it's not,
because of the DHCP. (I'm double-NATting.)
Clear-as-mud but I get it (sort of.)
Clear-as-mud but I get it (sort of.)
Now I (prolly) know my modem's address and the router's addresses should be on the same subnet. (I think I know, but there would be a conflict, so no)
Forcing the subnet on my router to use unused addresses on the modem's subnet is something I want to try, eventually (static IP on the PC with The modem as the gateway, should have worked, *did* work, in a half-ass way.
Google-news worked, but a few of the sites it pointed to did not.
Static-IP (modem-LAN), *Router* gateway, didn't work very well either.
Only DHCP. So (if you're following along) jiggling addresses just made stuff a lot worse.
Static-IP (modem-LAN), *Router* gateway, didn't work very well either.
Only DHCP. So (if you're following along) jiggling addresses just made stuff a lot worse.
 |
| Yeah, I *know*, but... |
Well...that doesn't solve my certificate-problem, except to spell out that DDNS is not an option.
I'm not running a server either.
I don't want every pissant with a keyboard trying to get into my router.
I don't want every pissant with a keyboard trying to get into my router.
So, any options left?
Trigonometry vs quantum physics:
It's not like this doesn't work, but if you dare to change a setting, or dare to "apply"
a setting that causes the router to reboot itself,
Then the certificate you just downloaded and installed per their instructions, becomes invalid.
Several times a guy is presented with the login-page, which is unsafe, then
after consenting to the danger, is presented with the login page!
Then a new warning comes up that it's unsafe, then you consent,
Then a new warning comes up that it's unsafe, then you consent,
then another login page!!
This is circular, in case you didn't notice.
Eventually though, through luck and pushing little buttons, it breaks out of this loop and actually logs you in. I already wrote that "37038", their latest version, caused this login loop.
This is circular, in case you didn't notice.
Eventually though, through luck and pushing little buttons, it breaks out of this loop and actually logs you in. I already wrote that "37038", their latest version, caused this login loop.
I also already vaguely referred to the command-line programs that true hackers use to hack into the router, ignoring whatever I see in menus.
In other words, It's all a crock of shit.
