octoi client binds to specific IP even if 0.0.0.0 is specified
Even if the config file specifies 0.0.0.0 as the local address for the client, the socket apparently still gets bound to a specifid address at the time of the bind/connect.
udp 0 0 192.168.2.6:3333 188.8.131.52:10010 VERBUNDEN
This means that the OCTOI connection breaks as soon as the client gets a different IP address (e.g. by DHCP).
The odd part is that this doesn't happen on the server side. My socket looks like this:
udp 0 0 0.0.0.0:10010 0.0.0.0:*
Yup. This problem doesn't occur when the external dynamic IP (after NAT) changes. I've seen that happening multiple times without issue.
There is a problem however, when the internal IPv4 address (192.168.2.6) in this case changes. Easy fix: Don't do that/use a static IP.
I think the main problem here is the error handling: When this bug occurs, there's a send error for each packet, but osmo-e1d stays alive. Just exit/aborting the program would be OK here and result in better (overall) uptime.
strangely, looking at the various IPs reported by stats.retronetworking.org, I have the feeling that osmo-e1d octoi-client mode does work correctly for users behind dynamic IPs.
Any feedback from other users?
I haven't seen this issue with osmo-e1d in client mode.
[T-DSL]<->[Fritzbox with NAT]<->[Linux-router]<->[Linux-box with icE1usb/osmo-e1d]
The frequent dis-/reconnects since some time from my side are caused by other issues in my setup at the moment.