listener not working if connect address is on Public IP
- Dominant language
- C#
- Stars
- 4.7k
- Forks
- 822
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I've installed Covenant twice on aws and tried listener with both it's own public ip address (IP and Public IP DNS) and with a redirector public ip but each time a grunt is not return. I've tried with defaultHTTP profile and customHTTP profile. Inbound rules on aws are allowing 80 and 443. I've tried multiple launchers with security disabled on the tested machine. The launcher seems to be correctly generated as it's trying a call back on the provided ip.
Using private IP address a grunt is return.
Am I missing something?
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or code entry point is named. Start by reproducing the listener with the same AWS public and private addresses, redirector, and defaultHTTP/customHTTP profiles, then compare the network configuration; done means identifying a confirmed cause and documenting the required settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, csharp
- Domain
- cloud, networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100