.92 issues

Donnie · Nov 5, 2005, 6:42 PM

so i think i upgraded to .92, but i really am not sure. I downloaded the full update labeled .90 - which I assume is labeled according to the version you are currently running since I did not see a .92 in the list. Then I installed the firmware via the web interface to my router.

It said it would reboot when it was done… though I watched the box the entire time and it did not reboot the entire system. It also still lists .90 as the installed version on the Firmware page.

I was just curious if I did anything wrong and if I actually upgraded the router or not.

Part 2 of this post is that I am now noticing alot of states being generated from the router. I am not sure if this is related to my upgrade attempt, though I didn't notice it until after I performed it. There are over 100 of these entries. Here are a few of what I'm referring to:

self tcp 192.168.100.254:80 <- 192.168.100.200:2108 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2109 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2110 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2111 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2112 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2113 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2114 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2115 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2116 TIME_WAIT:TIME_WAIT
self tcp 192.168.100.254:80 <- 192.168.100.200:2117 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2118 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2119 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2120 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2121 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2122 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2123 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2124 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2125 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2126 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2127 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2128 FIN_WAIT_2:FIN_WAIT_2

*edit - for clarification the router is 100.254, and 100.200 is the box i'm viewing the router's website from

Any thoughts on what is going on here? They eventually clear themselves out of the router if I don't visit the states page for a while (every time I refreshed the states page I got more)

Guest · Nov 5, 2005, 6:25 PM

You did not upgrade to version 0.92. Each firmware version is labled with its version number. If you already had version 0.90 installed and you "upgraded" to version 0.90, then of course your box wouldn't reboot.

Donnie · Nov 5, 2005, 6:40 PM

thanks submicron. I saw the announcment that .92 was released as an upgrade so I got confused when it wasn't in the upgrade list, yet all the packages were dated 11/5.

billm · Nov 6, 2005, 2:16 PM

@Donnie:

Part 2 of this post is that I am now noticing alot of states being generated from the router. I am not sure if this is related to my upgrade attempt, though I didn't notice it until after I performed it. There are over 100 of these entries. Here are a few of what I'm referring to:

self tcp 192.168.100.254:80 <- 192.168.100.200:2108 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2109 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2110 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2111 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2112 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2113 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2114 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2115 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2116 TIME_WAIT:TIME_WAIT
self tcp 192.168.100.254:80 <- 192.168.100.200:2117 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2118 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2119 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2120 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2121 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2122 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2123 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2124 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2125 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2126 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2127 FIN_WAIT_2:FIN_WAIT_2
self tcp 192.168.100.254:80 <- 192.168.100.200:2128 FIN_WAIT_2:FIN_WAIT_2

*edit - for clarification the router is 100.254, and 100.200 is the box i'm viewing the router's website from

Any thoughts on what is going on here? They eventually clear themselves out of the router if I don't visit the states page for a while (every time I refreshed the states page I got more)

The states page will refresh itself. Those states are coming from your client pulling down data from the firewall (css, images, html, etc). That looks a little high, but I'm not sure how often you refreshed to get that output ;)

–Bill

ZGamer · Nov 7, 2005, 2:39 AM

I haven't noticed that problem with .92(wrap) but I did notice that the wireless is running a lot better (atheros chipset).

sullrich · Nov 8, 2005, 8:48 PM

@ZGamer:

I haven't noticed that problem with .92(wrap) but I did notice that the wireless is running a lot better (atheros chipset).

Good deal. We actually are using a newer HAL for the ATH chipset than the one shipped with RELENG_6. It does appear much nicer.

Cyrandir · Nov 9, 2005, 12:21 AM

I haven't noticed any problems with .92 either, but I upgraded, so if it was installer issues, I wouldn't have seen it. And I'm using the harddrive version. I have noticed a little better performace too. Previous to the .92 upgrade I was noticing a lot of states as well, but once I had done the update, the performance increased again. ;D