Comments (2)
Agents are unable to register through NAT devices currently in the v8.x versions of SHIELD. The main obstacle is that the agent connects to the core for registration (via HTTP), traversing the NAT and picking up the NAT device as the agent IP. The core then (at a later time) connects back to the detected agent IP on the advertised port, which will be the NAT device, on the 5444 port. That isn't likelyto work.
The *_proxy
environment variables are aimed primarily at allowing agents to proxy their HTTP(s) traffic during plugin operations; i.e. accessing the AWS S3 API via a proxy in case direct egress HTTP(s) is disallowed by corporate perimeter firewalls in an on-premise environment.
Even if we lifted the constraint in the database, and solved the NAT issue by reporting IPs through the registration payload, you'd have a problem since SHIELD 8.x (and below) cores must initiate the SSH connection to the agent to "push" a task to it; if two agents have the same IP in different subnets, there's a good chance the SHIELD core won't be able to route to both of them without some sort of address translation, and if it could, the Linux kernel would be unable to differentiate the two endpoints on the wire.
from shield.
Hi @jhunt thanks for the explanation I'll close the ticket
from shield.
Related Issues (20)
- [BUG] Editing a Global Store with credentials with new lines does not properly get populated HOT 1
- [BUG] S3 use_instance_profile option doesn't actually use instance profile HOT 1
- [BUG] metashield plugin should trust system pool if ca not specified HOT 1
- shield create-store does not ask AWS information when creating store in s3[BUG] HOT 1
- UI shows inconsistency when shield restore itself while running [BUG]
- v9: Remove WebSocket HOT 1
- v9: Remove Stores / Migrate to SSG HOT 1
- v9: Redo shieldproject.io HOT 1
- v9: Remove Tenancy HOT 2
- [BUG] SHIELD Agent 8.7.2 incompatible with BOSH 263.4.0 HOT 16
- Shield could not restore itself through webUI for the case of shield itself is down.
- Nginx `client_max_body_size` is 10M, caused backup file for shield itself larger than that can not be restored HOT 1
- [BUG] Outputs bigger than 15G are not being saved
- [BUG] mongodump and s3 together fail randomly while backing up larger DBs (>~15 GB)
- [BUG] Failure when trying to restore archive to different target
- [BUG]
- [NEW]
- Shield could not restore from Data System->Scheduled Backup-> Restore
- [BUG] Unable to initialize the SHIELD Core HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from shield.