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

    Acer travelmate b usb to ethernet

    Scheduled Pinned Locked Moved
    FOG Problems
    usb-to-ethernet acer dhcp
    3
    14
    2.1k
    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.
    • george1421G
      george1421 Moderator @fox134
      last edited by

      @fox134 well if its shows the mac address of the usb nic, that means that iPXE should have a driver for it. At the screen where it says press “s” for the iPXE console. Go ahead and do that before the timeout.

      Then wait 30 seconds and key in the following to see if it picks up an IP address dhcp net0 or dhcp net1 if net0 doesn’t get an address because the usb network adapter is not the first one. If you do pick up an IP address after 30 seconds then I would surely explore what is going on with spanning tree.

      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!

      F 1 Reply Last reply Reply Quote 0
      • F
        fox134 @george1421
        last edited by

        @george1421 0_1520962095288_Capture.JPG

        this is what im getting

        george1421G 1 Reply Last reply Reply Quote 0
        • george1421G
          george1421 Moderator @fox134
          last edited by

          @fox134 Right at the point of the IPXE> _ prompt key in dhcp net0 or dhcp net1 after 30 seconds to see if it picks up an IP address. (I see you did a dncp net0, btw).

          Is that mac address listed the same mac address as on the usb adapter?

          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!

          F 1 Reply Last reply Reply Quote 0
          • F
            fox134 @george1421
            last edited by

            @george1421 I did the dhcp net0 with the same message. Yes, the mac matches the one listed. It’s strange because I’m so close but theres something that I’m missing.

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by

              @fox134 What do you see running ifstat net0 in th ipxe shell?

              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

              F 1 Reply Last reply Reply Quote 0
              • F
                fox134 @Sebastian Roth
                last edited by

                @sebastian-roth 0_1521047986930_Capture1.JPG

                george1421G 1 Reply Last reply Reply Quote 0
                • george1421G
                  george1421 Moderator @fox134
                  last edited by

                  @fox134 So if you are at the screen where you entered ifstat, it would be interesting to know what would happen if you keyed in the following commands, of course localized to your network.

                    set net0/ip 192.168.0.100
                    set net0/netmask 255.255.255.0
                    set net0/gateway 192.168.0.1
                  

                  And then see if you can ping something on your local network

                  ping 192.168.0.51
                  

                  The issue is here, that you had network connectivity to get this far. Why not now. It should be working, ifstat shows the link is up (has link connection) but nothing coming in from the switch.

                  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

                    @fox134 FOG uses undionly.kpxe by default as it does work in most cases. Please try other iPXE binary like ipxe.pxe or realtek.kpxe. In fact try all *.pxe you find in /tftpboot on your FOG server.

                    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

                    F 2 Replies Last reply Reply Quote 0
                    • F
                      fox134 @Sebastian Roth
                      last edited by

                      @sebastian-roth Ok. Is there a certain command to explore these options besides /tftboot and changing the binary?

                      1 Reply Last reply Reply Quote 0
                      • F
                        fox134 @Sebastian Roth
                        last edited by

                        @sebastian-roth I can see the permissions folder for tftpboot but how can I change it to use ipxe.exe?

                        george1421G 1 Reply Last reply Reply Quote 0
                        • george1421G
                          george1421 Moderator @fox134
                          last edited by

                          @fox134 Well lets hope you don’t have an ipxe.exe in there…

                          The client gets its booting information from (the) dhcp responsible for assigning an ip address to the target computer. So if you want the target computer to use a different boot file then you might update dhcp options 67.

                          Now with that said, from your OP you say that FOG is giving out the IP addresses on a dedicated imaging network. So if you want to change the boot file, you will need to edit the dhcp config file on your FOG server.

                          To see what you config file looks like, you can review this example: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Example_1

                          You will see for arch 7 and 9 it calls out ipxe.efi. You can replace that with maybe snponly.efi or any of the other efi files. Then you must restart your dns server. On ubuntu you would issue the command sudo systemctl restart isc-dhcp-server to restart the service.

                          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 1
                          • 1 / 1
                          • First post
                            Last post

                          142

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project