The change sets in SVN are sequentially numbered commits. This means that every time a person registers a save with the system it increments the number so that there is version control.
In this case, the build 09-18-2020-r44406 was built on that date from the r44406 configuration. Since the fix was done on commit 44407, it is not in that build. Thus you will have to wait for a build using 44407 or higher for the fix to be included.
Posted: Sat Sep 19, 2020 15:22 Post subject: Re: Open firewall ports when upgrading build
js290 wrote:
ohnoo wrote:
Hi, I've flashed a WRT54G2v1...
I've also been testing dd-wrt on the WRT54G2v1. The one I have is horrible for latency sensitive apps like RDP, which I noted in this thread. Web surfing and streaming seems fine. What's your experience with your G2?
BTW, I'm running v3.0-r44251 micro (08/27/20) on my G2. I ran nmap against the WAN interface, and I'm not seeing the port open issue you are.
Code:
# nmap -p 1-1055 10.23.21.46
Starting Nmap 7.70 ( https://nmap.org ) at 2020-09-18 21:42 EDT
Nmap scan report for 10.23.21.46
Host is up (0.0023s latency).
Not shown: 1051 filtered ports
PORT STATE SERVICE
22/tcp open ssh
53/tcp closed domain
80/tcp closed http
514/tcp closed shell
MAC Address: 00:21:29:D5:26:FB (Cisco-Linksys)
Nmap done: 1 IP address (1 host up) scanned in 19.09 seconds
.
Upgraded to v3.0-r44406 micro (09/18/20) with same nmap results (and same latency issue).
Let's preserve the nature of this post, I'll answer this in the other one, I guess we should delete these off topics and continue there
The change sets in SVN are sequentially numbered commits. This means that every time a person registers a save with the system it increments the number so that there is version control.
In this case, the build 09-18-2020-r44406 was built on that date from the r44406 configuration. Since the fix was done on commit 44407, it is not in that build. Thus you will have to wait for a build using 44407 or higher for the fix to be included.
That's what I suspected as well: that the 44407 fix would not have been in the 44406 build. Thanks for clarifying.
