Oh, the lr8 lets you connect via lan nearly out of the box. the only thing to do is add a firewall rule for ether1 to port 80, and voila, it works. the device gets a ip address and i can connect to webfig and it connects to the internet and to the lora-server.It is not found in the manual but you find a few resources online. But i dont know what are the settings in the background.
The other way is to connect over wifi but without internet access. the lr8 creates a open wifi network an you can connect and login to webfig.
But for changing configurations i normally login with winbox over lan.
So i have to establish a UDP connection to my lorawan-network-server in a data center.
But the actual gateway is somewhere in a house on the countryside. In the house they have some unknown router with wifi functionality and i have to connect the lr8 in their home-network to get internet access.
So i need to connect to the lr8 via winbox over lan select the wifi ssid and put in the password so that it connects to the wifi.
The default of the lr8 is the opposite, you first connect over wifi, change the settings there and deploy the device over lan.
this is the actual config file from the device in question. it is connected via lan cable in my office
The other way is to connect over wifi but without internet access. the lr8 creates a open wifi network an you can connect and login to webfig.
But for changing configurations i normally login with winbox over lan.
I think so, if you want to make a comparison, its more like a bluetooth iot device that sends data to a bluetooth gateway that translates into internet protocols.it is not exactly routing it is UDP packet forwarding
So i have to establish a UDP connection to my lorawan-network-server in a data center.
But the actual gateway is somewhere in a house on the countryside. In the house they have some unknown router with wifi functionality and i have to connect the lr8 in their home-network to get internet access.
So i need to connect to the lr8 via winbox over lan select the wifi ssid and put in the password so that it connects to the wifi.
The default of the lr8 is the opposite, you first connect over wifi, change the settings there and deploy the device over lan.
this is the actual config file from the device in question. it is connected via lan cable in my office
Code:
# feb/23/2024 06:42:52 by RouterOS 6.49.13# software id = blabla## model = RBwAPR-2nD# serial number = blabla/interface wirelessset [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-XX \ disabled=no distance=indoors frequency=auto installation=outdoor mode=\ ap-bridge ssid=MikroTik-0BF10E wireless-protocol=802.11/interface listadd comment=defconf name=WANadd comment=defconf name=LAN/interface wireless security-profilesset [ find default=yes ] supplicant-identity=MikroTik/ip pooladd name=default-dhcp ranges=192.168.88.10-192.168.88.254/ip dhcp-serveradd address-pool=default-dhcp disabled=no interface=wlan1 name=defconf/lora serversadd address=eu.mikrotik.blabla down-port=1700 name=blabla \ up-port=1700/ip neighbor discovery-settingsset discover-interface-list=LAN/interface list memberadd comment=defconf interface=wlan1 list=LANadd comment=defconf interface=ether1 list=WAN/ip addressadd address=192.168.88.1/24 comment=defconf interface=wlan1 network=\ 192.168.88.0/ip dhcp-clientadd comment=defconf disabled=no interface=ether1/ip dhcp-server networkadd address=192.168.88.0/24 comment=defconf dns-server=192.168.88.1 gateway=\ 192.168.88.1/ip dnsset allow-remote-requests=yes/ip dns staticadd address=192.168.88.1 comment=defconf name=router.lan/ip firewall filteradd action=accept chain=input comment="ether1 tcp allow" dst-port=80 \ in-interface=ether1 protocol=tcpadd action=accept chain=input comment=\ "defconf: accept established,related,untracked" connection-state=\ established,related,untrackedadd action=drop chain=input comment="defconf: drop invalid" connection-state=\ invalidadd action=accept chain=input comment="defconf: accept ICMP" protocol=icmpadd action=accept chain=input comment=\ "defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1add action=drop chain=input comment="defconf: drop all not coming from LAN" \ in-interface-list=!LANadd action=accept chain=forward comment="defconf: accept in ipsec policy" \ ipsec-policy=in,ipsecadd action=accept chain=forward comment="defconf: accept out ipsec policy" \ ipsec-policy=out,ipsecadd action=fasttrack-connection chain=forward comment="defconf: fasttrack" \ connection-state=established,relatedadd action=accept chain=forward comment=\ "defconf: accept established,related, untracked" connection-state=\ established,related,untrackedadd action=drop chain=forward comment="defconf: drop invalid" \ connection-state=invalidadd 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 natadd action=masquerade chain=srcnat comment="defconf: masquerade" \ ipsec-policy=out,none out-interface-list=WAN/loraset 0 antenna=uFL/system clockset time-zone-name=Europe/Rome/tool mac-serverset allowed-interface-list=LAN/tool mac-server mac-winboxset allowed-interface-list=LANStatistics: Posted by orangehead — Fri Feb 23, 2024 11:31 am