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.

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

[BUG] Secondary IP address does not get when USB to ETHERNET device is used #19

Open
5 tasks done
slinkfurball opened this issue Aug 1, 2022 · 5 comments
Open
5 tasks done
Assignees
Labels
bug Something isn't working

Comments

@slinkfurball
Copy link

Environment

Self-Hosted

System

20.04 LTS

Version

v7.2

Describe the problem

When using USB to Ethernet dongle to install the fluxnode (option#2)in multitoolbox, the secondary IP address does not get created for the ethernet interface. I have tried both TP-LINK Model UE-300 USB 3.0 to Gigabit Ethernet Adapter and Belkin USB 2.0 Ethernet Adapter F4U047 100Mbps and both have the same issue.

Users will see "Failed: Could not get Node Tier From Flux OS" in the ~/.fluxbenchmark/debug.log and option #3 does not provide helpful insight as to what the problem maybe. Improvement in option #3 is to report if secondary IP is missing and how to fix it.

Temporary Work around is to add the secondary interface manually at boot up via the following commands:

sudo ip addr add <public IP / Netmask> dev

run the following cmd to see the details of the interface: ip addr
priminary IP: LAN IP/netmask
secondary IP : Public IP/netmask <-- this one is missing after multitoolbox install of fluxnode (option #2)

Additional info

No response

Please tick the boxes

@TechDufus TechDufus added the bug Something isn't working label Aug 11, 2022
@floriangrousset
Copy link

floriangrousset commented Sep 19, 2022

Multiple scripts multitoolbox.sh, nodeanalizerandfixer.sh and install_pro.sh try to locate the physical ethernet adapter on the host using BROADCAST,MULTICAST,UP,LOWER_UP to add the public IP to it. It could pose a problem when using certain USB ethernet adapters, they would return a different string. The exact same problem occurs if you want to self-host your node behind a VPN where ip addr would for example just return POINTOPOINT,NOARP,UP,LOWER_UP on a wireguard interface.
Are there any plans for fixing this in the near future? I suggest adding a whiptail checklist asking the user for the interface to be used among the ones on the host.
@matthewjdegarmo @XK4MiLX

@XK4MiLX
Copy link
Member

XK4MiLX commented Sep 19, 2022

i will go in diff direction due not all user are networking expert and solution should work for all
can you dm me on discord :)

@floriangrousset
Copy link

floriangrousset commented Sep 19, 2022

Agree, that could add a layer of difficulty for less tech-savvy node operators so better keep it simple as default behavior. What's your handle on the Flux discord? I've looked up for XK4MiLX but can't seem to find you.

------------EDIT--------------
I found you under X4MiLX without the K :) Sending a DM.

@XK4MiLX
Copy link
Member

XK4MiLX commented Sep 30, 2022

New solution in development branch => option 10 > Device - create config
How run script form development branch:
multitoolbox development

@TechDufus
Copy link
Collaborator

@floriangrousset Are you still having issues with this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants