DLNA a MikroTik

Všetko o sieťach, nastaveniach, problémoch ...
Používateľov profilový obrázok
16cmfan
VIP
VIP
Príspevky: 3591
Dátum registrácie: Ne 12. Júl, 2009, 09:31
Bydlisko: Bardejov

DLNA a MikroTik

Príspevok od používateľa 16cmfan »

Ahojte,

mozete mi poradit - mam NAS, na nom DLNA server, nuz na klientovi DLNA server nevidim. UPnP mam zapnute...

Mam nainstalovane balicky IGMP a PIM, uz som to riesil aj podla navodu na youtube, nieco to podla logov robi...

Plus dufam, ze to nebude robit nejaky bordel smerom vonku ether1 pre mopjho ISP alebo ostatnych... alebo naopak, nejake bezpecnostne riziko/zahlcovanie smerom na MikroTik...

Kód: Vybrať všetko
















  MMM      MMM       KKK                          TTTTTTTTTTT      KKK
  MMMM    MMMM       KKK                          TTTTTTTTTTT      KKK
  MMM MMMM MMM  III  KKK  KKK  RRRRRR     OOOOOO      TTT     III  KKK  KKK
  MMM  MM  MMM  III  KKKKK     RRR  RRR  OOO  OOO     TTT     III  KKKKK
  MMM      MMM  III  KKK KKK   RRRRRR    OOO  OOO     TTT     III  KKK KKK
  MMM      MMM  III  KKK  KKK  RRR  RRR   OOOOOO      TTT     III  KKK  KKK

  MikroTik RouterOS 6.39 (c) 1999-2017       http://www.mikrotik.com/

[?]             Gives the list of available commands
command [?]     Gives help on the command and list of arguments

[Tab]           Completes the command/word. If the input is ambiguous,
                a second [Tab] gives possible options

/               Move up to base level
..              Move up one level
/command        Use command at the base level
[admin@Sestnastka_ROUTER] > log
[admin@Sestnastka_ROUTER] /log> print
may/02 17:45:50 system,info verified multicast-6.39-mipsbe.npk 
may/02 17:45:55 system,info verified user-manager-6.39-mipsbe.npk 
may/02 17:45:55 system,info installed user-manager-6.39 
may/02 17:45:55 system,info installed multicast-6.39 
may/02 17:45:55 system,info router rebooted 
may/02 17:46:01 interface,info ether1 link up (speed 100M, full duplex) 
may/02 17:46:01 interface,info ether2 link up (speed 100M, full duplex) 
may/02 17:46:01 interface,info ether5 link up (speed 100M, full duplex) 
may/02 17:46:01 dhcp,info dhcp-client on ether1 got IP address 10.251.0.10 
may/02 17:46:01 system,info item added 
may/02 17:46:01 system,info item added 
may/02 17:46:02 wireless,info C8:02:10:BE:2D:BF@2.4GHZ: connected 
may/02 17:46:03 wireless,info 84:98:66:E1:5B:65@2.4GHZ: connected 
may/02 17:46:03 dhcp,info DHCP_ether5 deassigned 192.168.5.10 from 00:08:9B:EF:08:C9 
may/02 17:46:03 dhcp,info DHCP_ether5 assigned 192.168.5.10 to 00:08:9B:EF:08:C9 
may/02 17:46:05 dhcp,info WIFI2.4 deassigned 192.168.24.91 from C8:02:10:BE:2D:BF 
may/02 17:46:05 dhcp,info WIFI2.4 assigned 192.168.24.91 to C8:02:10:BE:2D:BF 
may/02 17:46:21 system,info,account user admin logged in from 192.168.2.98 via winbox 
may/02 17:46:21 system,info,account user admin logged in from 192.168.2.98 via telnet 
may/02 17:46:47 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
may/02 17:47:13 system,info PIM interface added by admin 
may/02 17:47:13 pim,info Added new address to interface register: 127.0.0.2/8 
may/02 17:47:13 pim,info PIM interface started: register 
may/02 17:47:13 pim,info Added new address to interface ether1: 10.251.0.10/21 
may/02 17:47:13 pim,info PIM interface started: ether1 
may/02 17:47:13 pim,info Added new address to interface ether2: 192.168.2.1/24 
may/02 17:47:13 pim,info Added new address to interface ether2: 192.168.60.1/24 
may/02 17:47:13 pim,info PIM interface started: ether2 
may/02 17:47:13 pim,info IGMP interface started: ether2 
may/02 17:47:13 pim,info IGMP interface started: 2.4GHZ 
may/02 17:47:13 pim,info Added new address to interface 2.4GHZ: 192.168.24.1/24 
may/02 17:47:13 pim,info PIM interface started: 2.4GHZ 
may/02 17:47:13 pim,info Added new address to interface ether5: 192.168.5.1/24 
may/02 17:47:13 pim,info PIM interface started: ether5 
may/02 17:47:13 pim,info IGMP interface started: ether5 
may/02 17:47:13 pim,info IGMP interface started: ether1 
may/02 17:47:13 pim,warning JoinDesired(*,G) = true: RP for group 239.192.152.143: not found
 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.204 to 239.0.0.250 on
 vif ether1: source must be directly connected 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.204 to 239.255.255.25
0 on vif ether1: source must be directly connected 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.252.1.185 to 239.255.255.24
6 on vif ether1: source must be directly connected 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.252.2.20 to 224.0.1.60 on v
if ether1: source must be directly connected 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.213 to 239.255.255.25
1 on vif ether1: source must be directly connected 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.210 to 239.2.0.251 on
 vif ether1: source must be directly connected 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.209 to 239.2.0.252 on
 vif ether1: source must be directly connected 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 224.0.1.60 on 
vif ether1: source must be directly connected 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 239.2.0.252 on
 vif ether1: source must be directly connected 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.210 to 239.255.3.22 o
n vif ether1: source must be directly connected 
may/02 17:47:13 pim,warning JoinDesired(*,G) = true: RP for group 239.255.255.250: not found
 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 239.255.255.25
3 on vif ether1: source must be directly connected 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 239.255.17.18 
on vif ether1: source must be directly connected 
may/02 17:47:13 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 224.0.1.127 on
 vif ether1: source must be directly connected 
may/02 17:47:14 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.209 to 233.89.188.1 o
n vif ether1: source must be directly connected 
may/02 17:47:14 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.209 to 239.255.255.17
7 on vif ether1: source must be directly connected 
may/02 17:47:14 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 233.233.233.23
3 on vif ether1: source must be directly connected 
may/02 17:47:14 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 239.255.255.17
7 on vif ether1: source must be directly connected 
may/02 17:47:14 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.209 to 239.192.152.14
3 on vif ether1: source must be directly connected 
may/02 17:47:14 pim,warning JoinDesired(*,G) = true: RP for group 239.255.255.246: not found
 
may/02 17:47:15 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.252.1.8 to 239.255.255.238 
on vif ether1: source must be directly connected 
may/02 17:47:17 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.60 to 233.89.188.1 on
 vif ether1: source must be directly connected 
may/02 17:47:17 pim,warning JoinDesired(*,G) = true: RP for group 239.0.0.250: not found 
may/02 17:47:45 system,info sntp change time May/02/2017 17:47:21 => May/02/2017 17:47:45 
may/02 17:48:00 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.97 dst = 239
.255.255.250 len = 129: no RP address for this group 
may/02 17:48:00 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.97 dst = 239
.255.255.250 len = 122: no RP address for this group 
may/02 17:48:00 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.97 dst = 239
.255.255.250 len = 122: no RP address for this group 
may/02 17:48:00 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.97 dst = 239
.255.255.250 len = 129: no RP address for this group 
may/02 17:48:01 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.97 dst = 239
.255.255.250 len = 122: no RP address for this group 
may/02 17:48:01 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.97 dst = 239
.255.255.250 len = 129: no RP address for this group 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.206 to 239.255.255.25
0 on vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 239.0.0.250 on
 vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.210 to 239.2.0.251 on
 vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.213 to 239.255.255.25
1 on vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.206 to 239.2.0.252 on
 vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 239.255.255.24
6 on vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 224.0.1.60 on 
vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 239.255.255.25
3 on vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 239.255.17.18 
on vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.210 to 239.255.3.22 o
n vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 224.0.1.127 on
 vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.60 to 233.89.188.1 on
 vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 233.89.188.1 o
n vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 233.233.233.23
3 on vif ether1: source must be directly connected 
may/02 17:48:08 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.201 to 239.255.255.17
7 on vif ether1: source must be directly connected 
may/02 17:48:09 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.206 to 239.192.152.14
3 on vif ether1: source must be directly connected 
may/02 17:48:09 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.252.1.8 to 239.255.255.238 
on vif ether1: source must be directly connected 
may/02 17:48:18 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.91 dst = 239
.255.255.250 len = 297: no RP address for this group 
may/02 17:48:18 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.91 dst = 239
.255.255.250 len = 297: no RP address for this group 
may/02 17:48:23 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.2.98 dst = 239.
255.255.250 len = 165: no RP address for this group 
may/02 17:48:26 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.2.98 dst = 239.
255.255.250 len = 165: no RP address for this group 
may/02 17:48:29 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.2.98 dst = 239.
255.255.250 len = 165: no RP address for this group 
may/02 17:48:32 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.2.98 dst = 239.
255.255.250 len = 155: no RP address for this group 
may/02 17:48:32 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.2.98 dst = 239.
255.255.250 len = 155: no RP address for this group 
may/02 17:48:32 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.2.98 dst = 239.
255.255.250 len = 165: no RP address for this group 
may/02 17:48:35 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.2.98 dst = 239.
255.255.250 len = 165: no RP address for this group 
may/02 17:48:36 pim,warning JoinDesired(*,G) = true: RP for group 239.192.152.143: not found
 
may/02 17:48:37 pim,warning JoinDesired(*,G) = true: RP for group 239.255.255.250: not found
 
may/02 17:48:38 pim,warning JoinDesired(*,G) = true: RP for group 239.255.255.246: not found
 
may/02 17:48:38 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.2.98 dst = 239.
255.255.250 len = 165: no RP address for this group 
may/02 17:48:41 pim,warning JoinDesired(*,G) = true: RP for group 239.0.0.250: not found 
may/02 17:48:57 system,info IGMP proxy interface added by admin 
may/02 17:49:12 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.91 dst = 239
.255.255.250 len = 297: no RP address for this group 
may/02 17:49:12 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.91 dst = 239
.255.255.250 len = 297: no RP address for this group 
may/02 17:49:16 pim,warning JoinDesired(*,G) = true: RP for group 224.2.127.254: not found 
may/02 17:49:16 pim,warning JoinDesired(*,G) = true: RP for group 239.195.255.255: not found
 
may/02 17:49:16 pim,warning JoinDesired(*,G) = true: RP for group 239.255.255.255: not found
 
