Quantcast
Channel: Hamachi Discussions topics
Viewing all 3259 articles
Browse latest View live

Hamachi not workin when installed remotelly

$
0
0

Hi all!

 

I have realized that when hamahi is installed via windows remote desktop, team viewer or anydesk, there is no tap adapter created on the windows system, so it doesn't work.

 

There is also an advertisement in the hamachi aplication, that says there is a problem with the tunnel.

 

I have tried this in many machines and the same problem happens.

 

But if I try to install it locally, I mean with real keyboard, mouse and screen, installation works properly.

 

I also tried to install the tap device from command prompt, but an error appears at the end:

 

C:\Program Files (x86)\LogMeIn Hamachi\x64>hamachi-2.exe --add-tap "Hamachi"
10/20 14:36:49.948 [1096] tap: add_tapdev(Hamachi)
10/20 14:36:49.960 [1096] tap: list_netdev_win32() ..
10/20 14:36:50.019 [1096] vpn: adding tap device [Hamachi] ..
10/20 14:36:50.030 [1096] tap: Collecting information...
10/20 14:36:50.151 [1096] tap: Installing driver, step 1 ..
10/20 14:36:50.167 [1096] tap: Installing driver, step 3 ..
10/20 14:36:50.965 [1096] tap: Installing driver, step 4 ..
10/20 14:36:50.976 [1096] tap: Installing driver, step 5 ..
10/20 14:36:50.992 [1096] tap: Done, 0
10/20 14:36:51.004 [1096] tap: list_netdev_win32() ..
10/20 14:36:51.053 [1096] tap: find_new_tapdev: devs_org[0] -> [hamachi]
10/20 14:36:51.064 [1096] tap: find_new_tapdev: devs_org[1] -> [hamachi]
10/20 14:36:51.079 [1096] tap: find_new_tapdev: devs_org[2] -> [*teredo]
10/20 14:36:51.091 [1096] tap: find_new_tapdev: devs_org[3] -> [*isatap]
10/20 14:36:51.102 [1096] tap: find_new_tapdev: devs_org[4] -> [pci\ven_14e4&dev
_165a]
10/20 14:36:51.128 [1096] tap: find_new_tapdev: devs_org[5] -> [sw\{eeab7790-c51
4-11d1-b42b-00805fc1270e}]
10/20 14:36:51.155 [1096] tap: find_new_tapdev: devs_org[6] -> [ms_ndiswanip]
10/20 14:36:51.172 [1096] tap: find_new_tapdev: devs_org[7] -> [ms_ndiswanbh]
10/20 14:36:51.189 [1096] tap: find_new_tapdev: devs_org[8] -> [ms_ndiswanipv6]
10/20 14:36:51.208 [1096] tap: find_new_tapdev: devs_org[9] -> [ms_pppoeminiport
]
10/20 14:36:51.231 [1096] tap: find_new_tapdev: devs_org[10] -> [ms_pptpminiport
]
10/20 14:36:51.251 [1096] tap: find_new_tapdev: devs_org[11] -> [ms_l2tpminiport
]
10/20 14:36:51.276 [1096] tap: find_new_tapdev: devs_org[12] -> [ms_agilevpnmini
port]
10/20 14:36:51.302 [1096] tap: find_new_tapdev: devs_org[13] -> [ms_sstpminiport
]
10/20 14:36:51.329 [1096] tap: find_new_tapdev: devs_new[0] -> [hamachi]
10/20 14:36:51.343 [1096] tap: find_new_tapdev: devs_new[1] -> [hamachi]
10/20 14:36:51.354 [1096] tap: find_new_tapdev: devs_new[2] -> [hamachi]
10/20 14:36:51.369 [1096] tap: find_new_tapdev: devs_new[3] -> [*teredo]
10/20 14:36:51.388 [1096] tap: find_new_tapdev: devs_new[4] -> [*isatap]
10/20 14:36:51.399 [1096] tap: find_new_tapdev: devs_new[5] -> [pci\ven_14e4&dev
_165a]
10/20 14:36:51.428 [1096] tap: find_new_tapdev: devs_new[6] -> [sw\{eeab7790-c51
4-11d1-b42b-00805fc1270e}]
10/20 14:36:51.453 [1096] tap: find_new_tapdev: devs_new[7] -> [ms_ndiswanip]
10/20 14:36:51.464 [1096] tap: find_new_tapdev: devs_new[8] -> [ms_ndiswanbh]
10/20 14:36:51.477 [1096] tap: find_new_tapdev: devs_new[9] -> [ms_ndiswanipv6]
10/20 14:36:51.494 [1096] tap: find_new_tapdev: devs_new[10] -> [ms_pppoeminipor
t]
10/20 14:36:51.521 [1096] tap: find_new_tapdev: devs_new[11] -> [ms_pptpminiport
]
10/20 14:36:51.550 [1096] tap: find_new_tapdev: devs_new[12] -> [ms_l2tpminiport
]
10/20 14:36:51.577 [1096] tap: find_new_tapdev: devs_new[13] -> [ms_agilevpnmini
port]
10/20 14:36:51.605 [1096] tap: find_new_tapdev: devs_new[14] -> [ms_sstpminiport
]
10/20 14:36:51.632 [1096] tap: found new device
10/20 14:36:51.647 [1096] tap:     guid {EA5DB1D7-9E03-4E8C-A2E2-72105CA45E04}
10/20 14:36:51.664 [1096] tap:     name Hamachi Network Interface #3
10/20 14:36:51.678 [1096] tap:     desc Conexi¾n de ßrea local 4
10/20 14:36:51.705 [1096] tap:   dev_id ROOT\NET\0002
10/20 14:36:51.719 [1096] tap:    hw_id hamachi
10/20 14:36:51.733 [1096] tap:     type 2
10/20 14:36:51.745 [1096] tap:   hidden 0
10/20 14:36:51.768 [1096] tap:  enabled 0
10/20 14:36:51.788 [1096] tap:  running 0
10/20 14:36:51.802 [1096] tap:   status 01802401
10/20 14:36:51.822 [1096] tap:   errors 00000034
10/20 14:36:51.839 [1096] tap: set mtu
10/20 14:36:51.964 [1096] sys: run_command(netsh interface ipv4 set subinterface
 "Conexi¾n de ßrea local 4" mtu=1404 store=persistent), done with 1
