Jump to content

muondude

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About muondude

  • Rank
    Occasional Forum Poster
  1. muondude

    Retrospect 5.1 and Linux Clients

    Quote: natew said: The thing to keep in mind is that Multicast is only used for client discovery. If you have a workgroup or server version of Retrospect you can connect to the client by direct IP, bybassing multicast completely. How do I check which version I have. I recently upgraded from 4.3 (which had a 'server' mode) to 5.1 on my Mac. I haven't run it in any server mode, but I do have scripts that backup the different clients on my lan to DAT tape. I also think that I could use the route command to force the broadcast to the LAN nic.... maybe...
  2. Thanks for creating this. Any chance of getting a version that works with Debian 3.0r2 (stable)? I got it to install with --force-depends, but that causes problems with up-dating other packages. Is there anything in particular between stable and testing? regards, Sam
  3. muondude

    Retrospect 5.1 and Linux Clients

    Help me out here. 1. Are you saying that the retroclient uses some form of multicast (via udp??) to annouce itself to the network? And that it is the kernel that determines on which interface (eth0 or eth1) that broadcast shows up? So are you saying that on my dual NIC system the kernel is using eth0 and that is why I don't see it on eth1? If this is true I should be able to detect this on the eth0 side of my system? 2. I did an /sbin/ifconfig on my system and BOTH eth0 and eth1 show the line: UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 3. I'm really confused. What does the binding of the client to a particular IP then accomplish? 4. I may take my test system on my lan, on which the retroclient works fine, add another nic and see if I can see the client on either nic. I should be able to give both of them 192.168.x.x addresses and see what's up. thanks.
  4. muondude

    Retrospect 5.1 and Linux Clients

    I seem to have experienced the same problem and wonder if anyone has found a solution. I am using Debian 3.0r2. I setup a test box with a minimal debian install, and a single NIC on a 192.168.x.x LAN. It worked fine using Robin's Debian .deb file (although I had to use --force-depends). When installed on the Debian box with 2 NICs (my LAN/WAN interface) it doesn't seem to work, the Mac 5.1 Retrospect server doesn't see it. I ran nmap and netstat and it appears that the client is listening. I even tried setting the IP to the LAN interface only. Any suggestions? Also any chance of getting a Debian version that uses the "stable" version libraries so we don't have to force-depends (Debian doesn't like that). Thanks.
  5. Thanks! I don't plan on using the GUI, so I won't need Java. Cool
  6. You are correct. dpkg -l libc6 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-====================-====================-============== ii libc6 2.2.5-11.5 GNU C Library: Shared libraries and Timezone data I checked and the version in debian "testing" is: libc6 2.3.2-7 I haven't tried the install yet, but this gives me food for thought! Thanks.
  7. does the Retrospect client require Java to be installed? I'm going to try the Debian package you created on my system and want to make sure I have all the prerequisites. BTW: thanks for creating the .deb package.
×