- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
GS108Tv3/GS110TPP 7.0.5.2 Firmware Update 2x Bugs
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
GS108Tv3/GS110TPP 7.0.5.2 Firmware Update 2x Bugs
I have a GS108Tv3 and GS110TPP and upgraded the firmware from 7.0.5.2 on both today.
I don't have a support contract, but the newest firmware has introduced two bugs;
1) accessing the switch via dns name e.g. switch.local.lan returns "400 Bad Request" - it didn't do that on 7.0.4.8
2) import certificates has the public and server certifcate reversed.
Maintenance - Update - HTTP Firmware/File Update
- X.509 Public Certificate PEM
- X.509 Certificate Private Key PEM
The two are reversed. In other words; you have to upload the;
actual Private Certificate to the Public Certificate, and
the Public Certificate to the Certificate Private Key
Browsing will work with https but only if the IP Address is used. see 1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: GS108Tv3/GS110TPP 7.0.5.2 Firmware Update 2x Bugs
Hi There,
In relation to
1) there has been a change since 7.0.4.8.
I had a "_" in the host name. but it worked in all prior versions (and other non-netgear devices).
I see that "-" is a valid character, but "_" is not for a host name. So 7.0.5.2 would appear to be working according to strict specifications. Notwithstanding there is an "uncaught SyntaxError: expected expression, got '<'" on the login page.
2) This problem exists (i don't know if either of the tftp upload options is correct, and only the http is incorrect). The three places to upload certificates are;
- Security / Access / HTTPS / Certificate Update (as tftp)
- Maintenance / Update / TFTP File Update (as tftp)
- Maintenance / Update / HTTP File Update (as http)
I have only tried the HTTP option, but
"X.509 Public Certificate PEM" - has to be the Service Certificate - not the Public CA
"X.509 Certificate Private Key PEM" - has to be the Public CA - not the server certificate.
So i now have the devices working as i previously did.