????????????????????? can't follow, don't understand your desciption.
1: what is server1? What MAC is this here ? (alarm, ethernet hAP, which ethernet, bridged? )
2. ether2 down. Because set down/up by command? Or just happens ? Cable disconnect/connect ?
3. deassigned ? It was not assigned. Or has DHCP server given up the offering?
4. assigned. Now it succeeded? Or not ?
Client side
1. Network failure or no traffic because no IP address ?
2. DHCP failed.? It failed in point 2 and/or 3 above. Related failure?
Check:
- is IP address for DHCP lease used already?
- Does alarm have same static IP address already set?
- When as test static IP given to alarm, can you then communicate ?
- Are there other DHCP servers in the network?
- using a wifi repeater or extender between hAP and alarm ?
- what is bridged together? Ether2 on bridge ? What else?
I was actually a bit too general.
1) the "server1" is the dhcp server that offers a static ip to the "MAC" interface of the alarm
2) ethernet2 to which this alarm interface is physically connected has no physical cable problems. Probably, but this is only a guess, the interface of the alarm not having some kind of response from the router, carries out a disabling and a re-enabling of its own interface. Up & Down is not caused by the router in short
3/4) from the attached mikrotik log, I see that at a certain point the IP assigned by DHCP is deassigned, I don't understand why. Sometimes after deassignment the dhcp server reassigns it, other times not by displaying the : without success
for controls:
- the IP address is not already assigned to other devices. In addition, the dhcp dynamically has a range pool from 100 to 199. 200 is part of the static addresses
- the alarm has a dynamic IP ethernet interface configuration. The router through its MAC address (and it is always the same) assigns it the IP address I defined in 200
- when the interface is up, I can communicate until the connection drops, therefore a communication in periods of time that are not very defined and clear
- there are no other DHCP servers in the network, it's at the home level with about ten clients
- the connection between the alarm and hap ac2 is physical, with a few meters long ethernet cable patch, and is physically perfect (already tried and tested also with other cables). There are no repeaters between them
- on the bridge there are all the ethernet interfaces plus the wlan ones (ether1 is the WAN, all the other LANs, public INTERFACE and IP configuration)
Isn't it just for the ether2 interface (alarm) that I have to configure a particular dhcp lease? Anyway, thanks for the help and replies
/interface bridge
add admin-mac=18:FD:*** auto-mac=no name=bridge1
/interface ethernet
set [ find default-name=ether1 ]
set [ find default-name=ether2 ]
set [ find default-name=ether3 ]
set [ find default-name=ether4 ]
set [ find default-name=ether5 ]
/interface list
add name=WAN
add name=LAN
/interface wireless security-profiles
***
/interface wireless
***
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=wlan5
add bridge=bridge1 interface=wlan2
/interface list member
add interface=ether1 list=WAN
add interface=ether2 list=LAN
add interface=ether3 list=LAN
add interface=ether4 list=LAN
add interface=ether5 list=LAN
add interface=wlan5 list=LAN
add interface=wlan2 list=LAN
add interface=bridge1 list=LAN
/interface wireless access-list
***
/ip pool
add name=pool1 ranges=192.168.88.100-192.168.88.199
/ip dhcp-server
add address-pool=pool1 disabled=no interface=bridge1 lease-time=1h name=server1
/ip dhcp-server lease
***
add address=192.168.88.200 mac-address=00:03:*** server=server1
***
/ip dhcp-server network
add address=192.168.88.0/24 dns-server=192.168.88.1 gateway=192.168.88.1 netmask=24
/ip dns
set allow-remote-requests=yes servers=192.168.88.254
/ip neighbor discovery-settings
set discover-interface-list=all
/ip route
add distance=1 gateway=192.168.88.254
You do not have the required permissions to view the files attached to this post.