Jump to content
RESET Forums (homeservershow.com)

Luma behind Sophos UTM


cmccomas
 Share

Recommended Posts

Hi guys and gals, new listener to the pod cast and first time posting here.  Anyway I finally took delivery of my Luma 3 pack.  So far it’s been a bit bumpy road like the rest of you. I can vouch for it’s speed when it’s actually working!  I have mine setup behind a Sophos UTM, I allow TCP 4242, TCP 4505 and TCP 4506 out so that they can connect back to the cloud.  The odd thing is that they seem to be working in bridge mode!  This is something I want them to do but it’s something I don’t think they should be doing with this current firmware. Is anyone else getting behavior like this? Any ideas as to why?  I also get about 3 days of use before they decide to lock up.  Not sure if this is a bug in the internet pause feature or they just wonk out.  It doesn’t kill my wired network traffic just the wifi. The only way to restore connectivity is to unplug them one at a time. Just for the record I have not used the pause feature so it is not user error on my part!

 

Side note, I see a lot of dropped packets in the logs of Sophos and backup pfSense box.  I will snoop around in the log files and check wireshark this weekend and see what I can see.  Anyone have any ideas/solutions or similar experiences?

 

 

 

 

Link to comment
Share on other sites

Hi guys and gals, new listener to the pod cast and first time posting here.  Anyway I finally took delivery of my Luma 3 pack.  So far it’s been a bit bumpy road like the rest of you. I can vouch for it’s speed when it’s actually working!  I have mine setup behind a Sophos UTM, I allow TCP 4242, TCP 4505 and TCP 4506 out so that they can connect back to the cloud.  The odd thing is that they seem to be working in bridge mode!  This is something I want them to do but it’s something I don’t think they should be doing with this current firmware. Is anyone else getting behavior like this? Any ideas as to why?  I also get about 3 days of use before they decide to lock up.  Not sure if this is a bug in the internet pause feature or they just wonk out.  It doesn’t kill my wired network traffic just the wifi. The only way to restore connectivity is to unplug them one at a time. Just for the record I have not used the pause feature so it is not user error on my part!

 

Side note, I see a lot of dropped packets in the logs of Sophos and backup pfSense box.  I will snoop around in the log files and check wireshark this weekend and see what I can see.  Anyone have any ideas/solutions or similar experiences?

Welcome to the forums!

 

1. I would allow all outbound traffic from Luma, I would not restrict it in anyway. I have mine setup on a DMZ because I need to keep the FiOs router in place.

 

2. What makes you think Luma is setup in 'bridge mode' ?

 

3. What is the subnet or IP address of a device connect to Luma? Also in the Luma app on the main page if you tab on one of the connected Luma's it will give you the IP address of the Luma, Please tell me what that is. If its 192.168.55.x its not in 'bridge mode' Luma says there going to add support for it but like everything else Luma there no ETA.

 

4. As for the lockups, Are you you using Ethernet backhaul or wireless mesh on the two nodes?

 

5. Do you have any restrictions set on the default user profile and if yes what rating is it set on?

 

6. Did you setup users and add devices for those users and if yes what is the filter rating set to?

 

7. Does the lockup happen for all users?

Edited by itGeeks
Link to comment
Share on other sites

Welcome to the forums!

 

1. I would allow all outbound traffic from Luma, I would not restrict it in anyway. I have mine setup on a DMZ because I need to keep the FiOs router in place.

 

2. What makes you think Luma is setup in 'bridge mode' ?

 

3. What is the subnet or IP address of a device connect to Luma? Also in the Luma app on the main page if you tab on one of the connected Luma's it will give you the IP address of the Luma, Please tell me what that is. If its 192.168.55.x its not in 'bridge mode' Luma says there going to add support for it but like everything else Luma there no ETA.

 

4. As for the lockups, Are you you using Ethernet backhaul or wireless mesh on the two nodes?

 

5. Do you have any restrictions set on the default user profile and if yes what rating is it set on?

 

6. Did you setup users and add devices for those users and if yes what is the filter rating set to?

 

7. Does the lockup happen for all users?

 

Hi itGeeks,

 

 

1.  I'll give it a try in a DMZ honestly didn't think to try that!

 

2.  When I first power them on and my client (iPhone) connects I'm given a 192.168.55.0/24 address.  If I wait a min or two and then re-connect I'm popped onto 192.168.1.0/24  my normal network. It then works for a few days without a hitch and then hangs up.  I see some IGMP traffic getting blocked but I think this is the luma to luma traffic on multicast.

 

