Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Eduardo Schmidt
    @edufschmidt
    Hmm, yes. You're right.
    Eduardo Schmidt
    @edufschmidt
    @monarch:zerosrealm.xyz I have just merged a fix to dev. My PR also includes the feature you suggested, meaning that now whenever a new connection is created, it will allow by default all traffic matching the CIDR of the network.
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    I see you also updated the API URL to change based on the environment, nice. I'll go check it out!
    Eduardo Schmidt
    @edufschmidt
    Also, I recorded a screencast to demonstrate everything working
    Will upload it somewhere and share the link here
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Nice, thanks for the help 😀
    Eduardo Schmidt
    @edufschmidt
    Thank you for the feedback and patience
    As always, if you run into any other issue, please do share it with us
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    It's a cool project so happy to help out a bit
    Eduardo Schmidt
    @edufschmidt
    There you go
    data_dir  = "/tmp/drago"
    bind_addr = "0.0.0.0"
    
    name = "node-1"
    
    advertise { 
        peer = "192.168.178.38"
    }
    
    server {
        enabled =  false
    }
    
    client {
        enabled = true
        servers = ["192.168.178.37:8081"]
    }
    data_dir  = "/tmp/drago"
    bind_addr = "0.0.0.0"
    
    name = "node-2"
    
    advertise { 
        peer = "192.168.178.39"
    }
    
    server {
        enabled =  false
    }
    
    client {
        enabled = true
        servers = ["192.168.178.37:8081"]
        meta = {
            test_meta = "test_meta_value"
        }
    }
    Once you confirm it's working for you, I will merge dev into master
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Nice video, will test now
    Eduardo Schmidt
    @edufschmidt
    Cool!
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Think it has made me hit another bug, I tried just adding the connection to the peer and after doing so it makes the screen blank when viewing a client (looks like React is not getting the data it was expecting?)
    1 reply
    Want to debug it, or maybe just try deleting the client and let it create itself again?
    I'd imagine it's fine after just recreating the client
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Deleted all drago server data since I couldn't delete/remove a client manually
    Got it working now, but noticed I need to set the advertise peer, though it's supposed to be optional?
    1 reply
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Also, is it supposed to only be able to have one connection to one other peer on the network? As it is right now there doesn't seem to be a way to create multiple connections for the same network, which I'm guessing is undesirable?
    1 reply
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Yes I rebuilt everything from scratch so I dont think that's it. You might be able to reproduce it if you use master branch and get the setup that had the original issue, then built new one from dev and let it use the old existing clients
    Eduardo Schmidt
    @edufschmidt
    Oh, I get it now, you were using different versions in the same setup.
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Correct, so I suspect people who upgrade might have an issue is all
    2 replies
    Eduardo Schmidt
    @edufschmidt
    I will test the multiple connections issue when I have time
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    And not different versions between clients and servers, but simply switching binaries while using the same configuration and data from last
    1 reply
    And just for the sake of my understanding, is the advertise peer the same concept as the endpoint in a standard WireGuard setup? I'm thinking in some cases you might not be able to open up for the device but instead want it to be established to the one that has it exposed (like a central server)
    2 replies
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Thought so, thanks for clarifying!
    Eduardo Schmidt
    @edufschmidt
    Hey @monarch:zerosrealm.xyz , have you managed to setup everything? Is there anything you need help with?
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Nothing other than the connections thing no. Got it setup correctly between my two nodes, can test again later when home. But the fix you made did fix the issue I was having yes
    Eduardo Schmidt
    @edufschmidt
    Cool, I will reproduce the multiple connections issue and get back to you / push a fix when I have time. Meanwhile, feel free to reach out.
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Will do! I'll continue to see if I can find any more little bugs 😉
    Eduardo Schmidt
    @edufschmidt
    Great! I appreciate it :)
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Was checking my Drago setup and switched it to talk between VMs on the default network, but it doesnt seem that one of my VMs (docker2) is applying the Drago config correctly, No drago interface is made (doing ip addr | grep drago returns nothing) so they cant communicate obviously
    Tried restarting the client and also leaving and joining the network again
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Also noticed that the nodes API returns an incorrect amount of connections if you leave the network and not removing connection beforehand. Seems like the connections API however is returning correct data (it doesnt show my last connection before leaving)
    Eduardo Schmidt
    @edufschmidt
    Hi @monarch:zerosrealm.xyz. Sorry for the delay, but I was away last week. Will try to reproduce the issues you're facing, and keep you posted.
    1 reply
    Michael Trillo
    @trillom
    Hello. From what I can tell, REACT_APP_REST_API_URL must be set during the go generate step, which would require a separate build per environment. Is there a way to set the API URL at server startup? If I set that environment variable when starting the server agent, the API URL defaults to localhost:8080
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    This is luckily already known and had been changed in dev branch but not merged last I checked. I recommend checking out that branch
    Michael Trillo
    @trillom
    Anyone have luck with building on MacOS?
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Using Windows and Linux myself, but what issue are you having?
    Michael Trillo
    @trillom
    client/nic/controller.go:258:13: undefined: netlink.RouteReplace when I try to run in development mode on macOS. It looks like the netlink module doesn't support macOS
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Yeah if the netlink module can't be complied on Mac, then I sadly don't see it getting to work there. Only solution would be running it on a container which might not be ideal.
    Michael Trillo
    @trillom
    Yeah, my workaround is having the repo live on a raspberry pi and open the code in a workspace over SSH FS, then just build/run on the rpi
    3 replies
    Monarch
    @monarch:zerosrealm.xyz
    [m]

    It doesnt really, since the hot reloading of the server is just recompiling the source IRC.

    For my own testing though I have CI/CD setup that makes it easier

    Monarch
    @monarch:zerosrealm.xyz
    [m]
    Personally would just use normal Wireguard deployment untill the project is more stable. Though it's exciting to see the project grow and what it can do, still find it great
    1 reply
    Monarch
    @monarch:zerosrealm.xyz
    [m]
    That I do not doubt
    jacob
    @jacob:oscillas.com
    [m]
    Otherwise drago wouldn't exist I guess ;)
    Michael Trillo
    @trillom
    How can I use the UI to generate a new client key pair and allow them access to the VPN?
    1 reply