Hello, I have some challenges with network/communication breaks in the ship’s WIFI which is connected to LAN 2 with 3 networks in the trunk.
The problem is that the connection via the ship’s WIFI disappears and is gone for a few minutes, while those directly connected via the Peplink internal WIFI are connected at the same time.
It may seem that there is something with the trunk line between the MAX BR2 PRO and the Unify 6 WIFI system that is connecting down.
Suggested solution?
Hello @arve ,
Are you able to connect hardwired to your Ubiquiti network?, and see if the same happens then? i.e. to see if it is a pure wifi issue, or a whole network issue?
Thanks for the response,
The vessel is out fishing now, but I will try to get it checked as soon as it is ashore
Hello
I am on board and log via LAN connection, have run a ping test against 8.8.8.8 for over an hour and it is stable, but some pings have a slightly longer response time 130ms compared to most which are around 30-50ms above cellular connection.
There was 1 drop in 3 pings
The skipper says the connection drops out about every hour, and is stable when it’s in, but about every hour it drops out and is gone for a few minutes.
Anyone have suggestions?
Hello @arve ,
What I understand from your message is that
connecting to the LAN of the ubiquiti network, pinging the internet, you have stable connection, some with higher response which could well happen over a cellular connection.
This would prove that the connection between the ubiquiti network and the peplink is stable.
I would be confirming this by pinging the peplink (rather than the WAN connection).
I do not understand how “there was 1 drop in 3 pings” I assume if you did a test over an hour, you would have had many more pings.
When the skipper says it drops out, what actually drops out? general internet surfing, or is he connected to a specific site constantly?
I would be looking at the trunk configuration that you have at the connection with the ubiquiti network. I would check the DNS settings that there is no conflict, same if you are doing anything over a VPN.
But from above information (and from a distance!) I would be concentrating on the ubiquiti configuration.
Hello @tgorter
I connected my laptop with a cable to LAN3 on Peplink, set up a ping to 8.8.8.8 and observed whether there would be a break, this was reasonably stable from 08:00 to 10:00, changed to Peplink WIFI with the same ping from 10:00 to 11:15, still no drop of internet.
Connected to the ship’s WIFI with the same ping procedure, this was stable without drops from 11:15 to 12:10, but then the internet disappeared, switched back to Peplink WiFi, had internet, reconnected to the ship’s WiFi still without internet, after 2 minutes at 12:12 the net came back.
This explains what the skipper explains about the net disappearing about 1 hour apart and coming back. it doesn’t matter what they surf, this applies to all crew on board.
Reply from 8.8.8.8: bytes=32 time=35ms TTL=114
Reply from 8.8.8.8: bytes=32 time=34ms TTL=114 Talbor Crew WiFi kl 12:10
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.105.135: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Reply from 8.8.8.8: bytes=32 time=136ms TTL=114 This is connection Peplink WiFi
Reply from 8.8.8.8: bytes=32 time=96ms TTL=114
Reply from 8.8.8.8: bytes=32 time=46ms TTL=114
Reply from 8.8.8.8: bytes=32 time=255ms TTL=114
Reply from 8.8.8.8: bytes=32 time=39ms TTL=114
Reply from 8.8.8.8: bytes=32 time=220ms TTL=114
General failure.
General failure.
General failure.
General failure.
General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Reply from 8.8.8.8: bytes=32 time=46ms TTL=114 Talbor Crew online kl 12:12
Reply from 8.8.8.8: bytes=32 time=61ms TTL=114
Reply from 8.8.8.8: bytes=32 time=98ms TTL=114
Reply from 8.8.8.8: bytes=32 time=49ms TTL=114
As you mentioned, I also think the issue is between the WIFI network and Peplink trunk line.
I have forwarded what I observed with the ping drop over the ubiquiti WiFi to the ubiquiti technicians to see if he can see anything in the WIFI log.
We will also check the trunk line if there is any DNS conflict as you mentioned.
Hi,
What I mean that, is it possible to connect yourself to the switch that feeds the Ubiquiti APs? I am assuming here… that you are using Ubiquiti APs (multiple) as the single AP on the peplink does not cover the areas, which is why you are using additional APs (as well as it being a boat, fishing so most likely steel, the peplink being on the bridge, and the APs below deck somewhere). And with that I am “assuming” that the peplink feeds a switch (probably a managed ubiquiti POE switch, which feeds the APs). Further then that switch may be one of the ubiquiti routed switches…
Some Ubiquiti APs also have a 2nd ethernet port on them.
In essence the idea is to connect yourself within the ubiquiti network and test performance. Ubiquiti has many settings in various places that often confuse matters.
Also I note that a reply came from 192.168.105.135, which means you are not using default Peplink settings, so I’d be looking at, what is your DHCP server and its settings? vlans?
The other thing I would check is the ethernet cable you are using, a bad connection there may be causing port speed switching, the handshake between the NICs happening repetatively.
Good morning.
If you have an SSID in Peplink, you can’t do the same as Unifi. If you mirror the SSID of Peplink with Unifi it will generate a “Neighbors” conflict. Causing Unifi to restart.
Hi @tgorter
The way the connection is set up is as follows:
Peplink LAN 2 trunk line feed Ubiquit switch with 3 pcs. vlan:
Untagged LAN192.168.5.1/24
Admin 192.168.101.1/24 (VLAN ID 101)
Client 192.168.110.1/24 (VLAN ID 110)
Crew 192.168.105.1/24 (VLAN ID 105)
The address you mention 192.168.105.135 is when I connected via the ship’s crew wifi and tested ping, then the ping dropped out and I reconnected to the peplink wifi and had ping, connected back to the ship’s crew wifi and still had no ping before it came back as the report shows.
We will continue to check if there is any DNS conflict between Peplink and the ship’s WIFI network, I changed the Peplink DNS as shown in the picture, but there are still violations against the internet at regular intervals.
The cable between Peplink and the WiFi network has been newly laid.
Hello @arve ,
As mentioned, I would be connecting the PC directly (wired) to the ubiquiti switch, and check the throughput there, as this will confirm if the issue is between the router and the switch, or on the AP network.
And as @danielmagalhaes1985 mentioned, if the peplink is transmitting on the same SSID as the ubiquiti network, you will have the 2 networks interfering with each other.