may/02 17:49:19 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.97 dst = 239
.255.255.250 len = 122: no RP address for this group 
may/02 17:49:19 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.97 dst = 239
.255.255.250 len = 129: no RP address for this group 
may/02 17:49:19 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.97 dst = 239
.255.255.250 len = 122: no RP address for this group 
may/02 17:49:19 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.97 dst = 239
.255.255.250 len = 129: no RP address for this group 
may/02 17:49:20 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.97 dst = 239
.255.255.250 len = 122: no RP address for this group 
may/02 17:49:20 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.97 dst = 239
.255.255.250 len = 129: no RP address for this group 
may/02 17:49:28 pim,warning JoinDesired(*,G) = false: RP for group 239.195.255.255: not foun
d 
may/02 17:49:28 pim,warning JoinDesired(*,G) = false: RP for group 224.2.127.254: not found 
may/02 17:49:28 pim,warning JoinDesired(*,G) = false: RP for group 239.255.255.255: not foun
d 
may/02 17:49:36 pim,warning JoinDesired(*,G) = true: RP for group 239.192.152.143: not found
 
may/02 17:49:37 pim,warning JoinDesired(*,G) = true: RP for group 239.255.255.250: not found
 
may/02 17:49:38 pim,warning JoinDesired(*,G) = true: RP for group 239.255.255.246: not found
 
may/02 17:49:41 pim,warning JoinDesired(*,G) = true: RP for group 239.0.0.250: not found 
may/02 17:49:49 pim,warning RX IGMP_V2_MEMBERSHIP_REPORT from 10.254.1.60 to 233.89.188.1 on
 vif ether1: source must be directly connected 
may/02 17:50:06 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.91 dst = 239
.255.255.250 len = 297: no RP address for this group 
may/02 17:50:06 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.24.91 dst = 239
.255.255.250 len = 297: no RP address for this group 
may/02 17:50:10 pim,info PIM interface stopped: ether1 
may/02 17:50:10 pim,info IGMP interface stopped: ether1 
may/02 17:50:10 pim,info PIM interface stopped: ether2 
may/02 17:50:10 pim,info PIM interface stopped: ether5 
may/02 17:50:10 pim,info IGMP interface stopped: ether5 
may/02 17:50:10 pim,info PIM interface stopped: 2.4GHZ 
may/02 17:50:10 pim,info IGMP interface stopped: 2.4GHZ 
may/02 17:50:10 pim,info IGMP interface stopped: ether2 
may/02 17:50:10 system,info PIM interface removed by admin 
may/02 17:50:10 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 10.251.0.
127 and group 239.255.255.250: not found 
may/02 17:50:10 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.2
.1 and group 239.255.255.250: not found 
may/02 17:50:10 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.2
.98 and group 239.255.255.250: not found 
may/02 17:50:10 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.5
.10 and group 239.255.255.250: not found 
may/02 17:50:10 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.2
4.1 and group 239.255.255.250: not found 
may/02 17:50:10 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.2
4.91 and group 239.255.255.250: not found 
may/02 17:50:10 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.2
4.94 and group 239.255.255.250: not found 
may/02 17:50:10 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.2
4.97 and group 239.255.255.250: not found 
may/02 17:50:10 pim,warning JoinDesired(*,G) = false: RP for group 239.0.0.250: not found 
may/02 17:50:10 pim,warning JoinDesired(*,G) = false: RP for group 239.192.152.143: not foun
d 
may/02 17:50:10 pim,warning JoinDesired(*,G) = false: RP for group 239.255.255.246: not foun
d 
may/02 17:50:10 pim,warning JoinDesired(*,G) = false: RP for group 239.255.255.250: not foun
d 
may/02 17:50:32 system,info DHCP server DHCP_ether5 changed by admin 
may/02 17:50:52 system,info DHCP server DHCP_ether5 changed by admin 
may/02 17:51:04 system,info IGMP proxy interface removed by admin 
may/02 17:51:05 igmp-proxy,info stopping IGMP proxy forwarding 
may/02 17:51:05 igmp-proxy,info stopping IGMP proxy forwarding 
may/02 17:51:05 igmp-proxy,info stopping IGMP proxy forwarding 
may/02 17:51:05 igmp-proxy,info stopping IGMP proxy forwarding 
may/02 17:53:42 system,info IGMP proxy interface added by admin 
may/02 17:54:09 system,info filter rule changed by admin 
may/02 17:54:21 system,info filter rule added by admin 
may/02 17:54:28 system,info filter rule changed by admin 
may/02 17:54:35 system,info filter rule added by admin 
may/02 17:54:43 system,info filter rule moved by admin 
may/02 17:54:43 system,info filter rule moved by admin 
may/02 17:57:32 system,info IGMP proxy interface changed by admin 
may/02 17:57:33 igmp-proxy,info stopping IGMP proxy forwarding 
may/02 17:59:59 system,info filter rule moved by admin 
may/02 18:00:21 system,info IGMP proxy interface removed by admin 
may/02 18:00:22 igmp-proxy,info stopping IGMP proxy forwarding 
may/02 18:00:47 system,info IGMP proxy interface added by admin 
may/02 18:01:26 system,info IGMP proxy interface removed by admin 
may/02 18:01:27 igmp-proxy,info stopping IGMP proxy forwarding 
may/02 18:01:27 igmp-proxy,info stopping IGMP proxy forwarding 
may/02 18:01:27 igmp-proxy,info stopping IGMP proxy forwarding 
may/02 18:01:27 igmp-proxy,info stopping IGMP proxy forwarding 
may/02 18:06:51 pim,info Added new address to interface ether5: 192.168.5.1/24 
may/02 18:06:51 pim,info PIM interface started: ether5 
may/02 18:06:51 pim,info IGMP interface started: ether5 
may/02 18:06:51 system,info PIM interface added by admin 
may/02 18:06:53 pim,warning JoinDesired(*,G) = true: RP for group 239.255.255.250: not found
 
