SOunds like the gateway is firewalling (blocking) some IP port numbers* but not others, even in between LAN connections on the “inside” of your network.
I’m not used to american ISP connections, they seem weird (and overly controlled, I use whatever router I like on my ISP connections and always have).
I am not sure why you would need to be in “DMZ mode” unless you had another router after the ISP gateway: is the Orbi mesh system also a router?
If so then no, you should not be connecting your airlens or anything else apart from the internal router to your ISP gateway., which would conveniently fix your problem.
* e.g. web http traffic is port 80 by convention, https is 443, email is 25 etc. etc.
Something you need never think about, unless you are configuring a DMZ firewall.
TL;DR
If the Orbi system also routes as well as switches, then plug everything into the Orbi system and then run the orbi system to the gateway.
Thanks for that info John! Might take me a bit to digest and take action. I’m pretty sure the Orbi is a router, I know it can be, just not sure if it always is. It has one ethernet input and one output. I may have to try disconnecting everything from the gateway and run off the Orbi.
As I said, I’m not an IT type. I do a lot of things with a little bit of information, dangerous but I usually get to what I need. I know a lot of this information is out there, but I’m not always sure how to ask. Still not quite sure DMZ mode is. Always helpful when someone who can get through your confusion to the heart of the problem and provide a meaningful solution.
DeMilitarized Zone, comes from “the olden days” of internet where you have an external router, then in the DMZ you run things like web servers that you want the external world to access but which has limited access to all your other computers that all your company employees use, so that if a wrong 'un hacks your web server (which by its nature has to be exposed to the internet) they still can’t get to your “crown jewels” i.e. all your internal computer systems because between the DMZ and the internal LAN is another router.
Both internal and external routers have firewall rules that decide what traffic can get in and out from each zone.
So in your instance anything else connected to the ISP gateway is in the DMZ, so only has limited access back into your internal LAN (all the Orbi-connected stuff).
Like I said, this is guess work as I’m not familiar with the exact setup, but it still sounds like you should connect everything to the Orbi stuff, and not worry about having a direct connection: if it works, then go with it
Do you have DHCP turned on on both a base modem router (ATT Fiber) and on the Orbi? Or, is the Orbi in WAP (wireless access point) mode? If you have two devices giving out IP addresses in the house, then the address given out by the ATT might look like 192.168.0.xxx with a 0-point. Whereas the addresses given out by the Orbi might look like 192.168.1.xxx with a 1-point. Devices in the 1-pool like a phone running the MConnect app will not find devices like an AirLens that are ethernet wired in the 0-pool. Google items like “Orbi DHCP WA Mesh” and find someone else’s story that sounds like your house and see what their solution was.
As I understand it, any Roon Ready streamer like AirLens is running Roon RAAT, which is completely separate from Roon Core.
Lots of people have an Innuos Zen or Zenith and if you are using it next to your audio system by usb you are probably using both its server (Roon Core) and transport (Roon RAAT) services.
The nice thing about Innuos is you can use it purely as a server to AirLens or any other streamer, or as a Roon Ready transport alone with another server on the network, such as a QNAP, running Roon Core.
I’ve done all of these. There is no problem or in my experience difference in sound quality, all that matters is how well the usb output is implemented. Some companies, like Lumin, Innuos and SGM, focus on optimising usb over other formats, and various companies make external usb reclockers.
The Roon Core server software must always be on the network. It terms of performance - specifically mechanical and electrical noise - the music library can be on a separate server, and this can be a big advantage.
A NUC running Roon Core, yes, but you can (and we do) run it directly into your DAC. Or, as you suggest, an Innuos Roon End Point (RAAT) can connect to your DAC via USB.
While the Innuos runs some sort of off the shelf SBC that they put inside a nice box.
At the EOD, they are just two small computers connecting your DAC via USB. My point is, and remains, that USB is a very noisy means of connecting your DAC to a computer. Better if you can place an AirLens between the noisy outside world.
That was my primary complaint about my setup prior to the AirLens–I had to temporarily move my NUC near the audio system when the Bridge inside the DS Jr. died. I knew the incoming USB connection was cruddy, even with the USB cable I used (it was one of those which split the power leads from the data leads, so it needed to plug into two USB ports on the NUC) but it was either that or not have digital in my main system.
I see others elsewhere saying USB can be good but I don’t really believe that either. Schiit used to have the Wyrd, a USB “decrapifyer” (as they called it) which might have helped a little, but it still wasn’t isolation.
At any rate, the AirLens didn’t immediately hit me over the head as this gigantic stunning improvement, but it’s been more like an onion. I start hearing different improvements, like peeling back the layers of an onion, the longer I listen. At first I even thought it leaned a little towards sounding dark, only I realized that some of the brightness/harshness was due to the USB connection. The entire week, I’ve played it while working, and there are little things catching my attention as to how the sound has improved.
Carousel, I checked and both the gateway and the Orbi are acting as routers and are using DHCP. The Orbi uses IP addresses in the 10.0.0.x range so no conflict with the gateway. I think I will try wiring everything off the Orbi, I have most of the connections going to a switch so that should be easy. I do have a PC two floors up that is wired and I doubt the wire will reach the switch. Running a new wire is not something I look forward to.
Ok…so exactly which mconnect app should I be downloading? I have a choice of five in the Play Store. I just want a way to check the firmware–no need for a player.
Whatever I’ve already downloaded only times out when trying to access the AirLens. I was able to access it one time several days ago but ever since, I just get an error about a delay in response from the AirLens. I’ve also had to power cycle it to get DLNA working again.
Although given that firmware can be requested right from the AirLens via the WPS button, that would probably be the best way to go about it.
Mconnect control is the one you want. The HD version is for an iPad where you have a horizontal display, and that’s the one I use, without any issues. I assume the non-HD version is for phones or other small displays (never tried it).
One of the two mconnect Control versions is what you need for the Conversdigital board in the Airlens. Which one depends on the device you are using as a control.
OK, that second app (m Control) is working now. I don’t know what the deal is here, then, as I’d tried this same app a few days in a row and always got a timeout from AirLens. I also see where I can set up WiFi if I ever need to. Last time I got this to work, it didn’t give me all of this information.
I can see why the app gets such a terrible rating (2.5 stars). It seems to work when it feels like it. (Which is the same issue I had using it a few years ago–it’s fussy.)
(Which is the same issue I had using it a few years ago–it’s fussy.)