10/20 14:36:51.986 [1096] tap: GetAdapterIndexByGuid [{EA5DB1D7-9E03-4E8C-A2E2-7
2105CA45E04}]
10/20 14:36:52.010 [1096] tap: adapter 0000000b [\DEVICE\TCPIP_{F795BDD0-FA76-4F
38-9AD9-163286DC5641}]
10/20 14:36:52.033 [1096] tap: do_rename() failed
10/20 14:36:52.051 [1096] tap: del_tapdev(Hamachi)
10/20 14:36:52.064 [1096] tap: list_netdev_win32() ..
10/20 14:36:52.115 [1096] tap: unknown device
10/20 14:36:52.128 [1096] tap: add_tapdev() failed

C:\Program Files (x86)\LogMeIn Hamachi\x64>hamachi-2.exe --upd-tap
10/20 14:39:23.901 [3560] hamachi-2.exe10/20 14:39:23.902 [3560] assert pos != -
1 in ..\client2\engine\win32\main.cpp:413

C:\Program Files (x86)\LogMeIn Hamachi\x64>hamachi-2.exe --add-tap "Hamachi"
10/20 14:39:32.552 [3120] tap: add_tapdev(Hamachi)
10/20 14:39:32.565 [3120] tap: list_netdev_win32() ..
10/20 14:39:32.638 [3120] vpn: adding tap device [Hamachi] ..
10/20 14:39:32.650 [3120] tap: Collecting information...
10/20 14:39:32.782 [3120] tap: Installing driver, step 1 ..
10/20 14:39:32.804 [3120] tap: Installing driver, step 3 ..
10/20 14:39:33.481 [3120] tap: Installing driver, step 4 ..
10/20 14:39:33.496 [3120] tap: Installing driver, step 5 ..
10/20 14:39:33.509 [3120] tap: Done, 0
10/20 14:39:33.523 [3120] tap: list_netdev_win32() ..
10/20 14:39:33.570 [3120] tap: find_new_tapdev: devs_org[0] -> [*teredo]
10/20 14:39:33.584 [3120] tap: find_new_tapdev: devs_org[1] -> [*isatap]
10/20 14:39:33.600 [3120] tap: find_new_tapdev: devs_org[2] -> [pci\ven_14e4&dev
_165a]
10/20 14:39:33.625 [3120] tap: find_new_tapdev: devs_org[3] -> [sw\{eeab7790-c51
4-11d1-b42b-00805fc1270e}]
10/20 14:39:33.651 [3120] tap: find_new_tapdev: devs_org[4] -> [ms_ndiswanip]
10/20 14:39:33.667 [3120] tap: find_new_tapdev: devs_org[5] -> [ms_ndiswanbh]
10/20 14:39:33.680 [3120] tap: find_new_tapdev: devs_org[6] -> [ms_ndiswanipv6]
10/20 14:39:33.700 [3120] tap: find_new_tapdev: devs_org[7] -> [ms_pppoeminiport
]
10/20 14:39:33.723 [3120] tap: find_new_tapdev: devs_org[8] -> [ms_pptpminiport]