may/02 18:06:59 pim,warning JoinDesired(*,G) = true: RP for group 239.192.152.143: not found
 
may/02 18:06:59 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.5.10 dst = 239.
255.255.250 len = 157: no RP address for this group 
may/02 18:06:59 system,info,account user admin logged out from 192.168.2.98 via telnet 
may/02 18:07:00 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.5.10 dst = 239.
255.255.250 len = 157: no RP address for this group 
may/02 18:07:00 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.5.10 dst = 239.
255.255.250 len = 154: no RP address for this group 
may/02 18:07:00 pim,warning RX WHOLEPKT signal: vif_index = 31 src = 192.168.5.10 dst = 239.
255.255.250 len = 154: no RP address for this group 
may/02 18:07:53 pim,warning JoinDesired(*,G) = true: RP for group 239.255.255.250: not found
 
may/02 18:07:59 pim,warning JoinDesired(*,G) = true: RP for group 239.192.152.143: not found
 
may/02 18:08:05 pim,info PIM interface stopped: ether5 
may/02 18:08:05 system,info PIM interface removed by admin 
may/02 18:08:05 pim,info IGMP interface stopped: ether5 
may/02 18:08:05 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.5
.1 and group 239.255.255.250: not found 
may/02 18:08:05 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.5
.10 and group 239.255.255.250: not found 
may/02 18:08:05 pim,warning JoinDesired(*,G) = false: RP for group 239.192.152.143: not foun
d 
may/02 18:08:05 pim,warning JoinDesired(*,G) = false: RP for group 239.255.255.250: not foun
d 
may/02 18:12:34 system,info,account user admin logged out from 192.168.2.98 via winbox 
may/02 18:12:39 interface,info ether2 link down 
may/02 18:21:25 dhcp,info DHCP_ether2 deassigned 192.168.2.98 from 60:A4:4C:56:B7:E4 
may/02 18:31:28 wireless,info 84:98:66:E1:5B:65@2.4GHZ: disconnected, group key exchange tim
eout 
may/02 18:39:50 dhcp,info WIFI2.4 deassigned 192.168.24.97 from 84:98:66:E1:5B:65 
may/02 18:39:50 wireless,info C8:02:10:BE:2D:BF@2.4GHZ: disconnected, extensive data loss 
may/02 18:39:57 wireless,info C8:02:10:BE:2D:BF@2.4GHZ: connected 
may/02 18:39:59 dhcp,info WIFI2.4 deassigned 192.168.24.91 from C8:02:10:BE:2D:BF 
may/02 18:39:59 dhcp,info WIFI2.4 assigned 192.168.24.91 to C8:02:10:BE:2D:BF 
may/02 21:51:07 wireless,info C8:02:10:BE:2D:BF@2.4GHZ: disconnected, extensive data loss 
may/02 22:00:00 dhcp,info WIFI2.4 deassigned 192.168.24.91 from C8:02:10:BE:2D:BF 
may/02 22:22:06 wireless,info 84:98:66:E1:5B:65@2.4GHZ: connected 
may/02 22:22:08 dhcp,info WIFI2.4 assigned 192.168.24.97 to 84:98:66:E1:5B:65 
may/02 22:42:10 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, received deauth: unspe
cified (1) 
may/02 22:47:16 dhcp,info WIFI2.4 deassigned 192.168.24.94 from 58:94:6B:14:93:6C 
05:51:35 interface,info ether2 link up (speed 100M, full duplex) 
05:51:39 dhcp,info DHCP_ether2 assigned 192.168.2.98 to 60:A4:4C:56:B7:E4 
06:25:02 wireless,info C8:02:10:BE:2D:BF@2.4GHZ: connected 
06:25:05 dhcp,info WIFI2.4 assigned 192.168.24.91 to C8:02:10:BE:2D:BF 
06:34:47 interface,info ether4 link up (speed 100M, full duplex) 
06:35:00 interface,info ether4 link down 
06:35:02 interface,info ether4 link up (speed 100M, full duplex) 
06:35:03 interface,info ether4 link down 
06:35:04 interface,info ether4 link up (speed 100M, full duplex) 
06:35:04 dhcp,info DHCP_ether4 assigned 192.168.4.10 to 00:13:86:5E:4D:80 
06:35:07 dhcp,info DHCP_ether4 deassigned 192.168.4.10 from 00:13:86:5E:4D:80 
06:35:07 dhcp,info DHCP_ether4 assigned 192.168.4.10 to 00:13:86:5E:4D:80 
07:04:14 wireless,info C8:02:10:BE:2D:BF@2.4GHZ: disconnected, extensive data loss 
07:10:06 dhcp,info WIFI2.4 deassigned 192.168.24.91 from C8:02:10:BE:2D:BF 
07:23:33 interface,info ether4 link down 
07:24:49 interface,info ether2 link down 
07:31:04 dhcp,info DHCP_ether4 deassigned 192.168.4.10 from 00:13:86:5E:4D:80 
07:31:16 wireless,info 84:98:66:E1:5B:65@2.4GHZ: disconnected, extensive data loss 
07:31:39 dhcp,info DHCP_ether2 deassigned 192.168.2.98 from 60:A4:4C:56:B7:E4 
07:31:57 wireless,info 84:98:66:E1:5B:65@2.4GHZ: connected 
07:32:43 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:32:43 dhcp,info WIFI2.4 assigned 192.168.24.94 to 58:94:6B:14:93:6C 
07:32:44 wireless,info 84:98:66:E1:5B:65@2.4GHZ: disconnected, extensive data loss 
07:32:45 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:32:45 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:32:45 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:32:45 dhcp,info WIFI2.4 deassigned 192.168.24.94 from 58:94:6B:14:93:6C 
07:32:45 dhcp,info WIFI2.4 assigned 192.168.24.94 to 58:94:6B:14:93:6C 
07:32:47 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:32:47 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:32:47 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:32:49 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:32:49 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:32:49 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:32:55 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:32:55 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:32:55 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:32:57 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:32:57 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:32:57 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:33:07 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:33:07 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:33:07 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:33:09 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:33:09 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:33:09 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:33:13 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:33:13 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:33:13 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:33:15 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:33:15 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:33:15 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:33:16 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:33:16 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:33:16 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:33:19 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:33:19 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:33:19 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:33:26 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:33:26 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:33:26 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:33:32 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:33:32 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:33:32 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:33:34 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:33:34 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:33:34 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:33:37 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:33:37 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:33:37 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:33:40 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:33:40 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:33:40 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:33:42 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:33:42 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:33:42 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:34:15 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:34:15 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:34:15 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:34:16 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:34:16 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:34:16 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:34:29 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:34:29 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:34:29 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:34:36 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:34:36 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:34:36 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:34:39 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:34:39 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:34:39 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:34:48 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:34:48 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:34:48 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:34:53 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:34:53 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:34:53 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:34:58 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:34:58 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:34:58 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:35:05 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:35:05 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:35:05 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:35:08 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:35:08 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:35:08 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:35:11 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:35:11 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:35:11 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:35:15 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:35:15 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:35:15 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:35:18 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:35:18 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:35:18 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:35:27 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:35:27 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:35:27 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:35:32 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:35:32 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:35:32 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:35:39 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:35:39 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:35:39 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:35:42 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:35:42 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:35:42 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:35:48 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:35:48 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:35:48 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:36:09 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:36:09 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:36:09 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:36:12 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:36:12 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:36:12 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:36:35 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:36:35 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:36:35 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:36:38 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:36:38 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:36:38 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:36:43 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:36:43 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:36:43 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:36:46 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:36:46 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:36:46 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:37:04 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:37:04 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:37:04 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:37:06 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:37:06 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:37:06 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
07:42:05 dhcp,info WIFI2.4 deassigned 192.168.24.97 from 84:98:66:E1:5B:65 
07:56:43 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
07:56:43 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
07:56:43 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
08:02:40 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
08:02:40 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
08:02:40 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
08:02:48 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
08:02:48 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
08:02:48 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
08:02:58 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
08:02:58 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
08:02:58 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
08:05:08 wireless,info 58:94:6B:14:93:6C@2.4GHZ: reassociating 
08:05:08 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, ok 
08:05:08 wireless,info 58:94:6B:14:93:6C@2.4GHZ: connected 
08:06:01 wireless,info 58:94:6B:14:93:6C@2.4GHZ: disconnected, received deauth: unspecified 
(1) 
08:15:08 dhcp,info WIFI2.4 deassigned 192.168.24.94 from 58:94:6B:14:93:6C 
08:35:35 system,info,account user admin logged in from 10.254.1.1 via winbox 
08:36:52 system,info,account user admin logged out from 10.254.1.1 via winbox 
08:40:26 system,info,account user admin logged in from 10.254.1.1 via winbox 
08:45:43 system,info,account user admin logged in from 10.254.1.1 via telnet 
08:46:38 system,info,account user admin logged out from 10.254.1.1 via telnet 
08:46:39 system,info,account user admin logged in from 10.254.1.1 via telnet 
08:47:21 system,info,account user admin logged out from 10.254.1.1 via telnet 
08:47:23 system,info,account user admin logged out from 10.254.1.1 via winbox 
08:48:05 system,info,account user admin logged in from 10.254.1.1 via winbox 
08:48:20 system,info,account user admin logged in from 10.254.1.1 via telnet 

