Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Edgerouter X - not all interfaces are found after 2.1.1 #137

Open
benjycov opened this issue May 4, 2024 · 26 comments
Open

Edgerouter X - not all interfaces are found after 2.1.1 #137

benjycov opened this issue May 4, 2024 · 26 comments

Comments

@benjycov
Copy link

benjycov commented May 4, 2024

With 2.1.1 and 2.1.2 I have had to delete my original routers and readd.

I have 2 Edgerouter 12s, and both are discovering all of their interfaces okay. I have 1 Edgerouter X and only the switch and vtun interfaces are being found, no eth interfaces.
@benjycov
Copy link
Author

benjycov commented May 4, 2024

Just to add I'm seeing lots of log errors for openvpn:

2024-05-04 11:51:08.580 ERROR (MainThread) [custom_components.edgeos.data_processors.interface_processor] Failed to extract Interfaces data, Error: 'openvpn' is not a valid InterfaceTypes, Line: 105

Though if I monitor VTUN interfaces their stats seem to be okay.

@elad-bar
Copy link
Owner

elad-bar commented May 5, 2024

please provide diagnostic file so I will be able to analyze how it is configured, thanks

@Gunth
Copy link

Gunth commented May 5, 2024 •
edited by elad-bar
Loading

Same issue:

Logger: custom_components.edgeos.data_processors.interface_processor
Source: custom_components/edgeos/data_processors/interface_processor.py:115
integration: Ubiquiti EdgeOS Routers (documentation, issues)

First occurred: 10:56:30 (773 occurrences)
Last logged: 11:08:12

Failed to extract Interfaces data, Error: 'wireguard' is not a valid InterfaceTypes, Line: 105

Here is the diagnostic file :

@benjycov
Copy link
Author

benjycov commented May 5, 2024 •
edited by elad-bar
Loading

please provide diagnostic file so I will be able to analyze how it is configured, thanks

diagnostics attached.

A little more information:

  1. All three routers I have are logging the 'openvpn' is not a valid interfacetype, however the OpenVPN interfaces are all being monitored correctly. So this error may not be the root cause of this problem.
  2. The router that isn't finding all the interfaces has a slightly unusual 'peth' interface, so perhaps that is causing the problem.

Thanks for sorting this, and this addon in general, its very helpful! :)

This was referenced May 6, 2024
Closed
Closed
@elad-bar
Copy link
Owner

elad-bar commented May 7, 2024

released v2.1.3,
can you please check if it is working for you?

@CatalinGB
Copy link

Working as expected, thanks for the quick fix!

@Gunth
Copy link

Gunth commented May 7, 2024

Also correctly working now, thanks a lot !

@dar3khudy
Copy link

dar3khudy commented May 8, 2024 •
edited
Loading

With ER-X it is presenting all interfaces but for ER-12 it is only showing bond and vtun, all eth are missing.

PS: did anyone above opened the json file which attached ? There are passwords for example for dynamic dns accounts without any encryption, also mac addresses and a lot of information which shouldn't be posted in public!!!

@elad-bar
Copy link
Owner

elad-bar commented May 8, 2024

With ER-X it is presenting all interfaces but for ER-12 it is only showing bond and vtun, all eth are missing.

please send me diagnostic file, you can send it directly to my mail (elad.bar@hotmail.com).

PS: did anyone above opened the json file which attached ? There are passwords for example for dynamic dns accounts without any encryption, also mac addresses and a lot of information which shouldn't be posted in public!!!

removed links from comments, thanks for raising it, will redact that data, if you can point me to a path in which it is available

@elad-bar
Copy link
Owner

elad-bar commented May 9, 2024

@dar3khudy thanks for the diagnostic file,
I think I understand the root cause - interface is being created using websocket before rest api call,
Which supposed to work first,
As result of that interface is marked as non supported (missing details),
Since I do see that details are available, I would like to protect that flow by doing upsert (update or insert) from rest api, as opposed for today which is insert new only...
I will try to do it later today

@elad-bar
Copy link
Owner

pls check v2.1.4

@benjycov
Copy link
Author

benjycov commented May 13, 2024 via email

@elad-bar
Copy link
Owner

it's not an actual error but warning, it means that the intergation will ignore that interface, need to move it to debug message,
it should present the following interfaces:
considered as: ethernet, bridge, switch, openvpn, wireguard
name starts with: pppoe, vtun, bond

it means that devices that are: loopback or their name starts with: imq, npi, lo - will be ignored by intentionally.

interfaces that are not matching to any of the criteria above, will be ignored and the message is coming to serve when trying to understand the reason why it is not supported...

if you think interfaces are missing, please send me the diagnostic file over an email to elad.bar@hotmail.com

thanks

@benjycov
Copy link
Author

benjycov commented May 13, 2024 via email

@elad-bar
Copy link
Owner

elad-bar commented May 13, 2024 •
edited
Loading

@dar3khudy you are using v2.1.3, it was fixed in v2.1.4

corrected mention :)

@elad-bar
Copy link
Owner

@benjycov can you please remove it, restart and add it again,
something wrong over there generated lots of empty devices, i suspect it has something to do with it

@dar3khudy
Copy link

@dar3khudy you are using v2.1.3, it was fixed in v2.1.4

corrected mention :)
Did you read the right file because inside there is an info that I'm using 2.1.4

"edgeos": {
  "documentation": "https://github.com/elad-bar/ha-edgeos",
  "version": "2.1.4",
  "requirements": [
    "aiohttp"
  ]
},

@benjycov
Copy link
Author

benjycov commented May 13, 2024 via email

@elad-bar
Copy link
Owner

Found it, it seems that it's not working as i described, it fails the process if the type is not available,
Will fix it and release new version later today

@elad-bar
Copy link
Owner

elad-bar commented May 14, 2024 •
edited
Loading

added fix in v2.1.5

@dar3khudy
Copy link

v2.1.5 for me is working fine ! thank you.

@elad-bar
Copy link
Owner

@benjycov pls let me know if now it works for you as well

thanks

@benjycov
Copy link
Author

benjycov commented May 14, 2024 via email

@elad-bar
Copy link
Owner

Can you pls send me again over the mail diagnostic file and logs with v2.1.6?
Thank you for assisting fixing the issue, sorry it takes time :)

Sub interfaces are not supported, i need to learns it's structure and functionality before exposing it in HA

@benjycov
Copy link
Author

benjycov commented May 14, 2024 via email

@TraceWilson
Copy link

ha-edgeos v2.1.8 not detecting vlan interfaces. At least 1 previous version was working, but now none of the vlan interfaces (SWITCH0.10, etc) are being detected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Gunth @elad-bar @CatalinGB @TraceWilson @benjycov @dar3khudy