Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. No eth0, only eth1.

No eth0, only eth1.

Scheduled Pinned Locked Moved Support
4 Posts 3 Posters 144 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G
    G
    ghenry
    wrote on last edited by
    #1

    Hi,

    Trying to register here but getting the following as there is no eth0, only eth1:

    [root@localhost fop2]# ./fop2_server --register
    eth0: error fetching interface information: Device not found
    Can't get info from ifconfig:  at script/fop2_server.pl line 3699
    
    1 Reply Last reply
    0
    • N
      N
      nicolas
      wrote on last edited by
      #2

      The next release includes the " -i " command line option to specify the interface.

      1 Reply Last reply
      0
      • D
        D
        dansford
        wrote on last edited by
        #3

        Hi,

        I registered with the i command:

        /usr/local/fop2/fop2_server --register -1 eth1

        but i am still getting the error when I put in the command:

        /usr/local/fop2/fop2_server --test

        eth0: error fetching interface information: Device not found
        Can't get info from ifconfig: at script/fop2_server.pl line 6631.

        and unable to connect to http://<ip address>/fop2/fop2.html

        attempt 1, attempt 2 and so on. Was working fine on the demo, stopped working after registration for a whitelabel license.

        Using Elastix 2.2, please help.

        1 Reply Last reply
        0
        • N
          N
          nicolas
          wrote on last edited by
          #4

          You must ALWAYS pass the -i eth1 parameter when you invoke fop2_server

          /usr/local/fop2/fop2_server -i eth1 --test

          You must edit the OPTIONS line for the init script and add the -i parameter to, for fop 2.24, edit /etc/sysconfig/fop2 and to the OPTIONS="" line add -i eth1.

          Finally, be sure fop2 starts and keeps running

          service fop2 restart
          (wait 10 seconds)
          pgrep fop2
          (it should return the pid number)

          Best regards,

          1 Reply Last reply
          0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          Powered by NodeBB Contributors
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups