D-LAN: Technicalhttp://dev.d-lan.net/http://dev.d-lan.net/favicon.ico?15495416382021-10-24T18:48:39ZRedmine
Redmine Technical: RE: One Computer Finds the Other, but The Other Computer Doesn't Find the Firsthttp://dev.d-lan.net/boards/4/topics/98?r=100#message-1002021-10-24T18:48:39ZRomLAN RomLAN
<p>I forgot to say : wether you define a special NIC in D-LAN, the program will use the Virtualbox card instead without telling you. That's the essence of the problem.</p> Technical: RE: One Computer Finds the Other, but The Other Computer Doesn't Find the Firsthttp://dev.d-lan.net/boards/4/topics/98?r=99#message-992021-10-24T18:37:26ZRomLAN RomLAN
<p>Hi Siamak Ensafi , I've just found the solution of the problem.<br />I tried <em>LanShark</em> : and it also had the same "bug". <br />But when I tried the _ "Open web GUI"_ feature of LanShark, I noticed that the PC having only one entry had an IP like "169.xxx.xxx.xxx". It's a default IP that is set when IP auto-addressing fails.<br />By doing an ipconfig /all I also notices that VIRTUALBOX had addressed the exact same IP.</p>
*<del>---</del> SOLUTION TO D-LAN ASYMETRY ISSUE ----- *
<ol>
<li>Go in the <em>"Network sharing center"</em> (I won't explain how to).</li>
<li>Click on <em>"Modify the settings of the card"</em> (I'm french so I'm translating)</li>
<li>Right-click on the VirtualBox virtual card and disable it.</li>
<li>Do the same for programs like Kaspersky antivirus, they may replace Virtualbox as a primary NIC access.</li>
</ol>
<p>I guess that the definition of what is prefered by Windows is conflicting with programs like D-LAN. The funny thing is nobody seems to have ever noticed it <strong>because until programs can display the address they really use (like LanShark), you cannot even have a clue of what NIC is used</strong> .<br />An other funny thing is : I've recently been into NDI plugin for OBS Studio and faced the issue of the plugin choosing one of my two NIC card without me being able to direct him to the good one (the one used to link the PC with the other). Seems like a "deja vu" in the matrix ;)</p> Technical: One Computer Finds the Other, but The Other Computer Doesn't Find the Firsthttp://dev.d-lan.net/boards/4/topics/982020-07-07T08:46:28ZSiamak Ensafi
<p>Hello, I have this weird problem with D-LAN. I have set up both computers. One is a desktop and the other a laptop. Both are set to IPv6 (I have also tried IPv4 on both earlier).</p>
<p>However, Desktop detects and lists my laptop as a peer. and laptop fails to detect. I can send messages from laptop to desktop and they can be seen on desktop, but not vice versa.</p>
<p>Please help me figure out what is causing this?</p>
<p>By the way, thanks for the free program. Much appreciated.</p> Technical: RE: How to uninstall service on Ubuntu?http://dev.d-lan.net/boards/4/topics/81?r=85#message-852014-10-09T00:23:32ZSteven Hufhuffy7412@gmail.com
<pre>
d-lan-core --help
</pre><br /><strong>facepalm</strong> not sure why I didn't try that first :P<br />Thanks for the response.
<p>Looks like something is not working with UDP multicasts in my network... even windows -> windows cannot see each other at the moment...</p> Technical: RE: How to uninstall service on Ubuntu?http://dev.d-lan.net/boards/4/topics/81?r=83#message-832014-10-07T09:31:42ZGreg Burrigreg.burri@gmail.com
<p>Hi,<br />You can un-install D-LAN service by using the following command:<br /><pre>
d-lan-core -u
</pre></p>
<p>You can install D-LAN service for another user with:<br /><pre>
d-lan-core -i <user> <password>
</pre></p>
<p>Try this for more information:<br /><pre>
d-lan-core --help
</pre></p> Technical: How to uninstall service on Ubuntu?http://dev.d-lan.net/boards/4/topics/812014-10-01T15:08:51ZSteven Hufhuffy7412@gmail.com
<p>sudo d-lan-core -i seems to have installed it properly, but it's running under the wrong user.</p>
<p>How do I uninstall the service so I can reinstall it to run under the correct one?</p> Technical: RE: Fails installing D-Lan on linuxhttp://dev.d-lan.net/boards/4/topics/72?r=75#message-752014-05-15T18:25:20Zlynx MAXlynxmax@free.fr
<p>Hello,</p>
<p>Thank you for your reply.</p>
<p>I solve the problem by manually installing the good version of libprotobuf. I hae lernas the apt-get command :), and now every think works fine.</p>
<p>This topic cant be closed<br />LynxMax</p> Technical: RE: Fails installing D-Lan on linuxhttp://dev.d-lan.net/boards/4/topics/72?r=74#message-742014-05-14T09:29:17ZGreg Burrigreg.burri@gmail.com
<p>Hi, I tries to install on Xubuntu 14.04 and everything seems fine. D-LAN needs libprotobuf 2.4.1 or greater which is included in Ubuntu. Did you solve your issue?</p> Technical: RE: Fails installing D-Lan on linuxhttp://dev.d-lan.net/boards/4/topics/72?r=73#message-732014-05-14T08:52:21Zlynx MAXlynxmax@free.fr
<p>forget my answer wrong understandinf of the message</p> Technical: Fails installing D-Lan on linuxhttp://dev.d-lan.net/boards/4/topics/722014-05-10T08:16:37Zlynx MAXlynxmax@free.fr
<p>Hi,</p>
<p>I try to install D-Lan for linux on a Lubuntu 14.04. When I unpacted your .deb I have an error : "la dependance ne peut etre satisfaite : libprotobuf7 > 2.4.1.</p>
<p>As I understand you have a dependancie with have to updated, correct?</p>
<p>Thank for reply.<br />LynxMax</p> Technical: RE: Lintian checks on .deb package failshttp://dev.d-lan.net/boards/4/topics/59?r=62#message-622013-02-04T15:14:07ZSpace Fishdlan@spacefish.biz
<p>The new one works without complaining :) thanks a lot for the quick reply / fix!</p> Technical: RE: Lintian checks on .deb package failshttp://dev.d-lan.net/boards/4/topics/59?r=61#message-612013-02-04T01:09:14ZGreg Burrigreg.burri@gmail.com
<p>I made some changes, can you test this package: <a class="external" href="http://www.d-lan.net/home.html&dl=D-LAN-1.1.0Beta15-2013-02-04_00-51-amd64.deb&platform=Linux%2064-bits">http://www.d-lan.net/home.html&dl=D-LAN-1.1.0Beta15-2013-02-04_00-51-amd64.deb&platform=Linux%2064-bits</a></p> Technical: RE: Lintian checks on .deb package failshttp://dev.d-lan.net/boards/4/topics/59?r=60#message-602013-02-02T07:43:02ZGreg Burrigreg.burri@gmail.com
<p>Hi, thanks for reporting it, this is a known issue, it will be fixed in the next version (1.2): <a class="external" href="http://dev.d-lan.net/issues/231">http://dev.d-lan.net/issues/231</a></p> Technical: Lintian checks on .deb package failshttp://dev.d-lan.net/boards/4/topics/592013-02-02T01:42:21ZSpace Fishdlan@spacefish.biz
<p>i get the following lintian check failures when i try to install the package:</p>
<p>Lintian check results for /home/spacefish/Downloads/D-LAN-1.1.0Beta15-2012-12-16_16-45-amd64.deb:<br />E: d-lan-all-in-one: control-file-has-bad-permissions postinst 0775 != 0755<br />E: d-lan-all-in-one: control-file-has-bad-owner postinst gburri/gburri != root/root<br />E: d-lan-all-in-one: control-file-has-bad-permissions prerm 0775 != 0755<br />E: d-lan-all-in-one: control-file-has-bad-owner prerm gburri/gburri != root/root<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/ 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/ 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/applications/ 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/applications/d-lan.desktop 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/ 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/D-LAN.Core 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/D-LAN.GUI 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/languages/ 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/languages/d_lan_core.fr.qm 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/languages/d_lan_gui.fr.qm 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/ 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/ 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/arrow_down.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/checkbox_checked.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/checkbox_unchecked.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/close.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/dockwidget_close.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/dockwidget_min.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/grip.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/maximize.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/minimize.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/radiobox_checked.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/radiobox_unchecked.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/scrollbar_arrow_bot.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/scrollbar_arrow_left.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/scrollbar_arrow_right.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/scrollbar_arrow_top.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/style.css 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/title.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/treeview_arrow_closed.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/treeview_arrow_closed_highlight.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/treeview_arrow_opened.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/treeview_arrow_opened_highlight.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/d-lan/styles/l33t/unmaximize.png 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/icons/ 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/icons/hicolor/ 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/icons/hicolor/128x128/ 1000/1000<br />E: d-lan-all-in-one: wrong-file-owner-uid-or-gid usr/share/icons/hicolor/128x128/apps/ 1000/1000</p> Technical: RE: Erreur "queue.pb.cc non trouvé" en compilant D-LAN sous Sevenhttp://dev.d-lan.net/boards/4/topics/57?r=58#message-582012-11-08T22:37:18ZGreg Burrigreg.burri@gmail.com
<p>Bonjour,</p>
<p>Si vous utilisez la branche 1.1, ce qui me semble être le cas, il faut générer les fichiers C++ de Protocol Buffer à la main. Allez simplement dans le dossier "application" à l'aide d'une ligne de commande sous bash (en utilisant par exemple le raccourci "Git bash" installé avec git) et tapez "1.generate_protos_cpp.sh". Je vais l'ajouter dans le 'How-to'.</p>
<p>Les scripts se trouvant dans ce dossier servent principalement à la création d'une release.</p>
<p>++</p> Technical: Erreur "queue.pb.cc non trouvé" en compilant D-LAN sous Sevenhttp://dev.d-lan.net/boards/4/topics/572012-11-08T22:20:57ZDaniel Kihndaniel.kihn@gmail.com
<p>Bonjour,</p>
<p>L'idée D-LAN répond totalement à mon besoin de déployer rapidement et simplement des VM à usage pédagogique en réseau local. Je l'ai donc testé, avec succès chez moi, mais je rencontre un problème en environnement de production : l'adresse IP du client devient, pour les autres clients, l'adresse de la patte externe de la passerelle internet. Je suis en IPv4, sous 7x64, en domaine. Plutôt que m'en plaindre j'ai l'intention de comprendre et de corriger ce qui ne va pas.</p>
<p>J'ai donc suivi à la lettre le document "Howtos - Hack on Windows Seven."</p>
<p>Problème : [c:/D-LAN/application/Protos/queue.pb.cc] Error 1 Fichier non trouvé.<br />En sortie de compilation le premier des semblables nombreux warnings est :<br />WARNING: Failure to find: ..\Protos\gui_protocol.pb.cc</p>
<p>Pourriez-vous me dire où me suis-je trompé ?</p>
<p>Merci</p> Technical: RE: Peer discovery on 255.255.0.0 instead of 255.255.255.0 or a local peer cache, how to?http://dev.d-lan.net/boards/4/topics/51?r=56#message-562012-09-16T06:19:08ZGreg Burrigreg.burri@gmail.com
<p>Yes, it might work, the only problem is that the remote address is read directly from the received datagram: <a class="external" href="https://github.com/Ummon/D-LAN/blob/master/application/Core/NetworkListener/priv/UDPListener.cpp#L215">https://github.com/Ummon/D-LAN/blob/master/application/Core/NetworkListener/priv/UDPListener.cpp#L215</a> I don't know how you can resolve this problem.</p>
<p>The best solution would be to implement manually added peers, but it's not so easy. Maybe I will do that in the 1.1 branch.</p> Technical: RE: Peer discovery on 255.255.0.0 instead of 255.255.255.0 or a local peer cache, how to?http://dev.d-lan.net/boards/4/topics/51?r=55#message-552012-09-15T18:22:18ZEmad Medheremad.medher.swe@gmail.com
<p>Hi, Thank you for the fast reply. And I am terribly sorry not being able to reply any sooner. Especially since you really replied shortly after my last message.</p>
<p>I feel like a retard to mix multicast and broadcast up............... Thank you for pointing me to that direction.</p>
<p>Our network is quite restrictive and multicast is blocked. And I would think the ITC will block certain ports when we start using D-LAN on the network. So I thought since:<br />- More than one process can bind to the multicast port.<br />- D-LAN doesn't keep track of peerlist. because it finds them all at startup<br />- D-LAN is opensource, so as D-LAN's peer discovery protocol</p>
<p>I thought of opening the port locally again from a program I will make and "feed" D-LAN the addresses as I claim to be different users broadcasting. I think this would work since I tried connecting to other D-LANs guy directly from the settings and it works so unicast is working just fine.</p>
<p>Can you please confirm that what I wrote make sense? or slap me on the face and wake me up to my retardness again? Thank you.</p>
<p>If it made sense and quite doable. Would you please describe the initial communication over multicast so I imitate it? I would be using java to utilize the library "TomP2P" for caching peers.</p>
<p>Thank you very much for the help so far. I really appreciate it.</p>
<p>Emad/</p> Technical: RE: Peer discovery on 255.255.0.0 instead of 255.255.255.0 or a local peer cache, how to?http://dev.d-lan.net/boards/4/topics/51?r=54#message-542012-09-15T06:19:56ZGreg Burrigreg.burri@gmail.com
<p><cite>- The DHCP server sets our network to broadcast on 255.255.255.0, If we manually set the broadcast address to 255.255.0.0 (Assuming the routing actually allows it). Would that be just enough for the peer discovery to work</cite>?</p>
<p>No no!! Don't do that, this is the net mask to determine your sub-network number and your host number<sup><a href="#fn1">1</a></sup>, you will be unable to communicate with other networks if you change it. Actually D-LAN isn't using broadcasting but <strong>multicasting<sup><a href="#fn2">2</a></sup></strong>. The multicast address and the port are <code>236.13.43.24:59486</code> (IPv4).</p>
<p>[1]: <a class="external" href="http://en.wikipedia.org/wiki/Subnetwork">http://en.wikipedia.org/wiki/Subnetwork</a><br />[2]: <a class="external" href="http://en.wikipedia.org/wiki/Multicast">http://en.wikipedia.org/wiki/Multicast</a></p> Technical: RE: Peer discovery on 255.255.0.0 instead of 255.255.255.0 or a local peer cache, how to?http://dev.d-lan.net/boards/4/topics/51?r=53#message-532012-09-15T01:27:39ZEmad Medheremad.medher.swe@gmail.com
<p>Hello, Thank you for answering.</p>
<p>The inner working of the of the LAN is not public knowledge and our ITC is really not cooperating so we have to test these ports ourselves, we are working on it. Thank you for pointing us to the right direction, for code and settings.</p>
<p>Another small question if I may ask,</p>
<p>- The DHCP server sets our network to broadcast on 255.255.255.0, If we manually set the broadcast address to 255.255.0.0 (Assuming the routing actually allows it). Would that be just enough for the peer discovery to work?</p>
<p>Thank you again.</p>
<p>Emad</p> Technical: RE: Peer discovery on 255.255.0.0 instead of 255.255.255.0 or a local peer cache, how to?http://dev.d-lan.net/boards/4/topics/51?r=52#message-522012-09-14T15:59:23ZGreg Burrigreg.burri@gmail.com
<p>Hi, thanks for your comment.</p>
<p>There is actually no way to manually add some peers to the list. I will take a note about that to maybe implement this in a further version.</p>
<p>I guess your 'x' is the network address, so to communicate, for instance, between 10.80.1.1 and 10.80.2.1 the data has to pass a router (IP level). The router may not relay UDP multicast traffic for some reasons. The possible causes are listed here:</p>
<ul>
<li>The router explicitly forbids multicast </li>
<li>The router doesn't support multicast IPv4 (support of IPv4 multicast is optional but IPv6 is mandatory)</li>
<li>The port is intentionally blocked by the router (59486)</li>
<li>TTL (time to live) is decreased to 0. It should not be the case, the default value is 31.</li>
<li>Other reasons?</li>
</ul>
<p>Did you try to switch to IPv6? (in 'Settings' -> 'Network'), maybe it can resolve the issue.</p>
<p>Here is the involved code :</p>
<ul>
<li><a href="https://github.com/Ummon/D-LAN/blob/1.1/application/Core/NetworkListener/priv/UDPListener.cpp#L369" class="external">Multicast socket initialization</a></li>
<li><a href="https://github.com/Ummon/D-LAN/blob/1.1/application/Core/NetworkListener/priv/UDPListener.cpp#L221" class="external">Multicast datagram presence received</a></li>
<li><a href="https://github.com/Ummon/D-LAN/blob/1.1/application/Core/PeerManager/priv/PeerManager.cpp#L124" class="external">Adding or updating a peer</a></li>
</ul>
<p>There is some settings stored in "~/.d-lan/core_settings.txt", description of each fields is here : <a class="external" href="https://github.com/Ummon/D-LAN/blob/1.1/application/Protos/core_settings.proto">https://github.com/Ummon/D-LAN/blob/1.1/application/Protos/core_settings.proto</a></p>
<p>About the connectivity problems between a Windows and a Linux instance I'm not aware about it and I never saw such problem before.</p>
<p>cya</p>
<p>/Greg</p> Technical: Peer discovery on 255.255.0.0 instead of 255.255.255.0 or a local peer cache, how to?http://dev.d-lan.net/boards/4/topics/512012-09-14T00:41:23ZEmad Medheremad.medher.swe@gmail.com
<p>Hi, First of all I want to express my fascination with this project. really hats off to you over the years I found several similar projects like AllianceP2P, LAN Shark and else but got lost in complexity or lack of stability or interested developers.</p>
<p>I would like your help if you may, thank you in advance. We are in a college campus and we are trying to use D-LAN. We have no problem compiling, modifying the code and everything else we just want some heads up and pointers. Our LAN gives IP addresses in the form of 10.80.x.y where x is the building number and y are all IP addresses in the same building. For the same building D-LAN works like a charm but we cannot discover any peers outside the building. Is there any local cache of IP addresses we can manually fill? or can you point us to the peer discovery code so we can change it to our specific network. Thank you for any help.</p>
<p>Also I noticed connectivity problems for connecting a windows instance of D-LAN with a linux instance (Ubuntu 12.04 - 64x). I am still trying to make sure its a bug before I file it. If such connectivity problem is already know, Please tell me so.</p>
<p>Emad Medher</p> Technical: RE: Building on OSX 10.8 Mountain Lionhttp://dev.d-lan.net/boards/4/topics/38?r=50#message-502012-08-31T01:00:56ZColin Deancad@cad.cx
<p>Here's the full thread from above all-in-one.</p>
<p><a class="external" href="http://comments.gmane.org/gmane.comp.lib.qt.user/2206">http://comments.gmane.org/gmane.comp.lib.qt.user/2206</a></p> Technical: RE: Building on OSX 10.8 Mountain Lionhttp://dev.d-lan.net/boards/4/topics/38?r=49#message-492012-08-31T00:59:15ZColin Deancad@cad.cx
<p>I found that the initializer_list missing is an artifact of commenting out the -stdlib=libc++ in common.pri. I uncommented it and rebuilt, and I'm back to the error I'd been getting originally:</p>
<pre>
clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later)
</pre>
<p>So, I did a little more research and came across <a class="external" href="http://www.mail-archive.com/interest@qt-project.org/msg02225.html">http://www.mail-archive.com/interest@qt-project.org/msg02225.html</a>. The conversation just kinda dies without resolution.</p>
<p>I am running the updated Command Line Tools and restarted QtCreator after installing them.</p> Technical: RE: Building on OSX 10.8 Mountain Lionhttp://dev.d-lan.net/boards/4/topics/38?r=48#message-482012-08-31T00:36:57ZColin Deancad@cad.cx
<p>I decided to take another shot tonight, having updated to OSX 10.8.1, QtCreator 4.8.2, and Qt 5.0.0-beta1</p>
<p><a class="external" href="https://gist.github.com/3546582">https://gist.github.com/3546582</a></p>
<p>I think this might be a bug in Qt 5.0.0-beta1 - it appears to be missing a header file.</p>