@pep said in Using a separate NIC for multicast:
web = http: //192.168.1.100/fog/ ftp = 192.168.1.100 storage = 192.168.1.100: / images / dev / storageip = 192.168.1.100
Thanks! That works. I can leave my storage settings as default and Multticast will use eno2, then for anything not multicast I can set the correct parameters for eno3.
Just a note that for deployment the storage variable needs to be ip.address:/images/ (without the dev/)
@Sebastian-Roth OK thanks for the reply. It’s no biggie but I’ve got all these NICs and nothing to use them for 
As an idea, could I create another storage group for the images I might want to multicast, where all the settings except the interface and IP address are the same as the default group? If I set that to use eno3, and multicast to use eno3, that might achieve what I want?
I’ve a FOG server on Ubuntu 20.04, latest version of FOG. My server has 3 NICs all connected to the same subnet. I want to use eno2 for imaging and eno3 for Multicast, but I can’t get the multicast bit to work.
I’ve configured my storage node to use eno2 and set the IP address to the IP of eno2 and normal imaging works.
I then went fo FOG Settings->Multicast and set the interface to eno3. But when I start a multicast task the hosts all get stuck at the Partclone screen. I can see from the server logs that FOG is starting the multicast task using eno2.
If I change the config to use eno2 for multicast then my multicast tasks work, but I was hoping to utilise the extra bandwidth of the 3rd ethernet port I feel sure I’ve missed something obvious… but what?
@george1421 Thanks for the help … ohh Apple… on booting to the debug kernel I’m asked to ‘press Enter to continue’. However, it appears that as well no driver for the nvme, there’s also no driver for the keyboard. So, locating a USB keyboard I was able to determine the following:
[Wed Apr 03 root@fogclient ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 1.9G 0 disk
`-sda1 8:1 1 121M 0 part
[Wed Apr 03 root@fogclient ~]# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3ec4] (rev 07)
00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07)
00:01.1 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x8) [8086:1905] (rev 07)
00:01.2 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x4) [8086:1909] (rev 07)
00:12.0 Signal processing controller [1180]: Intel Corporation Device [8086:a379] (rev 10)
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:a36d] (rev 10)
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:a36f] (rev 10)
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:a360] (rev 10)
00:1b.0 PCI bridge [0604]: Intel Corporation Device [8086:a340] (rev f0)
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:a338] (rev f0)
00:1e.0 Communication controller [0780]: Intel Corporation Device [8086:a328] (rev 10)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a313] (rev 10)
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:a324] (rev 10)
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460] [1002:67ef] (rev e3)
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:aae0]
02:00.0 Mass storage controller [0180]: Apple Inc. Device [106b:2005] (rev 01)
02:00.1 Non-VGA unclassified device [0000]: Apple Inc. Device [106b:1801] (rev 01)
02:00.2 Non-VGA unclassified device [0000]: Apple Inc. Device [106b:1802] (rev 01)
02:00.3 Multimedia audio controller [0401]: Apple Inc. Device [106b:1803] (rev 01)
03:00.0 Network controller [0280]: Broadcom Limited Device [14e4:4464] (rev 03)
04:00.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] (rev 06)
05:00.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
05:01.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
05:02.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
05:04.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
06:00.0 System peripheral [0880]: Intel Corporation Device [8086:15eb] (rev 06)
07:00.0 USB controller [0c03]: Intel Corporation Device [8086:15ec] (rev 06)
7a:00.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] (rev 06)
7b:00.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
7b:01.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
7b:02.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
7b:04.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
7c:00.0 System peripheral [0880]: Intel Corporation Device [8086:15eb] (rev 06)
7d:00.0 USB controller [0c03]: Intel Corporation Device [8086:15ec] (rev 06)
@Tom-Elliott That’s just command-line system_profiler, which is used by the GUI version and only gives me the exact same info I posted in the images earlier. No hardware IDs at all.
@george1421 Thanks, but no chance. I don’t have a license to install Windows, Linux won’t boot, and MacOS system profiler no longer displays hardware IDs.
It’s really like Apple don’t want people to mess with their hardware 
@Sebastian-Roth I think this is the answer. No drivers for Apple’s nvme controller in the kernel yet 
https://askubuntu.com/questions/1052373/install-ubuntu-bionic-18-04-on-macbook-pro-2018
@Tom-Elliott unfortunately this is in a production environment and we can’t currently afford the down time, but I appreciate your efforts and thanks for the reply - at least it has given me confidence that I’m not doing it “wrong”.
As it happens I’m currently automating the entire FOG process by writing entries directly into the database and that is working fine for now, but I was looking at moving to the API as I’m sure it will be better for forwards compatibility - so when time allows I’l update my test server for 1.6 and work with that until we can update the production server.
Thanks for the advice.
@Sebastian-Roth Hmmm. Good call. Ubuntu 18.10 won’t even boot let alone recognise a disk. I get the initial GRUB menu but then very little after that. Black screen now for ~ 5 minutes.