EtherREGEN: Installation, Usage, Difficulty, Questions thread

[emailists]

After reading this thread a bit more I see I probably have to set a static IP for my bridge  card 

 

I am finding  Jriver frequent disconnects from the Directstream/Bridge 2, (it was very stable previously and if it did disconnect, quitiing and relaunching app fixed the issue)

 

I’m using the ER connected to my Mac Pro 2013 tower using mac’s second Ethernet port.

 

if I unplug the power from the ER for a few seconds, Jriver finds the bridge card.

 

I have no other devices on the ER.

[thyname]

17 hours ago, soares said:

Hi guys, will someone help me with the right SFP module to use with the eR? 
Tks Jorge

I had purchased this, before EtherRegen arrive. From Sonore website 

[Bones13]

I have used static IP addresses for my networked audio gear ever since learning how to do so. I did find issues, not with the drop outs being talked about here, but rather there has been a some audio software, in the past that could not find the hardware if the IP changed due to lease loss and power disturbances. Of course, turning everything off, then on, would fix things, but that gets tiring.

 

etherRegen, being an simple switch (not managed) does not get its own IP address, correct? Planning my static IP table, my Roon Core running NAS is already running with a fixed IP.

 

My etherRegen is in the second batch.

[soares]

12 minutes ago, thyname said:

I had purchased this, before EtherRegen arrive. From Sonore website 

Tks. I also ordered spare  one when I bought my oM, but it doesn’t seem to be working. Will try again! 

[thyname]

5 minutes ago, soares said:

Tks. I also ordered spare  one when I bought my oM, but it doesn’t seem to be working. Will try again! 

Hmmm... it works fine with me. Worked from the start.

 

Issues with yours could be:

 

1 - What are you feeding it with? Gigabit or fast speed? How is the connection done?

 

2 - Are you using a matching fiber cable?

 

From EtherRegen user manual:

——

Only Gigabit LC-optical or copper interface modules are compatible with the SFP cage of the EtherREGEN. They can be SX multi-mode, LX multi-mode, or LX single- mode, as long as they are Gigabit and match what is used at the other end of the optical cable.
The modules at each end can be from different manufacturers as long as their type and mode specifications match. While some manufacturer’s switches work only with special “branded” SFP modules, that is just an ID code stored in the module. The EtherREGEN ignores this code so any Gigabit SFP module can be used regardless of manufacturer code.

——

 

To recap: that SFP module works with EtherRegen. Confirmed. Something else is going on

 

[dminches]

12 hours ago, Nenon said:

 

@dminches - Since I did not have time today to complete your other request, can I help troubleshooting this? 

 

First, and most importantly, can you install an app called "Fing - Network scanner" on your IOS device? It would scan your network and find your Roon Server. Next time this happens, can you try to ping the Roon Server from Fing? Also, try to ping your ultraRendu at the same time.

 

Second, would it be possible to remove the Trendnet Switch and connect everything to the etherREGEN? Less things, easier to troubleshoot.

 

Third, some reports earlier pointed out to a power supply problems and/or network cable problems. Just to reduce the number of variables, can you confirm if the problem still happens with the stock power supply? And if you have any other ethernet cables to test would be nice. This may even sound like a stupid suggestion... it does not make any sense to me, but just to avoid some really really odd stupidly crazy scenario.

 

I think my initial issues were described well by John S.  When I hooked up the ultraRendu to the ER it was given a new IP address.  It tooks a little while for the Roon server to find it.

 

Now that my setup is stable so is my connection.

 

I am actually still using the stock PS.  The diagram shows a Channel Islands Audio PS which I ordered.  I was too lazy to put in the actual current configuration.

 

Thanks for your help with this.

 

[Superdad]

1 hour ago, soares said:

Tks. I also ordered spare  one when I bought my oM, but it doesn’t seem to be working. Will try again! 

Hi Jorge:

(Note that I have moved your question and related answers out of the Listening Impressions thread and into this one.) 

 

Make sure that your SFP modules are fully inserted. They might seem so but go ahead and push in a bit harder.

Previously I did not have a lot of experience with LC type SFP modules. But during EtherREGEN Q.C. testing we at first would often encounter a board where it seemed the SFP would not data connect. Even though it seemed like the module was fully inserted, pushing it in a little harder got it working fine.

 

That’s all I can think of for you. Assuming of course that you have matching modules at both ends and the correct type of fiber cabling. 

[Ricardo007]

