Welcome Guest ( Log In | Register )

175 Pages « < 148 149 150 151 152 > » Bottom

Outline · [ Standard ] · Linear+

Enterprise Networking Mikrotik Routers (RouterBoard & RouterOS), User and owner discussion group

views
     
OlgaC4
post Jan 2 2024, 11:42 AM

Look at all my stars!!
*******
Senior Member
5,292 posts

Joined: Nov 2006
user posted image
user posted image

Heavy modify antena and cooling. Top speed 5G i got was 480mbps.

This post has been edited by OlgaC4: Jan 2 2024, 11:50 AM
maxiscool
post Jan 2 2024, 08:58 PM

Casual
***
Junior Member
379 posts

Joined: Jan 2003
Hey, no worry. I understand you trying to figure out as well. I'm clueless now as well.

QUOTE(kwss @ Jan 2 2024, 09:31 AM)
Hi,
Sorry if you have to repeat the following check

IPv6 > DHCP Client. Note the prefix. Verify status is "bound".
IPv6 > ND > Prefixes. Note the prefix. There must be only 1 entry and it is "Dynamic".
IPv6 > Addresses. Note the IPv6 address for your bridge.

Are the prefix all the same? Yes, all the same.

If they are the same, do the following:
Go to Tools > Ping

Ping To: 2606:4700:f1::1
Interface: <Your dialer>

Did you get a echo reply? Yes, all get echo reply

When you upgrade your RouterOS, did you also upgrade the matching firmware?
Check via:
System > RouterBOARD
Current Firmware == Upgrade Firmware

Yes, both firmware show 7.12.

*
maxiscool
post Jan 2 2024, 09:06 PM

Casual
***
Junior Member
379 posts

Joined: Jan 2003
QUOTE(soonwai @ Jan 2 2024, 10:43 AM)
maxiscool Last time I have the same problem with Mikrotik & ipv6. It works for awhile then it stops working. Could be hours or days.

The problem was because when Routeros gets a new ipv6 prefix, it doesn't deprecate the previous one. I solved this with a script which sets the previous prefix to a lifetime of 0 whenever there's a new prefix.

You can verify if this is your problem by checking to see if you have multiple active Unifi ipv6 prefixes on your devices.

This was fixed in one of routeros7 releases last year. I forgot which and I don't know if it works since I'm still using the script.
*
Yes, I only see one prefix, 2001:e68:xxxx
kwss
post Jan 3 2024, 02:46 AM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(maxiscool @ Jan 2 2024, 08:58 PM)
Hey, no worry. I understand you trying to figure out as well. I'm clueless now as well.
*
Can you take a screenshot of:
Bridge > Ports

Also in the setting of your bridge:
1. Is IGMP Snooping is checked?
2. Screenshot of IGMP Snooping setting further down
soonwai
post Jan 3 2024, 11:48 AM


********
All Stars
11,455 posts

Joined: Oct 2007
From: KL


QUOTE(maxiscool @ Jan 2 2024, 09:06 PM)
Yes, I only see one prefix, 2001:e68:xxxx
*
One is fine. The problem only occurs when I have 2 or more. Force your router to get a different ipv6 prefix then see if you get the new prefix on your device. You should have 2 now. If everything is ok, the new prefix will have a valid lifetime, the previous prefix should have a lifetime of 00:00:00.

maxiscool
post Jan 3 2024, 06:59 PM

Casual
***
Junior Member
379 posts

Joined: Jan 2003
QUOTE(kwss @ Jan 3 2024, 02:46 AM)
Can you take a screenshot of:
Bridge > Ports

Also in the setting of your bridge:
1. Is IGMP Snooping is checked?
2. Screenshot of IGMP Snooping setting further down
*
Hei, I think you have resolved my issue. My IGMP Snooping was unchecked. Now have it checked, the IPv6 is on my client devices.
kwss
post Jan 3 2024, 11:32 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(maxiscool @ Jan 3 2024, 06:59 PM)
Hei, I think you have resolved my issue. My IGMP Snooping was unchecked. Now have it checked, the IPv6 is on my client devices.
*
Something in your Layer 2 is broken.
IGMP Snooping just provides the containment.
You need to find out why. IGMP Snooping might or might not be the best solution.
maxiscool
post Jan 4 2024, 08:46 AM

Casual
***
Junior Member
379 posts

Joined: Jan 2003
QUOTE(kwss @ Jan 3 2024, 11:32 PM)
Something in your Layer 2 is broken.
IGMP Snooping just provides the containment.
You need to find out why. IGMP Snooping might or might not be the best solution.
*
I see. No wonder it was working without this previously. Hmm, how do I start checking on this ?

kwss
post Jan 4 2024, 09:12 AM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(maxiscool @ Jan 4 2024, 08:46 AM)
I see. No wonder it was working without this previously. Hmm, how do I start checking on this ?
*
For RouterOS, this feature is documented here:
https://help.mikrotik.com/docs/pages/viewpa...pageId=59277403