10/20 14:39:33.753 [3120] tap: find_new_tapdev: devs_org[9] -> [ms_l2tpminiport]

10/20 14:39:33.777 [3120] tap: find_new_tapdev: devs_org[10] -> [ms_agilevpnmini
port]
10/20 14:39:33.810 [3120] tap: find_new_tapdev: devs_org[11] -> [ms_sstpminiport
]
10/20 14:39:33.845 [3120] tap: find_new_tapdev: devs_new[0] -> [hamachi]
10/20 14:39:33.863 [3120] tap: find_new_tapdev: devs_new[1] -> [*teredo]
10/20 14:39:33.878 [3120] tap: find_new_tapdev: devs_new[2] -> [*isatap]
10/20 14:39:33.899 [3120] tap: find_new_tapdev: devs_new[3] -> [pci\ven_14e4&dev
_165a]
10/20 14:39:33.923 [3120] tap: find_new_tapdev: devs_new[4] -> [sw\{eeab7790-c51
4-11d1-b42b-00805fc1270e}]
10/20 14:39:33.953 [3120] tap: find_new_tapdev: devs_new[5] -> [ms_ndiswanip]
10/20 14:39:33.968 [3120] tap: find_new_tapdev: devs_new[6] -> [ms_ndiswanbh]
10/20 14:39:33.986 [3120] tap: find_new_tapdev: devs_new[7] -> [ms_ndiswanipv6]
10/20 14:39:34.000 [3120] tap: find_new_tapdev: devs_new[8] -> [ms_pppoeminiport
]
10/20 14:39:34.023 [3120] tap: find_new_tapdev: devs_new[9] -> [ms_pptpminiport]

10/20 14:39:34.043 [3120] tap: find_new_tapdev: devs_new[10] -> [ms_l2tpminiport
]
10/20 14:39:34.070 [3120] tap: find_new_tapdev: devs_new[11] -> [ms_agilevpnmini
port]
10/20 14:39:34.093 [3120] tap: find_new_tapdev: devs_new[12] -> [ms_sstpminiport
]
10/20 14:39:34.117 [3120] tap: found new device
10/20 14:39:34.129 [3120] tap:     guid {5FD3D906-BFC8-496C-B1D3-1C27B97FFD1A}
10/20 14:39:34.148 [3120] tap:     name Hamachi Network Interface
10/20 14:39:34.166 [3120] tap:     desc Conexi¾n de ßrea local 2
10/20 14:39:34.178 [3120] tap:   dev_id ROOT\NET\0000
10/20 14:39:34.189 [3120] tap:    hw_id hamachi
10/20 14:39:34.209 [3120] tap:     type 2
10/20 14:39:34.222 [3120] tap:   hidden 0
10/20 14:39:34.234 [3120] tap:  enabled 0
10/20 14:39:34.252 [3120] tap:  running 0
10/20 14:39:34.263 [3120] tap:   status 01802401
10/20 14:39:34.280 [3120] tap:   errors 00000034
10/20 14:39:34.295 [3120] tap: set mtu
10/20 14:39:34.389 [3120] sys: run_command(netsh interface ipv4 set subinterface
 "Conexi¾n de ßrea local 2" mtu=1404 store=persistent), done with 1
10/20 14:39:34.415 [3120] tap: GetAdapterIndexByGuid [{5FD3D906-BFC8-496C-B1D3-1
C27B97FFD1A}]
10/20 14:39:34.438 [3120] tap: adapter 0000000b [\DEVICE\TCPIP_{F795BDD0-FA76-4F
38-9AD9-163286DC5641}]
10/20 14:39:34.461 [3120] tap: do_rename() failed
10/20 14:39:34.473 [3120] tap: del_tapdev(Hamachi)
10/20 14:39:34.493 [3120] tap: list_netdev_win32() ..
10/20 14:39:34.577 [3120] tap: unknown device
10/20 14:39:34.589 [3120] tap: add_tapdev() failed

 

Any help please?

 

Regards


Inbound traffic blocked - Inbound speed 4Bps

$
0
0

I have three PCs connected to a server (all from different locations ie: not that same house). Two out of three of this I can ping and appear to work flawlessly. The third on the other hand isn't. Diagnosing the issue returns the error " Inbound traffic blocked, check firewall settings".

 

  • We have tried allowing hamachi through the firewall in "Allowed apps" as Private and Public.
  • We have tried creating Inbound and Outbound Rules in "Windows Firewall with Advanced Security" with Public and Private profiles.
  • We have tried setting "Traffic" to "allow all" under Peer Properties in hamachi.
  • We have tried running hamachi in admin mode.
  • We have tried disabling Windows Firewall.

Further information

  • No 3rd party Anti-virus or firewall is used on the PC in question.
  • Under "Summary" in "Peer Properties" in hamachi the PC with issues has a In Speed of 4Bps where as the other PCs have a speed of 365 Bps.
  • All options under Peer Properties is identical between the PCs.

Could this issue be caused by the router. If so, and someone tries to explain a possible solution, please explain very clearly as I'm not particuly knowledgable in this area :-) 

 

Any help is greatly appreciated.

Hamachi and it’s cyan dot every 20 seconds.

$
0
0
Hello, so I have this on going problem that I’ve tried to solve for countless hours. I’ve tried almost everything that google has told me but nothing helps. The story is that my friends and I play minecraft, we are all connected by using the hamachi server. This usually happens when I initially start my computer and turn on my hamachi then proceed to join the server. I am able to join the server and then I get disconnected after 20 seconds or so, I go to hamachi and the host’s name on hamachi has a cyan dot while the other still have green. I wait untill the host’s dot turn back to green then I can join again, after 30 seconds I get disconnected again. Then the more I try to join I am able just a little bit longer each time untill there’s a point where I can stay in for a hours, my problem is that sometimes I would try to join 10 times and still only last a few seconds. It’s as if the hamachi server is a car and I need to warm her up before she can stay on.

One computer in network of 3 not working

$
0
0

I am trying to make a 3 node Hamachi Gateway network (all 3 nodes in different locations), I will add as much information as I can about each node.

 

Currently only Node 2 can communicate with the gateway (Node 1). Node 2 can access network drives and servers on the gateway network (192.168.1.X).

 

Node 3 can’t communicate with gateway or any servers on it. (Or ping their 192.168.1.x addresses)

Node 3 has firewall configured and has no errors/warning in “Hamachi Self-Diagnosis”

 

--------------------------------------------------------------------------------------------

Node 1:

Debian 9.2.1 Linux (Set as Gateway)

AMD Geode LX 800 (500MHz Processor)

Hamachi 2.1.0.174-1_i386
Haguichi 1.3.8 GUI

Computer is on a 192.168.1.X network and is allocated an IP via local router DHCP

IPv4 with CGNAT Global IP address

--------------------------------------------------------------------------------------------------

 

Node 2:

My laptop (works)

Windows 10 32bit

Hamachi Windows

 

IPv4 Routing Table

Network Destination        Netmask       Gateway       Interface                Metric

0.0.0.0                             0.0.0.0       192.168.178.1   192.168.178.137     50

0.0.0.0                             0.0.0.0             25.0.0.1      25.79.99.99          9256

 

Hamachi Virtual Adapter

IPv4 Address. . . . . . . . . . . : 25.79.99.99(Preferred)

 

Hamachi Virtual Adapter 2

IPv4 Address. . . . . . . . . . . : 192.168.1.99(Preferred)

-------------------------------------------------------------------------------------------

 

Node 3:

Other Client (Not working)

Windows 10 64bit

Hamachi Windows

 

Network Destination        Netmask          Gateway       Interface  Metric

0.0.0.0                             0.0.0.0    192.168.1.254  192.168.1.109     35

 

Hamachi Virtual Adapter

IPv4 Address. . . . . . . . . . . : 25.29.99.88(Preferred)

 

Hamachi Virtual Adapter 2

IPv4 Address. . . . . . . . . . . : 10.40.1.242(Preferred)

------------------------------------------------------------------------------------------

 

From what I can see, Hamachi Virtual Adapter 2 on Node 3 should be 192.168.1.X, but isn’t.

Node 3 has a Windows IPsec VPN configured in "Network & Internet Settings", but it's not active/connected.

 

What could be wrong?

hello

Detect caller Hamachi address when initiating RDP

$
0
0

Hello,

My application runs in an RDP virtual machine where users may have logged in from any of various local computers, all linked by a Hamachi network. Is there any way I can detect the hamachi address (or, less desirably, the public IP address because it may change) of the calling machine, i.e, the machine that was used to originate the RDP session?

Welcome to the new LogMeIn Hamachi Community!

$
0
0

Hello everyone!

 

I am very pleased to welcome you all to the new and improved LogMeIn Hamachi Community! Thank you for your patience during the maintenance window.

 

Along with giving our communities a new look we have also reorganized them, making it easier for you to find the information you need about LogMeIn products and services. We have some great new features for you to take advantage of such as:

  • Get mobile: our new design is responsive so you can get help on the go - from your tablet, phone or desktop device!
  • More product communities: We expanded the number of product communities for you to engage in here by adding our GoTo product forums to the LogMeIn Community. Select a product community from the navigation bar.
  • New avatars: All existing users’ avatars will be reset to the default avatar, so you can choose from our new collections or upload your own.
  • Share the Kudos: Show your appreciation for a helpful user but giving them a kudo! Click the thumbs up!

The community is the still the best place to share your knowledge and feedback, ask questions and get answers from fellow LogMeIn Hamachi users. I hope you enjoy the new experience!

 

For help getting started, please read the Getting Started post!

 

Sincerely,
Lisa Kate
LogMeIn Community Manager

My friend is having a problem with his hamachi client.

$
0
0

everytime he launches his hamachi client he gets a yellow error message saying this in diagnostic report

Hamachi self-diagnostic result file
Date2017 - 09/30 17:06:08.407

Tunnel:
VPN domain's tap device is down

Local results:
Adapter configuration:
Cannot get adapter config
Traffic test: Cannot complete test
Peer results: [202-305-469]
Adapter configuration: OK
Traffic test: OK

but when i diagnose him i get this:

 

Summary report
------------------------

Test name: Peer Result: [RED] -> Problems found
Details:

Tunnel: OK

Local results:
Adapter configuration: OK
Traffic test: OK
Peer results: [217-691-794]
Adapter configuration:
Cannot get adapter config
Traffic test: Cannot complete test

---------------------------------------------

   We have tried everything, including regedit deleting the tree and switching routers, and uninstalling and reinstalling, it would be very much apreciated if we could get some help.

 


hamachi doesn't connect wihtout proxy !!

$
0
0

hey guys i installed hamachi

i couldn't ever connect without using proxy changer

but this proxy softwares always make high ms and lag 

is there is a solution ?

