dolodobendan wrote: > Not surprising, actually. For whatever reason, the transport wasn't able > to get a "new" IP address, so it got that "strange" IP address, probably > 169.254.somethingsomething). Rebooting the router (which presumably also > is your DHCP server) may have fixed an issue with its DHCP server while > power-cycling the transporter may have fixed if there was an issue.No, the > strange adres was a regular but in use as a static ip adres of another device outside the dhcp scope. I.e. it shouldn't have had gotten that adress.
*SqueezeBoxes:* 1x Transporter (Living room) 1x SB2 (shed), 1x Radio (Kitchen), 1x Boom (Dining room), 1x piCorePlayer (jacuzzi), 1x piCorePlayer (Garden) 1x OSMC + Squeezelite (Movie room), 1x Touch (Study 2), few spare unit's *Server:* LMS on Pi3 7.9.1. on PcP 3.21 *Network:* AVM Fritzbox, Netgear Smart Switch 24p, 3x Ubiquity ------------------------------------------------------------------------ edwin2006's Profile: http://forums.slimdevices.com/member.php?userid=66926 View this thread: http://forums.slimdevices.com/showthread.php?t=113127 _______________________________________________ Duet mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/duet
