Categories

  • 12k Topics
    114k Posts
    george1421G

    @AlexisPHC Ok the pictures tells us a good story. Your dhcp server is working perfectly. Well its not working but its not your dhcp server’s fault at the moment.

    from the 10.1.6.x subnet can you ping the FOG server?
    Is there some some kind of screening router between your 10.1.6.x network and your 10.1.22.x networks?

    On a computer on the 10.1.6.x subnet, take a windows computer, disable the windows firewall. Then install the tftp client on the windows computer. From a command prompt key in tftp get 10.1.22.1 snponly.efi and see if you can pull that tftp image.

    10.1.22.1 is suspicious since typically the .1 or .254 is the default router for a subnet. It doesn’t need to be, but typically it is. Is the .1 address correct for the fog server?

    I feel this is a routing issue between the two subnets.

  • Get the latest news on what's happening.
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    A

    @george1421 I see now and you’re right as my clients are all legacy boot/BIOS boot non UEFI and would not benefit from the client-arch examination.

    I’ve already declarations set for each host in my dhcpd.conf file in terms if MAC to IP and so adding another field of filename “some boot loader file” won’t be impossible.

    Thanks you for this exercise as I’ve learned some very important things here.

  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    A

    @Tom-Elliott ah, that would work! Sorry, the documentation is such a mish-mash that it’s hard to find answers for some of this stuff!

162

Online

12.3k

Users

17.4k

Topics

155.8k

Posts