There is also some recommendation for SFP modules on whatbestforum from taiko audio

https://www.whatsbestforum.com/threads/taiko-audio-sgm-extreme-the-crème-de-la-crème.27433/page-46#post-587473

[soares]

29 minutes ago, Superdad said:

Hi Jorge:

(Note that I have moved your question and related answers out of the Listening Impressions thread and into this one.) 

 

Make sure that your SFP modules are fully inserted. They might seem so but go ahead and push in a bit harder.

Previously I did not have a lot of experience with LC type SFP modules. But during EtherREGEN Q.C. testing we at first would often encounter a board where it seemed the SFP would not data connect. Even though it seemed like the module was fully inserted, pushing it in a little harder got it working fine.

 

That’s all I can think of for you. Assuming of course that you have matching modules at both ends and the correct type of fiber cabling. 

Tks Alex! Just discovered that if I connected it to my router it works! The problem seems to be related exclusively when It is connected to the Cisco. 
So:

i) router >(copper) > oM > (fiber) > eR > (copper) > uR - ok

ii) router > (copper) > Cisco (copper) > oM> (fiber) > eR > (copper) >uR - no connection ( the light in the rj45 port is off)

iii) router > (copper) > Cisco> (fiber) > oM > (copper) > uR - ok

Cheers Jorge

[thyname]

34 minutes ago, soares said:

Tks Alex! Just discovered that if I connected it to my router it works! The problem seems to be related exclusively when It is connected to the Cisco. 
So:

i) router >(copper) > oM > (fiber) > eR > (copper) > uR - ok

ii) router > (copper) > Cisco (copper) > oM> (fiber) > eR > (copper) >uR - no connection ( the light in the rj45 port is off)

iii) router > (copper) > Cisco> (fiber) > oM > (copper) > uR - ok

Cheers Jorge

Cisco is most likely NOT gigabit

[soares]

30 minutes ago, thyname said:

Cisco is most likely NOT gigabit

You’re right. Just the fiber port. It’s explained! 
Thank you for your support. Best Jorge 

[esmit]

I also have connectivity problems. Both my ultraRendu and microRendu, and a Chromecast Audio that all are connected to the etherRegen get lost... All reserved ipadresses. 

[jcn3]

6 minutes ago, esmit said:

I also have connectivity problems. Both my ultraRendu and microRendu, and a Chromecast Audio that all are connected to the etherRegen get lost... All reserved ipadresses. 

Can you provide a full description of your network?

[esmit]

Isp Router connected to etherRegen, 8 port switch, Philips hue, netgear Access Point. 8 port Switch to Roon Server, TV, Shield TV and IKEA tradfri.  Netgear access point to other unrelated server and Microsoft Dock.

 

The etherRegen replaced a netgear 5 port switch which is not used now anymore.

 

Uptone 36 w power bricks for etherRegen, lps 1 powering microrendu, lps 1.2 powering ultraRendu, network power combo thing powering the chromecast audio.

 

Rebooting the Isp router seems to work for a while. 

[Bernstein]

Does anybody have an issue with sonictransporter as Roon Core with the ER? It disconnects very often, so I am switching back to my old switch. 
 

Router and sonictransporter connected on A side, DigiOne Signature on B side. I can access the DigiOne, but the sonictransporter is not available. Firmware needs improvements...

[soares]

Not yet but I will try later. Currently using my zen mkiii. I’ve got a STi5

[thotdoc]

This has occurred two times: The entire system has been idling. I go to play music and Roon shows that it is playing or doing something as the little bars next to the song I'm trying to play are moving up and down, but the music does not play and the indicator of the music playing is not moving across the bottom of the screen.

 

the set up is Cisco 2690 switch into 15 Sonic transport into ER into Optical Rendu into DAC.

 

The last time this occurred I rebooted the entire chain and it worked.

 

Help please

[Dutch]

16 hours ago, JohnSwenson said:

Hi Dutch,

Yes I have extensively tested multicast and mDNS, they both work fine in every scenario I've tested.

 

BTW, there is only one switch in the EtherREGEN--in the A side. One of the ports on the A side switch sends data through the "special sauce" which goes into a format converter which is not a switch. Whatever packets come in go out without any modification.

 

John S.

Hi John, that’s good to hear and thanks for elaborating on the ER internals. I hope to receive my ER coming Monday (this time I’m staying home to not miss the delivery guy until it’s here 😀). If I run into any issues I’ll do some in depth troubleshooting.

 

