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

My 2 instances dont see eachother in same cabal chat #303

Open
danrobi11 opened this issue Jan 28, 2021 · 5 comments
Open

My 2 instances dont see eachother in same cabal chat #303

danrobi11 opened this issue Jan 28, 2021 · 5 comments

Comments

@danrobi11
Copy link

danrobi11 commented Jan 28, 2021

Im running 2 instances. 1 on desktop and 1 on my laptop. Both run the desktop client. They dont see eachother in same cabal chat. Its the exact same cabal address but they dont see eachother in the chat. Over same local network.
Which exact ports would I need to allow tcp or udp /both ? I could test that, maybe thats the issue.

the cabal add: cabal://a7524059349be1e0c7e37e9dd8c082193010ef6dd5527e8f9c0ff35ad7de771d

Why is the cabal client pinging google?

connection: <1611803125> <eth0>:13331 => 13.91.107.34.bc.googleusercontent.com.:36401 (udp) up/down Bps: 12/19 process: "cabal-desktop"
connection: <1611803125> <eth0>:13331 => 13.91.107.34.bc.googleusercontent.com.:43869 (udp) up/down Bps: 12/19 process: "cabal-desktop"
connection: <1611803125> <eth0>:13331 => 13.91.107.34.bc.googleusercontent.com.:45765 (udp) up/down Bps: 12/19 process: "cabal-desktop"
connection: <1611803125> <eth0>:13331 => 13.91.107.34.bc.googleusercontent.com.:40943 (udp) up/down Bps: 12/19 process: "cabal-desktop"
connection: <1611803125> <eth0>:13331 => 13.91.107.34.bc.googleusercontent.com.:43017 (udp) up/down Bps: 12/19 process: "cabal-desktop"

cabal-desktop-6.0.6-linux-x86_64.AppImage
OS: MX 19.3 (patito feo) x86_64
SysV init version: 2.93
Debian GNU/Linux 10 (buster)
Kernel: 4.19.0-9-amd64

@danrobi11
Copy link
Author

danrobi11 commented May 3, 2021

After further testing. Doesnt matter if I change the port or not. (tested with the CLI version)

I thought this was suppose to work over local network. It does not here. Tested with same port and different port.

I join same cabal and both of my devices sit there alone :/ ???

@danrobi11
Copy link
Author

danrobi11 commented May 4, 2021

I'll describe step by step what I do. This might not be an issue. Maybe thats how cabal works. I dont know, im just a non-technical user.

I've installed on both devices the cabal-cli. With nvm. Nothingelse. I've not installed the cabal-core.

Both devices are on the same local network. I do allow in both devices the cabal port in both firewall through iptables. Theres no gufw nor ufw on my devices. I deal only with iptables.

I start the cabal-cli on the laptop with: ./cabal --new --port whatever (for example)

Now I've a laptop cabal address: cabal://1fdc83....

I start the desktop cabal with: ./cabal cabal://1fdc83.... --port whatever (I also tested with both cabal using the same port. Same result)

Now they both sit in the same cabal address. But they dont see eachother.

Are they suppose to see eachother at this point ?

Are you experiencing the same thing on your end ?

@cblgh
Copy link
Member

cblgh commented May 6, 2021

sorry to hear you are having issues!

Why is the cabal client pinging google?

seems odd. wonder if that's something to do with a hyperswarm bootstrap node, or if we're mistakenly downloading fonts from google in cabal desktop. cabal should not connect to google

Both devices are on the same local network. I do allow in both devices the cabal port in both firewall through iptables. Theres no gufw nor ufw on my devices. I deal only with iptables.

that should be all you need to do, if even that. could definitely be that yr firewall is really really strict in some other regard

Are they suppose to see eachother at this point ?

yes

Are you experiencing the same thing on your end ?

i would have to try with an explicitly disabled internet connection to confirm, but previously this has worked for me :)

@danrobi11
Copy link
Author

@ Thanks for the reply. I'll test without any iptables rules and report the result.

@danrobi11
Copy link
Author

Tested with iptables set to ACCEPT in/out on both devices. Same result :/

Now that makes no sense

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

2 participants