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

Using network interface altnames doesn't work #230

Open
hashworks opened this issue Jul 8, 2023 · 0 comments
Open

Using network interface altnames doesn't work #230

hashworks opened this issue Jul 8, 2023 · 0 comments

Comments

@hashworks
Copy link
Contributor

My main network interface has two altnames:

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether redacted brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    altname eno1

When I run a vopono session using -i eth0 it works just fine, but with the altnames -i eno1 or -i enp0s25 it doesn't (network connections just timeout).

Seems to be because the iptables forwarding expects the main interface name.

I guess this behavior should be documented.

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

1 participant