There is a Monitoring and troubleshooting section. I have to say Mikrotik documentation is very bad but that's where you start.

You need a hypothesis first. In this case I suspect one of your device is flooding your Layer 2 with multicast packet until it triggered storm control. Hence you get dropped multicast packet.

When IGMP Snooping is enabled, Mikrotik stop broadcasting those packet. You did not post your IGMP Snooping configuration, so I assume it's the default. By default RouterOS will forward unknown multicast, even when IGMP Snooping is enabled, so you can rule that out already.

There are several factor to look at, any IP address or MAC that show up is doing multicast and they should all be suspect. That's the starting point.

The strategy:
Most accurate is to mirror the port and start packet capture to see if they are multicasting.
Least accurate is just unplug anything that shows up in the list one by one until it works without IGMP Snooping.

The usual trigger:
Slow device.
Example: Your access port is 1Gbps but have slower device like 100mbps or even 10mbps.

The usual suspect:
Ghost server, media server, multi function printer. Literally anything that's not your typical corporate laptop, PC, server.

Anything that offers plug and play network discovery is also a suspect.

I do not know your network at all. If you have a detailed network diagram that would be helpful for me to give you hint on where to look first.
soonwai
post Jan 4 2024, 10:13 AM


********
All Stars
11,455 posts

Joined: Oct 2007
From: KL


QUOTE(maxiscool @ Jan 4 2024, 08:46 AM)
I see. No wonder it was working without this previously. Hmm, how do I start checking on this ?
*
FWIW, IGMP Snooping on my root bridge is Disabled. The bridges on the other 2 Mikrotiks should be off too. I'll have to check.
OlgaC4
post Jan 4 2024, 10:18 AM

Look at all my stars!!
*******
Senior Member
5,292 posts

Joined: Nov 2006
Ros 7.13 bring the best out of RB5009. Slow it down but stable fast.

This post has been edited by OlgaC4: Jan 4 2024, 10:19 AM
maxiscool
post Jan 4 2024, 07:05 PM

Casual
***
Junior Member
379 posts

Joined: Jan 2003
QUOTE(kwss @ Jan 4 2024, 09:12 AM)
For RouterOS, this feature is documented here:
https://help.mikrotik.com/docs/pages/viewpa...pageId=59277403

There is a Monitoring and troubleshooting section. I have to say Mikrotik documentation is very bad but that's where you start.
Ok, let me try to read up on this. But seems hard for me to fully understanding it as well

You need a hypothesis first. In this case I suspect one of your device is flooding your Layer 2 with multicast packet until it triggered storm control. Hence you get dropped multicast packet.

When IGMP Snooping is enabled, Mikrotik stop broadcasting those packet. You did not post your IGMP Snooping configuration, so I assume it's the default. By default RouterOS will forward unknown multicast, even when IGMP Snooping is enabled, so you can rule that out already.
Yeah I believed is default as well, but I attached for reference. See if there is any good here

There are several factor to look at, any IP address or MAC that show up is doing multicast and they should all be suspect. That's the starting point.

The strategy:
Most accurate is to mirror the port and start packet capture to see if they are multicasting. How do I start with this?
Least accurate is just unplug anything that shows up in the list one by one until it works without IGMP Snooping.

The usual trigger:
Slow device.
Example: Your access port is 1Gbps but have slower device like 100mbps or even 10mbps.

The usual suspect:
Ghost server, media server, multi function printer. Literally anything that's not your typical corporate laptop, PC, server.

Anything that offers plug and play network discovery is also a suspect.

I do not know your network at all. If you have a detailed network diagram that would be helpful for me to give you hint on where to look first.
*
Something I noticed also, if I reboot the router, it won't get IPv6 automatically on client device. I have to perform the IGMP Snooping on and off to get on client devices.

This post has been edited by maxiscool: Jan 4 2024, 08:09 PM


Attached thumbnail(s)
Attached Image
leezhijiang
post Jan 4 2024, 10:06 PM

Getting Started
**
Junior Member
272 posts

Joined: Jan 2010


QUOTE(soonwai @ Jan 2 2024, 01:06 AM)
Sorry to hear that. Probably some misconfiguration by Unifi in your area.
*
Hi I just double checked my Mikrotik firewall rules. I think I need to be glad that I didn't shoot TM directly. I found out there's one rule in the table that drop all incoming connections not from LAN. I created new rules to open up a few TCP and UDP ports and put them above that "drop all incoming connections not from LAN". And then it works.
.

kwss
post Jan 5 2024, 12:15 AM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(maxiscool @ Jan 4 2024, 07:05 PM)
Something I noticed also, if I reboot the router, it won't get IPv6 automatically on client device. I have to perform the IGMP Snooping on and off to get on client devices.
*
For the packet capture, it depends on where you want to capture. You can do it on your switch if it supports port mirroring.
On RouterOS it's in Tool > Packet Sniffer.
I always use Streaming and stream it to my PC / laptop connected via LAN.
Then just Wireshark it.
From here onward it is up to you to decide what constitute normal or abnormal in your network. Like I said, I don't know your network.