[admin@Sestnastka_ROUTER] /log> 
Firewall:

Kód: Vybrať všetko

0 XI  chain=forward action=fasttrack-connection log=no log-prefix="" 

 1    chain=forward action=accept connection-state=established,related 
      connection-nat-state="" in-interface=ether1 log=no log-prefix="" 

 2    chain=forward action=accept connection-state=established,related log=no log-prefix=">

 3    ;;; Povol MULTICAST
      chain=input action=accept protocol=igmp log=no log-prefix="" 

 4    chain=input action=accept protocol=udp log=no log-prefix="" 

 5    chain=forward action=accept protocol=udp log=no log-prefix="" 

 6    ;;; Povol L2TP VPN protokol 51
      chain=input action=accept protocol=ipsec-ah log=no log-prefix="" 

 7    ;;; Povol L2TP VPN protokol 50
      chain=input action=accept protocol=ipsec-esp log=no log-prefix="" 

 8    ;;; Povol L2TP VPN port 1701
      chain=input action=accept protocol=udp dst-port=1701 log=no log-prefix="" 

 9    ;;; Povol L2TP VPN port 500
      chain=input action=accept protocol=udp dst-port=500 log=no log-prefix="" 

10    ;;; Povol L2TP VPN port 4500
      chain=input action=accept protocol=udp dst-port=4500 log=no log-prefix="" 

11    ;;; Pristup na QNAP TS-128
      chain=input action=accept protocol=tcp dst-address=192.168.5.10 dst-port=8080 
      log=no log-prefix="" 

