nicox 2 Posted August 5, 2018 Posted August 5, 2018 (edited) Hello, I create a fresh server for emby. However, using netstat, I can see that emby only binds the loop back ipv6 interface for classical port 8096. However, I don't run ipv6 in my network. Is it possible to change it to one of the ipv4 interface ? Not using the web interface since I don't have access to it because of it . I have 2 interfaces : Lo 127.0.0.0/8 ipv6 stuff Eth0 local ip/24 I would like to bind it to the Eth0 ipv4 address. Thank you Edited August 5, 2018 by nicox
Luke 42078 Posted August 5, 2018 Posted August 5, 2018 Hi, it's not that we're binding specifically to ipv5, rather we bind to 0.0.0.0 which handles all ip addresses, including ipv4. Please let us know if this helps. Thanks.
nicox 2 Posted August 5, 2018 Author Posted August 5, 2018 Ok, in this case, why isn't it binding to other ip address ? What can I do to make it work ? I only did a simple install. I tried with a Centos VM and a Ubuntu Server VM and it was exactly the same.
Luke 42078 Posted August 5, 2018 Posted August 5, 2018 It doesn't bind to any specific address, rather it binds in a way that allows it to receive on all addresses.
pir8radio 1312 Posted August 5, 2018 Posted August 5, 2018 (edited) How is your vm setup? how is its nic tied to the host nic? Edited August 5, 2018 by pir8radio
nicox 2 Posted August 6, 2018 Author Posted August 6, 2018 I created a virtual bridge on Host that binds to the physical interface. The vm binds to this virtual bridge. In the vm I have 2 interfaces, the "lo" interface and eth0. Eth0 is the interface with the lan IP address. For example ssh binds correctly to it (I can access the vm from the LAN). It looks Indeed like a VM issue since creating another vm gives the same result. But I have no idea on what to do.
nicox 2 Posted August 7, 2018 Author Posted August 7, 2018 For information, when a service is binded to 0.0.0.0, the netstat commande only show the IPv6 loopback bind. Better explained here : https://unix.stackexchange.com/questions/152612/netstat-why-are-ipv4-daemons-listening-to-ports-listed-only-in-a-inet6 Thus, my problem is solved.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now