-
-
Notifications
You must be signed in to change notification settings - Fork 304
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: nachoparker <nacho@ownyourbits.com>
- Loading branch information
1 parent
bd0c23d
commit 1a8ac71
Showing
2 changed files
with
13 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1a8ac71
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, why should it be ok to remove the tmp file before it is used in the second request. I did the original patch, and it keeps the cookies for the second request….
As this seems to work, possibly the website does not depend anymore on the cookies?!
1a8ac71
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
duh, that is my mistake
1a8ac71
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but you are right, I forgot to remove tmp_file in case of open port :) This was probably, what you wanted to fix…
1a8ac71
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, I just thought it wasn't used anymore because I wasn't careful. I need somebody to test the fix by doing
sudo ncp-update devel
. I can't test this right now since my ports are not open with my new ISPthanks for the good catch
1a8ac71
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It shows closed to me too.
I think you can not strip the "-O -" in the wget (I don't remember what it was, but I added it and I get displayed open again)
and I had to remove: target_ip=${public_ip}& too ???
public_ip does not give my external (on the router) ip address… I gives a local ip6 address
Then of cause public_ip is not needed anymore?!
This shows open for me again:
1a8ac71
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the public IP is needed, in my case (closed ports) it always returns "open" if I don't use that parameter, and that parameter is what the real website expects. I have not however tested IPv6, so that could be a reason. The
-O -
is totally fine.So the thing is that it shows open if the query is incomplete, you can try this by doing
is_port_open <some_weird_port_that_is_closed>
. It just fails to detect something that is closed unless we use thispublic_ip
parameter.1a8ac71
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed my previous message asking to do some checks because you know what, it will be easier just to fix this myself in a couple days once my ISP opens my ports and I can test all cases.
Thanks!