IPv6 not Working with TCP Monitor
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
When trying to Monitor an TCP Port on IPv6, you get the Result: TCP connection failed: dial tcp: address [Monitored-IPv6]:[Monitored-Port]: too many colons in address
**To Reproduce**
Steps to reproduce the behavior:
1. Add an TCP Monitor with an IPv6
2. Get the Error.
**Expected behavior**
A Working Monitoring of an TCP Port over IPv6
**Screenshots**
**Additional context**
Peekaping is Hosted over the Docker Compose Stack with PostgreSQL
Contributor guide
No contributing guide indexed for this repository
Research direction
Look for TCP monitoring code that parses addresses, likely in a network check module. The error 'too many colons in address' suggests improper IPv6 handling when concatenating address and port. Find where the dial target is constructed, ensure IPv6 addresses are wrapped in brackets. Check existing tests for TCP monitoring to add an IPv6 test case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, go, postgresql
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100