Некорректная работа tftp на CentOS
Здравствуйте, уважаемые форумчане! Прошу сильно не пинать за «избитую» тему насчёт tftp, но по своей проблеме ничего найти не смог, да и с Linux-ом, если честно, не совсем на «ты»… В общем, есть сервер с CentOS 7, на нём поднято несколько программ для мониторинга сетевого оборудования (Nagios, Cacti и пр.). Хочу использовать его и как хранилище конфигов мониторируемого оборудования (есть желание поставить Rancid). Для сбора конфигов не хочется использовать стандартный скрипт и логику Rancid-а (парсинг вывода команды show running-configuration) — это долго и трафика съедает много — решил использовать более быстрый, на мой взгляд, способ: скопировать файл конфига на сервер посредством tftp. Установил tftp, tftp-server, xinetd (+ подтянулся один зависимый пакет). В качестве рабочей папки выбрал /var/share. Содержимое /etc/xinet.d/tftp:
service tftp
< socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -c -s -vvv /var/share
disable = no
per_source = 11
cps = 100 2
flags = IPv4
>
Судя по man-у, параметр -c должен создавать файл. Т.е. я хочу, чтоб tftpd сам создал файл, в который будет писать данные. Состояние сервисов:
[root@localhost xinetd.d]# systemctl status tftp
● tftp.service — Tftp Server
Loaded: loaded (/usr/lib/systemd/system/tftp.service; indirect; vendor preset: disabled)
Active: inactive (dead) since Ср 2019-11-06 13:43:37 MSK; 16min ago
Docs: man:in.tftpd
Process: 7626 ExecStart=/usr/sbin/in.tftpd -s /var/lib/tftpboot (code=exited, status=0/SUCCESS)
Main PID: 7626 (code=exited, status=0/SUCCESS)
ноя 06 13:28:37 localhost.localdomain systemd[1]: Started Tftp Server.
[root@localhost xinetd.d]# systemctl status xinetd
● xinetd.service — Xinetd A Powerful Replacement For Inetd
Loaded: loaded (/usr/lib/systemd/system/xinetd.service; enabled; vendor preset: enabled)
Active: active (running) since Ср 2019-11-06 13:28:34 MSK; 32min ago
Process: 7282 ExecStart=/usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid $EXTRAOPTIONS (code=exited, status=0/SUCCESS) Main PID: 7283 (xinetd)
CGroup: /system.slice/xinetd.service
└─7283 /usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid
ноя 06 13:28:34 localhost.localdomain xinetd[7283]: Started working: 2 available services
Захожу на какой-либо маршрутизатор и пробую слить конфиг:
Error: Failed to transfer the file completely because of network connection error.
Хотя адрес сервера пингуется. Захожу в папку /var/share и вижу там файл vrpcfg.zip размером 1 байт… Пробую отправить со своего компа файл на сервер… Сервер файл принимает. Смотрю логи (tail -1000 /var/log/messages, IP компа: 10.176.251.250, IP маршрутизатора: 10.176.245.129:
Nov 6 13:28:34 localhost xinetd[7283]: xinetd Version 2.3.15 started with libwrap loadavg labeled-networking options compiled in.
Nov 6 13:28:34 localhost xinetd[7283]: Started working: 2 available services
Nov 6 13:28:37 localhost systemd: Started Tftp Server. (это я на всякий случай перезапустил tftp)
Nov 6 13:29:01 localhost xinetd[7283]: START: tftp pid=9345 from=10.176.245.129
Nov 6 13:29:01 localhost in.tftpd[9346]: WRQ from 10.176.245.129 filename vrpcfg.zip
Nov 6 13:29:06 localhost in.tftpd[9775]: WRQ from 10.176.245.129 filename vrpcfg.zip
Nov 6 13:29:11 localhost in.tftpd[10219]: WRQ from 10.176.245.129 filename vrpcfg.zip
Nov 6 13:29:16 localhost in.tftpd[10638]: WRQ from 10.176.245.129 filename vrpcfg.zip
Nov 6 13:29:21 localhost in.tftpd[11804]: WRQ from 10.176.245.129 filename vrpcfg.zip
Nov 6 13:29:21 localhost in.tftpd[11804]: WRQ from 10.176.245.129 filename vrpcfg.zip
Nov 6 13:39:23 localhost in.tftpd[32236]: WRQ from 10.176.251.250 filename D-Link_images.vss
Т.е. видно, что маршрутизатор что-то отправляет на сервер несколько раз и, видимо, не удачно. Комп отправил файл сразу же… Не понимаю, куда дальше копать… Конкретно логов tftp/xinetd нет (не пишет?). Помогите, пожалуйста, советом… Может, есть какой-нибудь альтернативный tftp?
Попробовал atftp — результат аналогичный…
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: Advanced Trivial FTP server started (0.7.2) Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: started by inetd Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: logging level: 7 Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: directory: /var/share/ Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: user: nobody.nogroup Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: log file: /var/log/atftp_log Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: not forcing to listen on local interfaces. Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: server timeout: 60 Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: tftp retry timeout: 5 Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: maximum number of thread: 100 Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: option timeout: enabled Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: option tzise: enabled Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: option blksize: enabled Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: option multicast: enabled Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: address range: 239.255.0.0-255 Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: port range: 1758 Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173628856064]: socket may listen on any address, including broadcast Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173628856064]: Creating new socket: 10.176.241.252:45302 Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173628856064]: Fetching from 10.176.245.129 to vrpcfg.zip Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173628856064]: recvmsg: Connection refused Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173628856064]: tftpd_file.c: 338: recvfrom: Connection refused Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173628856064]: Server thread exiting Nov 06 15:17:03 localhost.localdomain atftpd[12874.140173628856064]: socket may listen on any address, including broadcast Nov 06 15:17:03 localhost.localdomain atftpd[12874.140173628856064]: Creating new socket: 10.176.241.252:52720 Nov 06 15:17:03 localhost.localdomain atftpd[12874.140173628856064]: Fetching from 10.176.245.129 to vrpcfg.zip Nov 06 15:17:03 localhost.localdomain atftpd[12874.140173628856064]: recvmsg: Connection refused Nov 06 15:17:03 localhost.localdomain atftpd[12874.140173628856064]: tftpd_file.c: 338: recvfrom: Connection refused Nov 06 15:17:03 localhost.localdomain atftpd[12874.140173628856064]: Server thread exiting Nov 06 15:17:08 localhost.localdomain atftpd[12874.140173628856064]: socket may listen on any address, including broadcast Nov 06 15:17:08 localhost.localdomain atftpd[12874.140173628856064]: Creating new socket: 10.176.241.252:42943 Nov 06 15:17:08 localhost.localdomain atftpd[12874.140173628856064]: Fetching from 10.176.245.129 to vrpcfg.zip Nov 06 15:17:08 localhost.localdomain atftpd[12874.140173628856064]: recvmsg: Connection refused Nov 06 15:17:08 localhost.localdomain atftpd[12874.140173628856064]: tftpd_file.c: 338: recvfrom: Connection refused Nov 06 15:17:08 localhost.localdomain atftpd[12874.140173628856064]: Server thread exiting Nov 06 15:17:13 localhost.localdomain atftpd[12874.140173628856064]: socket may listen on any address, including broadcast Nov 06 15:17:13 localhost.localdomain atftpd[12874.140173628856064]: Creating new socket: 10.176.241.252:39357 Nov 06 15:17:13 localhost.localdomain atftpd[12874.140173628856064]: Fetching from 10.176.245.129 to vrpcfg.zip Nov 06 15:17:13 localhost.localdomain atftpd[12874.140173628856064]: recvmsg: Connection refused Nov 06 15:17:13 localhost.localdomain atftpd[12874.140173628856064]: tftpd_file.c: 338: recvfrom: Connection refused Nov 06 15:17:13 localhost.localdomain atftpd[12874.140173628856064]: Server thread exiting Nov 06 15:17:18 localhost.localdomain atftpd[12874.140173628856064]: socket may listen on any address, including broadcast Nov 06 15:17:18 localhost.localdomain atftpd[12874.140173628856064]: Creating new socket: 10.176.241.252:47104 Nov 06 15:17:18 localhost.localdomain atftpd[12874.140173628856064]: Fetching from 10.176.245.129 to vrpcfg.zip Nov 06 15:17:18 localhost.localdomain atftpd[12874.140173628856064]: recvmsg: Connection refused Nov 06 15:17:18 localhost.localdomain atftpd[12874.140173628856064]: tftpd_file.c: 338: recvfrom: Connection refused Nov 06 15:17:18 localhost.localdomain atftpd[12874.140173628856064]: Server thread exiting
SElinux — выключен, если что…
месиво текста, невозможно читать
Прошу прощения: не совсем разобрался с разметкой Markdown… Первое сообщение исправил, второе — перепишу здесь с учётом форматирования. Лог atftp:
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: Advanced Trivial FTP server started (0.7.2)
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: started by inetd
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: logging level: 7
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: directory: /var/share/
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: user: nobody.nogroup
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: log file: /var/log/atftp_log
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: not forcing to listen on local interfaces.
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: server timeout: 60
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: tftp retry timeout: 5
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: maximum number of thread: 100
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: option timeout: enabled
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: option tzise: enabled
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: option blksize: enabled
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: option multicast: enabled
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: address range: 239.255.0.0-255
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173644048192]: port range: 1758
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173628856064]: socket may listen on any address, including broadcast
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173628856064]: Creating new socket: 10.176.241.252:45302
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173628856064]: Fetching from 10.176.245.129 to vrpcfg.zip
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173628856064]: recvmsg: Connection refused
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173628856064]: tftpd_file.c: 338: recvfrom: Connection refused
Nov 06 15:16:58 localhost.localdomain atftpd[12874.140173628856064]: Server thread exiting
Nov 06 15:17:03 localhost.localdomain atftpd[12874.140173628856064]: socket may listen on any address, including broadcast
Nov 06 15:17:03 localhost.localdomain atftpd[12874.140173628856064]: Creating new socket: 10.176.241.252:52720
Nov 06 15:17:03 localhost.localdomain atftpd[12874.140173628856064]: Fetching from 10.176.245.129 to vrpcfg.zip
Nov 06 15:17:03 localhost.localdomain atftpd[12874.140173628856064]: recvmsg: Connection refused
Nov 06 15:17:03 localhost.localdomain atftpd[12874.140173628856064]: tftpd_file.c: 338: recvfrom: Connection refused
Nov 06 15:17:03 localhost.localdomain atftpd[12874.140173628856064]: Server thread exiting
Nov 06 15:17:08 localhost.localdomain atftpd[12874.140173628856064]: socket may listen on any address, including broadcast
Nov 06 15:17:08 localhost.localdomain atftpd[12874.140173628856064]: Creating new socket: 10.176.241.252:42943
Nov 06 15:17:08 localhost.localdomain atftpd[12874.140173628856064]: Fetching from 10.176.245.129 to vrpcfg.zip
Nov 06 15:17:08 localhost.localdomain atftpd[12874.140173628856064]: recvmsg: Connection refused
Nov 06 15:17:08 localhost.localdomain atftpd[12874.140173628856064]: tftpd_file.c: 338: recvfrom: Connection refused
Nov 06 15:17:08 localhost.localdomain atftpd[12874.140173628856064]: Server thread exiting
Nov 06 15:17:13 localhost.localdomain atftpd[12874.140173628856064]: socket may listen on any address, including broadcast
Nov 06 15:17:13 localhost.localdomain atftpd[12874.140173628856064]: Creating new socket: 10.176.241.252:39357
Nov 06 15:17:13 localhost.localdomain atftpd[12874.140173628856064]: Fetching from 10.176.245.129 to vrpcfg.zip
Nov 06 15:17:13 localhost.localdomain atftpd[12874.140173628856064]: recvmsg: Connection refused
Nov 06 15:17:13 localhost.localdomain atftpd[12874.140173628856064]: tftpd_file.c: 338: recvfrom: Connection refused
Nov 06 15:17:13 localhost.localdomain atftpd[12874.140173628856064]: Server thread exiting
Nov 06 15:17:18 localhost.localdomain atftpd[12874.140173628856064]: socket may listen on any address, including broadcast
Nov 06 15:17:18 localhost.localdomain atftpd[12874.140173628856064]: Creating new socket: 10.176.241.252:47104
Nov 06 15:17:18 localhost.localdomain atftpd[12874.140173628856064]: Fetching from 10.176.245.129 to vrpcfg.zip
Nov 06 15:17:18 localhost.localdomain atftpd[12874.140173628856064]: recvmsg: Connection refused
Nov 06 15:17:18 localhost.localdomain atftpd[12874.140173628856064]: tftpd_file.c: 338: recvfrom: Connection refused
Nov 06 15:17:18 localhost.localdomain atftpd[12874.140173628856064]: Server thread exiting
Ты уж определись через что запускается tftpd: либо xinetd, либо systemd. Одновременно они работать не будут.
Эмм… Это к первому посту относится, где «Nov 6 13:28:37 localhost systemd: Started Tftp Server.»? Я просто перезапустил и xinetd, и tftp:
systemctl restart xinetd
systemctl restart tftp
В общем, отказался я от «стандартного» tftp и установил atftp из исходников по этому ману: Hippolab. Настроил, чтоб tftp запускался при обращении к нему (чтоб постоянно не висел в памяти). Работает неплохо. А проблема моя решилась, благодаря подробному логу atftp: как оказалось, проблема была не в сервере, а в специфике работы маршрутизаторов, с которых предполагалось сливать конфиг. Так что, придётся заниматься сетью… Но это уже другая история 🙂
Источник
Логи tftp сервера linux
Recently is have been unable to pxe boot and started to receive the following errors.
PXE-E11: ARP timeout
PXE-E11: ARP timeout
PXE-E38: TFTP cannot open connection
PXE-M0F: Exiting intel PXE ROM
The strangest part here is that syslog has not recorded any entries concerning TFTP-HPA leaving to wonder what the problem is.
sudo service tftpd-hpa status
tftpd-hpa start/running, process 4470
ps aux|grep tftp
root 4470 0.0 0.0 15092 176 ? Ss 15:11 0:00 /usr/sbin/in.tftpd —listen —user tftp —address 0.0.0.0:69 —secure —ipv4 —map-file /etc/tftpd.map —verbose /srv/pxeboot
xbmc 6665 0.0 0.0 9388 932 pts/0 S+ 16:03 0:00 grep —color=auto tftp
RUN_DAEMON=»YES»
TFTP_USERNAME=»tftp»
TFTP_DIRECTORY=»/srv/pxeboot»
TFTP_ADDRESS=»0.0.0.0:69″
TFTP_OPTIONS=»—secure —ipv4 —map-file /etc/tftpd.map —verbose»
#TFTP_OPTIONS=»—secure»
OPTIONS=»-l -s /var/lib/tftpboot»
assistance is appreciated. thank you.
It looks like there’s a conflict in your TFTP directories.
Try removing the TFTP_DIRECTORY line and changing the OPTIONS line to OPTIONS=»-l -s /srv/pxeboot»
Thanks for the reply Newbiw, however, that change in the config file did nothing.
still no log entries in syslog. which makes this that much harder to troubleshoot.
Just in case, i removed tftpd-hpa and re-installed it without success.
/srv/pxeboot contains syslinux and windows source.
xbmc@PlexOne:/srv$ ls -l
total 4
drwxrwxrwx 8 root root 4096 Oct 15 17:34 pxeboot
BTW — i have also turn off the firewall to see if it was a problem.
contents of /srv/pxeboot
xbmc@PlexOne:/srv/pxeboot$ ls -l
total 1708
-rwxrwxrwx 1 root root 439 Jul 2 2012 altmbr.bin
-rwxrwxrwx 1 root root 439 Jul 2 2012 altmbr_c.bin
-rwxrwxrwx 1 root root 439 Jul 2 2012 altmbr_f.bin
-rwxrwxrwx 1 xbmc xbmc 12288 Oct 15 16:05 BCD.LOG
-rwxrwxrwx 1 xbmc xbmc 0 Oct 15 16:05 BCD.LOG1
-rwxrwxrwx 1 xbmc xbmc 0 Oct 15 16:05 BCD.LOG2
drwxrwxr-x 3 xbmc xbmc 4096 Oct 15 17:43 Boot
-rwxrwxrwx 1 xbmc xbmc 315 Oct 15 17:31 b.sh
-rwxrwxrwx 1 root root 5824 Jul 2 2012 cat.c32
-rwxrwxrwx 1 root root 20704 Jul 2 2012 chain.c32
-rwxrwxrwx 1 root root 800 Jul 2 2012 cmd.c32
drwxrwxrwx 3 root root 4096 Oct 12 22:24 com32
-rwxrwxrwx 1 root root 4748 Jul 2 2012 config.c32
-rwxrwxrwx 1 root root 5516 Jul 2 2012 cpuid.c32
-rwxrwxrwx 1 root root 15448 Jul 2 2012 cpuidtest.c32
drwxr-xr-x 2 root root 4096 Oct 12 22:24 diag
-rwxrwxrwx 1 root root 5516 Jul 2 2012 disk.c32
-rwxrwxrwx 1 root root 37016 Jul 2 2012 dmitest.c32
drwxr-xr-x 2 root root 4096 Oct 12 22:24 dosutil
-rwxrwxrwx 1 root root 28752 Jul 2 2012 elf.c32
-rwxrwxrwx 1 root root 29008 Jul 2 2012 ethersel.c32
-rwxrwxrwx 1 root root 21948 Jul 2 2012 gfxboot.c32
-rwxrwxrwx 1 root root 440 Jul 2 2012 gptmbr.bin
-rwxrwxrwx 1 root root 440 Jul 2 2012 gptmbr_c.bin
-rwxrwxrwx 1 root root 440 Jul 2 2012 gptmbr_f.bin
-rwxrwxrwx 1 root root 2320 Jul 2 2012 gpxecmd.c32
-rwxrwxrwx 1 root root 89469 Jul 2 2012 gpxelinux.0
-rwxrwxrwx 1 root root 89375 Jul 2 2012 gpxelinuxk.0
-rwxrwxrwx 1 root root 342708 Jul 2 2012 hdt.c32
-rwxrwxrwx 1 root root 4492 Jul 2 2012 host.c32
-rwxrwxrwx 1 root root 1312 Jul 2 2012 ifcpu64.c32
-rwxrwxrwx 1 root root 19936 Jul 2 2012 ifcpu.c32
-rwxrwxrwx 1 root root 2444 Jul 2 2012 ifplop.c32
-rwxrwxrwx 1 root root 55 Jul 2 2012 int18.com
-rwxrwxrwx 1 root root 432 Jul 2 2012 isohdpfx.bin
-rwxrwxrwx 1 root root 432 Jul 2 2012 isohdpfx_c.bin
-rwxrwxrwx 1 root root 432 Jul 2 2012 isohdpfx_f.bin
-rwxrwxrwx 1 root root 432 Jul 2 2012 isohdppx.bin
-rwxrwxrwx 1 root root 432 Jul 2 2012 isohdppx_c.bin
-rwxrwxrwx 1 root root 432 Jul 2 2012 isohdppx_f.bin
-rwxrwxrwx 1 root root 24576 Jul 2 2012 isolinux.bin
-rwxrwxrwx 1 root root 24576 Jul 2 2012 isolinux-debug.bin
-rwxrwxrwx 1 root root 5212 Jul 2 2012 kbdmap.c32
-rwxrwxrwx 1 root root 16872 Jul 2 2012 linux.c32
-rwxrwxrwx 1 root root 9388 Jul 2 2012 ls.c32
-rwxrwxrwx 1 root root 249420 Jul 2 2012 lua.c32
-rwxrwxrwx 1 root root 34396 Jul 2 2012 mboot.c32
-rwxrwxrwx 1 root root 440 Jul 2 2012 mbr.bin
-rwxrwxrwx 1 root root 440 Jul 2 2012 mbr_c.bin
-rwxrwxrwx 1 root root 440 Jul 2 2012 mbr_f.bin
-rwxr—r— 1 root root 26140 Jul 2 2012 memdisk
-rwxrwxrwx 1 root root 5912 Jul 2 2012 memdump.com
-rwxrwxrwx 1 root root 5300 Jul 2 2012 meminfo.c32
-rwxrwxrwx 1 root root 56164 Jul 2 2012 menu.c32
-rwxrwxrwx 1 root root 32740 Jul 2 2012 pcitest.c32
-rwxrwxrwx 1 root root 13148 Jul 2 2012 pmload.c32
-rwxrwxrwx 1 root root 239 Jul 2 2012 poweroff.com
-rwxrwxrwx 1 root root 1932 Jul 2 2012 pwd.c32
-rwxrwxrwx 1 root root 998 Jul 2 2012 pxechain.com
-rwxrwxrwx 1 root root 26461 Jul 2 2012 pxelinux.0
drwxrwxrwx 2 root root 4096 Oct 12 23:57 pxelinux.cfg
-rwxrwxrwx 1 root root 800 Jul 2 2012 reboot.c32
-rwxrwxrwx 1 root root 21384 Jul 2 2012 rosh.c32
-rwxrwxrwx 1 root root 2448 Jul 2 2012 sanboot.c32
-rwxrwxrwx 1 root root 26192 Jul 2 2012 sdi.c32
-rwxrwxrwx 1 root root 40432 Jul 2 2012 sysdump.c32
-rwxrwxrwx 1 root root 1300 Jul 2 2012 ver.com
-rwxrwxrwx 1 root root 5260 Jul 2 2012 vesainfo.c32
-rwxrwxrwx 1 root root 155792 Jul 2 2012 vesamenu.c32
-rwxrwxrwx 1 root root 6052 Jul 2 2012 vpdtest.c32
-rwxrwxrwx 1 root root 2960 Jul 2 2012 whichsys.c32
drwxrwxr-x 4 xbmc xbmc 4096 Oct 12 20:51 windows
-rwxrwxrwx 1 root root 9616 Jul 2 2012 zzjson.c32
That is strange, i know there were entries in the syslog, especially, once i placed the «—verbose» option in the config file. it displayed the mapfile entries and other items.
Bootlog — shows nothing.
I am literally at a loss, here anyone else have other suggestions on how to get TFTD-HPA to respond? or find out what is the problem?
machine get ip via dhcp,
firwall is off,
tftpd-hpa service is running
config files look to be ok.
but i get tftp pxe-e11 arp timeout on the work station. or can this be a bug?
shortly after the last posting, i reboot the workstation and realized that the DHCP address was incorrect. The dhcp server was on a DHCP reservation that was home how mysteriously removed on the router.
once i made the change the workstation came right up!
this was harder to troubleshoot since there was to log entries reported.
Источник