Remote Gateway with 2 Network Adapters

$
0
0

I wanted to use Hamachi to have our on site techs use their Hotspot to connect to the internet via wifi and have the Hamachi pass the wired connection to the equipement racks so a remote support guy can log into the network and see the wired adapter of the on site guy so the remote support guy can see all of the gear in the rack to make changes to the systems. When we try this we only get the IP address of the WIFI adapter so there is no way to get to the rack. 

ie. The onsite guy gets 172.20.xx.xx on his wifi so the remote support user sees that address but the onsite guy has his computer wired to the rack with a 192.168.1.xxx address. 

Is there a way to "bridge" or forward everything so the remote support guy gets the 192.168.1.xx  network rather than the 172.20.xxx.xxx network? 

 

Ja pierdole

$
0
0

Kurwa mać, co to za chujstwo? człowiek półgodziny weryfikacje przechodzi a tylko chce poexpić no co to jest, pisze skarge do Uni Europejskiej ;D pozdro dla gimbuff

Getway Problem

$
0
0

Hello

I am new here and install Logmein Hamachi few days ago and I am stuck there.

I set a getway type network and try to get ip from my local router.

Getway

Hamachi

 

 

 

 

Nova rede IP: caraieusouummerdamermao Senha: joaopaulo

Entra ai Man

$
0
0

Nova rede IP: caraieusouummerdamermao Senha: joaopaulo

I can't connect back to my hardwired connection after Hamachi

$
0
0

I downloaded Hamachi to play a game, and now I cant go back to my proper hardwired connection. Please help.


New Router Problem (Possibly).

$
0
0

I was working on a new Minecraft server for me and my friends to enjoy. I invited one of my friends, who was in my Hamachi network that I hosted, to join me. I allowed Hamachi through my firewall, and even turned my firewall of completely. We made sure we were both connected, but he still couldn't get through. Neither can my other friend, after we tried the exact same thing. 

 

I found nothing on Google, and I narrowed it down to the fact that we got a new router recently, and that that might be the cause of the issue. Any help is greatly appreciated. If you need any more info contact me through this post.

 

Cam :D

MULTIPLAYER DOS GAME (F1 GP2)

$
0
0

I'm trying to play in multiplayer with a friend  with F1 GP2 , DOS version, 1995 game!!

Is there anyone that can explain me how to play in multiplayer online or with a cable that connect two pc in the same room?

Thank you

Hamachi trying to use ethernet and I don't have an ethernet cable, I have antennaes.

$
0
0

As stated, I don't have an ethernet cables, but it tries to use ethernet instead of wireless, what do I do?

Ubuntu 17.10 hamachid crashes on login (glibc 2.26)

$
0
0

Like Slackware and Arch Linux before it, the all new Ubuntu version 17.10 is now shipping with glibc 2.26 and Hamachi will crash as soon as you attempt to login. Just putting it out there.

 

Start hamachid with some debugging....

 

