My network is running perfectly with all my devices on the 192.168.1.*.
Unfortuanately I now have 1 important device that cannot run on anu other IP then 192.168.2.254.
What would be the best way to do this ?
I have tried adding the address to the bridge setup: Add 192.168.2.250/24 / Network 192.168.2.0. This does not seem to work
I have tried creating a different bridge, and adding the eth8 port to it (That has the device attached). This does not seem to work.
Conceptually I know something about this stuff but have nother done this, I would appreciate some help.
If your current subnet is on ethernet1, just connect the “device” to ethernet2 and give it an address from 192.168.2.0/24 and make it a default gateway for the subnet
Conected subnets comunicates by default so the whole operation should take less then two minutes…
Thanks, that sounds a lot easier then I thought it would be…
What I did now:
I added eth8 to bridge-local (to make sure the port works at all)
I added 192.168.2.0/24 as address to bridge-local (I think this is needed also ?)
The device is using 192.168.2.254 so that should be good.
I think I am missing something with respect to your last sentence:
and make it a default gateway for the subnet
What do you mean here? I know what a default gateway is, is this something I need to setup in the router or do you mean on the device side ?
anav
February 14, 2023, 12:44pm
4
You dont even need a new bridge…
Whatever etherport you are using, lets say ether4
(1) Take it off the original bridge.
(2) Make the following entries:
/interface ethernet
set [ find default-name=ether4 ] name=FixedDevice-eth4
/ip address
add ip-address=192.168.2.1/24 interface=FixedDevice-eth4 network=192.168.2.0
/ip pool
name=fixed-pool addresses=192.168.2.2-192.168.2.254
/ip dhcp-server
address-pool=fixed-pool add interface=FixedDevice-eth4 lease-time=1d
/ip dhcp-server network
address=192.168.2.0/24 dns-server=192.168.2.1 gateway=192.168.2.1
(2) Go into dhcp leases and enter the mac address of your device and assign it to 192.168.2.254 ( set as static )
(3) Whatever firewall rules and interfaces list changes are required should be made if any.
Thanks, that sounds a lot easier then I thought it would be…
What I did now:
I added eth8 to bridge-local (to make sure the port works at all)
I added 192.168.2.0/24 as address to bridge-local (I think this is needed also ?)
The device is using 192.168.2.254 so that should be good.
I think I am missing something with respect to your last sentence:
and make it a default gateway for the subnet
What do you mean here? I know what a default gateway is, is this something I need to setup in the router or do you mean on the device side ?
the IP address that you will give to ethernet2 is 192.168.2.1/24 then it has to be default gateway for your “device” at 192.168.2.254
o.k.?
anything else - at the moment - will be overkill!
The device is not using dhcp (and I am not using dhcp server of mikrotik at all), does that mean all I need to do is:
(1) Take it off the original bridge (meaning: the device is no longer part of a bridge)
(2) Make the following entry
/ip address
add ip-address=192.168.2.1/24 interface=eth8 network=192.168.2.0
If thats it then something is not working yet, so I should look at:
(3) Whatever firewall rules and interfaces list changes are required should be made if any.
I have nothing in interface list, which means the issue would lie in the firewall rules… I do not think I am doing anyther particular here to block something..
anav
February 14, 2023, 1:08pm
7
Then it looks like all you need is the IP address assignment to the subnet =192.168.2.1/24 interface=FixedDevice-eth4 network=192.168.2.0 and it should work.
The device is not using dhcp (and I am not using dhcp server of mikrotik at all), does that mean all I need to do is:
(1) Take it off the original bridge (meaning: the device is no longer part of a bridge)
(2) Make the following entry
/ip address
add ip-address=192.168.2.1/24 interface=eth8 network=192.168.2.0
If thats it then something is not working yet, so I should look at:
(3) Whatever firewall rules and interfaces list changes are required should be made if any.
I have nothing in interface list, which means the issue would lie in the firewall rules… I do not think I am doing anyther particular here to block something..
as I said, give the IP address to the interface, connect your “device” and be sure that it has correctly set DG
I do not understand what you mean by “FixedDevice-eth4”. I do not see an option to create this…
What I did was:
/ip address
add ip-address=192.168.2.1/24 interface=eth8 network=192.168.2.0
Is that not correct ?
If it is… then there must be something in the firewall blocking something, because it is not working…
anav
February 14, 2023, 1:15pm
10
sorry satman you were bang on… i was focused on why second bridge…
@OP , you really dont have a clue about MT configurations do you.
All I did was change the default name of the etherport ( in the ethernet interface settings) so it would be clear the purpose of etherX to the reader and yourself down the line…
ex.
/interface ethernet
set [ find default-name=ether8 ] name=FixedDevice-eth8
Not required just a suggestion.
@OP we are not mind readers, regarding other possible config issues. You didnt provide the full config!~~
Actually I halfly wrote some lines in my previous message stating that that “fixed” device sounded like some kind of alias ? And why that was necessary… I removed it to avoid sounding disrespectfull..
But you are correct, this is my first try doing something like this… have done various stuff in mikrotik and have always found my way using forums and manual, bit at a loss here..
I basically did what was advised (And some other things) but it is not working, leading me to thinking there must be something in the firewall rules.. Cannot locate it though..
Thanks for the help on this, and any tips are appreciated !
anav
February 14, 2023, 1:20pm
12
yup
post your config here
/export file=anynameyouwish ( minus router serial number and any public WANIP information )
Actually I halfly wrote some lines in my previous message stating that that “fixed” device sounded like some kind of alias ? And why that was necessary… I removed it to avoid sounding disrespectfull..
But you are correct, this is my first try doing something like this… have done various stuff in mikrotik and have always found my way using forums and manual, bit at a loss here..
I basically did what was advised (And some other things) but it is not working, leading me to thinking there must be something in the firewall rules.. Cannot locate it though..
Thanks for the help on this, and any tips are appreciated !
“it does not work” means nothing !!!
Please do some diagnostic!!!
sit behind your “device” on 192.168.2.254 and try to ping 192.168.2.1… then try to ping 192.168.1.x (whatever is the router address on the first subnet)
then tray to ping something on 192.168.1.0 subnet
O.K.?
BUT FIRST - DISABLE ALL THE FIREWALL RULES so we can avoid fixing several problems instead of on…
btw, you are answering the wrong guy… I did not comment on your experience at all…
Satman: woud love to do some diagnostics, but the only thing I can do is see if I get a webpage back, unfortunately I cannot sit behind it and ping. I am not getting the page, hence my “it does not work”. Thanks for the tips though !
Anav: thanks for the help, config below !
feb/14/2023 14:54:41 by RouterOS 6.49.7
software id = 0B7Q-V6ZW
model = RB4011iGS+5HacQ2HnD
serial number = B8E00A9775F8
/interface bridge
add arp=proxy-arp igmp-snooping=yes name=bridge-local protocol-mode=none
add name=bridge-tel
/interface ethernet
set [ find default-name=ether1 ] arp=proxy-arp l2mtu=1598 loop-protect=off
set [ find default-name=ether2 ] l2mtu=1598
/interface vlan
add interface=ether1 name=vlan1.4 vlan-id=4
add interface=ether1 loop-protect=off name=vlan1.6 vlan-id=6
add interface=ether1 loop-protect=off mtu=1594 name=vlan1.7 vlan-id=7
add interface=ether1 name=vlan5 vlan-id=5
add interface=ether10 loop-protect=off name=vlan10.7 vlan-id=7
/interface pppoe-client
add add-default-route=yes allow=pap disabled=no interface=vlan1.6
keepalive-timeout=20 max-mru=1500 max-mtu=1500 name=pppoe-client
password= user=@internet
/interface ethernet switch port
set 0 default-vlan-id=0
set 1 default-vlan-id=0
set 2 default-vlan-id=0
set 3 default-vlan-id=0
set 4 default-vlan-id=0
set 5 default-vlan-id=0
set 6 default-vlan-id=0
set 7 default-vlan-id=0
set 8 default-vlan-id=0
set 9 default-vlan-id=0
set 10 default-vlan-id=0
set 11 default-vlan-id=0
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
add authentication-types=wpa2-psk eap-methods=“” management-protection=
allowed mode=dynamic-keys name=“WH-Power5 security” supplicant-identity=
“” wpa2-pre-shared-key=
add authentication-types=wpa2-psk eap-methods=“” management-protection=
allowed mode=dynamic-keys name=“Guest security” supplicant-identity=“”
wpa2-pre-shared-key=
/interface wireless
set [ find default-name=wlan2 ] antenna-gain=0 band=2ghz-b/g/n country=
no_country_set disabled=no frequency=auto frequency-mode=manual-txpower
guard-interval=long installation=indoor mode=ap-bridge name=WH-Extra
security-profile=“WH-Power5 security” ssid=WH-Extra station-roaming=
enabled wireless-protocol=802.11
set [ find default-name=wlan1 ] antenna-gain=0 band=5ghz-a/n country=
no_country_set frequency-mode=superchannel mode=ap-bridge name=WH-Game
security-profile=“WH-Power5 security” ssid=WH-Game station-roaming=
enabled wireless-protocol=802.11 wmm-support=enabled
add keepalive-frames=disabled mac-address=76:4D:28:5A:17:4E master-interface=
WH-Extra multicast-buffering=disabled name=Guest security-profile=
“Guest security” ssid=Guest station-roaming=enabled wds-cost-range=0
wds-default-cost=0 wps-mode=disabled
/ip dhcp-client option
add code=60 name=option60-vendorclass value=“‘IPTV_RG’”
/ip dhcp-server option
add code=60 name=option60-vendorclass value=“‘IPTV_RG’”
add code=28 name=option28-broadcast value=“‘192.168.1.255’”
/ip dhcp-server option sets
add name=IPTV options=option60-vendorclass,option28-broadcast
/ip pool
add name=thuisnetwerk ranges=192.168.1.1-192.168.1.249
add name=dhcp_pool2 ranges=172.16.0.2-172.16.0.254
add name=dhcp_pool3 ranges=172.16.0.2-172.16.0.254
/ip dhcp-server
add address-pool=thuisnetwerk interface=bridge-local lease-time=1h30m name=
dhcp-thuis
add address-pool=dhcp_pool3 interface=Guest name=dhcp1
/routing bgp instance
set default disabled=yes
/snmp community
set [ find default=yes ] read-access=no
add addresses=::/0 name=iWinbox-0B7Q-V6ZW
/user group
set full policy=“local,telnet,ssh,ftp,reboot,read,write,policy,test,winbox,pas
sword,web,sniff,sensitive,api,romon,dude,tikapp”
/interface bridge port
add bridge=bridge-local interface=ether2
add bridge=bridge-local interface=ether3
add bridge=bridge-local interface=ether4
add bridge=bridge-local interface=ether5
add bridge=bridge-tel interface=vlan1.7
add bridge=bridge-tel interface=vlan10.7
add bridge=bridge-local interface=WH-Extra
add interface=Guest
/ip neighbor discovery-settings
set discover-interface-list=!dynamic
/ip address
add address=192.168.1.250/24 interface=bridge-local network=192.168.1.0
add address=172.16.0.1/24 interface=Guest network=172.16.0.0
add address=192.168.2.1/24 interface=ether8 network=192.168.2.0
/ip dhcp-client
add default-route-distance=210 dhcp-options=
option60-vendorclass,hostname,clientid disabled=no interface=vlan1.4
use-peer-dns=no use-peer-ntp=no
/ip dhcp-server config
set store-leases-disk=15m
/ip dhcp-server lease
<REMOVED OLD ADDRESSES (NO LONGER USED, DHCP SERVER IS DISABLED>
/ip dhcp-server network
add address=172.16.0.0/24 dns-server=8.8.8.8,8.8.4.4 gateway=172.16.0.1
add address=192.168.1.0/24 dns-server=8.8.8.8,8.8.4.4 domain=thuis.local
gateway=192.168.1.250
/ip dns
set cache-max-ttl=1d servers=8.8.8.8,8.8.4.4
/ip firewall filter
add action=accept chain=input comment=iWinbox-SNMP dst-port=161 protocol=udp
add action=accept chain=input disabled=yes dst-port=51820 protocol=udp
add action=accept chain=input comment=iWinbox-SNMP connection-state=
established,new disabled=yes dst-port=51820 in-interface=pppoe-client
protocol=tcp
add action=drop chain=input in-interface=pppoe-client protocol=icmp
add action=accept chain=input connection-state=related
add action=accept chain=input connection-state=established
add action=drop chain=input in-interface=pppoe-client protocol=tcp
add action=drop chain=input in-interface=pppoe-client protocol=udp
add action=accept chain=input in-interface=pppoe-client protocol=icmp
add action=accept chain=input connection-state=related
add action=accept chain=input connection-state=established
add action=reject chain=input in-interface=pppoe-client protocol=tcp
reject-with=icmp-port-unreachable
add action=reject chain=input in-interface=pppoe-client protocol=udp
reject-with=icmp-port-unreachable
add action=drop chain=input comment=
“Block access to mikrotik from guest network” dst-address=192.168.1.250
dst-port=80 protocol=tcp src-address=172.16.0.0/24
add action=accept chain=input disabled=yes dst-port=51820 in-interface=
pppoe-client log=yes protocol=udp
/ip firewall nat
add action=masquerade chain=srcnat comment=
“Route network traffic to internet” out-interface=pppoe-client
src-address=192.168.0.0/16
add action=masquerade chain=srcnat comment=
“Route Guest network traffic to internet” out-interface=pppoe-client
src-address=172.16.0.0/24
add action=masquerade chain=srcnat comment=“Needed for IPTV” dst-address=
213.75.112.0/21 out-interface=vlan1.4
add action=masquerade chain=srcnat comment=“Needed for IPTV” dst-address=
217.166.0.0/16 out-interface=vlan1.4
add action=dst-nat chain=dstnat comment=
“Allow incoming chia traffic and send to chia server” dst-port=8444
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
8444
add action=dst-nat chain=dstnat comment=
“Allow incoming plex traffic and send to plex server” dst-port=32400
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
32400
add action=dst-nat chain=dstnat comment=
“Allow incoming plex traffic and send to miniplex server” dst-port=32401
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.45
to-ports=32400
add action=dst-nat chain=dstnat comment=
“Allow incoming hddcoin traffic and send to chia server” dst-port=28444
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
28444
add action=dst-nat chain=dstnat comment=
“Allow incoming silicoin traffic and send to chia server” dst-port=22222
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
22222
add action=dst-nat chain=dstnat comment=
“Allow incoming Stor traffic and send to chia server” dst-port=8668
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
8668
add action=dst-nat chain=dstnat comment=
“Allow incoming Staicoin traffic and send to chia server” dst-port=1999
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
1999
add action=dst-nat chain=dstnat comment=
“Allow incoming Shibgreen traffic and send to chia server” dst-port=7442
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
7442
add action=dst-nat chain=dstnat comment=
“Allow incoming Maize traffic and send to chia server” dst-port=8644
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
8644
add action=dst-nat chain=dstnat comment=
“Allow incoming Flora traffic and send to chia server” dst-port=18647
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
18647
add action=dst-nat chain=dstnat comment=
“Allow incoming CryptoDodge traffic and send to chia server” dst-port=
15994 in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5
to-ports=15994
add action=dst-nat chain=dstnat comment=
“Allow incoming BTCGreen traffic and send to chia server” dst-port=9282
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
9282
add action=dst-nat chain=dstnat comment=
“Allow incoming nchain traffic and send to chia server” dst-port=58445
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
58445
add action=dst-nat chain=dstnat comment=
“Allow incoming flora traffic and send to chia server” dst-port=18644
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
18644
add action=dst-nat chain=dstnat comment=
“Allow incoming flax traffic and send to chia server” dst-port=6888
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
6888
add action=dst-nat chain=dstnat comment=
“Allow incoming chives traffic and send to chia server” dst-port=9699
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
9699
add action=dst-nat chain=dstnat comment=
“Allow incoming cactus traffic and send to chia server” dst-port=11444
in-interface=pppoe-client protocol=tcp to-addresses=192.168.1.5 to-ports=
11444
add action=dst-nat chain=dstnat comment=“Allow incomming xbox traffic study”
dst-port=3074 in-interface=pppoe-client protocol=tcp to-addresses=
192.168.1.67 to-ports=3074
add action=dst-nat chain=dstnat comment=“Allow incomming xbox traffic study”
dst-port=3074 in-interface=pppoe-client protocol=udp to-addresses=
192.168.1.67 to-ports=3074
add action=dst-nat chain=dstnat comment=
“Allow incomming xbox traffic livingroom” dst-port=49222 in-interface=
pppoe-client protocol=tcp to-addresses=192.168.1.67 to-ports=49222
add action=dst-nat chain=dstnat comment=
“Allow incomming xbox traffic livingroom” dst-port=49222 in-interface=
pppoe-client protocol=udp to-addresses=192.168.1.67 to-ports=49222
add action=dst-nat chain=dstnat comment=
“Allow incoming wireguard traffic and send to MINI” dst-port=51820
in-interface=pppoe-client protocol=udp to-addresses=192.168.1.29
to-ports=51820
add action=dst-nat chain=dstnat comment=
“Allow incoming wireguard traffic and send to wireguard server” disabled=
yes dst-port=51900 in-interface=pppoe-client protocol=udp to-addresses=
192.168.1.37 to-ports=51900
add action=dst-nat chain=dstnat comment=
“Allow incoming wireguard traffic and send to wireguard server” disabled=
yes dst-port=51900 in-interface=pppoe-client protocol=tcp to-addresses=
192.168.1.37 to-ports=51900
/ip upnp
set show-dummy-rule=no
/ip upnp interfaces
add interface=bridge-local type=internal
add interface=pppoe-client type=external
/routing igmp-proxy
set quick-leave=yes
/routing igmp-proxy interface
add alternative-subnets=0.0.0.0/0 interface=vlan1.4 upstream=yes
add interface=vlan1.7
add interface=bridge-local
add
/snmp
set enabled=yes
/system clock
set time-zone-name=Europe/Amsterdam
/system leds
add interface=WH-Extra leds=“WH-Extra_signal1-led,WH-Extra_signal2-led,WH-Extr
a_signal3-led,WH-Extra_signal4-led,WH-Extra_signal5-led” type=
wireless-signal-strength
add interface=WH-Extra leds=WH-Extra_tx-led type=interface-transmit
add interface=WH-Extra leds=WH-Extra_rx-led type=interface-receive
/system scheduler
add interval=1d name=“Daily reboot” on-event=“system reboot” policy=
ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon
start-date=mar/06/2022 start-time=02:00:00
anav
February 14, 2023, 2:39pm
15
Very confusing…
DO you have quadruple play? —> internet/IPTV/VOIP/UNK OTHER
you have four vlans associated to ether1 ???
pppoe is related to vlan6
Your vlan 7 on ether1 is also on ether10 ??? ( telephone stuff?)
Dont get why two identical pools…
add name=dhcp_pool2 ranges=172.16.0.2-172.16.0.254
add name=dhcp_pool3 ranges=172.16.0.2-172.16.0.254
This interface on /interface bridge port settings has NO BRIDGE assignment
add interface=Guest
You have assigned vlans to Bridge-tel and not etherports or wlans, may be incorrect!!!
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Overall unable to help as the config is too complex for my understanding.
As to the device in question… lets look
/ip address
add address=192.168.1.250/24 interface=bridge-local network=192.168.1.0
add address=172.16.0.1/24 interface=Guest network=172.16.0.0
add address=192.168.2.1/24 interface=ether8 network=192.168.2.0 { good! }
The firewall rules are horrible, at least the input chain…convoluted messy and not in any particular order.
There are ZERO forward chain rules ???
This means there should be nothing blocking any traffic in any direction to or from the subnets to the WAN or LAN and very UNSAFE .
Also, your device is not noted in any sourcenat rules…
you may want to consider if applicable
add action=masquerade chain=srcnat comment=
“Fixed Device to internet” out-interface=pppoe-client
src-address=192.168.2.0/24
Actually I halfly wrote some lines in my previous message stating that that “fixed” device sounded like some kind of alias ? And why that was necessary… I removed it to avoid sounding disrespectfull..
But you are correct, this is my first try doing something like this… have done various stuff in mikrotik and have always found my way using forums and manual, bit at a loss here..
I basically did what was advised (And some other things) but it is not working, leading me to thinking there must be something in the firewall rules.. Cannot locate it though..
Thanks for the help on this, and any tips are appreciated !
“it does not work” means nothing !!!
Please do some diagnostic!!!
sit behind your “device” on 192.168.2.254 and try to ping 192.168.2.1… then try to ping 192.168.1.x (whatever is the router address on the first subnet)
then tray to ping something on 192.168.1.0 subnet
O.K.?
BUT FIRST - DISABLE ALL THE FIREWALL RULES so we can avoid fixing several problems instead of on…
btw, you are answering the wrong guy… I did not comment on your experience at all…
It would be mush easier if you set the context earlier and give us more details..
SO can you sit by something /anything on your 192.168.1.0/24 network and do all the pings??
Thanks for your time, I really appreciate it.
It is indeed television, internet and telephony, all working fine (the duplicate ip range however is indeed wrong)
Everything inside is open bit from the outside all is closed (fully stealth in tools like shields-up by GRC), so no worries there. Basically nothing from outside in is allowed but for a very few specific ports.
I will dive into the documentation again and try to work things out, not to good an experience but it has worked before and hey, I might learn something.
Thanks again !
Make sure you set 192.168.2.1 as the default gateway on the device. This will allow that device to know where to look to find all your other clients. Just like how all your other clients will look at the default gateway (the IP address of this Mikrotik) and will be able to see the 192.168.2.0 network and the rest of the internet.
Can you ping 192.168.2.1 from one of your clients?
In the firewall I am basically:
accepting port 161 (snmp)
dropping icmp from the wan side
allowing outside traffic from existing sessions
allowing outside raffic from related sessions
then dropping all other tcp and udp
The block was doubled though… Correct that that was not nice (second block was not doing anything, but thanks, I will clean that up..)
anav
February 14, 2023, 3:18pm
20
That explains 3 of the four vlans, what is the fourth one for ( VLAN4, VLAN5, VLAN6, VLAN7 )