I’ve found an issue with this feature. We use separate management and customer data VLANs which I imagine is part of this issue.
169.254.1.1 always available untagged on the ethernet port has been extremely nice on the ePMP line. I figured it would work exactly the same on PMP450. Well, once the SM comes in session and VLAN goes active, trying to load the GUI via default IP is painfully slow. Pinging my SM, I can get replies with 1500 bytes while it’s scanning. After the session comes up, I have to back off the packet size to 1496, which makes sense because VLAN = 4 bytes.
Would be wonderful if this small issue could be fixed. Our field techs have complained that they can’t access the SM on the default IP after it goes in session and I never really bothered to dig into it until now.