Search the Community
Showing results for tags 'Multicast'.
Found 3 results
I've been searching for something in my network with wireshark as I'd realized that BTSync sends 8-10 multicast-packets for LAN-peer-find per second while connected via WiFi to my network. Is that a bug or a nice feature to force the users to get gigabit-switches?
Hi All, I've installed bittorrent sync successfully on my Qnap Nas (ARM) at home and my win 7 laptop at work, both machines are successfully "mated" and a full & complete sync has finished....in other works bittorrent has worked beautifully. The Problem: the Bsync client on my work Laptop is permanently sending out multicast messages on the Local LAN (work lan) on USP port 3838. While this wouldn't be a problem under normal circumstances where I'd be in control of both environments in this case it's driving the IT administrators crazy in my work place because they simply think I'm torrenting out to the wider internet (like traditional torrents). I would like to STOP network traffic on UDP port 3838 OR at a minimum put it on TCP (so as to keep them off my back). It's important to bear in mind that I don't have access to LAN routers so can't block the port at the router level. Can you guys tell me if this is possible and how I might do it (if possible) thanks in Advance
I observed a large number of packets from BitTorrent Sync's LAN discovery hitting my Linux firewall: [31888.915645] [UFW BLOCK] IN=eth0 OUT= MAC= SRC=184.108.40.206 DST=220.127.116.11 LEN=126 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=3838 DPT=3838 LEN=106 Running tcpdump at the same time displays the outgoing packets (and the firewall catches and blocks the return) When I shut off "LAN Search" for all my shares, it instantly stops. The problem with this is that my workstation running btsync is also my NAT router and WiFi AP, it has 3 interfaces: eth0 connected to the Internet eth1 connected to my LAN wlan0 wireless LAN, note this is on it's own subnet, not bridged with eth1 If I add the following route, the broadcasts immediately start getting sent out on eth1 where my LAN actually is: ip route add 18.104.22.168/14 dev eth1 Is there anyway to configure this within BitTorrent Sync, for example select a LAN interface so I don't broadcast multicast stuff to all my cable modem neighbors and so that I actually discover devices on my LAN? This also prevented LAN discovery from working. I imagine this could be a problem for laptops with Ethernet + WiFi, but they likely aren't both enabled at the same time.