Mikrotik tftp error code 0 string permission denied

Error code 0 string permission denied mikrotik tftp

Sun Jan 08, 2012 2:56 pm

I have a x86 with RouterOS 5.11
I try to configure the ROS to be a PXE server.
and I upload the pxe file to the «File» windows;set the Bootp Support to static;fill in the Boot File Name which I have upload to the ROS.
When the pxe client boots,I got an error:permission denied.
The ROS’s log was: «tftp error ERROR code:0 string permission denied!»
Any thing wrong with the tftp configure? I had set
# IP-ADDRESSES REQ-FILENAME REAL-FILENAME ALL REA ALL HITS
0 0.0.0.0 test.pxe test.pxe yes yes no 0

Is the REAL-FILENAME must to be set the full path? like «/sata1/file.txt»? But I can’t put the file to any other than the «file» window!
Any one has the experience of this can help me ?

Re: HELP! ROUTEROS to be a tftp server

Sun Jan 08, 2012 11:01 pm

Also, you have an IP set of 0.0.0.0. So, your client is using this IP address?! leave this field blank, or give it the specific IP of your clients. (You may have meant to enter 0.0.0.0/0?) but you can leave it blank and Mikrotik will automatically know this means the same as 0.0.0.0/0.

The permission denied is telling you the clue of where the problem is. it is not permitting the pxe to work because the client IP is not a valid IP, when matched with the server settings of a client having to have ‘0.0.0.0’

Re: HELP! ROUTEROS to be a tftp server

Mon Jan 09, 2012 7:43 am

Also, you have an IP set of 0.0.0.0. So, your client is using this IP address?! leave this field blank, or give it the specific IP of your clients. (You may have meant to enter 0.0.0.0/0?) but you can leave it blank and Mikrotik will automatically know this means the same as 0.0.0.0/0.

The permission denied is telling you the clue of where the problem is. it is not permitting the pxe to work because the client IP is not a valid IP, when matched with the server settings of a client having to have ‘0.0.0.0’

Now I had set «ip-address» to empty,like this:
# IP-ADDRESSES REQ-FILENAME REAL-FILENAME ALL REA ALL HITS
0 MAXDOS.PXE MAXDOS.PXE yes yes no 118

Then use dos command to tftp download the file:
C:Documents and SettingsAdministrator>tftp -i 192.168.0.254 get MAXDOS.PXE
Timeout occurred

In routeros,the log:
13:39:08 tftp,error ERROR: code 5
13:39:09 tftp,error ERROR: code 5
13:39:11 tftp,error ERROR: code 5
13:39:15 tftp,error ERROR: code 5
13:39:23 tftp,error ERROR: code 5
13:39:31 tftp,error ERROR: code 5
13:39:39 tftp,error ERROR: code 5
13:39:47 tftp,error ERROR: code 5
what’s the matter?

Источник

Error code 0 string permission denied mikrotik tftp

Wed Dec 20, 2017 1:06 pm

Hello everybody. I want to ask for help with my task.
I can’t configure network boot via TFTP on Mikrotik. I tried various instruction but result is the same, I can’t boot PC via PXE on Mikrotik.

Here is my configuration:
Mikrotik RB3011, ROS 6.39.2, SeliconPower USB 2.0 drive 16Gb
Bootloader — pxelinux.0

I have network boot server working under Debian with various images and it works fine.
I decided to configure such network boot service using mikrotik. I’ve formatted USB drive to ext2, but when it becomes clear that my configuration isn’t working, I tried to change filesystem to fat32 but it didn’t help me.
In general I’ve done such steeps:

• DHCP configuration
  Formatting USB drive
  Moving files to USB
  TFTP configuration

Re: TFTP boot configuration

Thu Dec 21, 2017 8:56 am

There are is records in router’s system journal about my problem:
tftp, error Error code: 0 string: permission denied!

Looks like problem with filesystem permissions. Any thoughts?

Re: TFTP boot configuration

Wed Jan 17, 2018 11:50 pm

Have you solved it yet?

I´m trying to do the exact same thing, and get «tftp: ERROR: code 0» in the log.

My target is to have a PXE Clonezilla on the router, I have tried out several different PXE images (Fedora, Ubuntu, Clonezilla, Kali and more) and can´t get any of them to work..

Re: TFTP boot configuration

Thu Jan 18, 2018 5:12 am

Some netboot experience from me:

1. Don’t assume you know what the problem is, even if you see messages on the server end. Do a packet sniff and open it up in Wireshark to see if it looks like the the problem you think it is. It’s hard to know exactly what the client is doing because there are usually no messages on the client end. So look at the traffic to see what it’s doing.

2. Maybe the «req. filename» vs. «real filename» thing is an issue? Did you try putting the boot file in the actual tftp root dir? I don’t know if that’s even relevant on a MikroTik TFTP server, I’ve never tried one.

(I learned most of what I know about netbooting using NetBSD as a boot server and client in the late 90s/early 2000s and haven’t done much since. )

Re: TFTP boot configuration

Thu Jan 18, 2018 8:14 pm

Re: TFTP boot configuration

