-
Notifications
You must be signed in to change notification settings - Fork 314
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
Network Traffic on Default Interface #4440
Comments
Metrics traffic seems to go from default gateway no matter what is in bind-address |
good catch! Main thing we'll need to update is this: to add something like .local_address("".parse().unwrap()) We also have shell scripts, but I think this is more for testing: need something like |
Assembled a test setup with 2 nodes (bootstrap and 1 validator) with two network interfaces. Specified the bind address for agave in both cases. No traffic found on bond0. There are some irregularities though, there are a few open listen ports on all interfaces: |
Ok so to trigger the bug the cluster entrypoint needs to be NOT in the DZ network. |
Identified bind on port 8003 -
|
Need to also test that transactions made via RPC work correctly |
Problem
Even after setting
bind-address
andgossip-host
to some other interface IP, some network egress appears to be sent from the bond0 interface during startup. This subsequently results in traffic being received on this interface.It is desired to be able to route all traffic to be sent from a specified interface.
Likely related to how this works: https://github.com/anza-xyz/agave/blob/v2.1.7/net-utils/src/lib.rs#L104-L109
Proposed Solution
Need to debug where traffic is originating from and send it from a specified interface. Could piggy back on the
bind-address
param or create something new, depending on what is appropriate after root cause.The text was updated successfully, but these errors were encountered: