Indeed, this bug is caused by the IPO associating the group with the LAN1 address for SCN purposes and they can't be bothered to fix it, the solution if you really must use DHCP client is to use the LAN2 port and then it never happens
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.