-
Notifications
You must be signed in to change notification settings - Fork 84
Issues: containers/netavark
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
network interface/firewall rules leaked after aardvark-dns start error
kind/bug
#1121
opened Nov 7, 2024 by
stuartm
Redeploying containers with macvlan + static IP does not inform of the new mac address
kind/feature
#1114
opened Oct 31, 2024 by
jerome59
macvlan network option metric doesn't change the metric with dhcp
kind/bug
#1073
opened Sep 5, 2024 by
literatesnow
network driver macvlan does not receive an ipv6 address from dhcp
kind/feature
#1072
opened Sep 2, 2024 by
TrevorBenson
Add port
53/udp
by default to netavark_zone
so default networks can use DNS
#1056
opened Aug 12, 2024 by
flouthoc
Aardvark doesn't get started in rootless mode on a system with system-wide but not per-user systemd
#1047
opened Aug 4, 2024 by
Orochimarufan
Container with podman network not receiving UDP traffic
kind/bug
#1045
opened Aug 1, 2024 by
booleanvariable
DHCP proxy - no available capacity / crash when using external DHCP service
#1024
opened Jul 12, 2024 by
jjzazuet
Container with network alias containing a space causes aardvark-dns crash
#1019
opened Jul 4, 2024 by
l-austenfeld
Cannot resolve container hostnames in internal network
kind/bug
network
#1055
opened May 25, 2024 by
jorti
RFE: firewall combine setup_network and setup_port_forward into one function
#957
opened Apr 3, 2024 by
Luap99
Attaching container to a network with any routes defined results in fail
kind/feature
#930
opened Feb 19, 2024 by
CDFN
Previous Next
ProTip!
Follow long discussions with comments:>50.