No peer detection on Linux

[Holyfive]

I have installed Lanshark on a Linux and a Windows PC. Using IP addresses, I am able to share files between these systems perfectly. But only the Windows PC creates an entry in the peer list, the Linux PC doesn't. Perhaps this is related to the fact that on the Linux PC there is more than one network interface in use!? Perhaps it would also be a good idea to enable manual entries in the peer list, so this bug would no more be troublesome.

[Jonas Wagner (veers)]

Hi Holyfive. I need some more information to fix that one:
From the Linux box I need the output of
* ifconfig -a
* route

From the Windows box the following would be nice:
* ipconfig /all
* route PRINT

Thanks :)

[Holyfive (patrick-holz)]

Hi,

alright, here we go:

LINUX

patrick@golgafrincham$ ifconfig -a
eth0 Link encap:Ethernet Hardware Adresse 00:c0:9f:95:30:83
          inet Adresse:134.95.128.31 Bcast:134.95.128.255 Maske:255.255.255.0
          inet6-Adresse: fe80::2c0:9fff:fe95:3083/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
          RX packets:68762 errors:0 dropped:0 overruns:0 frame:0
          TX packets:53311 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:53967587 (51.4 MB) TX bytes:23753445 (22.6 MB)
          Interrupt:16

eth1 Link encap:Ethernet Hardware Adresse 00:12:f0:3b:9f:e6
          BROADCAST MULTICAST MTU:1500 Metrik:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:17 Basisadresse:0x4000 Speicher:c8218000-c8218fff

lo Link encap:Lokale Schleife
          inet Adresse:127.0.0.1 Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING MTU:16436 Metrik:1
          RX packets:4228 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4228 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:7130651 (6.8 MB) TX bytes:7130651 (6.8 MB)

vmnet8 Link encap:Ethernet Hardware Adresse 00:50:56:c0:00:08
          inet Adresse:192.168.103.1 Bcast:192.168.103.255 Maske:255.255.255.0
          inet6-Adresse: fe80::250:56ff:fec0:8/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

patrick@golgafrincham$ route
Kernel-IP-Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
192.168.103.0 * 255.255.255.0 U 0 0 0 vmnet8
134.95.128.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default rzkr-gw.rrz.uni 0.0.0.0 UG 100 0 0 eth0

WINDOWS

C:\Dokumente und Einstellungen\Patrick Holz>ipconfig /all

Windows 2000-IP-Konfiguration

        Hostname. . . . . . . . . . . . . : trillian
        Primäres DNS-Suffix . . . . . . . :
        Knotentyp . . . . . . . . . . . . : Broadcastadapter
        IP-Routing aktiviert. . . . . . . : Nein
        WINS-Proxy aktiviert. . . . . . . : Nein
        DNS-Suffixsuchliste . . . . . . . : localdomain

Ethernetadapter "LAN-Verbindung":

        Verbindungsspezifisches DNS-Suffix: localdomain
        Beschreibung. . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

        Physikalische Adresse . . . . . . : 00-0C-29-6C-B7-85
        DHCP-aktiviert. . . . . . . . . . : Ja
        Autokonfiguration aktiviert . . . : Ja
     ...

[Jonas Wagner (veers)]

Hi Holyfive:

Is this right:
You've got a Linux box and Windows running in a VM and you want to use Lanshark to share file between them?

Can you try this:
On the linux box go to the configuration dialog. Select the advanced tab. Set the broadcast ip to 192.168.103.255.

Cheers!
Jonas

[Holyfive (patrick-holz)]

Hi,

indeed that works. So I have to choose the network interface I want to use by specifying the corresponding subnet?

CU, Patrick

[Jonas Wagner (veers)]

Hi Patrick,
 I
Well it indirectly does that. The routing tables on the linux machine say that the default broadcast address (255.255.255.255) points to eth0. Whereas 192.168.103.255 is routed to vmnet8. I guess it would be cool to somehow broadcast on all devices. I'll look arround for a nice solution :)