Force 4525L not getting IPV6 in NAT mode

Products ePMP
1

Hi every one.
I’ve been testing this setup, 4500L as AP, force 4525L clients.
In NAT mode, the clients don’t get any ipv6. IF I connect a force 300 in NAT mode to the same AP then It gets an IPv6 address and so does my laptop behind it. If the force 4525L is in Bridge mode then my laptop gets an IPv6 address. I have tested the AP and force4525L using both 5.9.1 and 5.9.2 vers. Both F300 and F4525L have exactly the same network config.
Please let me know if I’m missing something here…and apologies in advance if it is something trivial that I might be overlooking.
Cheers
Dimas

IMG_2483
IMG_24831920×1440 198 KB

2

@Fedor Hi Guys, Is there any one who could help me with this issue?, Cambium support said They needed to replicate the setup but I haven’t had any update since last week. I forgot to say that my public Vlan runs on 1700 MTU. As I said before, F300 cpe’s get Ipv6 address with no issues at all.

3

Hi Dimas,
We have successfully replicated the issue and opened a ticket for our developers to fix it.
Expecting this to be resolved in our next releases. We will let you know when it’s ready.
Thank you!

Regards,
Oleksii

4

Thanks for letting me know. All my deployment is based on Vlans and CPE’s in NAT mode . Many customers use a router from their own after the CPE creating a double NAT and some issues along with it. My way to overcome those issues is by sending IPV6 to their internal networks. I don’t want to use the CPE’s in bridge mode and exposing my network. I’d appreciate a prompt solution since this issue halts the jump onto the 4500 platform.

Best Regards

1 Like
5

I guess I’m not the only one.

I have had a ticket open since last march about this that hasn’t been updated since may 2nd.

I moved on to a different config for my network.

6

@Joshua_Teager, sorry for the lack of updates on your ticket. I checked and it was linked to internal engineering tickets AXG-8946 and AXG-8965, both of which were resolved in release 5.8.0. However, I’m not sure if the problem you described exactly matches those engineering tickets.

Are you able to confirm if your problem still exists since 5.8.0?

@dimas_j_perez, your support ticket is linked to engineering ticket AXG-11567, which is as yet unresolved.

1 Like
7

I will try it out when I have a few minutes free, but I’m not positive our current network will be compatible after we changed our core to work around the problem

Thanks

1 Like