Categories

• Announcements

  Get the latest news on what's happening.
  171
  Topics
  726
  Posts

  M

  @Sebastian-Roth Ok, thank you.
• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  2002
  Topics
  16120
  Posts

  3

  @george1421 - I can’t remember if it picked up the correct interface on install or if I changed it later when preparing to try multicasting, but it has been set to ens3 for at least a few weeks. ps only gives: [username] 18913 0.0 0.0 13136 1092 pts/0 S+ 01:39 0:00 grep --color=auto udp-send The multicast task appears as “queued” for each host in the Active Tasks pane, and the multicast log continues as if all is well: [04-07-20 11:59:25 am] | Task ID: 10 Name: Multi-Cast Task - Multicast t500 image file found, file: /images/T500Linux19-10desktopclean [04-07-20 11:59:25 am] | Task ID: 10 Name: Multi-Cast Task - Multicast t500 2 clients found [04-07-20 11:59:25 am] | Task ID: 10 Name: Multi-Cast Task - Multicast t500 sending on base port 61792 [04-07-20 11:59:25 am] | Command: /usr/local/sbin/udp-sender --interface dev --min-receivers 2 --max-wait 600 --portbase 61792 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/T500Linux19-10desktopclean/d1p1.img; [04-07-20 11:59:25 am] | Task ID: 10 Name: Multi-Cast Task - Multicast t500 has started If I start a multicast from the command line with sudo udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log --ttl 1 --nopointopoint I get root 20233 0.0 0.1 66696 4268 pts/1 S+ 01:48 0:00 sudo udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log --ttl 1 --nopointopoint root 20234 0.0 0.0 8884 896 pts/1 S+ 01:48 0:00 udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log --ttl 1 --nopointopoint [username] 20351 0.0 0.0 13136 1000 pts/0 S+ 01:49 0:00 grep --color=auto udp-send
• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  9725
  Topics
  96085
  Posts

  S

  @c70m83 Just to try and see why exactly those three (PC24, PC08 and PC12) seem problematic you might try to connect those to other ports on the switch where you know that other PCs work. As George said, PXE boot does not depend on Windows or any operating system. No matter what you have installed on disk PXE does work!! So if it used to work then something within your network / DHCP setup changed!
• Developers

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

  General

  Feature Request

  Bug Reports
  2092
  Topics
  19636
  Posts

  S

  @mckay said in Repurpose the restart notification to work for running/delaying Snapins: Is this documented anywhere? Sorry no. Not because we want to keep this secret but because we don’t have enough time to document it all. I will try to give some answers on the options but as I haven’t been the author of that code I might not know all the details either. The parameters are given as JSON string. So action is the name of one parameter and request it’s value. As far as I understand the code this parameter is not used in this case. I just used it in the example because it’s used in the fog-client code like this as well. Testing a bit more I found that you can run it without that parameter: {"period": 60, "options": 2, "aggregatedDelayTime": 0, "message": "This is a test message."} (encoded: eyJwZXJpb2QiOiA2MCwgIm9wdGlvbnMiOiAyLCAiYWdncmVnYXRlZERlbGF5VGltZSI6IDAsICJtZXNzYWdlIjogIlRoaXMgaXMgYSB0ZXN0IG1lc3NhZ2UuIn0=) Now with the options parameter you can switch the button label (see code here). It will show “Hide” when you set options to the value of 2 or 0 but “Cancel” when set to 1. Please don’t ask me why. It’s just the way it was coded and I can’t tell you why. As mentioned before I have that feeling that might not get what you want to achieve using FOGShutdownGUI. I am not even sure if it’s worth investigating any further. Probably better to look forward to working-1.6 instead.