3. When I first power it on clients are given the 192.168.55.0/24 address.  Then after a min to two it starts handing out 192.168.1.0/24 addresses?!  Not sure what's going on. The IP addresses of the Luma's are listed as 192.168.55.0/24 in the app.  specifically .1, .4 and .5.

 

4.  I'm using Ethernet backhaul on all 3 nodes.  Looks like they are communicating as I see multicast traffic on the network.

 

5. I did set up two profiles for my wife and myself and both are set to unrestricted.  Default policy is unrestricted as well.

 

6.  I added a few devices to each user but most of the devices are unassigned.  Filtering for everything is unrestricted.  Didn't seem to work anyway when I tested it with an adult site!

 

7. Yes all wireless users!  I can still reach it from the app if I drop to cellular data on my phone.  Tried to pause and un-pause in the app but that didn't help much.  All my wired devices continue to work fine.

 

Any ideas?!  I'll try popping it into the DMZ and see if that helps.  Thanks again for your time!

 

 

Link to comment
Share on other sites

Hi itGeeks,

 

 

1.  I'll give it a try in a DMZ honestly didn't think to try that!

 

2.  When I first power them on and my client (iPhone) connects I'm given a 192.168.55.0/24 address.  If I wait a min or two and then re-connect I'm popped onto 192.168.1.0/24  my normal network. It then works for a few days without a hitch and then hangs up.  I see some IGMP traffic getting blocked but I think this is the luma to luma traffic on multicast.

 

3. When I first power it on clients are given the 192.168.55.0/24 address.  Then after a min to two it starts handing out 192.168.1.0/24 addresses?!  Not sure what's going on. The IP addresses of the Luma's are listed as 192.168.55.0/24 in the app.  specifically .1, .4 and .5.

 

4.  I'm using Ethernet backhaul on all 3 nodes.  Looks like they are communicating as I see multicast traffic on the network.

 

5. I did set up two profiles for my wife and myself and both are set to unrestricted.  Default policy is unrestricted as well.

 

6.  I added a few devices to each user but most of the devices are unassigned.  Filtering for everything is unrestricted.  Didn't seem to work anyway when I tested it with an adult site!

 

7. Yes all wireless users!  I can still reach it from the app if I drop to cellular data on my phone.  Tried to pause and un-pause in the app but that didn't help much.  All my wired devices continue to work fine.

 

Any ideas?!  I'll try popping it into the DMZ and see if that helps.  Thanks again for your time!

Something is very wrong with your setup then, Luma does not support 'bridge mode' at this time, It is something they say will be added later via a firmware update with no ETA. Do you have any other WAP's active other then Luma?

 

Could you explain your setup starting with the line coming into your house?

Link to comment
Share on other sites

  • 1 month later...

Another little note about Luma and ethernet backhaul after getting off the phone with support. 

 

Here's my setup: Cable Modem - Sophos UTM 120 - Home Net on Lan - Luma on DMZ

 

I had another Luma in my living room and plugged in the lan cable for an ethernet backhaul. The switch in the living room was tied back to a switch off the Sophos Home Lan. 

 

Because the living room Luma was not connected to the DMZ network, it thought it was the Hub. However, I already had the Hub on the DMZ. Neither was aware of the other. 

 

I have the Sophos acting as a DHCP server for the home lan on a .1.0/24.  Since the Luma was on the Home Lan and thought it was a hub, it was also a DHCP server and running NAT as well for the .55.0/24 network.

 

My network, which was normally rock solid, started having issues because of the above setup. Internet connections started to fail, and my Sophos WAN interface would shut down. 

 

Moral of the story is that the Luma is designed for ethernet back haul from the node to the hub. If you run unmanaged switches in your house (i.e., no VLAN capability) you will have similar issues as i just described. 

 

Per Luma Support, the nodes are meant to be connected to the hub. It would be nice if they had that in their setup guide or other documentation. 

Link to comment
Share on other sites

Welcome to the forums!

 

Not to sound mean but with your configuration the results you got would be what I would of expected. For one Luma can't be put into 'bridge mode' so there is no way to disable the routing and DHCP server on Luma. 2nd the the subnet on Luma can't be changed so it uses 192.168.55.x and hands out IP address in that rang like it or note. 3rd you did the rite thing by setting up the first Luma on the DMZ but each node that is connected using 'Ethernet backhaul' also needs to be on a switch off the DMZ so they can communicate on a totally different network in the 192.168.55.x network. If you had used wireless mesh for the nodes it would of worked fine. Luma has told me support for setting up Luma in 'bridge mode' is on the list but no ETA. I agree support for setting up Luma in 'bridge mode' is needed and I can't wait for it to be supported. Many of us run our own routers with UTM and I am not interested in changing that.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...