mirror of
https://gitlab.com/pulsechaincom/lighthouse-pulse.git
synced 2024-12-26 22:26:44 +00:00
41b5af9b16
## Issue Addressed #3103 ## Proposed Changes Parse `http-address` and `metrics-address` as `IpAddr` for both the beacon node and validator client to support IPv6 addresses. Also adjusts parsing of CORS origins to allow for IPv6 addresses. ## Usage You can now set `http-address` and/or `metrics-address` flags to IPv6 addresses. For example, the following: `lighthouse bn --http --http-address :: --metrics --metrics-address ::1` will expose the beacon node HTTP server on `[::]` (equivalent of `0.0.0.0` in IPv4) and the metrics HTTP server on `localhost` (the equivalent of `127.0.0.1` in IPv4) The beacon node API can then be accessed by: `curl "http://[server-ipv6-address]:5052/eth/v1/some_endpoint"` And the metrics server api can be accessed by: `curl "http://localhost:5054/metrics"` or by `curl "http://[::1]:5054/metrics"` ## Additional Info On most Linux distributions the `v6only` flag is set to `false` by default (see the section for the `IPV6_V6ONLY` flag in https://www.man7.org/linux/man-pages/man7/ipv6.7.html) which means IPv4 connections will continue to function on a IPv6 address (providing it is appropriately mapped). This means that even if the Lighthouse API is running on `::` it is also possible to accept IPv4 connections. However on Windows, this is not the case. The `v6only` flag is set to `true` so binding to `::` will only allow IPv6 connections.
52 lines
1.5 KiB
Rust
52 lines
1.5 KiB
Rust
use beacon_chain::test_utils::EphemeralHarnessType;
|
|
use environment::null_logger;
|
|
use http_metrics::Config;
|
|
use reqwest::StatusCode;
|
|
use std::net::{IpAddr, Ipv4Addr};
|
|
use std::sync::Arc;
|
|
use tokio::sync::oneshot;
|
|
use types::MainnetEthSpec;
|
|
|
|
type Context = http_metrics::Context<EphemeralHarnessType<MainnetEthSpec>>;
|
|
|
|
#[tokio::test(flavor = "multi_thread", worker_threads = 2)]
|
|
async fn returns_200_ok() {
|
|
async {
|
|
let log = null_logger().unwrap();
|
|
|
|
let context = Arc::new(Context {
|
|
config: Config {
|
|
enabled: true,
|
|
listen_addr: IpAddr::V4(Ipv4Addr::new(127, 0, 0, 1)),
|
|
listen_port: 0,
|
|
allow_origin: None,
|
|
allocator_metrics_enabled: true,
|
|
},
|
|
chain: None,
|
|
db_path: None,
|
|
freezer_db_path: None,
|
|
gossipsub_registry: None,
|
|
log,
|
|
});
|
|
|
|
let ctx = context.clone();
|
|
let (_shutdown_tx, shutdown_rx) = oneshot::channel::<()>();
|
|
let server_shutdown = async {
|
|
// It's not really interesting why this triggered, just that it happened.
|
|
let _ = shutdown_rx.await;
|
|
};
|
|
let (listening_socket, server) = http_metrics::serve(ctx, server_shutdown).unwrap();
|
|
|
|
tokio::spawn(async { server.await });
|
|
|
|
let url = format!(
|
|
"http://{}:{}/metrics",
|
|
listening_socket.ip(),
|
|
listening_socket.port()
|
|
);
|
|
|
|
assert_eq!(reqwest::get(&url).await.unwrap().status(), StatusCode::OK);
|
|
}
|
|
.await
|
|
}
|