Opened 16 years ago
Closed 16 years ago
#4074 closed Bug report (rejected)
Version 3.16 not resolving decimal IP
| Reported by: | cozilla | Owned by: | |
|---|---|---|---|
| Priority: | high | Component: | FileZilla Client |
| Keywords: | decimal, IP | Cc: | |
| Component version: | Operating system type: | Windows | |
| Operating system version: | vista & xp-sp3 |
Description
Versions prior to 3.16 seems to resolve IPs in decimal format no problem but as soon as upgrade to version 3.16 it stop working. Solution for now is to put in the dot IP address. Tried with different dns and number of different ISP and networks but no luck.
Change History (5)
follow-up: 2 comment:1 by , 16 years ago
| Status: | new → moreinfo |
|---|
comment:2 by , 16 years ago
| Status: | moreinfo → new |
|---|
Replying to codesquid:
So you are saying it is working fine in 3.1.6-rc1? (It is an older version)
No, it's working fine with 3.15 and older versions but not 3.16 (build date 2nd Dec 08).
follow-up: 4 comment:3 by , 16 years ago
| Resolution: | → rejected |
|---|---|
| Status: | new → closed |
Nothing has changed between 3.1.5. and 3.1.6 that could possibly cause this. Something else on your system or network must have changed.
Note that I am unable to find any specifications on that numerical format. Are you sure these addresses are standards compliant?
comment:4 by , 16 years ago
| Resolution: | rejected |
|---|---|
| Status: | closed → reopened |
Replying to codesquid:
Nothing has changed between 3.1.5. and 3.1.6 that could possibly cause this. Something else on your system or network must have changed.
Note that I am unable to find any specifications on that numerical format. Are you sure these addresses are standards compliant?
I'm serving over 20 clients and 8 upgraded to 3.16 recently running on completely different networks and computers with the same error of not resolving IP.
I then do some testing and found that 3.15 and older version would works fine with decimal IP eg. "3512052580" but 3.16 is not working. I then change the IP back to the dot format eg. "209.85.171.100" and things is fine. The idea of using decimal IP is the make the real IP less obvious to general users. Decimal IP is widely accepted standard. Try doing a "dig" or "nslookup" on this IP "3512052580" you will find that it translate back to the dot IP just fine.
comment:5 by , 16 years ago
| Resolution: | → rejected |
|---|---|
| Status: | reopened → closed |
Decimal IP is widely accepted standard.
Then there has to be an RFC for it. Can you link it please?
There has nothing changed between 3.1.5 and 3.1.6 that could cause any such regression, just diff the source between the versions.
So you are saying it is working fine in 3.1.6-rc1? (It is an older version)