To MT:It is in TODO list and should be ready until final v5 is released. You can easily start to deploy IPv6 even without DHCPv6, use stateless address autoconfiguration.Any ideas when DHCPv6 will be implemented?
New Intel 1G card, SSTP, RPS, GRE?there is stable version v4, and on all mission critical routers this is the way to go,
[demo@demo2.mt.lv] > /ip route print count-only where dst-address "0.0.0.0/0"
0
so what do you want, new features or stability? you are contradicting yourself.New Intel 1G card, SSTP, RPS, GRE?there is stable version v4, and on all mission critical routers this is the way to go,
Normis, ROS is software that is provided by MT, so you should do, what you want (not me ).so what do you want, new features or stability? you are contradicting yourself.New Intel 1G card, SSTP, RPS, GRE?there is stable version v4, and on all mission critical routers this is the way to go,
On the side topic of ip route print it would be nice if when you do "where dst-address=blah" you can enter a host IP and have it report back the subnet's that route falls into.
When your dealing with a full route table it's dam hard to find a route when you only know the host, In cisco land you can put the host in and it will spit out routes that host falls into. A number of times now we've had to wait 10min for the full table to load in Winbox to manually find the /24 or /19 route that a /16 netblock has
/ip route print where 192.168.86.1 in dst-address
[TOTORO@Core0-Wenet] > /ip route print where 192.168.86.1 in dst-addressyou can do in clauseCode: Select all/ip route print where 192.168.86.1 in dst-address
andrijco you have full BGP feed there?
Thanks for this update !!Thank you very much for the reports about queues at 5.0rc6.
We can confirm two problems with queues right now,
1) When there is no address specified (target-address/dst-address), only IPv6 traffic is queued.
To fix it use any IPv4 address (e.g. 0.0.0.0/0) for target-address/dst-address for /queue simple.
To fix dynamic PPP queues, use /queue tree and dynamic-address-list.
2) /queue simple does not work on x86/miplse at all.
Both problems already fixed and will be included to the next release.
now i know why the queues work with pppoe and not working with user managerThank you very much for the reports about queues at 5.0rc6.
We can confirm two problems with queues right now,
1) When there is no address specified (target-address/dst-address), only IPv6 traffic is queued.
To fix it use any IPv4 address (e.g. 0.0.0.0/0) for target-address/dst-address for /queue simple.
To fix dynamic PPP queues, use /queue tree and dynamic-address-list.
2) /queue simple does not work on x86/miplse at all.
Both problems already fixed and will be included to the next release.
can you send your supout.rif file to support? we would like to see your script and how you run it, please give us more details.Hello,
I don't know if it's a bug or I need to configure something, but when I try to execute a script over ssh that is ~850 lines long in v5rc6, I get the message "Write failed: broken pipe". The script is with customer firewall and queue rules. The same script had no problem on v4.13 and if I shorten it to just a few customers (3 out of all 70) it works fine. (didn't try to see how many would work)
Any ideeas?
Thank you.
EDIT: I've downgraded from v5rc6 to v4.16 and now I get this error when ssh-ing into the system: " Protocol major versions differ: 2 vs. 1 "/ I also noticed that when the system first boots after the downgrade, it only generates an RSA key. After a clean v4.16 install, everything works fine.
tested on all platforms, works fine. make sure you have disk space available, this could cause it to not save anything.v5rc6 sniffer not work.
how did you upgrade, big package to FTP and reboot? which packages did you upload?Hi,
I've just upgraded from v5beta6 to rc6 and my 532 board not boot:
RouterBOOT booter 2.18
RouterBoard 532
CPU frequency: 399 MHz
Memory size: 32 MB
Press any key within 2 seconds to enter setup..
loading kernel from nand... OK
setting up elf image... OK
jumping to kernel code
Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
What to do?
regards,
We have no such problems with RB532. You will have to use Netinstall to restore RouterOS.yes, via ftp. all packages w/o calea, gps, ipv6, hotspot, ups and user-manager.
SSTP is still new and really does nothing new compared with L2TP and PPTP etc.
ROS 4.16 supports both protocol 1 and protocol 2. Its ssh daemon is based on an ancient OpenSSH release (2.3.0); ROS 5.0rc6 supports protocol 2 only so it seems based on, at least, OpenSSH 5.4. In fact, we decided disabling legacy protocol 1 by default on march's release after a transition period of ten years. Support for protocol 1 has not been removed from OpenSSH's source code, only disabled by default in the configuration files.I've downgraded from v5rc6 to v4.16 and now I get this error when ssh-ing into the system: " Protocol major versions differ: 2 vs. 1 "/ I also noticed that when the system first boots after the downgrade, it only generates an RSA key. After a clean v4.16 install, everything works fine.
"Write failed: Broken pipe" means that packet_write_poll() cannot write some of the output on a socket because there is no process to read the data on the other side. I would suggest (1) trying another sftp client, and (2) to make sure this is not a ROS-specific problem transferring a file to a BSD or Linux system running OpenSSH 5.4 up to 5.6 (as you noted, this problem does not happen with SSH service on 4.13).I don't know if it's a bug or I need to configure something, but when I try to execute a script over ssh that is ~850 lines long in v5rc6, I get the message "Write failed: broken pipe". The script is with customer firewall and queue rules. The same script had no problem on v4.13 and if I shorten it to just a few customers (3 out of all 70) it works fine. (didn't try to see how many would work)
Any ideeas?
Hello,
OK, we will increase the maximum length.
Regards,
Normunds
My post was about work arounds, SSTP offers nothing other than being simple, if you need secure stable VPN right now work around it, 5.0 is not for production deployment!SSTP is still new and really does nothing new compared with L2TP and PPTP etc.
Wow. You might wanna watch what you say when comparing L2TP/PPTP to an actual secure VPN solution..
My post was about work arounds, SSTP offers nothing other than being simple, if you need secure stable VPN right now work around it, 5.0 is not for production deployment!SSTP is still new and really does nothing new compared with L2TP and PPTP etc.
Wow. You might wanna watch what you say when comparing L2TP/PPTP to an actual secure VPN solution..
I just noticed a post about that a little before mine, so it's likely I was in the middle of my post and started on something when that got posted.Save your efforts. The User Manager RC5 and RC6 is not working at all. Don't you read the posts here?