1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. While the majority of active discourse on D20PRO has moved to our Discord Channels, this forum is still active and checked-in on regularly by our staff. However, for the very latest information, conversation and/or immediate support, please join us on Discord here: http://discord.gg/Ph38ckM
    Dismiss Notice

3.4.x -- Multiple network interfaces: Trouble!

Discussion in 'Bug Reports & Installation Support' started by Gnorr, Jan 19, 2015.

  1. Gnorr

    Gnorr New Member

    Joined:
    May 1, 2011
    Messages:
    25
    Likes Received:
    0
    d20Pro 3.4.{0,1} gets confused when a machine has multiple active network interfaces, of which only some actually provide external connectivity.

    Example: A machine here has WLAN on 192.168.178.22, LAN on 192.168.178.44, and a VirtualBox VM virtual interface on 192.168.57.33. d20Pro consistently picked the VM interface (which has no external connectivity) for the listening port of the server, ignoring both the LAN and WLAN interfaces. This could only be worked around by explicitly disabling the VM interface in Windows.

    Suggestion: Maybe add a popup menu in the `Advanced' mode (which now allows to just set a password and the port) to also explicitly select the interface (IP address) to use for listening?
     
  2. edwardcd

    edwardcd Administrator
    Staff Member

    Joined:
    Oct 13, 2010
    Messages:
    1,374
    Likes Received:
    9
    If you are looking at the Game Log command "/myip" , this will display:
    Public IP as found when hitting a http address (the originating IP of the request is displayed).
    Private IP d20Pro listens using all networks found, you can view this with "netstat -an" as evident of [::]:port The internal IP shown is the lowest IPv6 address or lowest IPv4 address.

    I've tested using (and it still follows the rules mentioned above):
    - 2 internet connections hard wired (Cox, AT&T), with 1 VPN - 3 Public IPs, 3 local IPs
    - 1 wired internet connection (Cox) with 1 hard wired and 1 wireless - 1 Public IP, 2 local IPs on separate local networks
    - 1 wired internet connection (Cox) with 1 hard wired and 1 wireless - 1 Public IP, 2 local IPs on same local network
    - 1 wired internet connection (Cox) with 1 hard wired and 1 wireless 1 Virtual VMWare Workstation network connectionn - 1 Public IP, 3 local IPs

    The takeaway here is:
    Regardless of the local/Private IP displayed, d20Pro accepts connections on any local network connected to the computer.
    Regardless of the Public IP displayed, d20Pro accepts connections on any internet connection provided router/port forwarding is working and port is not blocked by ISP.
    :D

    Perhaps in the Unlimited version we will display all public and all private IPs to make it easier for those with more complex networks.
     
  3. Gnorr

    Gnorr New Member

    Joined:
    May 1, 2011
    Messages:
    25
    Likes Received:
    0
    That sounds reasonable. But I was not able to get the client to connect until I killed the VirtualBox interface. Will test again over the weekend!
     
  4. edwardcd

    edwardcd Administrator
    Staff Member

    Joined:
    Oct 13, 2010
    Messages:
    1,374
    Likes Received:
    9
    Gnorr,

    When you are able to test and if you find an instance where the VM VirtualBox is taking sole ownership of the port you're trying to use on d20Pro on your non-virtualized OS, you can use a different port for d20Pro and configure the new port in the router and test to see if the port says open while having the d20Pro server/judge open and by looking online via http://www.canyouseeme.org . Alternatively, you could then use your VM VirtualBox to run d20Pro. Either way, you can test this way before your players connect to hopefully save a little bit of time.
     

Share This Page