12    ;;; PINGUJESE ZIJES!
      chain=input action=accept protocol=icmp log=no log-prefix="" 

13    chain=input action=accept connection-state=established 

14    chain=input action=accept connection-state=related 

15    ;;; VZDIALENY PRISTUP Z WINBOXu
      chain=input action=accept protocol=tcp dst-port=8291 log=no log-prefix="" 

16    ;;; Povol DNS navsteve cez TCP
      chain=input action=accept protocol=tcp src-address=192.168.60.0/24 dst-port=53 
      log=no log-prefix="" 

17    ;;; Povol DNS navsteve cez UDP
      chain=input action=accept protocol=udp src-address=192.168.60.0/24 dst-port=53 
      log=no log-prefix="" 

18    ;;; BLOKUJ VSETKY POZIADAVKY NA MOJE DNS Z VONKU (tcp)
      chain=input action=drop connection-state=new protocol=tcp in-interface=ether1 
      dst-port=53 log=no log-prefix="" 

19    ;;; BLOKUJ VSETKY POZIADAVKY NA MOJE DNS Z VONKU (udp)
      chain=input action=drop connection-state=new protocol=udp in-interface=ether1 
      dst-port=53 log=no log-prefix="" 

20    ;;; UKAZAT PROSTREDNICKEK PRI POKUSE O LOGIN NA MIKROTICEK
      chain=input action=drop src-address=192.168.60.0/24 log=no log-prefix="" 

21    ;;; SUKROMIE JE CENNE
      chain=forward action=reject reject-with=icmp-admin-prohibited 
      src-address=192.168.60.0/24 dst-address=192.168.2.0/24 log=no log-prefix="" 

22    chain=forward action=reject reject-with=icmp-admin-prohibited 
      src-address=192.168.60.0/24 dst-address=192.168.3.0/24 log=no log-prefix="" 

23    chain=forward action=reject reject-with=icmp-admin-prohibited 
      src-address=192.168.60.0/24 dst-address=192.168.4.0/24 log=no log-prefix="" 

24    chain=forward action=reject reject-with=icmp-admin-prohibited 
      src-address=192.168.60.0/24 dst-address=192.168.5.0/24 log=no log-prefix="" 

25    chain=forward action=reject reject-with=icmp-network-unreachable 
      src-address=192.168.60.0/24 dst-address=192.168.24.0/24 log=no log-prefix="" 

26    chain=forward action=reject reject-with=icmp-admin-prohibited 
      src-address=192.168.60.0/24 dst-address=192.168.50.0/24 log=no log-prefix="" 

27    ;;; defconf: drop invalid
      chain=forward action=drop connection-state=invalid log=no log-prefix="" 

28    ;;; defconf:  drop all from WAN not DSTNATed
      chain=forward action=drop connection-state=new connection-nat-state=!dstnat 
      in-interface=ether1 log=no log-prefix="" 

29    chain=input action=drop in-interface=ether1 log=no log-prefix=""
Dakujem za kazdu radu
Mobo Asus PRIME B450 Plus CPU Ryzen 7 5800X3D (Noctua NH-U12S + dual fan Noctua NF-A12) GPU MSI GeForce RTX 3070 Ventus 3X RAM G.Skill Ripjaws V F4-4000C18D-32GVK SSD Silicon Power P34A80 CASE Lancool 205 PSU Corsair RM550x case cooling: exhaust 2x Noctua F12, in-take 2x Lian Li 120mm

NB: Dell E7470 Skylake Core i5 + 8GB RAM + FHD IPS Foun: Oppo Reno 5Z
Main server: Asus PRIME A320M-K + Ryzen 5 2600 + GTX 1660Ti + 32GB Ram
NAS: QNAP TS-128 - 2TB Seagate Iron Wolf + MikroTik RB952
Peripherals: Dual monas setup 27" Samsung Odyssey G5 and AOC I2470Sw + Steelseries Apex 5 + Steelseries Rival 3 + QcK + Logitech G435
CageJ
Redaktor
Redaktor
Príspevky: 7967
Dátum registrácie: Ne 02. Jan, 2011, 01:43
Bydlisko: Presov

Re: DLNA a MikroTik

Príspevok od používateľa CageJ »

Aky NAS?
teoreticky je nutne nastavit porty...

Ak ti mam poradit, hod si PLEX.. s DLNA su len problemy.
Používateľov profilový obrázok
16cmfan
VIP
VIP
Príspevky: 3591
Dátum registrácie: Ne 12. Júl, 2009, 09:31
Bydlisko: Bardejov

Re: DLNA a MikroTik

Príspevok od používateľa 16cmfan »

Qnap TS-128... bezi mi to na porte 8200, ze som mal aj tento povolit ? Plex server mi uvidi android/smart TV popripade Cryptobox ?

V tomto som veru zaciatocnik..
Mobo Asus PRIME B450 Plus CPU Ryzen 7 5800X3D (Noctua NH-U12S + dual fan Noctua NF-A12) GPU MSI GeForce RTX 3070 Ventus 3X RAM G.Skill Ripjaws V F4-4000C18D-32GVK SSD Silicon Power P34A80 CASE Lancool 205 PSU Corsair RM550x case cooling: exhaust 2x Noctua F12, in-take 2x Lian Li 120mm

NB: Dell E7470 Skylake Core i5 + 8GB RAM + FHD IPS Foun: Oppo Reno 5Z
Main server: Asus PRIME A320M-K + Ryzen 5 2600 + GTX 1660Ti + 32GB Ram
NAS: QNAP TS-128 - 2TB Seagate Iron Wolf + MikroTik RB952
Peripherals: Dual monas setup 27" Samsung Odyssey G5 and AOC I2470Sw + Steelseries Apex 5 + Steelseries Rival 3 + QcK + Logitech G435
CageJ
Redaktor
Redaktor
Príspevky: 7967
Dátum registrácie: Ne 02. Jan, 2011, 01:43
Bydlisko: Presov

