mirrors/dae
1
0
Fork 0
mirror of https://github.com/daeuniverse/dae.git synced 2025-07-21 21:31:14 +07:00
Code Issues Packages Projects Releases Wiki Activity

ci: add check-docs workflow (#93)

Browse Source 
* ci: add check-docs workflow

* chore: ignore node_modules

* chore(deps): add package-lock

* style: apply formatting

* style: apply formatting

* fix: fix typo

* fix: fix all proposed changes by markdown-lint

* fix: fix trailing spaces

* fix(troubleshooting.md): apply minor fi

* fix(getting-started): apply minior fix

* ci: dont' kick off build when changes made to check-doc.yml

* ci: ONLY kick off build when target workflow file changes

* trigger build

* fix(build.yml): fix syntax

* trigger build

* fix: fix broken syntax
This commit is contained in:
Kevin Yu
2023-05-21 00:41:44 +08:00
committed by GitHub
parent ae6667bb5d
commit eac04e991b
24 changed files with 10005 additions and 90 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
docs/getting-started/troubleshooting.md
View File

@ -1,8 +1,8 @@
# Troubleshooting
### Unknown bpf_trace_printk
## Unknown bpf_trace_printk
```
```console
invalid argument: unknown func bpf_trace_printk
```
@ -10,51 +10,51 @@ Solution:
Compile dae with CFLAG `-D__REMOVE_BPF_PRINTK`. See [build-by-yourself](build-by-yourself.md).
### PVE related
## PVE related
1. [PVE NIC Hardware passthrough](https://github.com/daeuniverse/dae/issues/43)
- [PVE NIC Hardware passthrough](https://github.com/daeuniverse/dae/issues/43)
### Binding to WAN but no network
## Binding to WAN but no network
**1. Troubleshoot local DNS service**
### Troubleshoot local DNS service
If you use `adguardhome`, `mosdns` in `dns` section, refer to [external-dns](external-dns.md).
**2. Troubleshoot firewall**
### Troubleshoot firewall
If you bind to wan, make sure firewall is stopped or `12345` is allowed by firewall. Don't worry about the security of this port because this port has its own firewall rule.
Usual firewalls on Linux:
```
```bash
ufw
firewalld
```
**3. Troubleshoot PPPoE**
### Troubleshoot PPPoE
dae does not support PPPoE yet. We are working on it. However, binding to LAN for other machines should work fine.
### Binding to LAN but bad DNS in other machines
## Binding to LAN but bad DNS in other machines
**1. Troubleshoot config of dae**
### Troubleshoot config of dae
Make sure you have bind to the correct LAN interfaces.
For example, if your use the same interface eth1 for WAN and LAN, write it as `wan_interface: eth1` and also in `lan_interface: eth1`. If the LAN interfaces you want to proxy are eth1 and docker0, write them both as `lan_interface: eth1,docker0`.
**2. Troubleshoot DNS**
### Troubleshoot DNS
To verify on another machine in LAN:
```
```bash
curl -i 1.1.1.1
curl -i google.com
```
If the first line has a response and the second line doesn't, check whether port `53` is occupied by others on dae's machine.
```
```bash
netstat -ulpen|grep 53
# or
# lsof -i:53 -n