Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About jotech
jotech
Here to help
Member since Oct 25, 2023
Apr 25 2024
Community Record
9
Posts
6
Kudos
0
Solutions
Badges
Apr 16 2024
7:30 AM
We just upgraded from 18.107.2 to 18.210 on our MX75 and immediately noticed that the IPv6 uplink is no longer working. I can get our static IPv4 address on the same uplink, but v6 is stuck in 'Failed' state. It's not urgent as we don't use it, and I can't say if it's our ISP or not. It just started happening after the update.
... View more
Jan 24 2024
1:02 AM
That makes a lot of sense, and if they had allocated a /56 or other then I think I would have been able to figure it out and split it in multiple /64 subnets. For the record, this is in the UK with a BTnet leased line for a business. So I assumed they should know their stuff. I'll go back through their documentation and follow up with them as it's possible I missed something. EDIT: While I wait for them to get back to me, a thought occurs: is it possible there was a typo in the network mask they sent me? That it should be /48 instead of /64? The address they sent me is the first three groups which matches up with the table in the link provided by alemabrahao above. Whereas the /64 has four groups. I guess since the zeros have been ommitted it could still be a /64 mask but I found it interesting that they match up like that.
... View more
Jan 23 2024
9:16 AM
We recently recieved a dedicated line with multiple IPv4 addresses and a IPv6 address to use for our systems. I have configured our Meraki device with both IPv4 and v6, both say the uplink is active. Our internal network has always used IPv4 and I am interested in experimenting and learning more about using IPv6 if possible. Our ISP gave use the following information: IPV6 Network Address : 2345:0425:2CA1:: IPV6 Network Mask : /64 But I am not sure how to use this across multiple VLANS. I figure I need to add this as an IPv6 Prefix and I can then set each VLAN to 'Auto' in the config. It would be my assumption if I have two VLANs that I want to use these IPv6 addresses, in theory I would be able to split them into two subnets with 2a00:2381:71f3::/65 and 2a00:2381:71f3:0:8000::/65 (calculated with https://subnettingpractice.com/ipv6-subnet-calculator.html) But when adding a Prefix it says I need to use a "valid IPv6 CIDR with mask 1-64". If I add the prefix as 2a00:2381:71f3::/64 I can only assign this to one VLAN. Am I completely misunderstanding how this works? I am new to IPv6 so that's very possible. Or would I need multiple /64 addresses from my ISP to make this work?
... View more
Labels:
- Labels:
-
Other
Nov 14 2023
1:06 AM
Absolutely makes sense. As I said, I figured it was worth an ask just incase there was something magical I could do router side.
... View more
Nov 13 2023
7:14 AM
Thank you for the quick reply. Unfortunately this didn't work. I assume because the KVMs aren't using Bonjour, but that might be a question for the developers of the software.
... View more
Nov 13 2023
6:55 AM
Strange question I know. And I figure broadcasts are designed to only be sent over one subnet and defeats the purpose of seperating into multiple vlans. We have a few KVM switches on our network (one IP address is 192.168.10.10/24). I am connecting to the KVM through a client on my computer (my computer is in a different subnet with the address 192.168.50.10/24). I have set up firewall rules so I can access the KVM just fine. Everything works as expected there. The KVM client I run on my computer has the ability to display a list of all known KVMs on the network to allow for easy selection without having to type in the IP address. I can see all the KVMs if I connect my computer to the first subnet. But because I am on a different subnet the list of known KVMs isn't populated. Again, I can type in the IP address and connect. This would purely be a quality of life improvement. I don't actually know how this works in the background, but I assume there is some broadcast being sent across the network. And it is not able to cross over the subnets. That would make sense. I have also contacted the supplier of the KVM client software to see if there is anything they can do on their side. But I thought to ask here as well just in case there is any other way around this problem from the router side. Or I am being completely wrong about the broadcast being the cause of the issue.
... View more
Labels:
- Labels:
-
Other
Oct 27 2023
1:01 AM
4 Kudos
I accepted this as a solution because it helped me firgure out what I needed to do. So thank you! I reset the third switch to factory settings, so it worked exactly the same as the other two working ones. I set the Meraki port as a Trunk Native VLAN same as the others as you mentioned. I was then able to config the ports on the switch to be in the correct VLAN. This worked fine. I think the issue was caused because I set a static IP address on the third switch in the VLAN I wanted it to be in. By putting the switch in the Main VLAN with everything else, it worked as expected. Thank you all very much for your help. I'm learning something new every day!
... View more
Oct 26 2023
1:15 AM
2 Kudos
Thanks for everyone's responses. I don't have any links between switch 3 and any other switch. All three switches are connected only to their own port on the Meraki device (and then a few devices each). Settings Access VLAN 10 is no different from setting Trunk native VLAN 10. This was my thought as well. It works fine as Access VLAN 10, but as soon as I change the port to Trunk native VLAN 10, everything just stops working. I think this is something I need to figure out before configuring the switch ports on different VLANs. It probably would be simpler to config the same native VLAN everywhere and config the ports on the downstream switches as @PhilipDAth suggests, but it's my understanding that as long as the Allowed VLANs is set to 'all' it shouldn't matter too much? I have tried changing the native VLAN on the trunks, but it made no difference.
... View more
Oct 25 2023
9:40 AM
I am having real trouble setting up and configuring VLANs on my MX68. I am able to set up VLANs in the "Addressing and VLANs" settings page: (I've blurred out the ones I don't care about) I then assign them to individual LAN ports: I have three Managed Switches. One in Port 3, another in port 6 and another in port 10. These are all on different VLANs. I also have a server (including a DHCP server) on Port 4, in VLAN 3, same VLAN as one of the switches. The two switches in ports 3 and 6 are completely default settings. They get a DHCP address from the server and any devices connected to them also work fine. They can communicate with each other as I have set up firewall rules to allow this. The switch on Port 10 only seems to allow access if I configure the port in Access mode, not Trunk mode like the others. I have set a static IP on this switch (in the VLAN range - 10.0.0.2), but other than that everything else is standard. This all works. The issue arrises when I try to configure the third switch (on Port/VLAN 10) to use VLAN tagging. I want to be able to use VLAN 10 and VLAN 11 on this switch. I followed this guide: https://kb.netgear.com/11673/How-do-I-setup-a-VLAN-trunk-link-between-two-NETGEAR-switches?language=en_US and everything looks fine but I completely loose connection to the network. I think this might be related to having to change Port 10 from Access to Trunk. But I do set it with the correct VLAN settings: I am unable to access or ping any other device on the network, even the Meraki. Hoping you can point me in the right direction.I'm happy to answer and questions or clarify anything!
... View more
Labels:
- Labels:
-
Other
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 4 | 2036 | |
| 2 | 2081 |
© 2024 Cisco Systems, Inc.
