Bryn
Doubleplusgood
- Joined
- Oct 29, 2010
- Messages
- 16,894
Chat to Sinbad?
Is he a Ubnt guru?
Chat to Sinbad?
Think he just completed his setup at home...Is he a Ubnt guru?
Think he just completed his setup at home...
Is he a Ubnt guru?
It was a break yes.So tell me how old is this installation? complete new fibre? Definitely proved to be a cable break and not just a bad splice?
Do you know who did the original installation? Maybe it was the same splicer wandering around our area declaring splices are "good enough for FTTH" !![]()
No but I had the same schit as you did
Trick is to just use the out-the-box networking things IMHO. It gets really ****ed up if you try to change subnets etc. So my kit is all now on 192.168.1.x
I think it's almost impossible to migrate an existing network to a cloud key + usg. Go from scratch - get the USG talking to the controller, and from there add your APs etc.
I found this out the hard way with my Mikrotik as well. .No but I had the same schit as you did
Trick is to just use the out-the-box networking things IMHO. It gets really ****ed up if you try to change subnets etc. So my kit is all now on 192.168.1.x
I think it's almost impossible to migrate an existing network to a cloud key + usg. Go from scratch - get the USG talking to the controller, and from there add your APs etc.
But then whats the use of being able to configure things, if you leave it as is? Am i right in saying that is what you did, just allowed for it to automatically do its thing?No but I had the same schit as you did
Trick is to just use the out-the-box networking things IMHO. It gets really ****ed up if you try to change subnets etc. So my kit is all now on 192.168.1.x
I think it's almost impossible to migrate an existing network to a cloud key + usg. Go from scratch - get the USG talking to the controller, and from there add your APs etc.
The problem seems to be with the cloud key not liking having its ip address changed, especially when you have devices registered to it, as they can no longer find it to call home.But then whats the use of being able to configure things, if you leave it as is? Am i right in saying that is what you did, just allowed for it to automatically do its thing?
Surprisingly, yes.![]()
Heh, not for much longer. Vessel was just bought out and will be shut down.
Aah i see, understood nowThe problem seems to be with the cloud key not liking having its ip address changed, especially when you have devices registered to it, as they can no longer find it to call home.
I imagine you could make it work with different subnets but then you'd have to make sure you started with those subnets from scratch before adopting devices.
No but I had the same schit as you did
Trick is to just use the out-the-box networking things IMHO. It gets really ****ed up if you try to change subnets etc. So my kit is all now on 192.168.1.x
I think it's almost impossible to migrate an existing network to a cloud key + usg. Go from scratch - get the USG talking to the controller, and from there add your APs etc.
I found this out the hard way with my Mikrotik as well. .
Quite so.Not to be rude...but these sound more like amateur hour not quite sure what I'm doing problems.
Mikrotik and UBNT type devices are geared at professionals and don't hold your hand. They don't automatically change related settings if you change one setting.
You need to know the knock on effects of changing something and what it relates to and what sequence to follow etc otherwise you are going to have a bad time.
Enterprise devices don't offer "use default settings" as a solution.
Not to be rude...but these sound more like amateur hour not quite sure what I'm doing problems.
Mikrotik and UBNT type devices are geared at professionals and don't hold your hand. They don't automatically change related settings if you change one setting.
You need to know the knock on effects of changing something and what it relates to and what sequence to follow etc otherwise you are going to have a bad time.
Enterprise devices don't offer "use default settings" as a solution.
Guess the Ubiquiti staff are amateur too then, because they had no idea why their equipment wasn't working. And there are a bazillion counts of their equipment not working as intended on their own support forum, with staff often promising fixes in future firmware updates.
To be fair though, my Mikrotik DID come with a default configuration to be used by the home user - the only additional thing I had to configure was the firewall rules to drop unsolicited incoming traffic. The gurus here on MyBB helped me out pretty quickly.Wasn't replying to your issue, but specifically the "keep defaults" comments.
With a bespoke configuration there could be million answers to a problem.
Of course defaults would "just work" because it's delivered in a known working state without any user intervention.
To be fair though, my Mikrotik DID come with a default configuration to be used by the home user - the only additional thing I had to configure was the firewall rules to drop unsolicited incoming traffic. The gurus here on MyBB helped me out pretty quickly.
Saw a thread asking if IS was down tonight - by a Web Africa customer...CW fast becoming the worst ISP for gaming, whether that's an IS problem in general or not, it's not getting fixed. Can't believe it all started out so good and the worst part is, the account is perfect for everything else internet related![]()