title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Choose network interface

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • riwi

    • Dec 2016
    • 10

    Choose network interface

    Hi,
    I've just purchased assetUPNP (for linux 64 bit). I run Slackware.

    Is there documentation available about which commandline options are available?
    I would like to choose which network interface the AssetUPNP binds to. Currently it sees that I have 2 interfaces with an IP and Asset chooses the first one (which is down).
    I would like to either choose the IP on which Asset listens or the network interface (eg. eth2). Is that possible?

    Regards, Richard
    Last edited by riwi; December 24, 2016, 04:04 PM.
  • PeterP
    Super Moderator
    • Jul 2011
    • 1471

    #2
    Re: Choose network interface

    Running:
    ./AssetUPnP --help
    ...prints the currently available commandline switches, just four of them right now.
    For running on a specific IP in a multi IP environment, you want --ipaddress <ipv4 goes here>
    Last edited by PeterP; December 27, 2016, 02:02 PM.

    Comment

    • simes_pep
      dBpoweramp Enthusiast

      • Dec 2013
      • 297

      #3
      Re: Choose network interface

      @PeterP just out of interest, what are the other 3?
      I am away, at present, and don't have remote access to my network/Pi to run './AssetUPnP --help'

      Thanks,
      Simon

      Comment

      • PeterP
        Super Moderator
        • Jul 2011
        • 1471

        #4
        Re: Choose network interface

        Code:
        Usage: ./AssetUPnP [ arguments ]
        
        Accepted arguments:
          --help                :: Prints this message.
          --ipaddress <address> :: Specifies a local IP address to bind to.
                                :: If not specified, Asset will bind to all local IP addresses of the host.
          --shutdown            :: Signals an existing Asset instance to shut down.
          --no-config-page      :: Disables the configuration web interface.

        Comment

        • simes_pep
          dBpoweramp Enthusiast

          • Dec 2013
          • 297

          #5
          Re: Choose network interface

          Thank you.

          I was using a 'killall AssetUPnP' to shutdown Asset before undertaking NAS maintenance & the mounts would not be available.

          Simon

          Comment

          • riwi

            • Dec 2016
            • 10

            #6
            Re: Choose network interface

            Originally posted by PeterP
            Running:
            ./AssetUPnP --help
            ...prints the currently available commandline switches, just four of them right now.
            For running on a specific IP in a multi IP environment, you want --ipaddress <ipv4 goes here>
            Thank you very much. That is just what I needed. Great

            Regards Richard

            Comment

            • riwi

              • Dec 2016
              • 10

              #7
              Re: Choose network interface

              I managed to start it using the --ipaddress parameter :
              Code:
              root@riwixeon:/home/richard/asset_upnp/bin* ./AssetUPnP --ipaddress 192.168.1.11 &
              [1] 24028
              root@riwixeon:/home/richard/asset_upnp/bin* Asset UPnP startup...
              Version: R5.1
              Functionality: Premium Registered
              Supported formats: .aif .aiff .aifc .flac .fla .m4a .mp4 .m4b .aac .mp3 .mp2 .m2a .mpga .mpa .mpx .mpg .mp1 .mpeg .mpc .mpp .mp+ .ogg .oga .opus .wav .bwf .w64 .wv .dff .dsf .ape
              Starting Asset web interface at http://192.168.1.11:45537
              Although it says here that it started the web interface on 192.168.1.11, the web interface is not reachable when I start it like this.
              I did not specify the --no-config-page option.
              I do notice the mediaplayers can see the AssetUPn is running OK and serving music fine on the .11

              It would be nice to be able to use the web gui. I am doing something wrong here?

              Comment

              • PeterP
                Super Moderator
                • Jul 2011
                • 1471

                #8
                Re: Choose network interface

                Your --ipaddress usage looks good from here.
                I've been able to recreate this bug using a Slackware virtual machine; I'm looking into it.
                Interestingly there's no such bug on Debian system used to build Asset, or on development Macbook; web config works fine when using --ipaddress; even if multiple interfaces connecting to physically separate networks are in use.

                Comment

                • PeterP
                  Super Moderator
                  • Jul 2011
                  • 1471

                  #9
                  Re: Choose network interface

                  Beta version with attempted workaround for --ipaddress issues:



                  A bug affecting webconfig with --ipaddress in effect has been fixed. I hope this addresses your case.

                  Comment

                  • riwi

                    • Dec 2016
                    • 10

                    #10
                    Re: Choose network interface

                    Originally posted by PeterP
                    Beta version with attempted workaround for --ipaddress issues:



                    A bug affecting webconfig with --ipaddress in effect has been fixed. I hope this addresses your case.
                    I've tried the beta 64 bit and I confirm that it works. Now it starts at the desired ip and the web address is reachable
                    Thank you very much for the very quick resolution

                    Comment

                    Working...

                    ]]>