Re: DLNA a MikroTik

Príspevok od používateľa CageJ »

Pozri do obchodu ale na androidovu TV Plex bude ako appka.
Povoliť porty by som skúsil. Niekedy vraj pomáha zapnúť aj NAT..
keďže ja som DLNA nevedel zapnúť cez VPN tak som prešiel na Plex , podporuje ho napr aj PS3/4..
CageJ
Redaktor
Redaktor
Príspevky: 7967
Dátum registrácie: Ne 02. Jan, 2011, 01:43
Bydlisko: Presov

Re: DLNA a MikroTik

Príspevok od používateľa CageJ »

len dodam, ze mne islo o to aby mi DLNA fungoval aj vonku nielen lokalne.. a DLNA to akosi nevie... resp. niekomu sa to podari zapnut ale je to na dlhe lakte..
Používateľov profilový obrázok
16cmfan
VIP
VIP
Príspevky: 3591
Dátum registrácie: Ne 12. Júl, 2009, 09:31
Bydlisko: Bardejov

Re: DLNA a MikroTik

Príspevok od používateľa 16cmfan »

No toto je chalenge aj u mna uz len pri blbej SMB - pripajam sa cez L2TP/IPSEC no nedari sa mi to... skusam len mobil zatial.. neviem ako pri PPTP to uz nechcem pouzivat
Mobo Asus PRIME B450 Plus CPU Ryzen 7 5800X3D (Noctua NH-U12S + dual fan Noctua NF-A12) GPU MSI GeForce RTX 3070 Ventus 3X RAM G.Skill Ripjaws V F4-4000C18D-32GVK SSD Silicon Power P34A80 CASE Lancool 205 PSU Corsair RM550x case cooling: exhaust 2x Noctua F12, in-take 2x Lian Li 120mm

NB: Dell E7470 Skylake Core i5 + 8GB RAM + FHD IPS Foun: Oppo Reno 5Z
Main server: Asus PRIME A320M-K + Ryzen 5 2600 + GTX 1660Ti + 32GB Ram
NAS: QNAP TS-128 - 2TB Seagate Iron Wolf + MikroTik RB952
Peripherals: Dual monas setup 27" Samsung Odyssey G5 and AOC I2470Sw + Steelseries Apex 5 + Steelseries Rival 3 + QcK + Logitech G435
CageJ
Redaktor
Redaktor
Príspevky: 7967
Dátum registrácie: Ne 02. Jan, 2011, 01:43
Bydlisko: Presov

Re: DLNA a MikroTik

Príspevok od používateľa CageJ »

mne to ide len PPTP :)...
Tie nasky tie korporatne VPN nevedia dobre.. tusim potrebujes otvorit az 3 porty pre L2TP/IPSEC :)...

Pri VPN napr. nevidim vôbec sietovy disk cez PC :D.. cez Android som si ho vedel pripojit cez Total Commander.. nechapem.
Používateľov profilový obrázok
16cmfan
VIP
VIP
Príspevky: 3591
Dátum registrácie: Ne 12. Júl, 2009, 09:31
Bydlisko: Bardejov

Re: DLNA a MikroTik

Príspevok od používateľa 16cmfan »

Ako obsah si viem cez Qfile appku prezerat.. ale furt je to len sprosty maly telefon... Windows Desktop je proste ina kava
Mobo Asus PRIME B450 Plus CPU Ryzen 7 5800X3D (Noctua NH-U12S + dual fan Noctua NF-A12) GPU MSI GeForce RTX 3070 Ventus 3X RAM G.Skill Ripjaws V F4-4000C18D-32GVK SSD Silicon Power P34A80 CASE Lancool 205 PSU Corsair RM550x case cooling: exhaust 2x Noctua F12, in-take 2x Lian Li 120mm

NB: Dell E7470 Skylake Core i5 + 8GB RAM + FHD IPS Foun: Oppo Reno 5Z
Main server: Asus PRIME A320M-K + Ryzen 5 2600 + GTX 1660Ti + 32GB Ram
NAS: QNAP TS-128 - 2TB Seagate Iron Wolf + MikroTik RB952
Peripherals: Dual monas setup 27" Samsung Odyssey G5 and AOC I2470Sw + Steelseries Apex 5 + Steelseries Rival 3 + QcK + Logitech G435
CageJ
Redaktor
Redaktor
Príspevky: 7967
Dátum registrácie: Ne 02. Jan, 2011, 01:43
Bydlisko: Presov

Re: DLNA a MikroTik

Príspevok od používateľa CageJ »

vysvetli, nechapem...
Používateľov profilový obrázok
16cmfan
VIP
VIP
Príspevky: 3591
Dátum registrácie: Ne 12. Júl, 2009, 09:31
Bydlisko: Bardejov

Re: DLNA a MikroTik

Príspevok od používateľa 16cmfan »

Ze cez VPNko sa nedostanem na SAMBU ako ked sedim na lokalnej sieti...
Mobo Asus PRIME B450 Plus CPU Ryzen 7 5800X3D (Noctua NH-U12S + dual fan Noctua NF-A12) GPU MSI GeForce RTX 3070 Ventus 3X RAM G.Skill Ripjaws V F4-4000C18D-32GVK SSD Silicon Power P34A80 CASE Lancool 205 PSU Corsair RM550x case cooling: exhaust 2x Noctua F12, in-take 2x Lian Li 120mm

