Just loaded the demo i386 version of r3.0rc5. Everything seems OK, allocated IP address to ether1 and can Winbox to it, but any attempt to create a 0.0.0.0/0 gateway in Winbox ip route fails while using /ip route in terminal just times out.

An attempt to use /ip route add gateway=ether1 triggered a message to sent a supout.rif to Mikrotik support.

Before doing so I thought I'd check to see if this is:-

a, a bug already ironed out, or
b, a deliberate ploy in the demo licence to prevent it being of any use.

(Interestingly the 'Manual' link in Winbox connects to http://www.mikrotik.com even though I can't ping off my own network!)

Even more interestingly I've just installed the demo version I had of 2.9.35 for i386 on the same machine and found that /ip route set up the network gateway as soon as I allocated the ip address to ether1, so adding the gateway for 0.0.0.0/0 was easy. In this regard 3.0rc5 seems retrograde.

Unless, of course, this is all some sort of new undocumented Mikritok feature only available to those with bottomless pockets - or with the pockets of customers available to them to plunder - and who can afford to attend MUMs in all sorts of exotic and expensive places!

Even more interestingly I've just installed the demo version I had of 2.9.35 for i386 on the same machine and found that /ip route set up the network gateway as soon as I allocated the ip address to ether1, so adding the gateway for 0.0.0.0/0 was easy. In this regard 3.0rc5 seems retrograde.

I had issues with one of the RC's entering in the default route on an x86 platform as well, I think it was rc4, but it could have been rc5, i don't remember, an upgrade to the latest build fixed it.

Unless, of course, this is all some sort of new undocumented Mikritok feature only available to those with bottomless pockets - or with the pockets of customers available to them to plunder - and who can afford to attend MUMs in all sorts of exotic and expensive places!

I have been to both of the USA MUM's, and I never got the feeling they were trying to plunder my pockets, rather the opposite... I felt they were trying to offer a truly benificial event, and treated us as if they honestly valued our business as customers. I felt the event was put together as a thank you for our business, and I suggest everyone attend the events as they have been incredibly usefull for learning from peers using mikrotik products in both similar, and completly different ways.

I have been to both of the USA MUM's, and I never got the feeling they were trying to plunder my pockets, rather the opposite... I felt they were trying to offer a truly benificial event, and treated us as if they honestly valued our business as customers. I felt the event was put together as a thank you for our business, and I suggest everyone attend the events as they have been incredibly usefull for learning from peers using mikrotik products in both similar, and completly different ways.

I don't doubt their usefulness, but who paid for you to go?

I'm in New Zealand trying to run a tiny wireless network (a dozen users) for my remote, rural community on a purely voluntary basis as our only way of getting a half-way decent internet connection. Who is going to pay my way to a MUM in Egypt, or the USA or South Africa?

Yet attending MUMs (or 2nd-hand and serendipitously through this forum) seems to be the only way to find out about Mikrotik's (many) undocumented features(*), or even find out the real grist on many of their 'documented' ones. If Mikrotik's documentation was even half as good as its hardware and its software it would be head-and-shoulders above any competition (IMHO).

(*Like what is CALEA? And what does 'blink', which I saw on the 3.0rc5 root help list, actually do?)

But to return to the thread, I'd like to try an upgrade but I'm using the demo licence and upgrade doesn't seem to work. Is that deliberate, ie do I have to download the full 3.0rc6 i386 iso?

Is that deliberate, ie do I have to download the full 3.0rc6 i386 iso?

Well I did it anyway and the bug or bar is still there.

I cannot set any gateways in 3.0rc6 i386 running on an AMD-K6, viz:-

[admin@MikroTik] /ip route> print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC G GATEWAY DISTANCE INTERFACE

[admin@MikroTik] /ip route> /ip address print
Flags: X - disabled, I - invalid, D - dynamic
# ADDRESS NETWORK BROADCAST INTERFACE
0 10.3.2.104/24 10.3.2.0 10.3.2.255 ether1

[admin@MikroTik] /ip route> add dst-address=0.0.0.0/0 gateway=10.3.2.104
[admin@MikroTik] /ip route> add dst-address=0.0.0.0/0 gateway=10.3.2.104
action timed out - try again, if error continues contact MikroTik support and se
nd a supout file (13)
[admin@MikroTik] /ip route>

Is this a bug - a pretty dramatic one for a router - or a deliberate bar in the demo version?

I had no such problem with a 2.9.46 iso running on the same machine.

I loaded the iso, opened a Winbox to it by MAC address, set the Ether1 IP address and then tried to set the gateway. Nothing.

Anyone.

Tried using > setup instead, having noticed it for the first time while browsing idly through the various menus to see what is actually there in v3.

....
x - exit menu
your choice [press Enter to setup default gateway]: g
gateway: 10.3.2.1
#Adding default route
/ip route add dst-address=0.0.0.0/0 gateway=10.3.2.1 comment="added by setup"
+ a - add ip address
* g - setup default gateway
x - exit menu
your choice [press Enter to setup default gateway]: g
gateway: 10.3.2.1
#Adding default route
/ip route add dst-address=0.0.0.0/0 gateway=10.3.2.1 comment="added by setup"
+ a - add ip address
* g - setup default gateway
x - exit menu
your choice [press Enter to setup default gateway]: x
r - reset all router configuration
+ l - load interface driver
* a - configure ip address and gateway
d - setup dhcp client
s - setup dhcp server
p - setup pppoe client
t - setup pptp client
x - exit menu
your choice [press Enter to configure ip address and gateway]: x

[Safe Mode released]

Setup completed successfully.
Following commands were executed during this setup:
#Adding default route
/ip route add dst-address=0.0.0.0/0 gateway=10.3.2.1 comment="added by setup"
#Adding default route
/ip route add dst-address=0.0.0.0/0 gateway=10.3.2.1 comment="added by setup"
[admin@MikroTik] > ip route print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC G GATEWAY DISTANCE INTERFACE
[admin@MikroTik] > ping 10.3.2.1
10.3.2.1 64 byte ping: ttl=64 time=4 ms
10.3.2.1 64 byte ping: ttl=64 time=1 ms
10.3.2.1 64 byte ping: ttl=64 time=1 ms
10.3.2.1 64 byte ping: ttl=64 time=2 ms
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1/2.0/4 ms

[admin@MikroTik] > ping 10.0.3.1
no route to host
no route to host
no route to host
no route to host
no route to host
no route to host
no route to host
7 packets transmitted, 0 packets received, 100% packet loss
[admin@MikroTik] >

Impressed? Not half.

the only bar with demo license is 24 hour uptime limit, so, this is not a bar.

but i cannot recreate problem, i can set up default gateway with no prolbems
tested using rc6 on x86 RB500 and RB300

the only bar with demo license is 24 hour uptime limit, so, this is not a bar.

but i cannot recreate problem, i can set up default gateway with no prolbems

Code: Select all

/ip route add gateway=<gw address>

tested using rc6 on x86 RB500 and RB300

This is what I get, on a headless Presario 1200-XL103 with an AMD - K6-2 processor which I want to deploy as a remote User-Manager/RADIUS server for my system:

***************************************

MikroTik RouterOS 3.0rc6 (c) 1999-2007 http://www.mikrotik.com/


UPGRADE NOW FOR FULL SUPPORT
----------------------------
FULL SUPPORT benefits:
- receive technical support
- one year feature support
- one year online upgrades
(avoid re-installation and re-configuring your router)
To upgrade, register your license "software ID"
on our account server http://www.mikrotik.com

Current installation "software ID": W2FR-SJT

Please press "Enter" to continue!

Terminal vt102 detected, using multiline input mode

[admin@MikroTik] > ip address print
Flags: X - disabled, I - invalid, D - dynamic
# ADDRESS NETWORK BROADCAST INTERFACE
0 10.3.2.104/24 10.3.2.0 10.3.2.255 ether1

[admin@MikroTik] > ip route print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC G GATEWAY DISTANCE INTERFACE

[admin@MikroTik] > ping 10.3.2.1
10.3.2.1 64 byte ping: ttl=64 time=11 ms
10.3.2.1 64 byte ping: ttl=64 time=3 ms
10.3.2.1 64 byte ping: ttl=64 time=3 ms
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 3/5.6/11 ms

[admin@MikroTik] > ip route add gateway=10.3.2.1
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
[admin@MikroTik] >

**********************************

Would you like me to submit the supout file?

This is not a problem I had with any >2.9.35 release which has no ip routing difficulties on the same machine. Unfortunately scripting problems with >2.9.35 on this machine (which seem to be resolved in 3.0) prevent me deploying it with 2.9.x

Would you like me to submit the supout file?

Well?

something is definately right ... that should be a piece of cake add.

I would suggest taking a supout from the router and sending to support@mikrotik.com.

Maybe you are missing the routing package ?

Sam

routing packages only introduces BGP, OSPF, RIP, MME simple static routing should work without that package

supout.rif sent to support this morning.

The routing package is installed - in fact to try to solve the problem I installed all the packages, except the legacy ones.

Another small oddity - Winbox displays two buttons for 'Bridge', one above and one below 'PPP'. Both of them work.

From this extract of the posted code by Sweetsunday, way back in October last year: -

[admin@MikroTik] /ip route> /ip address print
Flags: X - disabled, I - invalid, D - dynamic
# ADDRESS NETWORK BROADCAST INTERFACE
0 10.3.2.104/24 10.3.2.0 10.3.2.255 ether1

[admin@MikroTik] /ip route> add dst-address=0.0.0.0/0 gateway=10.3.2.104

It looks as if your'e trying to set the default gateway as being equal to the interface address. That won't work. Think about the scenario where you have a gateway router on your LAN, but you set the default gateway for each device connected to the LAN to itself. They wouldn't find the actual gateway.

Your default gateway needs to be another address on the 10.3.2.0/24 network. On a point to point link, it would be the device at the other end.

This explains why you couldn't "ping" an outside device (I'd always suggest using traceroute, BTW, it's much more informative) but doesn't explain why you had the timeouts in the configuration.

Did you solve that problem?

HTH

William