• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. marted
    3. Posts
    M
    • Profile
    • Following 0
    • Followers 0
    • Topics 11
    • Posts 99
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Hosts are looking for tftp server.

      @george1421 said in Hosts are looking for tftp server.:

      VM (not the fog server) with dnsmasq running with an interface on each subnet would also work.

      Wow @george1421 very useful information. Now how to make an interface on each subnet in one dnsmasq? add info in the same config file or crate 4 different config files. Could you help me with that?
      Why we just not use the integrated tftp server with dnsmasq with the option enable-tftp and give the dnsmasq informaiton that we accept requests from 4 subnet?

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @Sebastian-Roth said in Hosts are looking for tftp server.:

      Have you looked at why DHCP queries come in duplicated?

      I have no idea. I looked in the config file. Nothing different than your example in wiki. I’ll make today a test with tcpdump on 69 to see the traffic info on the server. Also I’ll check this options in dnsmasq like:

      --tftp-no-fail
      Do not abort startup if specified tftp root directories are inaccessible.
      --tftp-max=<connections>
      Set the maximum number of concurrent TFTP connections allowed. This defaults to 50. When serving a large number of TFTP connections, per-process file descriptor limits may be encountered. Dnsmasq needs one file descriptor for each concurrent TFTP connection and one file descriptor per unique file (plus a few others). So serving the same file simultaneously to n clients will use require about n + 10 file descriptors, serving different files simultaneously to n clients will require about (2*n) + 10 descriptors. If --tftp-port-range is given, that can affect the number of concurrent connections.
      --tftp-no-blocksize
      Stop the TFTP server from negotiating the "blocksize" option with a client. Some buggy clients request this option but then behave badly when it is granted.
      --tftp-port-range=<start>,<end>
      A TFTP server listens on a well-known port (69) for connection initiation, but it also uses a dynamically-allocated port for each connection. Normally these are allocated by the OS, but this option specifies a range of ports for use by TFTP transfers. This can be useful when TFTP has to traverse a firewall. The start of the range cannot be lower than 1025 unless dnsmasq is running as root. The number of concurrent TFTP connections is limited by the size of the port range.
      

      I’ll try also to capture a log with a different model clients to see if there is a différents.

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @Sebastian-Roth said in Hosts are looking for tftp server.:

      grep “dnsmasq” /var/log/

      I have just seen the tftpd log and something is wrong. See the time I test today two times

      root@foglabunix:/var/log# systemctl status tftpd-hpa
      ● tftpd-hpa.service - LSB: HPA's tftp server
         Loaded: loaded (/etc/init.d/tftpd-hpa; generated)
         Active: active (running) since Mon 2020-03-09 12:13:55 EDT; 2h 2min ago
           Docs: man:systemd-sysv-generator(8)
        Process: 1473 ExecStart=/etc/init.d/tftpd-hpa start (code=exited, status=0/SUCCESS)
          Tasks: 1 (limit: 4915)
         CGroup: /system.slice/tftpd-hpa.service
                 └─1509 /usr/sbin/in.tftpd --listen --user root --address :69 -s /tftpboot
      
      Mar 09 12:55:51 foglabunix in.tftpd[3843]: tftp: client does not accept options
      Mar 09 12:55:51 foglabunix in.tftpd[3845]: tftp: client does not accept options
      Mar 09 12:55:51 foglabunix in.tftpd[3849]: tftp: client does not accept options
      Mar 09 12:55:51 foglabunix in.tftpd[3851]: tftp: client does not accept options
      Mar 09 12:55:51 foglabunix in.tftpd[3853]: tftp: client does not accept options
      Mar 09 13:24:03 foglabunix in.tftpd[6395]: tftp: client does not accept options
      Mar 09 13:24:03 foglabunix in.tftpd[6406]: tftp: client does not accept options
      Mar 09 13:24:03 foglabunix in.tftpd[6419]: tftp: client does not accept options
      Mar 09 13:24:03 foglabunix in.tftpd[6421]: tftp: client does not accept options
      Mar 09 13:24:03 foglabunix in.tftpd[6432]: tftp: client does not accept options
      

      and all log from today

      Mar  9 11:34:40 foglabunix in.tftpd[10796]: tftp: client does not accept options
      Mar  9 11:35:35 foglabunix in.tftpd[10979]: tftp: client does not accept options
      Mar  9 12:24:07 foglabunix in.tftpd[14779]: tftp: client does not accept options
      Mar  9 12:25:07 foglabunix in.tftpd[14950]: tftp: client does not accept options
      Mar  9 12:33:42 foglabunix in.tftpd[15559]: tftp: client does not accept options
      Mar  9 12:13:55 foglabunix tftpd-hpa[1473]:  * Starting HPA's tftpd in.tftpd
      Mar  9 12:13:55 foglabunix tftpd-hpa[1473]:    ...done.
      Mar  9 12:39:34 foglabunix in.tftpd[2389]: tftp: client does not accept options
      Mar  9 12:39:36 foglabunix in.tftpd[2391]: tftp: client does not accept options
      Mar  9 12:39:36 foglabunix in.tftpd[2393]: tftp: client does not accept options
      Mar  9 12:39:36 foglabunix in.tftpd[2395]: tftp: client does not accept options
      Mar  9 12:39:44 foglabunix in.tftpd[2411]: tftp: client does not accept options
      Mar  9 12:39:44 foglabunix in.tftpd[2413]: tftp: client does not accept options
      Mar  9 12:39:44 foglabunix in.tftpd[2415]: tftp: client does not accept options
      Mar  9 12:39:44 foglabunix in.tftpd[2417]: tftp: client does not accept options
      Mar  9 12:39:44 foglabunix in.tftpd[2419]: tftp: client does not accept options
      Mar  9 12:39:45 foglabunix in.tftpd[2421]: tftp: client does not accept options
      Mar  9 12:40:05 foglabunix in.tftpd[2455]: tftp: client does not accept options
      Mar  9 12:40:05 foglabunix in.tftpd[2457]: tftp: client does not accept options
      Mar  9 12:40:05 foglabunix in.tftpd[2458]: tftp: client does not accept options
      Mar  9 12:40:05 foglabunix in.tftpd[2461]: tftp: client does not accept options
      Mar  9 12:40:05 foglabunix in.tftpd[2462]: tftp: client does not accept options
      Mar  9 12:55:41 foglabunix in.tftpd[3796]: tftp: client does not accept options
      Mar  9 12:55:41 foglabunix in.tftpd[3798]: tftp: client does not accept options
      Mar  9 12:55:41 foglabunix in.tftpd[3800]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3815]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3817]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3819]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3821]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3823]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3825]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3826]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3827]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3831]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3833]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3834]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3837]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3838]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3840]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3843]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3845]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3847]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3849]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3851]: tftp: client does not accept options
      Mar  9 12:55:51 foglabunix in.tftpd[3853]: tftp: client does not accept options
      Mar  9 12:56:12 foglabunix in.tftpd[3890]: tftp: client does not accept options
      Mar  9 13:02:59 foglabunix in.tftpd[4521]: tftp: client does not accept options
      Mar  9 13:04:02 foglabunix in.tftpd[4599]: tftp: client does not accept options
      Mar  9 13:23:53 foglabunix in.tftpd[6370]: tftp: client does not accept options
      Mar  9 13:23:53 foglabunix in.tftpd[6372]: tftp: client does not accept options
      Mar  9 13:23:53 foglabunix in.tftpd[6374]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6394]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6395]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6398]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6401]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6400]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6402]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6406]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6408]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6409]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6411]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6413]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6416]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6418]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6419]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6421]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6424]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6426]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6428]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6430]: tftp: client does not accept options
      Mar  9 13:24:03 foglabunix in.tftpd[6432]: tftp: client does not accept options
      Mar  9 13:24:24 foglabunix in.tftpd[6479]: tftp: client does not accept options
      Mar  9 13:24:33 foglabunix in.tftpd[6490]: tftp: client does not accept options
      Mar  9 13:25:35 foglabunix in.tftpd[6553]: tftp: client does not accept options
      Mar  9 13:31:52 foglabunix in.tftpd[7174]: tftp: client does not accept options
      Mar  9 13:32:53 foglabunix in.tftpd[7241]: tftp: client does not accept options
      Mar  9 13:52:48 foglabunix in.tftpd[9009]: tftp: client does not accept options
      
      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @Sebastian-Roth I got the log file dnsmasq.log
      This are the MAC addresses which asked for tftp server
      00:4e:01:c5:f4:67
      00:4e:01:c5:fa:98
      00:4e:01:c5:e7:c4
      00:4e:01:c5:a5:9a

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 @Sebastian-Roth you’re right. This is a issue of the dnsmasq (DHCP proxy server) not FOG. If you want change the place of the topic.
      The Dnsmasq is not capable to handle many requests at a time. All tests I made Yesterday I found that up to 10-12 computers at a time there is no issues. Like I said earlier in my posts, the problem is ONLY with this new model we have, because they boot simultaneously and I guess almost all at the same time ‘‘ask’’ the proxy dhcp for information. Like you said if the proxy is not capable to handle the request for a host, this host will pass to the next dhcp in the network, and because we don’t have 3th one dhcp in the network, it will return to the main dhcp (DHCP of the University) . We see this request in the wireshark file like a request on the exit IP 192.168.148.1 and answer from it.
      Now the question is how to fix this situation. In this close private network we have 10 rooms each room with 25 computers, all of them (250) installed on 4 sub net 192.168.148.0, 192.168.149.0 192.168.150.0 192.168.151.0. The server FOG is a virtual server fixed on 192.168.149.43 and configured on our private switch in the lab like an IP Helper (DHCP proxy). Up to now almost 5 months, no issues with FOG for booting. Like I said this is the first time we have a problem like this, simply because in other rooms the old models, when I send a task for 25 hosts they don’t wake up on LAN exactly in the same time, and because of that they don’t '‘ask’ dhcp proxy for information in the same time. Now the new model hosts I see it do that.
      My questions (I am just asking I don’t know the question is correct or no 🙂 )
      Is it possible to setup the dnsmasq to handle requests one at a time and like this to be able to proceed all requests?
      Can we have second port open to handle part of the requests?
      or second dnsmasq on the same server?
      or second server only with dnsmasq installed which will transfer only the information which leads to the real FOG server?
      or getting(install) better network card?
      If you have some other suggestion I am open to listen.
      I know it is always possible just to boot the hosts one at a time with F12 and it will work a 100% or make small groups of 5-10 hosts for this model, but I like very much the way FOG can handle many hosts at a time and.
      Another thing I turnoff all hosts in the evening and when I wake up on LAN room by room in the morning just in this room I have to go and reboot again manually or enter tftp server info.
      I hope to find some solution!
      Thanks again for all your help

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 now one more thing - when I boot manually host by host with F12 every host boot correctly with no problems. The problem come only when I try to boot them all with a task and wake up on LAN. I have impression that there is a limit of hosts to connect to tftp server simultaneously at the same time. this is a new model very fast with i7 8th Gen , 1 Tb SSD and it boot for few seconds.

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 if I just press enter without entering tftp server it gives this
      68823AB5-35D2-415E-AE10-A611413D88E5.jpeg

      Same host on the next boot

      B5648102-29B2-4838-9485-F31F55F9214F.jpeg

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 Yes, all of them. Next time when I stop the hosts and started with wake up on LAN now other 10-15 ask for tftp server, always in the same room of 25 hosts

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 @Sebastian-Roth I chanced the options in dnsmasq, restarted and nothing changed, always 5 to 10 different hosts ask for tftp server after taking an IP from DHCP of the University 4BC4DFCE-10B8-4D29-A826-D798776024F3.jpeg ![0_1583510428281_547BADC4-E100-4376-B025-9D12F6A3F622.jpeg](Uploading 0%)

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @Sebastian-Roth tel me how to make the test with wireshark to see the actual situation. Thanks

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 thank you so much. I’ll fix that tomorrow and will post the resold. Thanks again!

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 when a host boot I see it takes ip from dhcp, I see the dhcp address, I see the fog server on dhcp proxy place and everything is fine just to tftp: server. I put tftp server and it boot in fog menu. Like I say 25 hosts boot and 10 to 15 hosts ask for tftp server BUT have already IP and ready, just tftp server missing. Next time I send task other hosts ask for tftp server, always different hosts

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 I reinstalled recently the server with https .
      first time When I installed it I put the DNS IP for the server but this time I just skipped it. !BA804B4F-F0D9-4756-880F-12D8B90D34C4.jpeg

      Maybe this is the problem. Our DNS is DHCP server

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 the client takes IP from DHCP of the University. Me in the lab I use dnsmasq for proxy server. My server 192.168.149.43 is configured like IP helper in the switch of my lab which has 4 subnet and 400 hosts. We have only one address NAT for all hosts 132.208… which address all hosts use for exit address. It works like router . DHCP of the University is on 132.208. and works fine it gives IP

      Exit address 192.168.148.1

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 Ok , I’ll try tomorrow.
      It’s very very strange all this. Same hosts yesterday just one asked for TFTP server. Today 15 hosts ???
      With this config I use fog almost 4 months on different models HP and I saw one or two times to ask me for tftp server

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 do I have change it like this

      @marted said in Hosts are looking for tftp server.:

      dhcp-range=192.168.149.43,proxy

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 @Sebastian-Roth can I add some lines in my dnsmasq config which tells the tftp server. I think I saw that somewhere. I went today to other completely different lab with the same new model with new fog server I have just installed and I used the dnsmasq config like example to activate dhcp proxy and again the same problem, 40 hosts 15 ask for tftp server and when I enter it works.

      posted in FOG Problems
      M
      marted
    • RE: Hosts are looking for tftp server.

      @george1421 I need the dhcp range. I do pxe on 4 segments 192.168.148.0. 192.168.149.0 192.168.150.0 and 192.168.151.0

      posted in FOG Problems
      M
      marted
    • Hosts are looking for tftp server.

      We have just receved new computers Dell AIO 7470 and we found that when we send wake up on LAN, approximately 10 hosts from total of 25, block on tftp server and ask to enter it when we boot pxe. Second test different hosts make the same thing. We got the wiresharck file and please somebody to check it. This is a brand new model in our lab. I can show you too the dnsmasq config, just in case me missed something there.
      output.pcap

      # Don't function as a DNS server:
      port=0
      
      # Log lots of extra information about DHCP transactions.
      log-dhcp
      
      # Set the root directory for files available via FTP.
      tftp-root=/tftpboot
      
      # The boot filename, Server name, Server Ip Address
      dhcp-boot=undionly.kpxe,,192.168.149.43
      
      # Disable re-use of the DHCP servername and filename fields as extra
      # option space. That's to avoid confusing some old or broken DHCP clients.
      dhcp-no-override
      
      # inspect the vendor class string and match the text to set the tag
      dhcp-vendorclass=BIOS,PXEClient:Arch:00000
      dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
      dhcp-vendorclass=UEFI,PXEClient:Arch:00007
      dhcp-vendorclass=UEFI64,PXEClient:Arch:00009
      
      # Set the boot file name based on the matching tag from the vendor class (above)
      dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,192.168.149.43
      dhcp-boot=net:UEFI,ipxe.efi,,192.168.149.43
      dhcp-boot=net:UEFI64,ipxe.efi,,192.168.149.43
      
      # PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
      pxe-prompt="Booting FOG Client", 1
      
      # The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
      # Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
      # This option is first and will be the default if there is no input from the user.
      pxe-service=X86PC, "Boot to FOG", undionly.kpxe
      pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
      pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi
      
      dhcp-range=192.168.149.43,proxy,255.255.252.0
      
      posted in FOG Problems
      M
      marted
    • RE: Post-install snapin failed

      I found the smart installer for 11.19 🙂 Now it works on http. We will try to activate https on our server and activate https on the client

      posted in Windows Problems
      M
      marted
    • 1
    • 2
    • 3
    • 4
    • 5
    • 2 / 5