NB: Dell E7470 Skylake Core i5 + 8GB RAM + FHD IPS Foun: Oppo Reno 5Z
Main server: Asus PRIME A320M-K + Ryzen 5 2600 + GTX 1660Ti + 32GB Ram
NAS: QNAP TS-128 - 2TB Seagate Iron Wolf + MikroTik RB952
Peripherals: Dual monas setup 27" Samsung Odyssey G5 and AOC I2470Sw + Steelseries Apex 5 + Steelseries Rival 3 + QcK + Logitech G435
mp3turbo
Pokročilý používateľ
Pokročilý používateľ
Príspevky: 12258
Dátum registrácie: St 27. Apr, 2011, 11:16
Bydlisko: ta Blava, ňe ?

Re: DLNA a MikroTik

Príspevok od používateľa mp3turbo »

hladaj chybu vo firewall pravidlach... s DLNA neviem poradit, neviem ako funguje, nemam skusenost a ani priestor teraz na spekulovanie/studium, sorry
Som matematik... Vzrusuju ma cisla, napriklad 8300 na otackomeri alebo 2,15 baru z kompresora a este aj 1-12-5-8-3-10-6-7-2-11-4-9.
Používateľov profilový obrázok
16cmfan
VIP
VIP
Príspevky: 3591
Dátum registrácie: Ne 12. Júl, 2009, 09:31
Bydlisko: Bardejov

Re: DLNA a MikroTik

Príspevok od používateľa 16cmfan »

Chalenge accepted!
Mobo Asus PRIME B450 Plus CPU Ryzen 7 5800X3D (Noctua NH-U12S + dual fan Noctua NF-A12) GPU MSI GeForce RTX 3070 Ventus 3X RAM G.Skill Ripjaws V F4-4000C18D-32GVK SSD Silicon Power P34A80 CASE Lancool 205 PSU Corsair RM550x case cooling: exhaust 2x Noctua F12, in-take 2x Lian Li 120mm

NB: Dell E7470 Skylake Core i5 + 8GB RAM + FHD IPS Foun: Oppo Reno 5Z
Main server: Asus PRIME A320M-K + Ryzen 5 2600 + GTX 1660Ti + 32GB Ram
NAS: QNAP TS-128 - 2TB Seagate Iron Wolf + MikroTik RB952
Peripherals: Dual monas setup 27" Samsung Odyssey G5 and AOC I2470Sw + Steelseries Apex 5 + Steelseries Rival 3 + QcK + Logitech G435
Používateľov profilový obrázok
Snake
VIP
VIP
Príspevky: 13677
Dátum registrácie: Ne 23. Júl, 2006, 02:00
Bydlisko: Bratislava/Galanta

Re: DLNA a MikroTik

Príspevok od používateľa Snake »

DLNA a SMB nemusi fungovat ak sa jedna o traversal, resp ho treba povolit a danemu tunelu zapnut NAT, kedze berem Mikrotiky ako bordel zariadenia a nedal by osm ich ani na WC tak neviem poradit ako, cez Cisco mi to ale vzdy normalne islo.

PS: pouzivat PPTP v dnesnej dobe je dufam iba vtip, to uz by mali odstranit zo sluzieb aby to nejaky dilino nezapinal.





.
CageJ
Redaktor
Redaktor
Príspevky: 7967
Dátum registrácie: Ne 02. Jan, 2011, 01:43
Bydlisko: Presov

Re: DLNA a MikroTik

Príspevok od používateľa CageJ »

Yep Snake, akurát, ze na niektorých routrov NAT snad ani je v nastaveniach... Tusim, ze to ten shit Huawei na FTTH od Orange nevie.
Používateľov profilový obrázok
16cmfan
VIP
VIP
Príspevky: 3591
Dátum registrácie: Ne 12. Júl, 2009, 09:31
Bydlisko: Bardejov

Re: DLNA a MikroTik

Príspevok od používateľa 16cmfan »

Snake napísal:DLNA a SMB nemusi fungovat ak sa jedna o traversal, resp ho treba povolit a danemu tunelu zapnut NAT, kedze berem Mikrotiky ako bordel zariadenia a nedal by osm ich ani na WC tak neviem poradit ako, cez Cisco mi to ale vzdy normalne islo.

PS: pouzivat PPTP v dnesnej dobe je dufam iba vtip, to uz by mali odstranit zo sluzieb aby to nejaky dilino nezapinal.
Si sa tu vyhejtoval.. :D argumentuj alebo lepsie. Porad nz
Mobo Asus PRIME B450 Plus CPU Ryzen 7 5800X3D (Noctua NH-U12S + dual fan Noctua NF-A12) GPU MSI GeForce RTX 3070 Ventus 3X RAM G.Skill Ripjaws V F4-4000C18D-32GVK SSD Silicon Power P34A80 CASE Lancool 205 PSU Corsair RM550x case cooling: exhaust 2x Noctua F12, in-take 2x Lian Li 120mm

NB: Dell E7470 Skylake Core i5 + 8GB RAM + FHD IPS Foun: Oppo Reno 5Z
Main server: Asus PRIME A320M-K + Ryzen 5 2600 + GTX 1660Ti + 32GB Ram
NAS: QNAP TS-128 - 2TB Seagate Iron Wolf + MikroTik RB952
Peripherals: Dual monas setup 27" Samsung Odyssey G5 and AOC I2470Sw + Steelseries Apex 5 + Steelseries Rival 3 + QcK + Logitech G435

Návrat na "Siete"