Bug: Local network IP not detected correctly
Posted: Tue May 14, 2013 5:16 pmHello,
I have problems reaching my subsonic.org redirect in the local network because the local ip of my subsonic host is not detected correctly.
I even changed my configuration to listen only on the right interface, but that didn't change anything. My /etc/network/interfaces is configured as follows:
As you can see, I have two network cards. One only for communicating with the USV if the power is down, and the regular network interface. Note that the USV-Network doesn't even have a gateway set as it is only connected to one host and there is no routing going on whatsoever in this network.
However, for some reason, Subsonic decides that 192.168.1.2 must be the correct local IP and tries to connect to it, which of course fails.
I would be very grateful if you could point me to how to fix this (if possible) or if you could improve the detection or enable a manual override for the internal ip in the next release.
TIA
schichtleiter
I have problems reaching my subsonic.org redirect in the local network because the local ip of my subsonic host is not detected correctly.
I even changed my configuration to listen only on the right interface, but that didn't change anything. My /etc/network/interfaces is configured as follows:
- Code: Select all
# Local
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 10.0.0.3
netmask 255.255.255.0
network 10.0.0.0
broadcast 10.0.0.255
gateway 10.0.0.1
# USV
auto eth1
allow-hotplug eth1
iface eth1 inet static
address 192.168.1.2
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
As you can see, I have two network cards. One only for communicating with the USV if the power is down, and the regular network interface. Note that the USV-Network doesn't even have a gateway set as it is only connected to one host and there is no routing going on whatsoever in this network.
However, for some reason, Subsonic decides that 192.168.1.2 must be the correct local IP and tries to connect to it, which of course fails.
I would be very grateful if you could point me to how to fix this (if possible) or if you could improve the detection or enable a manual override for the internal ip in the next release.
TIA
schichtleiter