Giter VIP home page Giter VIP logo

Comments (13)

pymq avatar pymq commented on June 7, 2024

Hey! thanks for your report

Can you please provide more info about how you setup your two nodes? did you have any logs with ERROR or WARN level? Did you try to restart both nodes? (just in case) are you sure that you use correct ip address from x64 node? (you can list your known peers with command ./awl cli peers status)

from awl.

cnjmj avatar cnjmj commented on June 7, 2024

Hey! thanks for your report

Can you please provide more info about how you setup your two nodes? did you have any logs with ERROR or WARN level? Did you try to restart both nodes? (just in case) are you sure that you use correct ip address from x64 node? (you can list your known peers with command ./awl cli peers status)

I want to send log to your mailbox or other contact mode.

from awl.

cnjmj avatar cnjmj commented on June 7, 2024

[root@arm:/root]# awl cli me id
your peer id: 12D3KooWSjXQsWhoaYZ4LUhXRi6jdZiqkGfZkzRpUkqbkw8YSUxi

This is an arm device, you can also have a try.

from awl.

cnjmj avatar cnjmj commented on June 7, 2024

udp 0 0 127.0.0.66:53 0.0.0.0:* 11400/awl

2022-10-27 10:59:41 WARN awl/dns send request to upstream dns: read udp 127.0.0.1:46867->127.0.0.1:53: read: connection refused
2022-10-27 10:59:41 WARN awl/dns send request to upstream dns: read udp 127.0.0.1:40916->127.0.0.1:53: read: connection refused
2022-10-27 10:59:41 WARN awl/dns send request to upstream dns: read udp 127.0.0.1:44678->127.0.0.1:53: read: connection refused
2022-10-27 10:59:41 WARN awl/dns send request to upstream dns: read udp 127.0.0.1:39644->127.0.0.1:53: read: connection refused

from awl.

pymq avatar pymq commented on June 7, 2024

These logs seems fine, dns could not work on some linux configurations, but vpn should work. I have tested awl on arm devices (android with 32 and 64 bit cores), it worked fine. I have no ideas on what could be wrong here, yet, will try to investigate on my personal arm server (raspberry pi) later

I sent a friend request to your arm node

from awl.

cnjmj avatar cnjmj commented on June 7, 2024

These logs seems fine, dns could not work on some linux configurations, but vpn should work. I have tested awl on arm devices (android with 32 and 64 bit cores), it worked fine. I have no ideas on what could be wrong here, yet, will try to investigate on my personal arm server (raspberry pi) later

I sent a friend request to your arm node

[root@OTCloud_5634:/root]#awl cli peers status
№ | PEER | STATUS | LAST SEEN | NETWORK USAGE | CONNECTIONS | VERSION
| | | | (↓IN/↑OUT) | ADDRESS | PROTOCOL |
-----+------------------+---------+------------+--------------------+--------------------+----------
1 | maxbook test | online | 2022-10-28 | ↓ 0 B/s (1.62 KiB) | through relay | dev
| maxbook_test.awl | | 18:55:31 | ↑ 0 B/s (1.76 KiB) | |
| 10.66.0.6 | | | | |
-----+------------------+---------+------------+--------------------+--------------------+----------
2 | 10.66.0.5 | offline | 2022-10-28 | ↓ 0 B/s (0 B) | |
| | | 15:10:52 | ↑ 0 B/s (0 B) | |
-----+------------------+---------+------------+--------------------+--------------------+----------
3 | aaa | offline | 2022-10-28 | ↓ 0 B/s (0 B) | |
| aaa.awl | | 14:14:50 | ↑ 0 B/s (0 B) | |
| 10.66.0.4 | | | | |
-----+------------------+---------+------------+--------------------+--------------------+----------
4 | arm_B | offline | 2022-10-27 | ↓ 0 B/s (0 B) | |
| a.awl | | 10:40:39 | ↑ 0 B/s (0 B) | |
| 10.66.0.2 | | | | |
-----+------------------+---------+------------+--------------------+--------------------+----------
5 | x86 | offline | 2022-10-28 | ↓ 0 B/s (0 B) | |
| x86.awl | | 15:10:52 | ↑ 0 B/s (0 B) | |
| 10.66.0.3 | | | | |
-----+------------------+---------+------------+--------------------+--------------------+----------
[root@OTCloud:/root]#ping 10.66.0.6
PING 10.66.0.6 (10.66.0.6): 56 data bytes
64 bytes from 10.66.0.6: seq=0 ttl=64 time=329.531 ms
64 bytes from 10.66.0.6: seq=1 ttl=64 time=305.934 ms
64 bytes from 10.66.0.6: seq=2 ttl=64 time=359.749 ms
64 bytes from 10.66.0.6: seq=3 ttl=64 time=389.133 ms
64 bytes from 10.66.0.6: seq=4 ttl=64 time=307.593 ms
^C
--- 10.66.0.6 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 305.934/338.388/389.133 ms

from awl.

pymq avatar pymq commented on June 7, 2024

I tested and ping didn't work for me either

$ ping 10.66.0.23
PING 10.66.0.23 (10.66.0.23) 56(84) bytes of data.
^C
--- 10.66.0.23 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9222ms

But I can send you tcp packets, for example via nmap or accessing directly from http http://10.66.0.23:8800/

$ nmap 10.66.0.23                                 

Nmap scan report for cnjmj-github.awl (10.66.0.23)
Host is up (0.31s latency).
Not shown: 987 closed ports
PORT      STATE    SERVICE
22/tcp    filtered ssh
23/tcp    filtered telnet
8800/tcp  open     sunwebadmin

Is it possible that your server has firewall that blocks ping requests? Otherwise there is definitely a bug, thanks for pointing this out!

Could you please try to access your arm node with http or any other tcp protocol from your other node? Seems like this works fine

from awl.

cnjmj avatar cnjmj commented on June 7, 2024

default is ACCEPT

*filter
:INPUT ACCEPT

from awl.

pymq avatar pymq commented on June 7, 2024

That's strange, I can't get to 9999 port, but 8800 works fine

$ curl http://10.66.0.23:8800                                         
{"sign_rtn":100}%                                                                                                                                                                               
$ curl http://10.66.0.23:9999 
^C

from awl.

cnjmj avatar cnjmj commented on June 7, 2024

That's strange, I can't get to 9999 port, but 8800 works fine

$ curl http://10.66.0.23:8800                                         
{"sign_rtn":100}%                                                                                                                                                                               
$ curl http://10.66.0.23:9999 
^C

now 9999 is ok

from awl.

cnjmj avatar cnjmj commented on June 7, 2024

sorry, all is ok, it's my firewall rule denied awl.

-A INPUT -p tcp -m tcp --dport 9999 -j DROP
-A INPUT -p icmp -m icmp --icmp-type 8 -j DROP

from awl.

cnjmj avatar cnjmj commented on June 7, 2024

Thank you!

from awl.

pymq avatar pymq commented on June 7, 2024

Glad it's working for you!

Overall, how's your experience with awl? Does it meet your requirements? Maybe you have any feedback on what we can do better or any feature suggestions?

from awl.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.