Muse Research

tjodoin · Post by **tjodoin** » Wed Feb 15, 2006 3:33 am

I'm noticing that tcp/ip settings don't persist if the receptor is powered up without a connection. Shouldn't the setting be saved and the configuration remain as set until intentionally changed? Using receptor OS 1.4.

Thanks.

gregh1 · Post by **gregh1** » Wed Feb 15, 2006 4:40 am

It's a bit odd... but Receptor WILL revert to the TCP/IP settings you entered, once you re-connect to your network and power up again.

tjodoin · Post by **tjodoin** » Wed Feb 15, 2006 2:39 pm

Yeah, I've encountered that. Still with something like a crossover connection, you also need to reboot the laptop as well. I've tried refreshing the connections (ipconfig /renew on WinXP) but that works intermittenly at best. Seems you have to renew at the point that the receptor DHCP will accept requests. If that window is missed during bootup, the receptor gets confused and assigns itself some bizzare IP. Just doesn't make sense why it is dependent on the connection being present at boot up. The DHCP server should just be running if crossover mode is selected. This doesn't occur on Linux, Windows, etc. network configs. If maximizing performance is the issue, then maybe it's best to have an option in setup to turn off networking if not needed but keep the configuration stored for when it's enabled again. Both WinXp and Linux support enabling/disabling network services without requiring a reboot so I'm not sure why it's implemented like this on the Receptor OS.

gregh1 · Post by **gregh1** » Wed Feb 15, 2006 4:15 pm

I've set my Receptor to use a fixed IP (e.g. 192.168.0.XX). I've always preferred fixed addresses rather than DHCP for my office setup. Right now, I'm using a crossover cable, but I'll add another hub next. I connect the crossover between the PC and the Receptor, then boot the Receptor. It only bugs me if I boot before connecting - the hub should solve that, since Receptor would always be connected.

Hybernation · Post by **Hybernation** » Wed Feb 15, 2006 5:06 pm

gregh1 wrote:I've set my Receptor to use a fixed IP (e.g. 192.168.0.XX). I've always preferred fixed addresses rather than DHCP for my office setup. Right now, I'm using a crossover cable, but I'll add another hub next. I connect the crossover between the PC and the Receptor, then boot the Receptor. It only bugs me if I boot before connecting - the hub should solve that, since Receptor would always be connected.

Indeed it does. I have mine set to fixed IP using a gigabit switch and I have never had the problems you speak of with forgetting the IP when things aren't connected. Like you say, the switch will always be connected.

tjodoin · Post by **tjodoin** » Wed Feb 15, 2006 5:35 pm

That's definitely a work around thanks. While it's great if you already have the hardware though, I don't think requiring it to make sure your TCP/IP settings persist is a valid solution. Maybe Muse can add this to the bug list?

Bryan@MuseResearch · Post by **Bryan@MuseResearch** » Thu Feb 16, 2006 6:21 pm

Consider it added... I haven't personally experienced this, but we'll definitely look into it.

Thanks

Bryan

Briggity · Post by **Briggity** » Sat Feb 18, 2006 12:28 am

I can confirm that I'm having problems with TCP/IP settings not being stored.
Even after switching both Receptors to Manual IP addressing, they will boot up with the wrong settings if ethernet is not connected to my computer.

brian

Bryan@MuseResearch · Post by **Bryan@MuseResearch** » Sat Feb 18, 2006 1:15 am

Wait a second gang... I think you are reporting behavior that is normal...

The entire nature of AUTO DHCP mode is that the addresses are dynamic. There is a query and negotiation routine that happens after power on, and only then does a Receptor get an address. That address is dynamic and reassignable by the DHCP server, in other words, that address will NEVER be memorized or saved. That's the whole point of AUTO DHCP. There theoretically could be a different TCP/IP address every time the unit boots up, assuming that other components in the network have changed.

In MANUAL mode, the address SHOULD be saved, and if it isn't then there is a bug, assuming of course that you entered the TCP/IP address, entered the subnet address, and then selected YES from the ARE YOU SURE? query that follows an address change. I've checked this behavior on a couple of Receptor around the office, and they all properly retain their manual TCP/IP settings.

In crossover mode, Receptor basically issues the TCP/IP addresses, so they will always be the same.

So if you are not seeing the TCP/IP settings retained in AUTO DHCP mode, that is normal behavior. In fact, the TCP/IP address field will be blank until such time as the network comes alive and all hosts have finished their negotiation. Then, as if by magic, the new dynamically assigned address will appear.

Is anyone losing TCP-IP addresses in manual mode? That is abnormal behavior and I'd really like to know about it...

thanks

bryan

gregh1 · Post by **gregh1** » Sat Feb 18, 2006 1:55 am

I'm using manual TCP/IP settings, and Receptor DOES retain the address upon each bootup. Of course, it will only USE my settings if the network cable is plugged in before power on.
But it's annoying if I forget to plug in the network cable, because Receptor won't revert to my configuration if I plug in AFTER booting. That's what I'd like to see fixed, if it can be.

tjodoin · Post by **tjodoin** » Sat Feb 18, 2006 3:49 am

The nature of DHCP is that client addressing is dynamic. The server address is not. If it was completely dynamic then you would basically have two clients trying to request addresses from each other. Whether or not the hardware connection is established at boot up, the DHCP server still should know it's own address, network and the address pool it has available for devices when they connect and make the request to join the network. I think this is what should be happening when the receptor is set to crossover mode (where it is the DHCP server) but the absence of a connection at bootup causes problems. Does the ethernet card on the receptor get disabled if no connection is present at bootup? If so, maybe the problem lies in the way networking services are brought online if the ethernet card is returned to service after the receptor is booted.

Bryan@MuseResearch · Post by **Bryan@MuseResearch** » Sat Feb 18, 2006 5:47 am

Receptor does require that Ethernet is connected at power up. And Ethernet services are only started and stopped at power up / power down. You are correct that Receptor in the absence of a connection will be confused and not acquire and address after the Ethernet services have started. I suppose we can address this issue in a future software update, but the Ethernet services are all very low level so it would have to be part of a major software update...

tjodoin · Post by **tjodoin** » Sat Feb 18, 2006 6:22 pm

Thanks Bryan for the confirmation.

Muse Research

KVR Audio

TCP/IP Settings