|
1 | 1 | ## Known issues
|
2 | 2 |
|
3 |
| -> My local machine network configuration has changed but extension does not pick up the changes. |
| 3 | +- 🚩 [#6 [mac osx] Do you want the application "gh net" to accept incoming network connections? come and go out quickly](https://github.com/github/gh-net/issues/6) |
| 4 | + |
| 5 | +### 🚩 SSH stack trace |
| 6 | + |
| 7 | + |
| 8 | +### 🚩 I'm getting an `Permissions denied` error an a stack trace immediatelly after starting the extension |
| 9 | + |
| 10 | +- Most likely you forgot to use `sudo` to run the extension. Sudo is required to bind to network sockets on the local machine. If you still seeing the error after running the same command with `sudo`, please create a [Bug report](https://github.com/github/gh-net/issues/new?assignees=&labels=bug&template=bug_report.md&title=). |
| 11 | + |
| 12 | +### 🚩 My local machine network configuration has changed but extension does not pick up the changes |
4 | 13 |
|
5 | 14 | - Please restart the extension by pressing `q` and connecting to the Codespace again. The extension currently does not watch for changes in network configuration and hence does not detect new network interfaces or changes in interfaces config. This will be fixed in the future.
|
6 | 15 |
|
7 |
| -> I'm getting an error an a stack trace immediatelly after starting the extension. |
| 16 | +### 🚩 [Alpine Linux] DNS resolution inside an `Alpine Linux`-based Codespace sporadically fails |
| 17 | + |
| 18 | +Apline Linux kernel queries a random known nameserver as oppose to doing queries in sequence as other Linux distros would do. This means that sometimes DNS requests go past extension-defined nameserver so DNS resolution will fail. |
| 19 | + |
| 20 | +Known workarounds: |
8 | 21 |
|
9 |
| -- Most likely you forgot to use `sudo` to run the extension. If `sudo` was used, please create a [Bug report](https://github.com/github/gh-net/issues/new?assignees=&labels=bug&template=bug_report.md&title=). |
| 22 | +- add explicit `ip-address hostname` mapping to `/etc/hosts` file inside a Codespace |
| 23 | +- modify the `/etc/resolv.conf` file to keep only the VPN Gateway-defined nameserver (one marked with `# Codespaces VPN Gateway` comment) |
10 | 24 |
|
11 |
| -> Extension suddenly stops working after some time and I see some stack traces in the console. |
| 25 | +### 🚩 Extension suddenly stops working after some time and I see some stack traces in the console |
12 | 26 |
|
13 | 27 | Most likely `SSH` connection was dropped or there was an intermittent network issue on your machine. The extension does not currently reconnects to the Codespace automatically. This will be fixed in the future. If this happens too often, please create a [Bug report](https://github.com/github/gh-net/issues/new?assignees=&labels=bug&template=bug_report.md&title=).
|
14 | 28 |
|
15 |
| -> I'm trying to send `Ethernet Datagrams`(L2 network layer) directly and expect those to be forwarded but they are not. |
| 29 | +### 🚩 I'm trying to send `Ethernet Datagrams`(L2 network layer) directly and expect those to be forwarded but they are not |
16 | 30 |
|
17 | 31 | The extension currently forwards `IP`(L3 network layer) traffic and above. If the datagrams contain `IP` packets that are addressed to a remote resource addressible from your local machine it should work. If it does not, please create a [Bug report](https://github.com/github/gh-net/issues/new?assignees=&labels=bug&template=bug_report.md&title=). If you want to send `Ethernet Datagrams` directly, please create a [Feature request](https://github.com/github/gh-net/issues/new?assignees=&labels=enhancement&template=feature_request.md&title=), we would love to know about your use case!
|
18 | 32 |
|
19 |
| -> I'm using some transport protocol that does not work. |
| 33 | +### 🚩 I'm using some transport protocol that does not work |
20 | 34 |
|
21 | 35 | Currently `TCP`/`UDP` and `ICMP` are supported. Other protocols should work but were not tested extensivelly. Please create [Bug report](https://github.com/github/gh-net/issues/new?assignees=&labels=bug&template=bug_report.md&title=) so we can address the issue.
|
22 | 36 |
|
0 commit comments