Fri Jan 19, 2018 11:51 pm

I made a Wireshark trace, but I can´t really see the problem..

The PXE client sends a request to read the file «default» as configured in the DHCP servers ´Boot File Name field´, the router answers with the file length.
Next the PXE client sends an error code «Code 0, Not defined, Message: TFTP aborted»
And after that the PXE client sends a new request to read the «default» file, the router sends an acknowledge and then transmit the «default» file, and the PXE client makes an acknowledge after receiving the file.

Thats it, nothing more is happening.

I belive I may have a problem in the «default» file, I think the PXE client should request to get the boot image and start the boot sequence after the last ack.

The default file is from the Clonezilla web page;

Источник

Error code 0 string permission denied mikrotik tftp

Fri Oct 23, 2009 5:44 pm

And when, on my windows host, i type
«tftp 192.168.1.1 GET st2030s.inf»

Did i miss something ?

Thanks four your replies.

Re: mikrotik tftp server not working

Fri Oct 23, 2009 5:58 pm

The «ip-addresses» parameter configures the IP addresses of clients permitted to access the file. Since you appear to be configuring that to be only the server itself, the client is denied access.

Re: mikrotik tftp server not working

Fri Oct 23, 2009 6:28 pm

Ok thanks, didn’t understood that.
now «hits» field increments, but I have this message :
C:>tftp 192.168.1.1 GET st2030s.inf
Délai d’attente dépassé

Any idea ?
Thanks again

Re: mikrotik tftp server not working

Fri Oct 23, 2009 8:10 pm

32 MB file size.

If you need to transfer a bigger file, try using tftp-hpa (works well).

Re: mikrotik tftp server not working

Tue Oct 27, 2009 10:03 am

Re: mikrotik tftp server not working

Wed Oct 28, 2009 10:32 am

Re: mikrotik tftp server not working

Wed Oct 28, 2009 12:12 pm

Re: mikrotik tftp server not working

Thu Oct 29, 2009 10:35 am

Ok, it finally works well, it was a firewall mangle problem.

Re: mikrotik tftp server not working

Tue May 27, 2014 8:21 pm

I seem to be having a similar issue with TFTP. I’m running 6.13(just upgraded to see if it would help, was on 5.24 before)

I have some files for a cisco 7940 that i’m trying to upgrade to SIP.

I am able to do this just fine using TFTP server on my local machine and the phone does everything it needs to.

The issue is when i try to run the TFTP on the mikrotik i get a Error code: 0 strink permission denied.

Here is what i have under /ip tftp

23 P0S3-8-12-00.loads P0S3-8-12-00.loads yes yes no 0
24 P0S3-8-12-00.sb2 P0S3-8-12-00.sb2 yes yes no 0
25 P003-8-12-00.bin P003-8-12-00.bin yes yes no 0
26 P003-8-12-00.sbn P003-8-12-00.sbn yes yes no 0
27 SEP0014A972571A.cnf SEP0014A972571A.cnf yes yes no 0
28 SEP0014A972571A.cnf.xml SEP0014A972571A.cnf.xml yes yes no 0
29 SIP0014A972571A.cnf SIP0014A972571A.cnf yes yes no 1
30 OS79XX.TXT OS79XX.TXT yes yes no 0

Files have been uploaded to the MT as i have been able to use it for other phones just fine.

Any ideas of why i would be getting this error?

Источник

Windows-терминалы WTware

Программа-клиент службы терминалов Windows Terminal Services, для бездисковых терминалов и загрузки по сети. Основной сайт http://www.wtware.ru

mikrotik RB951 + WTWare v.5.1.28 ПРОБЛЕМЫ

mikrotik RB951 + WTWare v.5.1.28 ПРОБЛЕМЫ

Сообщение rockpati » Пн май 05, 2014 9:38 am

Помогите, не могу понять куда копать.
Данные:
Есть маршрутизатор mikrotik rb951ui-2hnd IP:192.168.0.1
Сервер RDS: Windows Server 2008 r2 sp1 IP:192.168.0.252 порт RDP 64500
WTWare v.5.1.28
Необходимо:
Чтобы на mikrotik-е был WTware который поднимал бы терминалы до Сервера.
Что сделал:
— С рабочего сервера WTware, скопировал содержимое папки TFTPDROOT
— Вставил файлы в память mikrotik (за исключением файла TFTPDROOT5.1.28packageschrome так как на него физически не хватало места). по следующему пути tftp/
— Настроил DHCP mikrotik-а со следующими параметрами (далее выдержка конфигурации mikrotik) :
/ip dhcp-server option
add code=66 name=SerZagruzki value=»‘192.168.0.252:64500′»
/ip pool
add name=default-dhcp ranges=192.168.0.10-192.168.0.254
/ip dhcp-server
add address-pool=default-dhcp disabled=no interface=bridge-local name=default
/ip dhcp-server network
add address=192.168.0.0/24 boot-file-name=tftp/5.1.28/wtware.pxe comment=
dhcp-lan dhcp-option=SerZagruzki dns-server=192.168.0.1 gateway=
192.168.0.1 netmask=24 next-server=192.168.0.1
— Включил TFTP для файлов (далее выдержка конфигурации mikrotik):
/ip tftp
add allow-rollover=yes real-filename=tftp/5.1.28/wtware.pxe req-filename=
wtware.pxe
add allow-rollover=yes real-filename=tftp/5.1.28/pxe.cfg req-filename=pxe.cfg
add allow-rollover=yes real-filename=tftp/5.1.28/wtware.nbi req-filename=
wtware.nbi
add allow-rollover=yes real-filename=tftp/5.1.28/wtware.http req-filename=
wtware.http
add allow-rollover=yes real-filename=tftp/5.1.28/http.cfg req-filename=
http.cfg
add allow-rollover=yes real-filename=tftp/5.1.28/debug.pxe req-filename=
debug.pxe
add allow-rollover=yes real-filename=tftp/5.1.28/packages/kernel
req-filename=packages/kernel
add allow-rollover=yes real-filename=tftp/5.1.28/packages/alsa req-filename=
packages/alsa
add allow-rollover=yes real-filename=tftp/5.1.28/packages/alsalib
req-filename=packages/alsalib
add allow-rollover=yes real-filename=tftp/5.1.28/packages/alsalib4
req-filename=packages/alsalib4
add allow-rollover=yes real-filename=tftp/5.1.28/packages/alsalib6
req-filename=packages/alsalib6
add allow-rollover=yes real-filename=tftp/5.1.28/packages/chprf.zip
req-filename=packages/chprf.zip
add allow-rollover=yes real-filename=tftp/5.1.28/packages/f req-filename=
packages/f
add allow-rollover=yes real-filename=tftp/5.1.28/packages/fwt req-filename=
packages/fwt
add allow-rollover=yes real-filename=tftp/5.1.28/packages/graphic
req-filename=packages/graphic
add allow-rollover=yes real-filename=tftp/5.1.28/packages/lib4 req-filename=
packages/lib4
add allow-rollover=yes real-filename=tftp/5.1.28/packages/lib6 req-filename=
packages/lib6
add allow-rollover=yes real-filename=tftp/5.1.28/packages/linphone
req-filename=packages/linphone
add allow-rollover=yes real-filename=tftp/5.1.28/packages/memtest
req-filename=packages/memtest
add allow-rollover=yes real-filename=tftp/5.1.28/packages/oss req-filename=
packages/oss
add allow-rollover=yes real-filename=tftp/5.1.28/packages/print req-filename=
packages/print
add allow-rollover=yes real-filename=tftp/5.1.28/packages/samba req-filename=
packages/samba
add allow-rollover=yes real-filename=tftp/5.1.28/packages/sc req-filename=
packages/sc
add allow-rollover=yes real-filename=tftp/5.1.28/packages/scan req-filename=
packages/scan
add allow-rollover=yes real-filename=tftp/5.1.28/packages/setup req-filename=
packages/setup
add allow-rollover=yes real-filename=tftp/5.1.28/packages/u req-filename=
packages/u
add allow-rollover=yes real-filename=tftp/5.1.28/packages/uati req-filename=
packages/uati
add allow-rollover=yes real-filename=tftp/5.1.28/packages/uetc req-filename=
packages/uetc
add allow-rollover=yes real-filename=tftp/5.1.28/packages/uintel
req-filename=packages/uintel
add allow-rollover=yes real-filename=tftp/5.1.28/packages/unouveau
req-filename=packages/unouveau
add allow-rollover=yes real-filename=tftp/5.1.28/packages/uopenchrome
req-filename=packages/uopenchrome
add allow-rollover=yes real-filename=tftp/5.1.28/packages/usbip req-filename=
packages/usbip
add allow-rollover=yes real-filename=tftp/5.1.28/packages/usis req-filename=
packages/usis
add allow-rollover=yes real-filename=tftp/5.1.28/packages/uvesa req-filename=
packages/uvesa
add allow-rollover=yes real-filename=tftp/5.1.28/packages/wtc.log
req-filename=packages/wtc.log
add allow-rollover=yes real-filename=tftp/5.1.28/packages/x req-filename=
packages/x
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xapm req-filename=
packages/xapm
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xark req-filename=
packages/xark
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xchips
req-filename=packages/xchips
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xcirrus
req-filename=packages/xcirrus
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xgeode
req-filename=packages/xgeode
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xglint
req-filename=packages/xglint
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xi810 req-filename=
packages/xi810
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xmga req-filename=
packages/xmga
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xnet req-filename=
packages/xnet
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xnsc req-filename=
packages/xnsc
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xrdc req-filename=
packages/xrdc
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xrendition
req-filename=packages/xrendition
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xs3 req-filename=
packages/xs3
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xs3virge
req-filename=packages/xs3virge
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xsavage
req-filename=packages/xsavage
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xsis req-filename=
packages/xsis
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xtdfx req-filename=
packages/xtdfx
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xtrident
req-filename=packages/xtrident
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xtseng
req-filename=packages/xtseng
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xunichrome
req-filename=packages/xunichrome
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xvesa req-filename=
packages/xvesa
add allow-rollover=yes real-filename=tftp/5.1.28/packages/xxgi req-filename=
packages/xxgi
add allow-rollover=yes real-filename=tftp/5.1.28/packages/initrd
req-filename=packages/initrd
add allow-rollover=yes real-filename=tftp/5.1.28/packages/initrd.cpp
req-filename=packages/initrd.cpp
add allow-rollover=yes real-filename=tftp/Chrome req-filename=tftp/Chrome
add allow-rollover=yes real-filename=tftp/Connections req-filename=
tftp/Connections
add allow-rollover=yes real-filename=tftp/Everyone/all.wtc req-filename=
tftp/Everyone/all.wtc
add allow-rollover=yes real-filename=tftp/Everyone/list.wtc req-filename=
tftp/Everyone/list.wtc
add allow-rollover=yes real-filename=tftp/Everyone/wtware.lic req-filename=
tftp/Everyone/wtware.lic
add allow-rollover=yes real-filename=tftp/Templates req-filename=
tftp/Templates
add allow-rollover=yes real-filename=tftp/Graphic/sample/menu.gif
req-filename=tftp/Graphic/sample/menu.gif
add allow-rollover=yes real-filename=tftp/Graphic/sample/popup.gif
req-filename=tftp/Graphic/sample/popup.gif
add allow-rollover=yes real-filename=tftp/Graphic/sample/wait.gif
req-filename=tftp/Graphic/sample/wait.gif
add allow-rollover=yes real-filename=tftp/ListIncludes req-filename=
tftp/ListIncludes
add allow-rollover=yes real-filename=tftp/Terminals req-filename=
tftp/Terminals
Что получилось: PXE файл загружает доходит до «визорда» Настройка видеокарты и тд. Пишет что не найдено индивидуального конфигурационного файла для этого терминала. Дальше что не делаю или настраиваю терминал или пропускаю выдает следующую ошибку:
ОШИБКА: INTRNAL ERROR
WTware: v.5.1.28
File: initrd.cpp
Line: 336
Fanction: main
Please, report this information to WTware tech support.

Подскажите куда капать?
что только не пробовал создавать файл конфигурации в ручную все бесполезно.

Re: mikrotik RB951 + WTWare v.5.1.28 ПРОБЛЕМЫ

Сообщение Antonio » Пн май 05, 2014 10:28 am

Re: mikrotik RB951 + WTWare v.5.1.28 ПРОБЛЕМЫ

Сообщение aka » Пн май 05, 2014 8:46 pm

1. Свежая версия втвари называется 5.1.62.
2. На http://wtware.ru/download.html лежит дистрибутив в .zip. Он там лежит специально для использования с ненашими TFTP.
3. Я правильно понимаю, что командой:

add allow-rollover=yes real-filename=tftp/5.1.28/wtware.pxe req-filename=
wtware.pxe

ты загубил нашу структуру каталогов? Не надо это делать. В .zip будет правильная структура каталогов, и надо научить TFTP сервер отдавать именно нашу стркутуру. Файл tftp/5.1.28/wtware.pxe должен остаться файлом tftp/5.1.28/wtware.pxe. Не надо сокращать его до wtware.pxe

Re: mikrotik RB951 + WTWare v.5.1.28 ПРОБЛЕМЫ

Сообщение Гость » Вт май 06, 2014 10:12 am

Установил свежую версию (WTware для платформы x86, процессоры Intel, AMD, VIA) wtware.5.1.62.zip — результат:
INTERNAL ERROR
WTware v.5.1.62
File: initrd.cpp
Line: 297
Function: main
.
В общем ошибка другая но результат тот-же.
По шагам:
1) скопировал и разархивировал файл
2) ресетнул mikrotik и до типовой конфигурации
3) скопировал в корень mikrotika папку wtware (она аналогична wtware.5.1.62.ru)
4) переделал DHCP
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
/ip dhcp-server
add address-pool=default-dhcp disabled=no interface=bridge-local name=default
/ip address
add address=192.168.88.1/24 comment=»default configuration» interface=wlan1
network=192.168.88.0
/ip dhcp-server network
add address=192.168.88.0/24 boot-file-name=wtware/5.1.62/wtware.pxe comment=
«default configuration» dns-server=192.168.88.1 gateway=192.168.88.1
netmask=24 next-server=192.168.88.1
5) показал микротику структуру TFTP
/ip tftp
add allow-rollover=yes real-filename=wtware/5.1.62/wtware.pxe req-filename=
wtware/5.1.62/wtware.pxe
add allow-rollover=yes real-filename=wtware/5.1.62/pxe.cfg req-filename=
wtware/5.1.62/pxe.cfg
add allow-rollover=yes real-filename=wtware/5.1.62/wtware.nbi req-filename=
wtware/5.1.62/wtware.nbi
add allow-rollover=yes real-filename=wtware/5.1.62/wtware.http req-filename=
wtware/5.1.62/wtware.http
add allow-rollover=yes real-filename=wtware/5.1.62/http.cfg req-filename=
wtware/5.1.62/http.cfg
add allow-rollover=yes real-filename=wtware/5.1.62/debug.pxe req-filename=
wtware/5.1.62/debug.pxe
add allow-rollover=yes real-filename=wtware/5.1.62/packages/kernel
req-filename=wtware/5.1.62/packages/kernel
add allow-rollover=yes real-filename=wtware/5.1.62/packages/initrd
req-filename=wtware/5.1.62/packages/initrd
add allow-rollover=yes real-filename=wtware/5.1.62/packages/initrd.cpp
req-filename=wtware/5.1.62/packages/initrd.cpp
add allow-rollover=yes real-filename=wtware/5.1.62/packages/alsa
req-filename=wtware/5.1.62/packages/alsa
add allow-rollover=yes real-filename=wtware/5.1.62/packages/alsalib
req-filename=wtware/5.1.62/packages/alsalib
add allow-rollover=yes real-filename=wtware/5.1.62/packages/alsalib4
req-filename=wtware/5.1.62/packages/alsalib4
add allow-rollover=yes real-filename=wtware/5.1.62/packages/alsalib6
req-filename=wtware/5.1.62/packages/alsalib6
add allow-rollover=yes real-filename=wtware/5.1.62/packages/chprf.zip
req-filename=wtware/5.1.62/packages/chprf.zip
add allow-rollover=yes real-filename=wtware/5.1.62/packages/f req-filename=
wtware/5.1.62/packages/f
add allow-rollover=yes real-filename=wtware/5.1.62/packages/fwt req-filename=
wtware/5.1.62/packages/fwt
add allow-rollover=yes real-filename=wtware/5.1.62/packages/graphic
req-filename=wtware/5.1.62/packages/graphic
add allow-rollover=yes real-filename=wtware/5.1.62/packages/lib4
req-filename=wtware/5.1.62/packages/lib4
add allow-rollover=yes real-filename=wtware/5.1.62/packages/lib6
req-filename=wtware/5.1.62/packages/lib6
add allow-rollover=yes real-filename=wtware/5.1.62/packages/linphone
req-filename=wtware/5.1.62/packages/linphone
add allow-rollover=yes real-filename=wtware/5.1.62/packages/memtest
req-filename=wtware/5.1.62/packages/memtest
add allow-rollover=yes real-filename=wtware/5.1.62/packages/oss req-filename=
wtware/5.1.62/packages/oss
add allow-rollover=yes real-filename=wtware/5.1.62/packages/print
req-filename=wtware/5.1.62/packages/print
add allow-rollover=yes real-filename=wtware/5.1.62/packages/samba
req-filename=wtware/5.1.62/packages/samba
add allow-rollover=yes real-filename=wtware/5.1.62/packages/sc req-filename=
wtware/5.1.62/packages/sc
add allow-rollover=yes real-filename=wtware/5.1.62/packages/scan
req-filename=wtware/5.1.62/packages/scan
add allow-rollover=yes real-filename=wtware/5.1.62/packages/setup
req-filename=wtware/5.1.62/packages/setup
add allow-rollover=yes real-filename=wtware/5.1.62/packages/u req-filename=
wtware/5.1.62/packages/u
add allow-rollover=yes real-filename=wtware/5.1.62/packages/uati
req-filename=wtware/5.1.62/packages/uati
add allow-rollover=yes real-filename=wtware/5.1.62/packages/uetc
req-filename=wtware/5.1.62/packages/uetc
add allow-rollover=yes real-filename=wtware/5.1.62/packages/uintel
req-filename=wtware/5.1.62/packages/uintel
add allow-rollover=yes real-filename=wtware/5.1.62/packages/unouveau
req-filename=wtware/5.1.62/packages/unouveau
add allow-rollover=yes real-filename=wtware/5.1.62/packages/uopenchrome
req-filename=wtware/5.1.62/packages/uopenchrome
add allow-rollover=yes real-filename=wtware/5.1.62/packages/usbip
req-filename=wtware/5.1.62/packages/usbip
add allow-rollover=yes real-filename=wtware/5.1.62/packages/usis
req-filename=wtware/5.1.62/packages/usis
add allow-rollover=yes real-filename=wtware/5.1.62/packages/uvesa
req-filename=wtware/5.1.62/packages/uvesa
add allow-rollover=yes real-filename=wtware/5.1.62/packages/wtc.log
req-filename=wtware/5.1.62/packages/wtc.log
add allow-rollover=yes real-filename=wtware/5.1.62/packages/x req-filename=
wtware/5.1.62/packages/x
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xapm
req-filename=wtware/5.1.62/packages/xapm
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xark
req-filename=wtware/5.1.62/packages/xark
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xchips
req-filename=wtware/5.1.62/packages/xchips
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xcirrus
req-filename=wtware/5.1.62/packages/xcirrus
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xgeode
req-filename=wtware/5.1.62/packages/xgeode
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xglint
req-filename=wtware/5.1.62/packages/xglint
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xi810
req-filename=wtware/5.1.62/packages/xi810
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xmga
req-filename=wtware/5.1.62/packages/xmga
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xnet
req-filename=wtware/5.1.62/packages/xnet
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xnsc
req-filename=wtware/5.1.62/packages/xnsc
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xrdc
req-filename=wtware/5.1.62/packages/xrdc
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xrendition
req-filename=wtware/5.1.62/packages/xrendition
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xs3 req-filename=
wtware/5.1.62/packages/xs3
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xs3virge
req-filename=wtware/5.1.62/packages/xs3virge
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xsavage
req-filename=wtware/5.1.62/packages/xsavage
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xsis
req-filename=wtware/5.1.62/packages/xsis
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xtdfx
req-filename=wtware/5.1.62/packages/xtdfx
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xtrident
req-filename=wtware/5.1.62/packages/xtrident
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xtseng
req-filename=wtware/5.1.62/packages/xtseng
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xunichrome
req-filename=wtware/5.1.62/packages/xunichrome
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xvesa
req-filename=wtware/5.1.62/packages/xvesa
add allow-rollover=yes real-filename=wtware/5.1.62/packages/xxgi
req-filename=wtware/5.1.62/packages/xxgi
add allow-rollover=yes real-filename=wtware/Documentation/audit.html
req-filename=wtware/Documentation/audit.html
add allow-rollover=yes real-filename=wtware/Documentation/boot.html
req-filename=wtware/Documentation/boot.html
add allow-rollover=yes real-filename=wtware/Documentation/config.html
req-filename=wtware/Documentation/config.html
add allow-rollover=yes real-filename=wtware/Documentation/configurator.html
req-filename=wtware/Documentation/configurator.html
add allow-rollover=yes real-filename=wtware/Documentation/dhcp.html
req-filename=wtware/Documentation/dhcp.html
add allow-rollover=yes real-filename=wtware/Documentation/openvpn.html
req-filename=wtware/Documentation/openvpn.html
add allow-rollover=yes real-filename=wtware/Documentation/tune.html
req-filename=wtware/Documentation/tune.html
add allow-rollover=yes real-filename=wtware/Documentation/wifi.html
req-filename=wtware/Documentation/wifi.html
add allow-rollover=yes real-filename=wtware/Documentation/wtide.html
req-filename=wtware/Documentation/wtide.html
add allow-rollover=yes real-filename=wtware/Documentation/wtiso.html
req-filename=wtware/Documentation/wtiso.html
add allow-rollover=yes real-filename=wtware/Documentation/wtusb.html
req-filename=wtware/Documentation/wtusb.html
add allow-rollover=yes real-filename=wtware/Documentation/pic/012.png
req-filename=wtware/Documentation/pic/012.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/012_wt.png
req-filename=wtware/Documentation/pic/012_wt.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/018.png
req-filename=wtware/Documentation/pic/018.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/018_wt.png
req-filename=wtware/Documentation/pic/018_wt.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/066.png
req-filename=wtware/Documentation/pic/066.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/066_wt.png
req-filename=wtware/Documentation/pic/066_wt.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/067.png
req-filename=wtware/Documentation/pic/067.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/067_wt.png
req-filename=wtware/Documentation/pic/067_wt.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/074.png
req-filename=wtware/Documentation/pic/074_wt.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/blue_3.png
req-filename=wtware/Documentation/pic/blue_3.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/cdrom.png
req-filename=wtware/Documentation/pic/cdrom.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/cdsetup.png
req-filename=wtware/Documentation/pic/cdsetup.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/comics.png
req-filename=wtware/Documentation/pic/comics.png
add allow-rollover=yes real-filename=
wtware/Documentation/pic/connection_fix.png req-filename=
wtware/Documentation/pic/connection_fix.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/d.png
req-filename=wtware/Documentation/pic/d.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/del2setup.png
req-filename=wtware/Documentation/pic/del2setup.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/dhcp.png
req-filename=wtware/Documentation/pic/dhcp.png
add allow-rollover=yes real-filename=
wtware/Documentation/pic/editor_noversion.png req-filename=
wtware/Documentation/pic/editor_noversion.png
add allow-rollover=yes real-filename=
wtware/Documentation/pic/editor_version.png req-filename=
wtware/Documentation/pic/editor_version.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/error.png
req-filename=wtware/Documentation/pic/error.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/floppy.png
req-filename=wtware/Documentation/pic/floppy.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/green_2.png
req-filename=wtware/Documentation/pic/green_2.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/hdd.png
req-filename=wtware/Documentation/pic/hdd.png
add allow-rollover=yes real-filename=
wtware/Documentation/pic/index_internal_light_small.png req-filename=
wtware/Documentation/pic/index_internal_light_small.png
add allow-rollover=yes real-filename=
wtware/Documentation/pic/logowtware_light.png req-filename=
wtware/Documentation/pic/logowtware_light.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/logs.png
req-filename=wtware/Documentation/pic/logs.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/makeiso1.png
req-filename=wtware/Documentation/pic/makeiso1.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/makeiso2.png
req-filename=wtware/Documentation/pic/makeiso2.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/makeiso3.png
req-filename=wtware/Documentation/pic/makeiso3.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/makeiso4.png
req-filename=wtware/Documentation/pic/makeiso4.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/nic.png
req-filename=wtware/Documentation/pic/nic.png
add allow-rollover=yes real-filename=
wtware/Documentation/pic/openvpn-keygen.png req-filename=
wtware/Documentation/pic/openvpn-keygen.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/red_1.png
req-filename=wtware/Documentation/pic/red_1.png
add allow-rollover=yes real-filename=
wtware/Documentation/pic/ScreensTerminal.png req-filename=
wtware/Documentation/pic/ScreensTerminal.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/small_arrow.png
req-filename=wtware/Documentation/pic/small_arrow.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/text.png
req-filename=wtware/Documentation/pic/text.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/usbflash.png
req-filename=wtware/Documentation/pic/usbflash.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/utilities.png
req-filename=wtware/Documentation/pic/utilities.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/wifi_wtdisc.png
req-filename=wtware/Documentation/pic/wifi_wtdisc.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/wifi_wtiso.png
req-filename=wtware/Documentation/pic/wifi_wtiso.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/wizard_1.png
req-filename=wtware/Documentation/pic/wizard_1.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/wizard_2.png
req-filename=wtware/Documentation/pic/wizard_2.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/wizard_3.png
req-filename=wtware/Documentation/pic/wizard_3.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/wizard_4.png
req-filename=wtware/Documentation/pic/wizard_4.png
add allow-rollover=yes real-filename=
wtware/Documentation/pic/wizard_configurator.png req-filename=
wtware/Documentation/pic/wizard_configurator.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/wizard_menu.png
req-filename=wtware/Documentation/pic/wizard_menu.png
add allow-rollover=yes real-filename=
wtware/Documentation/pic/wizard_server.png req-filename=
wtware/Documentation/pic/wizard_server.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/wizard_test.png
req-filename=wtware/Documentation/pic/wizard_test.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/wtiso.png
req-filename=wtware/Documentation/pic/wtiso.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/wtpassword.png
req-filename=wtware/Documentation/pic/wtpassword.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/wtusb.png
req-filename=wtware/Documentation/pic/wtusb.png
add allow-rollover=yes real-filename=wtware/Documentation/pic/wtware.css
req-filename=wtware/Documentation/pic/wtware.css
add allow-rollover=yes real-filename=wtware/Chrome req-filename=wtware/Chrome
add allow-rollover=yes real-filename=wtware/Connections/example.wtc
req-filename=wtware/Connections/example.wtc
add allow-rollover=yes real-filename=wtware/Everyone/all.wtc req-filename=
wtware/Everyone/all.wtc
add allow-rollover=yes real-filename=wtware/Everyone/list.wtc req-filename=
wtware/Everyone/list.wtc
add allow-rollover=yes real-filename=wtware/Everyone/wtware.lic req-filename=
wtware/Everyone/wtware.lic
add allow-rollover=yes real-filename=wtware/Templates/example.wtc
req-filename=wtware/Templates/example.wtc
add allow-rollover=yes real-filename=wtware/Graphic/sample/menu.png
req-filename=wtware/Graphic/sample/menu.png
add allow-rollover=yes real-filename=wtware/Graphic/sample/popup.png
req-filename=wtware/Graphic/sample/popup.png
add allow-rollover=yes real-filename=wtware/Graphic/sample/wait.png
req-filename=wtware/Graphic/sample/wait.png
add allow-rollover=yes real-filename=wtware/ListIncludes req-filename=
wtware/ListIncludes
add allow-rollover=yes real-filename=wtware/COPYRIGHT.txt req-filename=
wtware/COPYRIGHT.txt
add allow-rollover=yes real-filename=
wtware/Terminals/00.01.23.45.AB.CD/config.wtc req-filename=
wtware/Terminals/00.01.23.45.AB.CD/config.wtc

Это все что было в zip архиве
6) Естественно перезапустил терминал а результат я описал выше.

Re: mikrotik RB951 + WTWare v.5.1.28 ПРОБЛЕМЫ

Сообщение aka » Вт май 06, 2014 12:08 pm

initrd.cpp? Как это?

Когда она падает, она запускает командную строку. Из командной строки надо запустить команду:
cat /tmp/all.log
Она выдаст много текста. Листать текст вверх можно, нажимая Shift-PageUp. Хочу фотографии последнего экрана и нескольких экранов вверх.

Подозреваю, окажется, что какой-то из файлов битый, с нулевым размером, из старой версии и т.д. Ошибка не типиичная, на исправной структуре файлов такое не могло стучиться.

Re: mikrotik RB951 + WTWare v.5.1.28 ПРОБЛЕМЫ

Сообщение Гость » Ср май 07, 2014 2:02 am

1) Ситуация следующая файл «initrd.cpp» как таковой в дистрибутиве WTware v.5.1.62
отсутствует, также он отсутствовал и в дистрибутиве 5.1.28. В изначальном варианте когда я писал первое сообщение я пробовал его создавать из файла пакета initrd добавим ему расширение cpp и прописав его в mikrotik-е потому вы там и увидели строку:
add allow-rollover=yes real-filename=wtware/5.1.62/packages/initrd.cpp req-filename=wtware/5.1.62/packages/initrd.cpp
Прошу заметить что файла initrd.cpp уже в последнем сообщении нету. но ситуация не меняется.

2) После вывода лога вижу следующее:
http://s52.radikal.ru/i137/1405/c0/0bc4fec81b2c.jpg
Насколько я понимая он начинает скачивать файл graphic и на этом затык.

Re: mikrotik RB951 + WTWare v.5.1.28 ПРОБЛЕМЫ

Сообщение aka » Ср май 07, 2014 7:05 pm

На фотке ужас какой-то. Такого не может быть, потому что такого не может быть никогда.

Удали ВСЁ, что ты насовал в микротика. Чтобы никаких следов самодеятельности там не осталось. Потом скачай заново втварь в .zip архиве с wtware.ru. Разархивируй. И запиши в микроитка заново. Не меняй структуру файлов. Не создавай никаких файлов кроме одного текстового конфига.

Re: mikrotik RB951 + WTWare v.5.1.28 ПРОБЛЕМЫ

Сообщение Гость » Чт май 08, 2014 9:05 am

Re: mikrotik RB951 + WTWare v.5.1.28 ПРОБЛЕМЫ

Сообщение aka » Пт май 09, 2014 12:43 am

Там подгружается 1 (один) файл. С этим ты уже справился Теперь надо понять, почему вместо подгрузки остальных файлов втварь получает что-то не то.

ЗЫ: add allow-rollover=yes real-filename=wtware/5.1.62/packages/wtc.log
req-filename=wtware/5.1.62/packages/wtc.log

В .zip архиве точно нет файла wtc.log. Значит ты опять копируешь не из .zip архива, а из какого-то другого, неправильного места.

Re: mikrotik RB951 + WTWare v.5.1.28 ПРОБЛЕМЫ

Сообщение rockpati » Пт май 09, 2014 2:53 am

Источник

7 hours ago, adron2 said:

Я микротик только и использую в качестве tftp + dhcp.

Однако категорично.

Прошу прощения у ТС за то, что не совсем по теме (хотя и близко, вроде как ответ на вопрос «А собственно, зачем?». 

Предупреждение: все, что ниже — исключительно ИМХО.

При всех глюках неясной природы, закрытости и не самой свежей версии ядра лично мне гораздо комфортнее в CLI и особенно в Winbox от RoS, чем в WinSCP или консоли OpenWRT/LEDE. По Webfig и Luci скажу проще — первое всегда disabled, второе просто не ставлю. А от глюков RoS можно избавиться, если соблюдать несколько простых правил.

— Заметил, что часто остаются «хвосты» от старых настроек. Так однажды я вывел конфиг через export verbose вместо привычного export compact, и увидел давно ставшие ненужными new-route-mark=»name» disabled=yes. Winbox и export compact ничего такого не показывали, но если зайти винбоксом в ip route, кликнуть + и раскрыть Routing Mark, то там кроме  main и действующих марок можно было выбрать name. И все просто — если новые правила всегда создавать, ненужные всегда удалять, но только НЕ редактировать одно в другое (особенно в Винбоксе), то таких «хвостов» не будет — проверено.

— Забыть о QuickSet. Совсем забыть.

— Девайс «искаропки» первым делом познакомить с Netintall, причем прошить отдельные пакеты, а не общий .npk (мне в большинстве случаев достаточно шести пакетов: advenced-tools, dhcp, ppp, security, system, wireless). При обновлениях прошивки не забывать обновлять загрузчик.

— При первом входе в систему после нетинсталл-чистки сразу сделать /system backup file=true-virgin.backup — всегда пригодится. Если есть готовый *.rsc, не копипастить его целиком в /, а последовательно по пунктам и с учетом зависимостей: назначить IP-адрес еще несуществующему bridge не получится. А после export compact порядок у настроек часто строго от балды.

— Ну и по мелочи: всегда явно указывать MAC для bridge, иначе он будет от первого поднявшегося интерфейса в мосте. Как такая ситуация: бридж это dhcp-клиент, dhcp-сервер выдает static-only аренды, порты бриджа — eoip1 и wlan1. EoIP поверх l2tp, wlan mode=ap-bridge, имеется только удаленный доступ. Неподалеку от ТД постоянно шляются смартфоны с верным паролем, а l2tp из-за неправильного MTU постоянно падает… Когда-то я чуть с ума не сошел пытаясь понять, почему вай-фай «все-все-как-в-родном-офисе-хотя-мы-в-гостях» то работает то нет.

Так же лучше будет в /ip route шлюзом по возможности назначать IP  а не интерфейс.

Еще раз — всё вышеописанное — ИМХО. Но я давно придерживаюсь этих правил и глюков в моих RoS-девайсах не замечал.

P.S. а вот если для OpenWRT/LEDE появится похожий на Winbox GUI….. 

Изменено 22 февраля, 2018 пользователем DAF

← Вернуться в раздел «В помощь системному администратору»

Страницы: 1

Предыдущая тема: Как узнать circuit id

Форум Ru-Board.club — поднят 15-09-2016 числа. Цель — сохранить наследие старого Ru-Board, истории становления российского интернета. Сделано для людей.