• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Ethernet Adapter and unique identifier

Scheduled Pinned Locked Moved Solved
General
3
4
1.0k
Loading More Posts
  • 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.
  • S
    SlimJim
    last edited by Jul 27, 2017, 4:49 PM

    Server
    • FOG Version: 1.4.4
    • OS: Ubuntu 16.04
    Client
    • Service Version: MAC os x
    • OS: Sierrra
    Description: Wondering if anyone has run into this issue… So specifically the issue I face is with macbook air’s which have no ethernet port, so the logical step I took was to grab some thunderbolt adapters and move on… Problem is the adapter’s mac address is what fog will use and fog has no way of distinguishing one Macbook from the other if using the same ethernet adapter?

    Thanks in Advance,

    James

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Jul 27, 2017, 5:25 PM

      I have not personally experienced this as of now, but I know others are able to manage around this. This is a similar issue as with the Surface Pros and their doc. People will image the surface pros in a staging dock, so technically all devices will have the same mac address (since the wifi isn’t capable to image across).

      Hopefully someone will come along that has first hand experience with this process. I just wanted to say its been done before and not specific to your Mac.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by Sebastian Roth Jul 27, 2017, 5:21 PM Jul 27, 2017, 11:19 PM

        @SlimJim Same as George I don’t have first hand experience but remember reading about it in the forums.

        On the other hand we are working towards using the system UUID as key to identify clients. Tom already added this to the parameters sent by iPXE. As well he’s told me that this is considered in the PHP code as well. So I am sure it won’t take very long till we can use this. I am working on adjusting the fog-client to use this as well!

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 1
        • S
          Sebastian Roth Moderator
          last edited by Sep 11, 2017, 8:52 PM

          @SlimJim Did you get to test this on a release candidate installation? Should be working there already.

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post

          151

          Online

          12.1k

          Users

          17.3k

          Topics

          155.3k

          Posts
          Copyright © 2012-2024 FOG Project