I think when you reboot your router, you just need to disconnect / disable your network adapter and enable it again.
On phone, just disconnect / reconnect wifi.
This is a known problem for TM because they did not follow best practice for IPv6 deployment. Their mindset is stuck in dial-up era.
Actually many people in this forum has the exact same mindset and seems to have a distinction for business vs home user when it comes to IPv6. This is the root cause of all the issues.

If anyone is interested in IPv6 best practice for service provider, there is an article here:
https://www.ripe.net/publications/docs/ripe-690
maxiscool
post Jan 5 2024, 11:38 PM

Casual
***
Junior Member
379 posts

Joined: Jan 2003
QUOTE(kwss @ Jan 5 2024, 12:15 AM)
For the packet capture, it depends on where you want to capture. You can do it on your switch if it supports port mirroring.
On RouterOS it's in Tool > Packet Sniffer.
I always use Streaming and stream it to my PC / laptop connected via LAN.
Then just Wireshark it.
From here onward it is up to you to decide what constitute normal or abnormal in your network. Like I said, I don't know your network.

I think when you reboot your router, you just need to disconnect / disable your network adapter and enable it again.
On phone, just disconnect / reconnect wifi.
This is a known problem for TM because they did not follow best practice for IPv6 deployment. Their mindset is stuck in dial-up era.
Actually many people in this forum has the exact same mindset and seems to have a distinction for business vs home user when it comes to IPv6. This is the root cause of all the issues.

If anyone is interested in IPv6 best practice for service provider, there is an article here:
https://www.ripe.net/publications/docs/ripe-690
*
Ok, let me trying to research this and on how to perform packet sniffer. Don't quite get you on how to stream it to PC and wireshark it.
I tried after reboot then disconnect and connect client, it doesn't work. So I have to turn off IGMP Snooping to make it work, so my conclusion is that i just need to toggle igmp snooping to get IPv6 for now.
kwss
post Jan 6 2024, 12:57 AM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(maxiscool @ Jan 5 2024, 11:38 PM)
Ok, let me trying to research this and on how to perform packet sniffer. Don't quite get you on how to stream it to PC and wireshark it.
I tried after reboot then disconnect and connect client, it doesn't work. So I have to turn off IGMP Snooping to make it work, so my conclusion is that i just need to toggle igmp snooping to get IPv6 for now.
*
What's the model of your Mikrotik?
I think it's better we do it the easy way.
Unplug everything from your Mikrotik, plug in just one computer and see if the problem occur.

Plug in more stuff and repeat the test.
maxiscool
post Jan 6 2024, 03:12 PM

Casual
***
Junior Member
379 posts

Joined: Jan 2003
QUOTE(kwss @ Jan 6 2024, 12:57 AM)
What's the model of your Mikrotik?
I think it's better we do it the easy way.
Unplug everything from your Mikrotik, plug in just one computer and see if the problem occur.

Plug in more stuff and repeat the test.
*
RB962UiGS.
Sadly, still occur. Perhaps I should consider upgrade and try on another model.
Quanta
post Jan 6 2024, 04:29 PM

Idiot member
******
Senior Member
1,425 posts

Joined: Jan 2003
From: Pearl 14000 + Kayangan 01000


My RB750Gr3 is not able to keep up to IPV6 speed. Not able get 100% BW and always lingering around 300-333Mbps. My IPV4 is able to get 510Mbps easily.

Also, the Maxis Koan router has no problem on both IPV6 and IPV4. Able to get 510/106Mbps.

Is there any solution to boost RB750Gr3 IPV6's speed to 500Mbps?
go626201
post Jan 6 2024, 05:25 PM

Regular
******
Senior Member
1,882 posts

Joined: Sep 2017
QUOTE(Quanta @ Jan 6 2024, 04:29 PM)
My RB750Gr3 is not able to keep up to IPV6 speed. Not able get 100% BW and always lingering around 300-333Mbps. My IPV4 is able to get 510Mbps easily.

Also, the Maxis Koan router has no problem on both IPV6 and IPV4. Able to get 510/106Mbps.

Is there any solution to boost RB750Gr3 IPV6's speed to 500Mbps?
*
CPU bottleneck,change to Hap ax2 or ax3 should be able to hit more than 600M.
Quanta
post Jan 6 2024, 07:08 PM

Idiot member
******
Senior Member
1,425 posts

Joined: Jan 2003
From: Pearl 14000 + Kayangan 01000


QUOTE(go626201 @ Jan 6 2024, 05:25 PM)
CPU bottleneck,change to Hap ax2 or ax3 should be able to hit more than 600M.
*
thxn for the recommendation. anything that can fool-proof it? like no issue with 1Gbps on ipv6 as well.

175 Pages « < 148 149 150 151 152 > » Top
 

Change to:
| Lo-Fi Version
0.0321sec    0.39    6 queries    GZIP Disabled
Time is now: 29th November 2025 - 05:52 AM