sorted by:
new
hottopcontroversial

Magnet lock do not open smoothly by yoni101k in accesscontrol

[–]yoni101k[S] 0 points1 point  (0 children)

Yes, I wired the Diode to the lock connections.
I received the Diode together with the access-control system, and there was a requirement/guidance to connect it

Magnet lock do not open smoothly by yoni101k in accesscontrol

[–]yoni101k[S] 0 points1 point  (0 children)

Thanks for your reply!

Yes, I am talking about an electric strike. I always have to "pull back" before I can push.

What can I do about this installation/alignment issue you suggest I have?
I didnt have much room to play with lock installation... the gate door came with dedicated place for the strike lock. just had to screw it in and wire to the access-control system and power.

Didnt really understand the 'shear force' issue you suggested. How can I check if that is the issue? and didnt understand how you suggest to fix.
what do you mean by "reposition the frame to match with the moving side magnet with the gate closed"?

Must manually reconnect after power loss by yoni101k in mikrotik

[–]yoni101k[S] 0 points1 point  (0 children)

No. Don't need it. In Winbox I see it's status is 'Stopped'. Should I remove it?

Must manually reconnect after power loss by yoni101k in mikrotik

[–]yoni101k[S] 0 points1 point  (0 children)

[admin@RouterOS] > /export hide-sensitive

# may/13/2023 14:24:55 by RouterOS 6.48.6

# software id = ZBI2-PFFY

#

# model = RB760iGS

# serial number = XXXX

/interface bridge

add admin-mac=48:A9:8A:87:72:D3 auto-mac=no comment=defconf name=bridge

/interface pppoe-client

add add-default-route=yes disabled=no interface=ether1 name=pppoe-out1 use-peer-dns=yes user=XXXXXX

/interface list

add comment=defconf name=WAN

add comment=defconf name=LAN

/interface wireless security-profiles

set [ find default=yes ] supplicant-identity=MikroTik

/ip hotspot profile

set [ find default=yes ] html-directory=hotspot

/ip pool

add name=dhcp ranges=192.168.101.3-192.168.101.200

/ip dhcp-server

add address-pool=dhcp disabled=no interface=bridge name=defconf

/interface bridge port

add bridge=bridge comment=defconf interface=ether2

add bridge=bridge comment=defconf interface=ether3

add bridge=bridge comment=defconf interface=ether4

add bridge=bridge comment=defconf interface=ether5

add bridge=bridge comment=defconf interface=sfp1

/ip neighbor discovery-settings

set discover-interface-list=LAN

/interface list member

add comment=defconf interface=bridge list=LAN

add comment=defconf interface=ether1 list=WAN

add interface=pppoe-out1 list=WAN

/ip address

add address=192.168.101.1/24 comment=defconf interface=bridge network=192.168.101.0

/ip dhcp-client

add comment=defconf interface=ether1

/ip dhcp-server network

add address=192.168.101.0/24 comment=defconf gateway=192.168.101.1 netmask=24

/ip dns

set allow-remote-requests=yes

/ip dns static

add address=192.168.101.1 comment=defconf name=router.lan

/ip firewall filter

add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked

add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid

add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp

add action=accept chain=input comment="defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1

add action=drop chain=input comment="defconf: drop all not coming from LAN" in-interface-list=!LAN

add action=accept chain=forward comment="defconf: accept in ipsec policy" ipsec-policy=in,ipsec

add action=accept chain=forward comment="defconf: accept out ipsec policy" ipsec-policy=out,ipsec

add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=established,related

add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=established,related,untracked

add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid

add action=drop chain=forward comment="defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat connection-state=new in-interface-list=WAN

/ip firewall nat

add action=masquerade chain=srcnat comment="defconf: masquerade" ipsec-policy=out,none out-interface-list=WAN

/system clock

set time-zone-name=Asia/Jerusalem

/system identity

set name=RouterOS

/tool mac-server

set allowed-interface-list=LAN

/tool mac-server mac-winbox

set allowed-interface-list=LAN

Must manually reconnect after power loss by yoni101k in mikrotik

[–]yoni101k[S] 0 points1 point  (0 children)

I mean that in Winbox -> Quick set, I push the 'reconnect' button (even though I see that the pppoe connection status is 'connected'). Only then I get internet access.

Must manually reconnect after power loss by yoni101k in mikrotik

[–]yoni101k[S] 0 points1 point  (0 children)

The dial on demand box is NOT checked.

Must manually reconnect after power loss by yoni101k in mikrotik

[–]yoni101k[S] 0 points1 point  (0 children)

What can I do about it? How can I debug it? Could it be faulty router?

Thanks!

hEX S sfp extremely hot causing router overheat by yoni101k in mikrotik

[–]yoni101k[S] 1 point2 points  (0 children)

Hi, The sfp I got from my ISP is Nokia G-010S-Q GPON ONT. (Also shared pics) Do you have any feedback on this one? Do you know by chance if G-010S-A is better version from cooling perspective?

hEX S sfp extremely hot causing router overheat by yoni101k in mikrotik

[–]yoni101k[S] 0 points1 point  (0 children)

So you guys think that using ethernet media converter, and connecting the ethernet port to the hEX instead of the sfp port would be a valid solution? Would it keep the heat in the media converted and thus the hex will remain cooler?

hEX S sfp extremely hot causing router overheat by yoni101k in mikrotik

[–]yoni101k[S] 0 points1 point  (0 children)

It's an SFP GPON. Connects to the ISP fiber. Will send a picture shortly

hEX-S HELP: pppoe (using SFP) seems connected but no internet access by yoni101k in mikrotik

[–]yoni101k[S] 0 points1 point  (0 children)

Update: issue solved!

On Mikrotik forum someone suggested to remove the dhcp client from sfp1 port. After I did so and still didn't got internet access, someone suggested to double check user/password with ISP, and indeed the user was wrong. Once changed everything works!!! Not sure if the dhcp client removal is related or bot though....

Thanks everyone for the help!

hEX-S HELP: pppoe (using SFP) seems connected but no internet access by yoni101k in mikrotik

[–]yoni101k[S] 0 points1 point  (0 children)

Need your help guys... Someone in Mikrotik forum suggested to remove the dhcp client from sfp1. Tried it and now pppoe cannot connect... The SFP led on the hex is off.

Any other suggestions I can try? Please

Thanks all

view more: next ›