ztefn@ubuntu:~$ sudo /opt/logmein-hamachi/bin/hamachid debug
10.19 13:09:14.491 cfg: load()
10.19 13:09:14.492 dbg: deploy_id '' parse failed
10.19 13:09:14.492 cfg: hkc set: [2048] [2048]
10.19 13:09:14.492 cfg: save()
10.19 13:09:14.515 cfg: hks: [0] [2048]
10.19 13:09:14.515 cfg: hkc: [0] [2048] [2048]
10.19 13:09:14.515 starting up ..
10.19 13:09:14.515 sys: version linux-2.1.0.174
10.19 13:09:14.516 sys: os Linux 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64
10.19 13:09:14.516 vpn: IPv6 support is: 3
10.19 13:09:14.517 ipc: 5 listening at /var/run/logmein-hamachi/ipc.sock
10.19 13:09:14.517 avc: start
10.19 13:09:14.517 sys: initializing vpn domains, vpn-reinstall = 0 ..
10.19 13:09:14.517 vpn: added [Hamachi] domain (not roaming)
10.19 13:09:14.517 10.19 13:09:14.517 dbg: setup_vpn_domain [Hamachi]
avc: retry 2, [1]
10.19 13:09:14.517 dbg: vpn_domain::config - [Hamachi]
10.19 13:09:14.517 vpn: switched [Hamachi] domain into L3 mode, 0.0.0.0/0.0.0.0
10.19 13:09:14.517 dbg: enable(Hamachi), locked: 0
10.19 13:09:14.518 vpn: domain [Hamachi] -> 'VPN_opening'
10.19 13:09:14.518 vpn: enabling [Hamachi] domain ..
10.19 13:09:14.518 vpn: on_set_tapdev(, 1) -> ok
10.19 13:09:14.518 tap: device ham0 opened
10.19 13:09:14.520 vpn: domain [Hamachi] -> 'VPN_up'
10.19 13:09:14.520 dbg: setup_vpn_domain [Hamachi]
10.19 13:09:14.520 dbg: vpn_domain::config - [Hamachi]
10.19 13:09:14.521 vpn: domain [Hamachi] -> 'VPN_setting_up'
10.19 13:09:14.521 tap: config(ham0, 0.0.0.0, 0.0.0.0, [/0])
10.19 13:09:14.521 tap: if_config() -> 1
10.19 13:09:14.521 vpn: tap config done, [ok]
10.19 13:09:14.521 vpn: domain [Hamachi] -> 'VPN_up'
10.19 13:09:14.521 vpn: added [Null] domain (not roaming)
10.19 13:09:14.521 dbg: setup_vpn_domain [Null]
10.19 13:09:14.521 dbg: vpn_domain::config - [Null]
10.19 13:09:14.568 avc: retry 2, [2]
10.19 13:09:14.619 avc: retry 2, [3]
10.19 13:09:14.669 avc: retry 2, [4]
10.19 13:09:14.720 avc: retry 2, [5]
10.19 13:09:14.770 avc: th_end
10.19 13:09:14.770 avc: warning, avc not ready, fallback
10.19 13:09:14.770 resolv: url has ip on it
10.19 13:09:17.910 avc: retry 1, [1]
10.19 13:09:17.910 resolv: url has ip on it
10.19 13:09:20.916 avc: retry 1, [2]
10.19 13:09:20.917 resolv: url has ip on it
10.19 13:09:23.988 avc: retry 1, [3]
10.19 13:09:23.989 resolv: url has ip on it
10.19 13:09:27.060 avc: retry 1, [4]
10.19 13:09:27.060 resolv: url has ip on it
10.19 13:09:30.132 avc: retry 1, [5]
10.19 13:09:30.133 resolv: url has ip on it
10.19 13:09:33.204 avc: false, f: [send], e: [71]
10.19 13:09:33.204 avc: on_avc_res, [1], [0]
10.19 13:09:33.204 avc: send later at sync

 

...and see what happens after "hamachi login" command...

 

10.19 13:10:32.586 ipc: user ztefn allowed
10.19 13:10:32.586 ipc: 01590740 add client 1
10.19 13:10:32.586 cfg: save()
10.19 13:10:32.597 cfg: hks: [0] [2048]
10.19 13:10:32.597 cfg: hkc: [0] [2048] [2048]
10.19 13:10:32.597 sys: connmgr_go_online, reconnect 0
10.19 13:10:32.636 ses: on_conn_state(connected, 0x0)
10.19 13:10:32.636 ses: select conn mode 'dns lb'
10.19 13:10:32.636 ses: go_offline, keep_tunnels 1, login_on_relaunch 0, actual state 4 ..
10.19 13:10:32.673 sys: go_online, reconnect 0
10.19 13:10:32.691 ses: resolving hamachi-dc.logmein-gateway.com ..
10.19 13:10:32.706 ses: resolving hamachi-list.10.logmein-gateway.com ..hamachid: relocation error: hamachid: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

 

Hamachi not working when restarting my router (raspbian)

$
0
0

Hi guys i have a network set up between my laptop and my rasbian raspberry pi from home, the thing is someone at my house restart the router the raspberry pi doesnt seem to connect back to the network unleast i restart the pi, how can i fix this?

Viewing all 3259 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>