And for the life of me, cant get this thing to ping upstream router nor lan client. and cant ping it from these other devices also…
Starting with /system reset-configuration no-defaults=yes skip-backup=yes
Tried dhcp client on wan first - upstream router seems to offer dhcp lease but complains it is not accepted:
default offering lease 192.168.77.252 for 00:0C:42:CF:67:F8 without success
Finally removed wan dhcp-client, used manual ip address for wan, 192.168.77.252.
I can see this device from upstream RB750GL, where it is present in ip neighbours. But I cannot ping it.
I can see its arp packets from lan client, when it attempts to ping same lan client - but no pings can be seen arriving at lan client
Perhaps these symptoms sound like some very common rookie mistake, that you have seen time and time again?
Lan client is connected at ether2, wan router on ether8.
Maybe something very obivious jumps at you:
[admin@RB1200] > export compact
# jan/02/1970 07:11:51 by RouterOS 7.1.3
# model = 1200
/interface bridge
add name=local
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip pool
add name=dhcp_pool0 ranges=192.168.88.2-192.168.88.254
/ip dhcp-server
add address-pool=dhcp_pool0 interface=local name=dhcp1
/port
set 0 name=serial0
set 1 name=serial1
/interface bridge port
add bridge=local interface=ether1
add bridge=local interface=ether2
add bridge=local interface=ether3
add bridge=local interface=ether4
add bridge=local interface=ether5
/ip address
add address=192.168.88.1/24 interface=local network=192.168.88.0
add address=192.168.77.252/24 interface=ether8 network=192.168.77.0
/ip dhcp-server network
add address=192.168.88.0/24 dns-server=8.8.8.8 gateway=192.168.88.1
/ip dns
set servers=8.8.8.8
/ip route
add gateway=192.168.77.1
/system identity
set name=RB1200
/system routerboard settings
set auto-upgrade=yes
Perhaps it’s missing or not properly configured masquerade or, if you are using the default rule, either remove out-interface=WAN or add ether8 to the WAN interface list
Am I missing something if I assume that even with complete lack of any firewall rules wan ip should be able to ping its upstream box and lan bridge ip should also be able to do same towards lan client?
I have some random small mikrotik hanging around here, with same kind of empty config and it can ping out and it can be pinged itself just fine. What makes RB1200 behavior different?
7.1.3 is what it came with. Only thing that I have been able to do so far, is to break in and reset its config. And then following said document… Only access so far has been serial port. Not exactly rushing to upgrade until these first things get solved.
Ah yes, actually had to solder 2 very-badly-soldered power input pins on pcb (https://imgur.com/a/XMBLkvr) before I managed to even see the (blue) light.
Default config was working exactly same amount. It sets ether1 to 88.1 and when I attach my lan client (with ip 88.50) to it, I cannot ping it. Neither can I ping lan client from router itself… So I tried with no config and that document titled “Default Router Configuration”.
Route might be incorrect… yet it is what that mikrotik document suggests. I assumed, it being so short, it relies on defaults? https://wiki.mikrotik.com/wiki/Manual:IP/Route – dst-address (IP prefix; Default: 0.0.0.0/0)
How it looks from here:
[admin@RB1200] > ip route print
Flags: D - DYNAMIC; A - ACTIVE; c, s, y - COPY
Columns: DST-ADDRESS, GATEWAY, DISTANCE
# DST-ADDRESS GATEWAY DISTANCE
0 As 0.0.0.0/0 192.168.77.1 1
DAc 192.168.77.0/24 ether8 0
DAc 192.168.88.0/24 local 0
I did try dhcp, few times. Like I said, it is not working. Upstream dhcp server makes an offer and…
* from that very same document example:
/ip dhcp-client add disabled=no interface=ether8
* at upstream router:
/ip dhcp-server lease print
20 D 192.168.77.252 00:0C:42:CF:67:F8 MikroTik default offered 1s
* later at upstream log:
default offering lease 192.168.77.252 for 00:0C:42:CF:67:F8 without success
After that I removed dhcp client and went with static ip address, route, dns.
How would I know what its default is? Thats what I get when I shall hold on to its reset and plug in a power.
Yes, will deal with forwarding and nat and even upgrading, as soon as I get my ‘first things’ solved… Those pings to and from it towards both sides. What a weird thing, this. At least it was not expensive. And came with free cap-lite. Which alone probably costs touch more than I paid for 1200.
Tried winbox too. This can access my 750 and 952 and that cap-lite, but no, not 1200… Havent tried netinstall yet. If I get no better ideas soon enough from my reading-list that I have gathered in few days, then I will give netinstall a try.
OK, can you export that config ? You should be able to use winbox to get in.
I think it may be possible it uses more a switch config instead of a router config.
Found it.
Default RB1200 has NO config, only fixed IP on ether1 and nothing else.
Definitely look at the linked article then.
It has a normal default config for a router explained line by line (which on itself shouldn’t be too hard if you have a bit of experience with RouterOS devices).
So, now I can ping in and out and whichever way; with exactly same config that I started with. Just moved wan side to ether9 and lan to ether10. Nice 10-port-device, with 2 working ports.
Remains to be seen, how linux netinstall-cli works when I will attempt to force routeros 6 to that thing.
Kinda disgusted from that discovery, though. 2 damn years should be plenty time to figure out some fix for such an issue, that many have seemingly reported to them, when they do have actually working example in existence - v6 ros, than can be then compared and debugged and whatever needed, fixed in new version. Not to mention all these cases from older times, where many have complained that these very same eth9 and 10 are the ones that may or may not work, depends on moon phase and wind direction…
