Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What it is not working? #9

Open
facetime88 opened this issue Dec 6, 2016 · 2 comments
Open

What it is not working? #9

facetime88 opened this issue Dec 6, 2016 · 2 comments

Comments

@facetime88
Copy link

Hi,

I have a web server accessed with port 80 behind NAT and there is no way to port forwarding since the ISP itself block the port. So I hope this will help to to solve the problem.

I started "pwnat -s" on the webserver machine. Then on a client want to connect to the server I run "pwnat -c 8500 202.62.16.132 127.0.0.1 80". 202.62.16.132 is the public ip address of the web server.

Then I open browser and navigate to localhost:8500. But it failed with error "Bind failed". What does it mean?

Thank you so much.

@bauen1
Copy link

bauen1 commented Dec 6, 2016

2 Things i can thing of:

  1. Try running them both as root using sudo <original command here>
  2. You could be behind Carrier Grade NAT in which case as far as i know your out of luck

@devxpy
Copy link

devxpy commented Apr 12, 2018

  1. i already ran stuff as sudo since it gave and error when i didnt
  2. I dont think i'm behind one, i referred this. a traceroute to my public ip reveals only one hop.
⋊ ~> traceroute <public ip>
traceroute to <public ip> (<public ip>), 30 hops max, 60 byte packets
 1  <public ip> (<public ip>)  0.597 ms  0.476 ms  0.493 ms

my public ip is of the form 43.247.***.**
Certainly not 100.64.0.0 or 10.100

BTW, Can chownat work with Carrier Grade NAT?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants