Jump to content

r13

Forum Members
 View Profile  See their activity

  • Posts

    5,227

  • Joined

  • Last visited

  • Days Won

    64

 Content Type 

Posts posted by r13

    Снять лимит ограничения пользователей.

    in Развитие

    Posted

    40 минут назад, milokc сказал:

    это я так понимаю с ветки експерементальных 2,09 прошивка? у меня с драфта 2,08 сейчас. и у меня есть галочка не пускать незнакомые хосты! но у меня проблема в том что количество "знакомых" уже перевалило за 64 я увалил пару юзеров старых, которые потеряли телефоны и т д. но их оказалось всего 2 и количество мест скоро тупо закончится и мне придется всем дать возможность качать в весь канал и тогда мне пипец т к меня все съедят с потрохами.

    2.09 перешла в статус беты уже. И команда только через cli, в вебе это не настраивается. 

    Снять лимит ограничения пользователей.

    in Развитие

    Posted

    7 минут назад, milokc сказал:

    у меня уже около 35 кампов в офисе + телефоны планшеты ноуты и т д. интернет 5 мегабит и поэтому у каждого юзера стоит ограничение по 1-2 мегабита. и стоит запрет на новых юзеров пока я их не пропишу. Вот достигло уже критической массы удаляю старых но их уже осталось не так много.

    Если основная цель ограничение скорости, то в 2.09 появилась команда ограничения для незарегистрированных пользователей:

    • ip traffic-shape unknown-host rate X

    Возможно в текущей ситуации как вариант. 

    Снять лимит ограничения пользователей.

    in Развитие

    Posted

    3 минуты назад, drugold сказал:

    Хмм, а речь не про DHCP разве?

    Я интерпритирую "пользователь" как учетку пользователя(с логином и паролем), а не как зарегистрированный хост. Ну может ТС уточнит каих именно пользователей не хватает. 

    Все о туннелях IPIP, GRE и EoIP

    in Обсуждение IPsec, OpenVPN и других туннелей

    Posted

    10 минут назад, Le ecureuil сказал:

    Чот слишком узкое применение и не окупает сложностей по разработке новой системы команд. Хотя подумаем, но ничего не обещаю.

    Это да, в принципе при такой схеме в текущей реализации у нас просто дольше будет уход на резерв из-за необходимости переподнять туннель.

    ЗЫ ну и в схеме когда на ISP не стоит галка использовать для выхода в интернет текущую реализацию туннеля в качестве резерва задействовать не удастся я полагаю?

    Все о туннелях IPIP, GRE и EoIP

    in Обсуждение IPsec, OpenVPN и других туннелей

    Posted

    51 минуту назад, Le ecureuil сказал:

    А зачем?

    например есть скажем Интернет через ISP сверху через него PPTP c галкой использовать для выхода в интернет

    Параллельно поднимаем авто туннель также с галкой использовать для выхода в интернет в режиме резеовирования

    И чтобы этот туннель не инкапсулировался в PPTP а шел через ISP или еще какое нибудь резервное соединение такая настройка была бы применима.

    Новый авто туннель не поднимается(no acceptable traffic selectors found)

    in Обсуждение IPsec, OpenVPN и других туннелей

    Posted

    Дано:

      Ultra2 - сервер с белым IP

      Giga2 - клиент за нат

    Создал автоматический IPIP туннель

    Со стороны сервера в логах все ок туннель поднялся: 

    IpSec::Configurator: crypto map "IPIP2" is up.

    А вот со стороны клиеннта следующая ошибка: 

    Jun 10 16:44:25ipsec
12[IKE] no acceptable traffic selectors found 
Jun 10 16:44:25ipsec
12[IKE] closing IKE_SA due CHILD_SA setup failure 
Jun 10 16:44:25ndm
IpSec::Configurator: error while establishing CHILD_SA crypto map "IPIP2" connection.

    И клиент уходит на реконнект

    селф с клиента далее.

    Через интерфейс не включается Band Steering

    in 2.09

    Posted

    25 минут назад, SigmaPlus сказал:

    Давно сказано, но сценарии при переходе с неофициальной беты на официальную при подготовке прошивки 2.08 и 2.09 для Ultra абсолютно разные. Да и посмотрите, в анонсе к официальной бета-версии упоминается Ultra. отсюда и вопрос.

    В официальном changelog ultra нет. И хватит на этом.

    Не отображаются подключения ipsec VPN

    in Обсуждение IPsec, OpenVPN и других туннелей

    Posted · Edited by r13

    В 23.05.2017 в 19:48, Le ecureuil сказал:

    В эту пятницу страница снова преобразится. У нас идут активные перемены, чтобы она стала как можно более удобной для всех. Счетчик пользователей однозначно вернем + может что-то еще будет.

    @Le ecureuil В обновленном системном мониторе по IPSec VirtualIP подключенные пользователи должны показываться или еще не допилили?

    Сейчас у меня VirtualIP показывается в секции IPSec VPN, а в секции пользователи сервера IPSec пусто.

     

    Ошибка: вдруг модем выдает ошибку в логах

    in 2.09

    Posted

    18 минут назад, edm сказал:

    так как в режиме дианостики не наблюдается ошибка, то селф-тест не получается.

    Поэтому скопировал доступные логи из веб-интерфейса

      Показать содержимое 
    

May 28 18:33:40ndmkernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3626: inode #666627: block 2622336: comm apache2: unable to read itable block
May 28 18:33:40ndmkernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4453: IO failure
May 28 18:33:40ndmkernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3626: inode #666627: block 2622336: comm apache2: unable to read itable block
May 28 18:33:40ndmkernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4453: IO failure
May 28 18:33:40ndmkernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3626: inode #666627: block 2622336: comm apache2: unable to read itable block
May 28 18:33:40ndmkernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4453: IO failure
May 28 18:33:40ndmkernel: EXT4-fs warning (device sda1): ext4_evict_inode:186: couldn't mark inode dirty (err -5)
May 28 18:33:40ndmkernel: EXT4-fs error (device sda1): ext4_wait_block_bitmap:410: comm apache2: Cannot read block bitmap - block_group = 10, block_bitmap = 966
May 28 18:33:40ndmkernel: EXT4-fs error (device sda1): ext4_discard_preallocations:3869: comm apache2: Error reading block bitmap for 10
May 28 18:33:40ndmkernel: usb 2-2: device descriptor read/64, error -71
May 28 18:33:40ndmkernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3626: inode #522357: block 2097191: comm apache2: unable to read itable block
May 28 18:33:40ndmkernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4453: IO failure
May 28 18:33:40ndmkernel: EXT4-fs warning (device sda1): ext4_evict_inode:186: couldn't mark inode dirty (err -5)
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3626: inode #522254: block 2097184: comm apache2: unable to read itable block
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1): ext4_find_entry:941: inode #525000: comm mysqld_safe: reading directory lblock 0
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1): ext4_find_entry:941: inode #659503: comm mysqld_safe: reading directory lblock 0
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1): ext4_find_entry:941: inode #522255: comm mysqld_safe: reading directory lblock 0
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1): ext4_find_entry:941: inode #522246: comm mysqld_safe: reading directory lblock 0
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1): ext4_find_entry:941: inode #524804: comm mysqld_safe: reading directory lblock 0
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4453: IO failure
May 28 18:33:41ndmkernel: EXT4-fs warning (device sda1): ext4_evict_inode:186: couldn't mark inode dirty (err -5)
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3626: inode #522250: block 2097184: comm apache2: unable to read itable block
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4453: IO failure
May 28 18:33:41ndmkernel: EXT4-fs warning (device sda1): ext4_evict_inode:186: couldn't mark inode dirty (err -5)
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3626: inode #666627: block 2622336: comm apache2: unable to read itable block
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4453: IO failure
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3626: inode #666627: block 2622336: comm apache2: unable to read itable block
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4453: IO failure
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:3626: inode #666627: block 2622336: comm apache2: unable to read itable block
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:4453: IO failure
May 28 18:33:41ndmkernel: usb 2-2: New USB device found, idVendor=12d1, idProduct=1001
May 28 18:33:41ndmkernel: usb 2-2: Product: HUAWEI Mobile
May 28 18:33:41ndmkernel: usb 2-2: Manufacturer: HUAWEI
May 28 18:33:41ndmkernel: Buffer I/O error on device sda1, logical block 33739
May 28 18:33:41ndmkernel: EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 666660 (offset 462848 size 4096 starting block 33739)
May 28 18:33:41ndmkernel: Buffer I/O error on device sda1, logical block 357169
May 28 18:33:41ndmkernel: EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 666627 (offset 51998720 size 4096 starting block 357169)
May 28 18:33:41ndmkernel: JBD2: Detected IO errors while flushing file data on sda1-8
May 28 18:33:41ndmkernel: Aborting journal on device sda1-8.
May 28 18:33:41ndmkernel: Buffer I/O error on device sda1, logical block 1606588
May 28 18:33:41ndmkernel: lost page write due to I/O error on sda1
May 28 18:33:41ndmkernel: JBD2: Error -5 detected when updating journal superblock for sda1-8.
May 28 18:33:41ndmkernel: scsi 2:0:0:0: Direct-Access     MXT-USB  Storage Device   1308 PQ: 0 ANSI: 0 CCS
May 28 18:33:41ndmkernel: sd 2:0:0:0: Attached scsi generic sg0 type 0
May 28 18:33:41ndmkernel: usbip-host 2-2:1.0: 2-2 is not in match_busid table... skip!
May 28 18:33:41ndmkernel: option 2-2:1.0: GSM modem (1-port) converter detected
May 28 18:33:41ndmkernel: EXT4-fs error (device sda1): ext4_put_super:855: Couldn't clean up the journal
May 28 18:33:41ndmkernel: EXT4-fs (sda1): Remounting filesystem read-only
May 28 18:33:41ndmkernel: usb 2-2: GSM modem (1-port) converter now attached to ttyUSB0
May 28 18:33:41ndmkernel: usbip-host 2-2:1.1: 2-2 is not in match_busid table... skip!
May 28 18:33:41ndmkernel: option 2-2:1.1: GSM modem (1-port) converter detected
May 28 18:33:41ndmkernel: sd 2:0:0:0: [sdb] 31291392 512-byte logical blocks: (16.0 GB/14.9 GiB)
May 28 18:33:41ndmkernel: usb 2-2: GSM modem (1-port) converter now attached to ttyUSB1
May 28 18:33:41ndmkernel: usbip-host 2-2:1.2: 2-2 is not in match_busid table... skip!
May 28 18:33:41ndmkernel: option 2-2:1.2: GSM modem (1-port) converter detected
May 28 18:33:41ndmkernel: usb 2-2: GSM modem (1-port) converter now attached to ttyUSB2
May 28 18:33:41ndmNetwork::Interface::Usb: interface "UsbModem0" is plugged (port 2).
May 28 18:33:41ndmkernel: sd 2:0:0:0: [sdb] Write Protect is off
May 28 18:33:41ndmkernel: sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
May 28 18:33:41ndmkernel: sd 2:0:0:0: [sdb] No Caching mode page found
May 28 18:33:41ndmkernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
May 28 18:33:41ndmkernel: sd 2:0:0:0: [sdb] No Caching mode page found
May 28 18:33:41ndmkernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
May 28 18:33:41ndmkernel:  sdb: sdb1
May 28 18:33:41ndmkernel: sd 2:0:0:0: [sdb] No Caching mode page found
May 28 18:33:41ndmkernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
May 28 18:33:41ndmkernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk
May 28 18:33:41ndmFileSystem::Ext: "/dev/sdb" has an unknown partition type, ignored.
May 28 18:33:41ndmFileSystem::Ext: ext4 "b2e285a0-e096-48f3-a225-d99237c22b6f:": filesystem initialized.
May 28 18:33:42ndmDns::Manager: proxy reload.
May 28 18:33:43ndmkernel: EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 525794
May 28 18:33:43ndmkernel: EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 525753
May 28 18:33:43ndmkernel: EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 524928
May 28 18:33:43ndmkernel: EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 524837
May 28 18:33:43ndmkernel: EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 523406
May 28 18:33:43ndmkernel: EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 522357
May 28 18:33:43ndmkernel: EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 522254
May 28 18:33:43ndmkernel: EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 522250
May 28 18:33:43ndmkernel: EXT4-fs (sdb1): 8 orphan inodes deleted
May 28 18:33:43ndmkernel: EXT4-fs (sdb1): recovery complete
May 28 18:33:43ndmkernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
May 28 18:33:43ndmkernel: EXT4-fs (sdb1): re-mounted. Opts: (null)
May 28 18:33:43ndmFileSystem::Repository: "b2e285a0-e096-48f3-a225-d99237c22b6f:" registered.
May 28 18:33:43ndmSwap::Manager: initializing swap area b2e285a0-e096-48f3-a225-d99237c22b6f::swapfile.
May 28 18:33:43ndmOpkg::Manager: /tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f mounted to /tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f.
May 28 18:33:43ndmOpkg::Manager: /tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f mounted to /opt/.
May 28 18:33:43ndmOpkg::Manager: /tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f initialized.
May 28 18:33:43ndmkernel: Adding 511996k swap on /tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f/:swapfile.  Priority:-1 extents:9 across:622592k 
May 28 18:33:43ndmSwap::Manager: enabled swap area b2e285a0-e096-48f3-a225-d99237c22b6f::swapfile.
May 28 18:33:44root 
May 28 18:33:44rootСтарт sshd с sftp на порту 2222
May 28 18:33:44ndmOpkg::Manager: /opt/etc/initrc: starting sshd...
May 28 18:33:44sshd[4322]Server listening on 0.0.0.0 port 2222.
May 28 18:33:44sshd[4322]Server listening on :: port 2222.
May 28 18:33:44rootСтарт bandwidthd - мониторинг юзер-трафика
May 28 18:33:44bandwidthdMonitoring subnet 255.0.0.0 with netmask 255.0.0.0
May 28 18:33:44bandwidthdMonitoring subnet 255.255.0.0 with netmask 255.255.0.0
May 28 18:33:44bandwidthdMonitoring subnet 255.240.0.0 with netmask 255.240.0.0
May 28 18:33:45bandwidthdOpening ra0
May 28 18:33:45root  
May 28 18:33:45root     
May 28 18:33:45bandwidthdPacket Encoding: Ethernet
May 28 18:33:45СообщениеСтарт Debian сервисы...
May 28 18:33:46rootс т а р т: ssh
May 28 18:33:47ndmOpkg::Manager: /opt/etc/initrc: Starting OpenBSD Secure Shell server: sshd.
May 28 18:33:47sshd[4350]Server listening on 0.0.0.0 port 22.
May 28 18:33:47sshd[4350]Server listening on :: port 22.
May 28 18:33:48rootс т а р т: #cron
May 28 18:33:48ndmOpkg::Manager: /opt/etc/initrc: chroot: can't execute '/etc/init.d/#cron': No such file or directory.
May 28 18:33:49rootс т а р т: #php5-fpm
May 28 18:33:49ndmOpkg::Manager: /opt/etc/initrc: chroot: can't execute '/etc/init.d/#php5-fpm': No such file or directory.
May 28 18:33:50rootс т а р т: apache2
May 28 18:33:51pppd[4352]pppd 2.4.4-4 started by root, uid 0
May 28 18:33:51ndmkernel: hub 2-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
May 28 18:33:51ndmkernel: usb 2-1: USB disconnect, device number 5
May 28 18:33:51ndmkernel: Aborting journal on device sdb1-8.
May 28 18:33:51ndmkernel: JBD2: Error -5 detected when updating journal superblock for sdb1-8.
May 28 18:33:51ndmkernel: journal commit I/O error
May 28 18:33:51ndmFileSystem::Repository: unregistering "b2e285a0-e096-48f3-a225-d99237c22b6f:" filesystem...
May 28 18:33:51ndmkernel: EXT4-fs error (device sdb1): ext4_find_entry:941: inode #261121: comm ndm: reading directory lblock 0
May 28 18:33:51ndmProcess: system failed [0xcffd09a3], "/opt/bin/sh" executable not found.
May 28 18:33:51ndmProcess: unable to create and initialize "Opkg shell" process.
May 28 18:33:51ndmIo::Process: "Opkg shell" is broken.
May 28 18:33:51ndmOpkg::Manager: process /opt/etc/initrc: failed to start.
May 28 18:33:51ndmkernel: EXT4-fs error (device sdb1): ext4_journal_start_sb:328: 
May 28 18:33:51ndmkernel: EXT4-fs error (device sdb1): ext4_find_entry:941: inode #2: comm sshd: reading directory lblock 0
May 28 18:33:51ndmkernel: Detected aborted journal
May 28 18:33:51ndmkernel: EXT4-fs (sdb1): Remounting filesystem read-only
May 28 18:33:51sshd[4322]Received signal 15; terminating.
May 28 18:33:51sshd[4350]Received signal 15; terminating.
May 28 18:33:52ndmkernel: EXT4-fs error (device sdb1): ext4_find_entry:941: inode #522255: comm sshd: reading directory lblock 0
May 28 18:33:52ndmOpkg::Manager: /opt/etc/initrc: Starting web server: apache2.
May 28 18:33:52ndmOpkg::Manager: /opt/etc/initrc: exit code -1.
May 28 18:33:52ndmkernel: EXT4-fs error (device sdb1): ext4_find_entry:941: inode #2: comm ndm: reading directory lblock 0
May 28 18:33:52ndmkernel: EXT4-fs error (device sdb1): ext4_find_entry:941: inode #391681: comm ndm: reading directory lblock 0
May 28 18:33:52ndmkernel: EXT4-fs error (device sdb1): ext4_find_entry:941: inode #2: comm ndm: reading directory lblock 0
May 28 18:33:52ndmkernel: EXT4-fs error (device sdb1): ext4_find_entry:941: inode #2: comm ndm: reading directory lblock 0
May 28 18:33:52ndmCore::Syslog: last message repeated 2 times.
May 28 18:33:52ndmOpkg::Manager: disk unmounted.
May 28 18:33:52ndmSwap::Manager: releasing swap area b2e285a0-e096-48f3-a225-d99237c22b6f::swapfile.
May 28 18:33:52ndmSwap::Manager: system failed [0xcffd0300], read-only filesystem.
May 28 18:33:52ndmSwap::Manager: unable to turn off swap area b2e285a0-e096-48f3-a225-d99237c22b6f::swapfile in an "unmount prepare" event handler.
May 28 18:33:52ndmFileSystem::Native: failed to unmount "/tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f": device or resource busy.
May 28 18:33:52ndmkernel: usb 2-1: new high-speed USB device number 8 using ehci-platform
May 28 18:33:52ndmkernel: option1 ttyUSB0: option_instat_callback: error -71
May 28 18:33:52ndmkernel: usb 2-1: New USB device found, idVendor=aaaa, idProduct=8816
May 28 18:33:52ndmkernel: usb 2-1: Product: MXT USB Device
May 28 18:33:52ndmkernel: usb 2-1: Manufacturer: MXTronics
May 28 18:33:52ndmkernel: usb 2-1: SerialNumber: 130818v01
May 28 18:33:52ndmkernel: scsi3 : usb-storage 2-1:1.0
May 28 18:33:52ndmkernel: hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
May 28 18:33:52ndmkernel: usb 2-2: USB disconnect, device number 7
May 28 18:33:52ndmkernel: option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
May 28 18:33:52ndmkernel: option 2-2:1.0: device disconnected
May 28 18:33:52ndmkernel: option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
May 28 18:33:52ndmkernel: option 2-2:1.1: device disconnected
May 28 18:33:52ndmkernel: option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
May 28 18:33:52ndmkernel: option 2-2:1.2: device disconnected
May 28 18:33:52ndmNetwork::Interface::Usb: interface "UsbModem0" is unplugged.
May 28 18:33:52chat[4374]Can't get terminal parameters: Input/output error
May 28 18:33:52pppd[4352]Initializer script failed
May 28 18:33:52ndmNetwork::Interface::IP: "UsbModem0": IP address cleared.
May 28 18:33:52ndmNetwork::Interface::UsbModem: device is not plugged.
May 28 18:33:52ndmNetwork::Interface::PPP: "UsbModem0": connection service standby.
May 28 18:33:52ndmNetwork::Interface::Base: "UsbModem0": interface is up.
May 28 18:33:52ndmkernel: usb 2-2: new high-speed USB device number 9 using ehci-platform
May 28 18:33:52ndmkernel: usb 2-2: New USB device found, idVendor=12d1, idProduct=1001
May 28 18:33:52ndmkernel: usb 2-2: Product: HUAWEI Mobile
May 28 18:33:52ndmkernel: usb 2-2: Manufacturer: HUAWEI
May 28 18:33:52ndmkernel: usbip-host 2-2:1.0: 2-2 is not in match_busid table... skip!
May 28 18:33:52ndmkernel: option 2-2:1.0: GSM modem (1-port) converter detected
May 28 18:33:53ndmkernel: usb 2-2: GSM modem (1-port) converter now attached to ttyUSB0
May 28 18:33:53ndmkernel: usbip-host 2-2:1.1: 2-2 is not in match_busid table... skip!
May 28 18:33:53ndmkernel: option 2-2:1.1: GSM modem (1-port) converter detected
May 28 18:33:53ndmkernel: usb 2-2: GSM modem (1-port) converter now attached to ttyUSB1
May 28 18:33:53ndmkernel: usbip-host 2-2:1.2: 2-2 is not in match_busid table... skip!
May 28 18:33:53ndmkernel: option 2-2:1.2: GSM modem (1-port) converter detected
May 28 18:33:53ndmkernel: usb 2-2: GSM modem (1-port) converter now attached to ttyUSB2
May 28 18:33:53ndmNetwork::Interface::Usb: interface "UsbModem0" is plugged (port 2).
May 28 18:33:53ndmFileSystem::Native: failed to unmount "/tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f": device or resource busy.
May 28 18:33:54ndmFileSystem::Native: failed to unmount "/tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f": device or resource busy.
May 28 18:33:54ndmkernel: hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
May 28 18:33:54ndmkernel: usb 2-2: USB disconnect, device number 9
May 28 18:33:54ndmkernel: option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
May 28 18:33:54ndmkernel: option 2-2:1.0: device disconnected
May 28 18:33:54ndmNetwork::Interface::Usb: interface "UsbModem0" is unplugged.
May 28 18:33:54ndmkernel: option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
May 28 18:33:54ndmkernel: option 2-2:1.1: device disconnected
May 28 18:33:54ndmkernel: option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
May 28 18:33:54ndmkernel: option 2-2:1.2: device disconnected
May 28 18:33:54ndmNetwork::Interface::IP: "UsbModem0": IP address cleared.
May 28 18:33:54ndmNetwork::Interface::UsbModem: device is not plugged.
May 28 18:33:54ndmNetwork::Interface::PPP: "UsbModem0": connection service standby.
May 28 18:33:54ndmkernel: usb 2-2: new high-speed USB device number 10 using ehci-platform
May 28 18:33:55ndmkernel: usb 2-2: New USB device found, idVendor=12d1, idProduct=1001
May 28 18:33:55ndmkernel: usb 2-2: Product: HUAWEI Mobile
May 28 18:33:55ndmkernel: usb 2-2: Manufacturer: HUAWEI
May 28 18:33:55ndmFileSystem::Native: failed to unmount "/tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f": device or resource busy.
May 28 18:33:55ndmkernel: usbip-host 2-2:1.0: 2-2 is not in match_busid table... skip!
May 28 18:33:55ndmkernel: option 2-2:1.0: GSM modem (1-port) converter detected
May 28 18:33:55ndmkernel: usb 2-2: GSM modem (1-port) converter now attached to ttyUSB0
May 28 18:33:55ndmkernel: usbip-host 2-2:1.1: 2-2 is not in match_busid table... skip!
May 28 18:33:55ndmkernel: option 2-2:1.1: GSM modem (1-port) converter detected
May 28 18:33:55ndmkernel: usb 2-2: GSM modem (1-port) converter now attached to ttyUSB1
May 28 18:33:55ndmkernel: usbip-host 2-2:1.2: 2-2 is not in match_busid table... skip!
May 28 18:33:55ndmkernel: option 2-2:1.2: GSM modem (1-port) converter detected
May 28 18:33:55ndmkernel: usb 2-2: GSM modem (1-port) converter now attached to ttyUSB2
May 28 18:33:55ndmkernel: scsi 3:0:0:0: Direct-Access     MXT-USB  Storage Device   1308 PQ: 0 ANSI: 0 CCS
May 28 18:33:55ndmkernel: sd 3:0:0:0: Attached scsi generic sg0 type 0
May 28 18:33:55ndmkernel: hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
May 28 18:33:55ndmkernel: usb 2-2: USB disconnect, device number 10
May 28 18:33:55ndmkernel: option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
May 28 18:33:55ndmkernel: option 2-2:1.0: device disconnected
May 28 18:33:55ndmkernel: option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
May 28 18:33:55ndmkernel: option 2-2:1.1: device disconnected
May 28 18:33:55ndmkernel: option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
May 28 18:33:55ndmkernel: option 2-2:1.2: device disconnected
May 28 18:33:55ndmkernel: usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd ndm rqt 128 rq 6 len 4 ret -143
May 28 18:33:55ndmUsb::Device: system failed [0xcffd00a2], cannot send after transport endpoint shutdown.
May 28 18:33:55ndmUsb::Device: invalid string descriptor.
May 28 18:33:55ndmUsb::Device: unable to read available language IDs.
May 28 18:33:55ndmNetwork::Interface::Usb: system failed [0xcffd0301], /proc/bus/usb/002/010 UsbModem0.
May 28 18:33:55ndmkernel: sd 3:0:0:0: [sda] 31291392 512-byte logical blocks: (16.0 GB/14.9 GiB)
May 28 18:33:55ndmkernel: sd 3:0:0:0: [sda] Write Protect is off
May 28 18:33:55ndmkernel: sd 3:0:0:0: [sda] Mode Sense: 03 00 00 00
May 28 18:33:55ndmkernel: sd 3:0:0:0: [sda] No Caching mode page found
May 28 18:33:55ndmkernel: sd 3:0:0:0: [sda] Assuming drive cache: write through
May 28 18:33:55ndmkernel: sd 3:0:0:0: [sda] No Caching mode page found
May 28 18:33:55ndmkernel: sd 3:0:0:0: [sda] Assuming drive cache: write through
May 28 18:33:55ndmkernel:  sda: sda1
May 28 18:33:55ndmkernel: sd 3:0:0:0: [sda] No Caching mode page found
May 28 18:33:55ndmkernel: sd 3:0:0:0: [sda] Assuming drive cache: write through
May 28 18:33:55ndmkernel: sd 3:0:0:0: [sda] Attached SCSI removable disk
May 28 18:33:55ndmkernel: usb 2-2: new high-speed USB device number 11 using ehci-platform
May 28 18:33:55ndmkernel: usb 2-2: New USB device found, idVendor=12d1, idProduct=1001
May 28 18:33:55ndmkernel: usb 2-2: Product: HUAWEI Mobile
May 28 18:33:55ndmkernel: usb 2-2: Manufacturer: HUAWEI
May 28 18:33:56ndmkernel: usbip-host 2-2:1.0: 2-2 is not in match_busid table... skip!
May 28 18:33:56ndmkernel: option 2-2:1.0: GSM modem (1-port) converter detected
May 28 18:33:56ndmkernel: usb 2-2: GSM modem (1-port) converter now attached to ttyUSB0
May 28 18:33:56ndmkernel: usbip-host 2-2:1.1: 2-2 is not in match_busid table... skip!
May 28 18:33:56ndmkernel: option 2-2:1.1: GSM modem (1-port) converter detected
May 28 18:33:56ndmkernel: usb 2-2: GSM modem (1-port) converter now attached to ttyUSB1
May 28 18:33:56ndmkernel: usbip-host 2-2:1.2: 2-2 is not in match_busid table... skip!
May 28 18:33:56ndmkernel: option 2-2:1.2: GSM modem (1-port) converter detected
May 28 18:33:56ndmkernel: usb 2-2: GSM modem (1-port) converter now attached to ttyUSB2
May 28 18:33:56ndmFileSystem::Native: failed to unmount "/tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f": device or resource busy.
May 28 18:33:56ndmUsb::Device: system failed [0xcffd029e], unable to open "/proc/bus/usb/002/010": operation timed out.
May 28 18:33:56ndmNetwork::Interface::Usb: system failed [0xcffd0301], /proc/bus/usb/002/010 UsbModem0.
May 28 18:33:57ndmFileSystem::Native: failed to unmount "/tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f": device or resource busy.
May 28 18:33:58ndmFileSystem::Native: failed to unmount "/tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f": device or resource busy.
May 28 18:33:58ndmUsb::Device: system failed [0xcffd029e], unable to open "/proc/bus/usb/002/010": operation timed out.
May 28 18:33:58ndmNetwork::Interface::Usb: system failed [0xcffd0301], /proc/bus/usb/002/010 UsbModem0.
May 28 18:33:58ndmNetwork::Interface::UsbModem: "UsbModem0": duplicate event for ttyUSB0.
May 28 18:33:58ndmNetwork::Interface::UsbModem: "UsbModem0": duplicate event for ttyUSB1.
May 28 18:33:58ndmNetwork::Interface::UsbModem: "UsbModem0": duplicate event for ttyUSB2.
May 28 18:33:59ndmFileSystem::Native: failed to unmount "/tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f": device or resource busy.
May 28 18:34:02ndmCore::Syslog: last message repeated 3 times.
May 28 18:34:02ndmFileSystem::Ext: failed to unmount.
May 28 18:34:02ndmFileSystem::Native: failed to unmount "/tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f": device or resource busy.
May 28 18:34:02ndmFileSystem::Directory: system failed [0xcffd00ed], unable to remove "/tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f": device or resource busy.
May 28 18:34:02ndmFileSystem::Repository: "b2e285a0-e096-48f3-a225-d99237c22b6f:" filesystem unregistered.
May 28 18:34:02ndmFileSystem::Ext: "/dev/sda" has an unknown partition type, ignored.
May 28 18:34:02ndmFileSystem::Ext: a filesystem with the same UUID (b2e285a0-e096-48f3-a225-d99237c22b6f) already mounted.
May 28 18:34:02ndmFileSystem::Repository: failed to create a new filesystem.
May 28 18:34:02ndmFileSystem::Directory: system failed [0xcffd00ed], unable to remove "/tmp/mnt/b2e285a0-e096-48f3-a225-d99237c22b6f": device or resource busy.
May 28 18:36:09ndmkernel: hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
May 28 18:36:09ndmkernel: usb 2-2: USB disconnect, device number 11
May 28 18:36:09ndmkernel: option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
May 28 18:36:09ndmkernel: option 2-2:1.0: device disconnected
May 28 18:36:09ndmkernel: option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
May 28 18:36:09ndmkernel: option 2-2:1.1: device disconnected
May 28 18:36:09ndmkernel: option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
May 28 18:36:09ndmkernel: option 2-2:1.2: device disconnected
May 28 18:36:09ndmkernel: usb 2-2: new high-speed USB device number 12 using ehci-platform
May 28 18:36:09ndmkernel: usb 2-2: device descriptor read/64, error -71
May 28 18:36:10ndmkernel: usb 2-2: device descriptor read/64, error -71
May 28 18:36:10ndmCore::Syslog: last message repeated 3 times.
May 28 18:36:10ndmkernel: usb 2-2: new high-speed USB device number 14 using ehci-platform
May 28 18:36:11ndmkernel: usb 2-2: device not accepting address 14, error -71
May 28 18:36:11ndmkernel: usb 2-2: new high-speed USB device number 15 using ehci-platform
May 28 18:36:11ndmkernel: usb 2-2: device not accepting address 15, error -71
May 28 18:36:11ndmkernel: hub 2-0:1.0: unable to enumerate USB device on port 2
May 28 18:36:12ndmkernel: usb 3-2: new full-speed USB device number 2 using ohci-platform
May 28 18:36:12ndmkernel: usb 3-2: not running at top speed; connect to a high speed hub
May 28 18:36:12ndmkernel: usb 3-2: New USB device found, idVendor=12d1, idProduct=1001
May 28 18:36:12ndmkernel: usb 3-2: Product: HUAWEI Mobile
May 28 18:36:12ndmkernel: usb 3-2: Manufacturer: HUAWEI
May 28 18:36:12ndmkernel: usbip-host 3-2:1.0: 3-2 is not in match_busid table... skip!
May 28 18:36:12ndmkernel: option 3-2:1.0: GSM modem (1-port) converter detected
May 28 18:36:12ndmkernel: usb 3-2: GSM modem (1-port) converter now attached to ttyUSB0
May 28 18:36:12ndmNetwork::Interface::UsbModem: "UsbModem0": duplicate event for ttyUSB0.
May 28 18:36:12ndmkernel: usbip-host 3-2:1.1: 3-2 is not in match_busid table... skip!
May 28 18:36:12ndmkernel: option 3-2:1.1: GSM modem (1-port) converter detected
May 28 18:36:12ndmkernel: usb 3-2: GSM modem (1-port) converter now attached to ttyUSB1
May 28 18:36:12ndmNetwork::Interface::UsbModem: "UsbModem0": duplicate event for ttyUSB1.
May 28 18:36:12ndmkernel: usbip-host 3-2:1.2: 3-2 is not in match_busid table... skip!
May 28 18:36:12ndmkernel: option 3-2:1.2: GSM modem (1-port) converter detected
May 28 18:36:12ndmkernel: usb 3-2: GSM modem (1-port) converter now attached to ttyUSB2
May 28 18:36:12ndmNetwork::Interface::UsbModem: "UsbModem0": duplicate event for ttyUSB2.

     

     

    Селфтест без режима диагностики есть на вкладке файлы. 

    Настройка IPsec для NDMS

    in Обсуждение IPsec, OpenVPN и других туннелей

    Posted · Edited by r13

    1 час назад, gaaronk сказал:

    А вот не кривые руки

     

    На вкладке /#security.ipsec есть только туннели и кнопка Add для нового туннеля. А опции VPN Server нет вообще

     

    Страничка выглядит так

     

    2017-05-27 10.24.44 am.png

    Сервер переехал в приложения

    ЗЫ и в системном мониторе теперь virtualip тоже показывается. 

    400 Bad Request в Transmission

    in 2.09

    Posted

    1 час назад, Cha-Cha сказал:

    Дада, но я думал,  что проблема в transmission сперва, а не облаке. Кстати, а как попадает трафик на локальный ip? Пинги идут на внешний адрес. 

    Нет, на локальный 78.47.125.180, он у всех кинетиков одинаковый.

    400 Bad Request в Transmission

    in 2.09

    Posted

    12 минуты назад, Cha-Cha сказал:

    Что самое интересное, доступ по keendns из интернета возвращает Bad Request.

    Но если заходить с устройства(ноутбук), подключенного к роутеру(тоже по внешнему имени) - то работает.

    Из локалки внешнее имя завернуто на локальный ip роутера. Так что результат не удивительный.

    Все о туннелях IPIP, GRE и EoIP

    in Обсуждение IPsec, OpenVPN и других туннелей

    Posted

    19 минут назад, dexter сказал:

    IPIP, который автоматом настроен, отлично работает. Проблема с туннелем EoIP, который в IPIP туннеле.

    Тогда точно подстраивать, для ручных автоматическая настройка не работает нужно ручками.

    ЗЫ а все на основе одного EoIP over ipsec не возможно реализовать? Зачем доп инкапсуляция?

    Все о туннелях IPIP, GRE и EoIP

    in Обсуждение IPsec, OpenVPN и других туннелей

    Posted

    1 час назад, dexter сказал:

    Не обратил внимания, в виндовой консоле написал и всё.

    Про MSS поподробнее можно?

    У вас эта проблема с IPIP over ipsec который автоматом настроен?

    По идее автоматический туннель сам выставляет mtu. Но раз не работает надо пробовать какого максимально размера пинги проходят и соразмерно корректировать mtu (interface IPIP0 ip mtu <число>)

×
×
  • Create New...