Categories

• Announcements

  Get the latest news on what's happening.
  168
  Topics
  706
  Posts

  T

  @Tom-Elliott said in Ubuntu is FOG's enemy: apt-get -y remove unattended-upgrades This saved my bacon, thank you very much, first command failed but second one worked, i have also run the unattended-upgrades command, once again thank you.
• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  1970
  Topics
  15809
  Posts

  T

  I did manage to get the FOG and the CA certificate installed and functional. It took a little rewriting of the functions.sh. This made HTTPS work properly, too. However (and I figured this would happen), iPXE does not work. When it attempts to use the HTTPS site, it throws an error (http://ipxe.org/err/3e1161). Says DNS isn’t happy. That does not appear to be accurate. When I hop in the iPXE shell, and do a ‘show dns’ it returns the correct DNS server. And when I ping, by name, the FOG server, it succeeds. So, I’m not sure why iPXE is complaining about that. I did figure out that if I disable the HTTPS rewrite on Apache and change the iPXE chain to use the normal HTTP site, iPXE does begin to work. This, of course, allows browsing to the normal HTTP FOG site - not super great. Deploying an image works, too. Don’t know if any of this helps out.
• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  9456
  Topics
  93368
  Posts

  M

  Hey @Daniel-Miller and @george1421 thanks again for your effort in helping me figure this out. I think the complexity (for me) for what I was about to do scared me into thinking of a roundabout approach to solving this issue. I think I found a better solution than what I was originally trying to do (and WAY simpler). I will post here in case this will be of use for anyone in the future. Rather than appending a date to the hostname so I can change the computer name I decided to start out with the date appended to the hostname so that renaming the computer would be exactly how I want it to be then for my other requirements (adding the user to be admin of the computer) I simply removed the date from the hostname to come up with the username. Basically, if my username is bobsmith and today’s date is 2019-12-06, I will name the host: bobsmith191206 then in my Powershell script I just need to set $userName = $env:computername -replace '[0-9]' then the hostname remains bobsmith191206 and now I have a variable $userName that now equals BOBSMITH Anyhow, that is one of those… so easy it is dumb solutions. Not sure why I didn’t think of it earlier. Thanks again you guys for helping me to think outside of the box I stuck myself in.
• Developers

  Report bugs, request features, or get the latest progress.

  General

  Feature Request

  Bug Reports
  2048
  Topics
  19286
  Posts

  

  First let me preface this with I don’t feel wifi is the proper technology to use for imaging. I do acknowledge there are certain circumstances where it is the only option. For that reason I worked out a path to image over wifi. To be able to successfully do this the FOG tech will need to be able to boot the target device using FOS loaded onto a usb flash drive. Since we are dealing with WIFI leaving iPXE out of the solution was the best route. To that end if you use the usb booting methodology you the FOG tech will give up certain features that are supplied by iPXE. I’m mainly documenting this process in case has to duplicate the process some time in the future. To successfully build the wifi option you will need to have a buildroot and linux kernel environment. For buildroot I used 2019.02.4 and for the linux kernel linux-4.19.65 For the linux kernel here is the patch from the FOS 1.5.7 base image kernel_4.19.65_wifi.patch-1.5.7.txt For buildroot here is the patch from the FOS 1.5.7 base image BR-wireless.patch-1.5.7.txt In the build root environment these are the applications I added to the build Target packages ---> Networking applications ---> [*] iw [*] wireless-regdb [*] wireless tools [*] Install shared library [ ] wireshark [*] wpa_supplicant [*] Enable nl80211 support [ ] Enable AP mode [*] Enable autoscan [*] Enable EAP [*] Enable HS20 [*] Enable syslog support [*] Enable WPS [*] Install wpa_cli binary [*] Install wpa_client shared library [*] Install wpa_passphrase binary In addition I had to create and patch 2 startup files that go into …/board/FOG/FOS/rootfs_overlay/etc/init.d directory. S35wifiset.txt and I added a bit of code to S40network S40network.txt That code would be in this section of S40network Here are two wifi configuration files that go into the …/board/FOG/FOS/rootfs_overlay/etc directory wpa_default.conf.txt wpa_supplicant.conf.txt Kernel parameters added: ssid == SSID to connect to ssidpw == SSID Password of the wifi SSID ssidkeymgmt == Key Managment method will set the key_mgmt= value in the wpa_supplicant.conf file. echo "Starting $iface interface and waiting for the link to come up" echo -e "auto $iface\niface $iface inet dhcp\n\n" >> /etc/network/interfaces /sbin/ip link set $iface up ## New code start if [ ! -z "$ssid" ] then read isWifi <<< $(/sbin/iwconfig $iface 2> >(awk '{print toupper($2)}')) if [ "$isWifi" != "NO" ]; then echo "Assigning WiFi drivers to $iface" /usr/sbin/wpa_supplicant -B -i$iface -c/etc/wpa_supplicant.conf -Dnl80211,wext -s -I/etc/wpa_default.conf sleep 10 fi fi ## New code end # Wait till the interface is fully up and ready (spanning tree) timeout=0 linkstate=0 The FOS Linux USB grub configuration file would look like this to support wifi. set myfogip=192.168.1.100 set myimage=/boot/bzImageWiFi set myinits=/boot/initwifi.xz set myloglevel=4 set timeout=-1 set ssid=mudpuppy set ssidpw=idontknowit insmod all_video menuentry "1. FOG Image Deploy/Capture" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 ssid=$ssid ssidpw=$ssidpw echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "2. Perform Full Host Registration and Inventory" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=manreg ssid=$ssid ssidpw=$ssidpw echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "3. Quick Registration and Inventory" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=autoreg ssid=$ssid ssidpw=$ssidpw echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "4. Client System Information (Compatibility)" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=sysinfo ssid=$ssid ssidpw=$ssidpw echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "5. Quick Deploy an Image" { echo loading the kernel linux $myimage root=/dev/ram0 rw ramdisk_size=275000 ip=dhcp web=$myfogip/fog/ consoleblank=0 loglevel=4 type=down img=Win7SP1x64 ftp=$myfogip imgType=n imgPartitionType=all osid=5 storage=$myfogip:/images/ capone=1 boottype=usb ssid=$ssid ssidpw=$ssidpw echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "6. FOG Debug Kernel" { echo loading the kernel linux $myimage loglevel=7 init=/sbin/init root=/dev/ram0 rw ramdisk_size=275000 keymap= boottype=usb consoleblank=0 rootfstype=ext4 isdebug=yes ssid=$ssid ssidpw=$ssidpw echo loading the virtual hard drive initrd $myinits echo booting kernel... }