For now (besides having a good weekend) I wish you and Alex the best of luck in troubleshooting the issues some have. I know how hard this can be especially when there’s no way to have some ‘hands on time’ with these remote client systems.

[Bernstein]

47 minutes ago, soares said:

Not yet but I will try later. Currently using my zen mkiii. I’ve got a STi5

ok...now I have put the ER aside. Feeling like beta tester, as much as I like Uptone and the guys behind. 

[skatbelt]

1 hour ago, Bernstein said:

Does anybody have an issue with sonictransporter as Roon Core with the ER? It disconnects very often, so I am switching back to my old switch. 
 

Router and sonictransporter connected on A side, DigiOne Signature on B side. I can access the DigiOne, but the sonictransporter is not available. Firmware needs improvements...

 

I had the same with Roon Core on a Mac mini (macOS High Sierra) on the A side with a dCS Network Bridge on the B side. The dCS stayed accessible after the Mac mini disappearing from the network. Setting the network speed in macOS manually to 100BaseTX (full duplex) seemed to cure it. It now runs more than a day without problems. I don't know if it is possible to set this variable manually with your sonicTransporter.

[thotdoc]

2 hours ago, thotdoc said:

This has occurred two times: The entire system has been idling. I go to play music and Roon shows that it is playing or doing something as the little bars next to the song I'm trying to play are moving up and down, but the music does not play and the indicator of the music playing is not moving across the bottom of the screen.

 

the set up is Cisco 2690 switch into 15 Sonic transport into ER into Optical Rendu into DAC.

 

The last time this occurred I rebooted the entire chain and it worked.

 

Help please

If I reboot the entire system from the switch to the renderer works again.  I tried just rebooting the sonic transport and that didn't work. So I rebooted the whole chain.

[jcn3]

4 hours ago, esmit said:

Isp Router connected to etherRegen, 8 port switch, Philips hue, netgear Access Point. 8 port Switch to Roon Server, TV, Shield TV and IKEA tradfri.  Netgear access point to other unrelated server and Microsoft Dock.

 

The etherRegen replaced a netgear 5 port switch which is not used now anymore.

 

Uptone 36 w power bricks for etherRegen, lps 1 powering microrendu, lps 1.2 powering ultraRendu, network power combo thing powering the chromecast audio.

 

Rebooting the Isp router seems to work for a while. 

Can you put the Roon server and the Rendus all on the ER?

 

What kind of switch is the 8 port switch? How did you have the 8 port switch connected to the ER (what on what side)? (Most issues seem to be because of trying to put gigabit connections on the B side)

[dctom]

On 11/15/2019 at 6:39 PM, JohnSwenson said:

For all of you having problems with droputs and disconnections I think I have figured out what is happening. A little background first: the endpoints most people use get an IP address from a DHCP server on your network (usually in the router). The DHCP server creates a "DHCP lease" which itsends to the endpoint, this contains an IP address and a range of time it is good for. When a music server connects to the endpoint (each protocol does this part differently) the endpoint sends this IP address to the server, which then uses it to talk to the endpoint.

 

The fun part happens when the lease expires, the endpoint then goes back to the DHCP server and says "renew my lease", in most situations the DHCP server will give it back a new lease with the same IP address it gave it the first time. BUT sometimes the new lease contains a different IP address, this is what causes the problem. The server keeps on sending the audio data to the old address, but the endpoint doesn't get it because it now has a different address. The music data goes into Ye Olde Bit Bucket.

 

Somehow the music server has to get the new IP address of the endpoint. There are a few ways of doing this:

