1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Bonjour over VPN Tunnel?

Discussion in 'Tomato Firmware' started by EntityPacket, Dec 24, 2010.

  1. EntityPacket

    EntityPacket LI Guru Member

    I'm running a TUN VPN between two Linksys routers and am wondering how to go about getting Bonjour working across the tunnel. Is it possible to relay the multicast traffic, specifically for Bonjour across the tunnel?

    On a side note... I use the tunnel primarily as a way to secure remote desktop connection to my parents computer to assist them as needed. I use my side as the client and their side as the server. I have the 'Allow Client<->Client' setting enabled on the server side, however, from my parents network I am unable to initiate communication with my network. I'm wondering why this is?
     
  2. SgtPepperKSU

    SgtPepperKSU Network Guru Member

    I've never done it, so I don't know if there are any complications, but I think you'd have to use TAP to get Bonjour working over the tunnel.

    "Allow Client<->Client" does just that: allows one client to route to another client. It has nothing to do with Client<->Server communication. See here on how to get server-initiated connections working.
     
  3. occamsrazor

    occamsrazor Network Guru Member

    I use a TAP tunnel and Bonjour works fine. E.g. After I've connected and have Apple Remote Desktop (admin program) running, client devices quickly pop in the list of "local" devices
     
  4. rhester72

    rhester72 Network Guru Member

    Ditto.

    Rodney
     
  5. EntityPacket

    EntityPacket LI Guru Member

    Thanks for the replies. I got the server to client communication working which is great. I switched from TUN to TAP and readdressed my network so they're all on the same subnet, however, I am unable to communicate layer 3 across the tunnel. I see bytes sent and read on both sides but unable to pass any layer 3 traffic. I'll have to go back and look at the logs and try and figure out what I did wrong. In the meantime I switched back to TUN.
     
  6. EntityPacket

    EntityPacket LI Guru Member

    I'm trying again to get TAP working and I just can't figure it out. I see the following values from the server which seem to indicate the tunnel is up, but I am unable to communicate across the tunnel. I pretty much changed TUN to TAP (TLS) and used the same keys. Any suggestions what I'm doing wrong?

    Value
    TUN/TAP read bytes
    0
    TUN/TAP write bytes
    11040
    TCP/UDP read bytes
    15988
    TCP/UDP write bytes
    5298
    Auth read bytes
    11040
    pre-compress bytes
    0
    post-compress bytes
    0
    pre-decompress bytes
    9048
    post-decompress bytes
    1077
     
  7. SgtPepperKSU

    SgtPepperKSU Network Guru Member

    If you were using TUN, your server and client had to have been on different subnets. For TAP, they either need to be on the same subnet or have "Server is on same subnet" unchecked on the client. However, they have to be on the same subnet to gain any of the benefits of TAP (having "Server is on same subnet" unchecked is pretty much just an inefficient version of using TUN).
     
  8. EntityPacket

    EntityPacket LI Guru Member

    I do change the subnet on one side (the server) to match the client subnet so everyone is utilizing a 192.168.1.0/24 one router with 192.168.1.1 and one 1.2
     

Share This Page