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

SCION IP Gateway (SIG) is not working #4715

Open
SonProCode opened this issue Feb 27, 2025 · 0 comments
Open

SCION IP Gateway (SIG) is not working #4715

SonProCode opened this issue Feb 27, 2025 · 0 comments

Comments

@SonProCode
Copy link

SonProCode commented Feb 27, 2025

Hi everyone, I'm trying to set up the SIG following this link: https://docs.scionlab.org/content/apps/remote_sig.html
But SIG didn't work. When i ran the command curl -sfS localhost:30456/status, there was nothing:

Image

I have verified the connectivity between the two ASes, and it is operating normally over SCION

Image

Here was the log when i started the scion-ip-gateway.service:

2025-02-27 10:47:12.325014+0000	INFO	             env/logging.go:42	=====================> Service started SCION IP Gateway scion-ip-gateway
  Scion version: v0.11.0-22-gb45a8ff2a-scionlab

  pid:           174
  euid/egid:     0 0
  cmd line:      ["/usr/bin/scion-ip-gateway" "--config" "/etc/scion/sig.toml"]

2025-02-27 10:47:12.371980+0000	INFO	                env/env.go:189	Exporting prometheus metrics	{"addr": "127.0.0.1:30456"}
2025-02-27 10:47:12.380113+0000	INFO	        gateway/gateway.go:247	Learned local IA from SCION Daemon	{"ia": "1-153"}
2025-02-27 10:47:12.380568+0000	INFO	      periodic/periodic.go:133	Starting periodic task	{"debug_id": "c15d5622", "task": "revocation_store_cleaner"}
2025-02-27 10:47:12.432918+0000	INFO	        gateway/gateway.go:436	QUIC client connection initialized	{"local_addr": "1-153,10.153.0.71:32766"}
2025-02-27 10:47:12.443752+0000	INFO	        control/watcher.go:171	Starting periodic gateway discovery	{"debug_id": "b279dc98", "remote": "1-151"}
2025-02-27 10:47:12.444564+0000	INFO	        control/watcher.go:196	Failed to discover remote gateways	{"debug_id": "b279dc98", "remote": "1-151", "err": {"msg": "no path available", "stacktrace": ["github.com/scionproto/scion/gateway/control/grpc.Discoverer.Gateways /builds/PRV-PERRIG/scionlab/scion-builder/scion/gateway/control/grpc/discoverer.go:39", "github.com/scionproto/scion/gateway/control.(*GatewayWatcher).run /builds/PRV-PERRIG/scionlab/scion-builder/scion/gateway/control/watcher.go:192", "github.com/scionproto/scion/gateway/control.(*GatewayWatcher).Run /builds/PRV-PERRIG/scionlab/scion-builder/scion/gateway/control/watcher.go:176", "github.com/scionproto/scion/gateway.(*watcherWrapper).Run /builds/PRV-PERRIG/scionlab/scion-builder/scion/gateway/watcher.go:123", "github.com/scionproto/scion/gateway/control.(*RemoteMonitor).process.func1 /builds/PRV-PERRIG/scionlab/scion-builder/scion/gateway/control/remotemonitor.go:160"]}}
2025-02-27 10:47:12.489783+0000	INFO	              snet/snet.go:111	Provided port is outside the SCION/UDP range, it will only receive packets if shim dispatcher is configured	{"start": 31000, "end": 32767, "port": 30256}
2025-02-27 10:47:12.534362+0000	INFO	        gateway/gateway.go:529	QUIC server connection initialized	{"local_addr": "1-153,10.153.0.71:30256"}
2025/02/27 10:47:12 connection doesn't allow setting of receive buffer size. Not a *net.UDPConn?. See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
2025-02-27 10:47:12.545712+0000	INFO	              snet/snet.go:111	Provided port is outside the SCION/UDP range, it will only receive packets if shim dispatcher is configured	{"start": 31000, "end": 32767, "port": 30856}
2025-02-27 10:47:12.546980+0000	INFO	        grpc/probeserver.go:37	ProbeDispatcher: starting
2025-02-27 10:47:12.548836+0000	INFO	              snet/snet.go:111	Provided port is outside the SCION/UDP range, it will only receive packets if shim dispatcher is configured	{"start": 31000, "end": 32767, "port": 30056}
2025-02-27 10:47:12.563480+0000	INFO	...rol/enginecontroller.go:171	Starting new forwarding engine.	{"routing_chain_mapping": {}}
2025-02-27 10:47:12.567580+0000	INFO	          gateway/loader.go:89	Published new configurations	{"session_policies": true, "routing_policy": true}
2025-02-27 10:47:12.672516+0000	INFO	 pathhealth/pathwatcher.go:165	Starting path watcher	{"remote_isd_as": "1-151", "debug_id": "fd759370", "id": 32765, "path": "Hops: [1-153 1>1 1-150 2>1 1-151] MTU: 1500 NextHop: 10.0.0.4:30001"}
2025-02-27 10:47:12.674056+0000	INFO	 pathhealth/pathwatcher.go:165	Starting path watcher	{"remote_isd_as": "1-151", "debug_id": "c44073f5", "id": 32764, "path": "Hops: [1-153 1>1 1-150 3>2 1-152 1>2 1-151] MTU: 1500 NextHop: 10.0.0.4:30001"}
2025-02-27 10:47:17.463358+0000	INFO	        control/watcher.go:215	Start prefix discovery	{"debug_id": "b279dc98", "remote": "1-151", "gateways": [{"Control":{"IP":"127.0.0.1","Port":30256,"Zone":""},"Probe":{"IP":"127.0.0.1","Port":30856,"Zone":""},"Data":{"IP":"127.0.0.1","Port":30056,"Zone":""},"Interfaces":null}]}

I would appreciate it if you could help identify the cause of the error. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant