Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
In thread [1.800] ipsec0 is shown as network interface [CONFIRMED] it was agreed to only show physical devices. In the screenshot you see eth0 and eth3, the only configured and active physical interfaces on the device. All other interfaces are either not configured or are bridge-interfaces.
If you want to bridge-interfaces to be shown just as well, we might be able to do so. But we will not show unconfigured interfaces.
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
I hope this is your real name. I thought it would be nice to call you by your name ... [;)] Hope you are fine with that.
Regarding the problem. Might it be possible that the second interface was added after the device was already connected to the ACC?
Could you please do the following for us. From the ASG supply the following data to acc-beta@astaro.com:
# /etc/active_interfaces # /etc/sysmond.ph
There are probably two issues.
1) The system monitor daemon does not get signaled when new interfaces are added or existing ones are removed. Hence, the device-agent will continue working with old data. This is a framework issue which have in our internal issue tracking system.
2) Even if 1) would work, the device-agent cannot (yet) send a proper update to the ACC that a new interface was added or an existing one removed. The functionality did not make it into the 7.270 release, I am sorry. It will be available with the RC of V7.3 and with the next Up2Date of ACC V1.9 BETA.
The kudos will go mainly to Bruce because he pinpointed the problem more exactly, but I will also award a point to Henrik because he initially reported the issue.