turn off the endpoint then turn it back on (unplug it, many endpoint's power switch just puts them in low power mode), sometimes this may need to off for 10 to 15 minutes.

 

Unplug the Ethernet cable for 10 to 15 minutes.

 

Reboot the music server

 

This gets the server back talking to the endpoint.

 

In many instances this is all that is required, from then on the DHCP coninues to renew the lease with the same address it gave out the second time.

 

For some systems it might take two times for the DHCP server to settle down.

 

 

 

Tried this procedure and it set a new (local) ip address and worked for awhile but then lost internet and Jriver connection.

 

Have now reconnected my TP-link switch and have Nas, server, router and ethernet to ER "A" side all connected  into the switch - then  "B" side of ER to end point. This has been working fine all day - I don't think this arrangement compromises the regen - or is another link in the chain not a good idea?

 

Something I have noticed, running AL on server and end point, having the monitor panel open on both machines it shows the status of the cpu etc. It also shows the same local ip address in each panel which is different to the router assigned address. I am assuming this is the LAN?  it is this indicator that has informed me, visually, of disconnections.

 

 

 

 

[Bernstein]

2 hours ago, skatbelt said:

 

I had the same with Roon Core on a Mac mini (macOS High Sierra) on the A side with a dCS Network Bridge on the B side. The dCS stayed accessible after the Mac mini disappearing from the network. Setting the network speed in macOS manually to 100BaseTX (full duplex) seemed to cure it. It now runs more than a day without problems. I don't know if it is possible to set this variable manually with your sonicTransporter.

ok unfortunately not an option for this within sonictransporter...but your setup is the same as mine meaning that the endpoint was still accessible and the core not. 

 

I mean: shouldn’t it be usable without adjustment. We are speaking about an unmanaged switch. I don’t want to be hard on them, as I know how hard they work to achieve perfection. I trust @Superdad @JohnSwenson that they will find a solution eventually. Still frustrating...

[rogerdn]

On 11/15/2019 at 1:39 PM, JohnSwenson said:

For all of you having problems with droputs and disconnections I think I have figured out what is happening. A little background first: the endpoints most people use get an IP address from a DHCP server on your network (usually in the router). The DHCP server creates a "DHCP lease" which itsends to the endpoint, this contains an IP address and a range of time it is good for. When a music server connects to the endpoint (each protocol does this part differently) the endpoint sends this IP address to the server, which then uses it to talk to the endpoint.

 

The fun part happens when the lease expires, the endpoint then goes back to the DHCP server and says "renew my lease", in most situations the DHCP server will give it back a new lease with the same IP address it gave it the first time. BUT sometimes the new lease contains a different IP address, this is what causes the problem. The server keeps on sending the audio data to the old address, but the endpoint doesn't get it because it now has a different address. The music data goes into Ye Olde Bit Bucket.

 

Somehow the music server has to get the new IP address of the endpoint. There are a few ways of doing this:

turn off the endpoint then turn it back on (unplug it, many endpoint's power switch just puts them in low power mode), sometimes this may need to off for 10 to 15 minutes.

 

Unplug the Ethernet cable for 10 to 15 minutes.

 

Reboot the music server

 

This gets the server back talking to the endpoint.

 

In many instances this is all that is required, from then on the DHCP coninues to renew the lease with the same address it gave out the second time.

 

For some systems it might take two times for the DHCP server to settle down.

 

Another option is to make sure the address of the endpoint never changes, there are two ways to do this:

set a static IP address on the endpoint. Not all endpoints allow you to do this.

Set a reserved IP address on your DHCP server, almost all allow you to do this, the endpoint still asks for a lease or renewal, but you reserve a specific address for that specific endpoint, the DHCP server HAS to always use that one.

 

Most people's system do not have the problem in the first place. For the ones that potentially do have this issue there seems to be some sort of trigger that causes the DHCP server to behave this way, it usually has to do with something "new" in the system. A new endpoint will almost always trigger this. Sometimes the same endpoint but with a different configuration, or a network with a significant change. Simple switches will usually not trigger this, but managed switches (or different configuration of the same switch) being added, or taken out can also trigger this.

 

So while this seems to happen when you add the EtherREGEN it is probably not anything inherently wrong with the EtherREGEN, but rather that you have significantly changed your network topology that is somehow triggering this behavior in t your DHCP server.

 

Ether just living with it until the DHCP server settles down or clamping down the IP address of the endpoint should get rid of the issue. If you want to spend time playing with different network configurations, endpoints etc, I would recommend you reserve the IP address of your endpoint so the DHCP server cannot mess you up in the future.

 

Note: I do not know exactly what the triggers are or exactly how the DHCP server determines when something is "new". And most likely different models behave differently. So please don't ask questions like "will my system have this problem?" "Exactly what do I do if I have it?" "Which router should I buy so it won't happen to me?" I don't know the answers to those questions. Tomorrow I probably will not know the answers either. So please don't ask.

 

What I know about it is already in this post.

 

If you do have the problem and you follow the advice above and it does not go away, please post THAT, we will try and get to the bottom of it.

 

John S.

I had this issue with my DirectStream, first dropout was after 10 minutes, next at 24 hours, at that point I repowered the EtherREGEN and it’s been fine going on a week now.