Xtophe38

Hi, Well, I cannot reproduce the symptom. If I understand correctly, you have 2 devices with a physical interface each and interfaces are directly connected to each other, right ? Which setup are you using: iTop + extensions or teemIP standalone ? And which version ? In the mean time, did you have a look at the wiki ?

Hello, I apologize for the delayed response. I don't know what steps you followed (if any) but I'd try to upgrade to 2.7 first before migrating to 3.0 then to the laster 3.2.2. As a general statement, I'd strongly advise you to regularly update teemIP to the latest version. You may wait a couple of month to make sure that the software is stable, though.

Hello, As stated on the wiki of the extension, it is included in iTop community from iTop 3.1.0. Unfortunately, it has not been included in teemIP's package... I guess that was because "combodo-my-account", a dependency of "authent-token", was not public at that time. But it is, now ! So I should include them in next teemIP standalone version. In the meantime, I'd suggest you to get the 2 extensions "authent-token" and "combodo-my-account" from GitHub, install them under your <standalone>/extensions/...

Hi, FYI, a PR has just been created on the Network Management Extension to model VPN Links? Feel free to comment.

FYI, I'm starting to work on VPN model. Change can be seen on the Add-VPNLink branch of the teemip-network-mgmt-extended extension. Once complete, I'll transform the branch into a PR.

Thanks for your inputs. Type of VPNs, if I'm correct, could be site-to-site or remote-access. Here as well, the question is: should we have one class with a type attribute to make the difference or 2 different classes ? The second option would be preferred if attributes are significantly different in both cases.

Hi, What not. Could you, please, list here all the attributes that you'd like to have on this class ? Could an enhancement of the class WANLink do the job or would it be better to use a dedicated class ?

Hello Pascal, Sorry for not having answered !! But anyway, you found the right xml directives to hide that menu as you wanted. Cheers