Update wgd.sh to latest

[amirhmoradi]

update wgd.sh to latest and making clear the sections modified by wiregate project by enclosing mods with clear comment blocks.

[NOXCIS]

update wgd.sh to latest and making clear the sections modified by wiregate project by enclosing mods with clear comment blocks.

This is nice but what does it have to do with the TLS pipe?

[amirhmoradi]

thanks for the reply. I was setting up the dev env and did this first PR to start cleaning around and getting confortable with the project. I will be working on the tlspipe in upcoming weeks.

[NOXCIS]

thanks for the reply. I was setting up the dev env and did this first PR to start cleaning around and getting confortable with the project. I will be working on the tlspipe in upcoming weeks.

Nice,

udptlspipe:
    depends_on: [wiregate]
    image: ghcr.io/ameshkov/udptlspipe
    container_name: udptlspipe
    restart: unless-stopped
    command: >
      --server
      -l 0.0.0.0:8443
      -d wiregate:4200
      -p YourSecurePassword
    ports:
      - "443:8443/tcp"
    networks:
      private_network:
        ipv4_address: 10.2.0.4

this is all that really needs to be updated on the gate way.

• WGD_REMOTE_ENDPOINT_PORT = your.server.public.ip:443 # The public IP where udptlspipe is listening
• WGD_PORT_RANGE_STARTPORT = 4200
• WGD_PEER_ENDPOINT_ALLOWED_IP=0.0.0.0/0, ::/0

but the tunnel would apply to all interfaces. this is if we use the docker container for udptls pipe. What would be good if you can automate the tediousness on the server side for large deployments.