• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Claw22000
    C
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 17
    • Best 2
    • Controversial 0
    • Groups 0

    Claw22000

    @Claw22000

    2
    Reputation
    2
    Profile views
    17
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Claw22000 Unfollow Follow

    Best posts made by Claw22000

    • RE: Imaging works in VM and not on bare metal

      @sebastian-roth Great info guys I ordered an unmanaged switch to replace the managed on to see if that corrects the issue. I don’t use any of its features since Its just My family and I. I just like to nerd out and this was a gift to play with. Haven’t change a thing on it since the day I received it. I will report back as soon as I am able to test. Should be here Tuesday.

      Claw

      posted in FOG Problems
      C
      Claw22000
    • RE: Imaging works in VM and not on bare metal

      @sebastian-roth Sorry about the confusion. The Cisco is managed and the new Netgear is unmanaged. taking the Cisco out of the mix fixed the issue.

      Claw

      posted in FOG Problems
      C
      Claw22000

    Latest posts made by Claw22000

    • RE: Imaging works in VM and not on bare metal

      @sebastian-roth Sorry about the confusion. The Cisco is managed and the new Netgear is unmanaged. taking the Cisco out of the mix fixed the issue.

      Claw

      posted in FOG Problems
      C
      Claw22000
    • RE: Imaging works in VM and not on bare metal

      @sebastian-roth Great news the unmanaged switch showed up and its solved the issue I was having. I have had that thing for going on a decade and never had an issue with it. Well I learned a big lesson if you don’t need a managed switch and your not using VLANs your better off with an unmanaged switch.

      Crazy thing is never had any other issues with it.

      Thank you all for helping me trouble shoot this. If any one comes across this a cheap Netgear unmanaged switch from amazon will let you test to see if this was also your issue!

      Claw

      posted in FOG Problems
      C
      Claw22000
    • RE: Imaging works in VM and not on bare metal

      @sebastian-roth Great info guys I ordered an unmanaged switch to replace the managed on to see if that corrects the issue. I don’t use any of its features since Its just My family and I. I just like to nerd out and this was a gift to play with. Haven’t change a thing on it since the day I received it. I will report back as soon as I am able to test. Should be here Tuesday.

      Claw

      posted in FOG Problems
      C
      Claw22000
    • RE: Imaging works in VM and not on bare metal

      I appreciate the help. When you say firewall are you talking about my PFsense Box or are we talking about something that resides in the FogServer?

      Claw

      posted in FOG Problems
      C
      Claw22000
    • RE: Imaging works in VM and not on bare metal

      @sebastian-roth Ok some progress today. I tried the following commands and it failed

      mkdir /images
      mkdir /images/dev
      mount -o nolock,proto=tcp,rsize=32768,intr,noatime x.x.x.x:/images /images
      mount -o nolock,proto=tcp,rsize=32768,intr,noatime x.x.x.x:/images/dev/ /images/dev

      However the following command worked

      mount -o nolock,proto=udp,rsize=32768,intr,noatime x.x.x.x:/images /images
      mount -o nolock,proto=udp,rsize=32768,intr,noatime x.x.x.x:/images/dev/ /images/dev

      I am able to list the files in the folder and it works correctly.

      So now the issue is why TCP doesn’t work on the bare metal and does work on the VM.

      Suggestions?

      Claw

      posted in FOG Problems
      C
      Claw22000
    • RE: Imaging works in VM and not on bare metal

      @sebastian-roth Yes you can access the HTML side and ping the server. I’m stumped. I would be glad to let you see it your self if you have time. I’m a mid to low level linux user so I might be missing something obvious.

      Claw

      posted in FOG Problems
      C
      Claw22000
    • RE: Imaging works in VM and not on bare metal

      @sebastian-roth
      My setup is is this

      Hypervisor: VMware ESXi, 6.5.0, 14320405
      Model: PowerEdge R815
      Processor Type: AMD Opteron™ Processor 6276
      Logical Processors: 64
      Ram: 186 Gigs

      2 NICS are use and 1 DRAC
      1 NIC is directly to the Modem and only accessed by PFSense
      the other NIC is shared across all the the VMs PFSense feeding the internet.
      The DRAC and internal Network run to a SG 200-08 8-Port Gigabit Smart Switch (Spanning Tree is disabled)
      This runs to the other side of the lab to a Netgear JGS516 16 Port unmanaged switch

      All computers in the house are then wired to this switch.

      VM for the FOG server is
      4 CPU’s across 2 sockets with at least 1GHZ reservation
      8GB Ram with at least 4Gig Reservation
      HD is Thick provisioned with 300gigs. I will increase this once I document how this works and it will get a dedicated drive for this
      NIC Adapter Type is VMXNET 3

      Install steps of current server
      sudo -i
      wget https://github.com/FOGProject/fogproject/archive/1.5.9.tar.gz
      tar -xzvf 1.5.9.tar.gz
      rm 1.5.9.tar.gz
      cd fogproject-1.5.9/bin
      ./installfog.sh
      click button in browser
      press enter in termanal
      log in
      change default password
      create new user for self
      chmod -R 777 /images
      chown fogproject:nogroup /images

      Info after all this is done.
      sudo iptables -L
      Chain INPUT (policy ACCEPT)
      target prot opt source destination

      Chain FORWARD (policy ACCEPT)
      target prot opt source destination

      Chain OUTPUT (policy ACCEPT)
      target prot opt source destination

      /etc/hosts.deny
      # /etc/hosts.deny: list of hosts that are _not_ allowed to access the system.
      #                  See the manual pages hosts_access(5) and hosts_options(5).
      #
      # Example:    ALL: some.host.name, .some.domain
      #             ALL EXCEPT in.fingerd: other.host.name, .other.domain
      #
      # If you're going to protect the portmapper use the name "rpcbind" for the
      # daemon name. See rpcbind(8) and rpc.mountd(8) for further information.
      #
      # The PARANOID wildcard matches any host whose name does not match its
      # address.
      #
      # You may wish to enable this to ensure any programs that don't
      # validate looked up hostnames still leave understandable logs. In past
      # versions of Debian this has been the default.
      # ALL: PARANOID
      
      /etc/exports
      /images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
      /images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
      
      ls -al /
      drwxr-xr-x  23 root       root          4096 Mar 20 22:50 .
      drwxr-xr-x  23 root       root          4096 Mar 20 22:50 ..
      lrwxrwxrwx   1 root       root             7 Jul 31  2020 bin -> usr/bin
      drwxr-xr-x   3 root       root          4096 Mar 20 18:57 boot
      drwxr-xr-x   2 root       root          4096 Mar 20 17:15 cdrom
      drwxr-xr-x  17 root       root          4000 Mar 20 18:51 dev
      drwxr-xr-x 102 root       root          4096 Mar 21 15:55 etc
      drwxr-xr-x   4 root       root          4096 Mar 20 22:41 home
      drwxrwxrwx   5 fogproject nogroup       4096 Mar 20 23:15 images
      lrwxrwxrwx   1 root       root             7 Jul 31  2020 lib -> usr/lib
      lrwxrwxrwx   1 root       root             9 Jul 31  2020 lib32 -> usr/lib32
      lrwxrwxrwx   1 root       root             9 Jul 31  2020 lib64 -> usr/lib64
      lrwxrwxrwx   1 root       root            10 Jul 31  2020 libx32 -> usr/libx32
      drwx------   2 root       root         16384 Mar 20 17:14 lost+found
      drwxr-xr-x   2 root       root          4096 Jul 31  2020 media
      drwxr-xr-x   2 root       root          4096 Jul 31  2020 mnt
      drwxr-xr-x   3 root       root          4096 Mar 20 22:41 opt
      dr-xr-xr-x 291 root       root             0 Mar 20 18:51 proc
      drwx------   5 root       root          4096 Mar 21 07:27 root
      drwxr-xr-x  36 root       root          1140 Mar 21 15:51 run
      lrwxrwxrwx   1 root       root             8 Jul 31  2020 sbin -> usr/sbin
      drwxr-xr-x   6 root       root          4096 Mar 20 18:52 snap
      drwxr-xr-x   4 root       root          4096 Mar 20 22:41 srv
      -rw-------   1 root       root    4294967296 Mar 20 17:18 swap.img
      dr-xr-xr-x  13 root       root             0 Mar 20 18:51 sys
      drwxr-xr-x   5 fogproject root          4096 Mar 20 22:50 tftpboot
      drwxr-xr-x   2 root       root          4096 Mar 20 22:50 tftpboot.prev
      drwxrwxrwt  15 root       root          4096 Mar 21 15:39 tmp
      drwxr-xr-x  14 root       root          4096 Jul 31  2020 usr
      drwxr-xr-x  14 root       root          4096 Mar 20 22:34 var
      
      ls -al /images
      -rwxrwxrwx  1 fogproject root       0 Mar 21 07:20 .mntcheck
      drwxrwxrwx  3 fogproject root    4096 Mar 20 23:15 dev
      drwxrwxrwx  2 fogproject root    4096 Mar 20 22:50 postdownloadscripts
      drwxrwxrwx  2 root       root    4096 Mar 20 23:15 win10basic
      
      ls -al /images/dev
      drwxrwxrwx 3 fogproject root    4096 Mar 20 23:15 .
      drwxrwxrwx 5 fogproject nogroup 4096 Mar 20 23:15 ..
      -rwxrwxrwx 1 fogproject root       0 Mar 20 22:50 .mntcheck
      drwxrwxrwx 2 fogproject root    4096 Mar 20 22:50 postinitscripts
      

      Hope this helps I really appreciate your help. Sorry it takes so long to get back some times I work 50 - 60 hours a week so get wrapped up alot

      Claw

      posted in FOG Problems
      C
      Claw22000
    • RE: Imaging works in VM and not on bare metal

      @sebastian-roth
      Tried VM to VM and was able to use the mount command to connect just can’t connect from bare metal to the server.

      Also tried reinstalling and using Ubuntu tested exactly the same can connect VM to VM and cannot Bare metal to VM

      Claw

      posted in FOG Problems
      C
      Claw22000
    • RE: Imaging works in VM and not on bare metal

      @sebastian-roth
      What I did to test this further was to install and recreate the fog server on a bare metal machine. Then try it the other way round. Neither the bare metal machine or the VM can image on this. Only way it works is VM to VM. Tonight after work I will turn on the VM and do the test again VM to VM.

      I appreciate all the suggestions as I have no ideas as to what could be the problem.

      Claw

      posted in FOG Problems
      C
      Claw22000
    • RE: Deploy install ISO over PXE with FogProject

      @lmaoroot said in Deploy install ISO over PXE with FogProject:

      @george1421 No problem. I get the overall concept, I just dont know where to start on the WinPE part, I’ll have another look though. I got ubuntu 18.04 server installing properly, but not oddly enough… its like its server when i install the desktop version. It’s so weird, but I cant find the netboot.tar.gz for ubuntu 20.04. Does it no longer exist?

      They use a different method of the net install now. Can’t remember how I found it but there are instructions.

      As for windows the ipxe sight has great tutorials.

      posted in FOG Problems
      C
      Claw22000