I don't remember what all they have changed/fixed/added, but IPv6 has
had some work done on it since 3.30.
On 5/19/2011 3:23 PM, Jeromie Reeves wrote:
I am doing v6 just fine with 3.30. In fact I think that is why I went
from the first stable MLPPP version to 3.30.
What are people finding that 4/5 has for v6 that 3.30 does not?
I also agree with 'if it works dont fix it' but that is not a option.
A water leak has killed a number of my routers and servers in my rack.
Seeking 3.30 all I found on the MT site was 4.17 and 5.2
Since I have to do a full new build any how, I was wondering if I
should not just go with one of them. Most of my routers could be
replaced with some RB's. I do not do much at this site, the MLPPP box
will be going to 8 lines, but I figure I will use a vlan switch
and bring them all in on 1 port. The NAT box will stay a x86 unit of
some time most likely. The firewall and snort boxes will also
stay x86, but I am thinking of combining them into a vmware unit.
On Thu, May 19, 2011 at 9:32 AM, Scott Reed<sr...@nwwnet.net> wrote:
If you are anticipating IPv6, and we all should be, at sometime you will
want to get to 5.x.
On 5/19/2011 11:46 AM, Robert Andrews wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The reason we went over was to get ready for IPV6. We do want to run 6
sometime in the near future. We do think that it will be a
requirement. So better the devil you know... Otherwise it would
definitely be "if it works, don't ...k with it" Like many things we
trust old code more than new code. So far we have seen good results
with 5.2 and we have not seen eroding memory. My speculation is that
something the Dude is tickling is causing the SNMP memory erosion. Our
nagios queries don't seem to be doing anything.
Robert
On 05/19/2011 08:32 AM, Jeromie Reeves wrote:
I am fine with leaving the current gear where it is at. MT Does not
look to offer 3.30 for download still and I finely wore out my mt cd.
All my RBs
have been left at what ever came on them, so thats a mix of a dozen or
so versions. I am not doing anything exotic with them so they have
been fine.
I am just wondering if I should go ahead and go with 4.17 or 5.2 for
the new router or stick to 3.30. The old one was doing MLPPP on 4
lines with OSPF
feeds. Script rebooted it once a week but I think that was a left over
from 3.13ish days (what ever the first MLPPP supported version was
with the memory
bug)
On Thu, May 19, 2011 at 6:56 AM, Josh Luthman
<j...@imaginenetworksllc.com> wrote:
I'm pretty sure I have some 3.30 running just fine. I have a couple
2.9.50
and 51 that are almost just fine, too.
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Thu, May 19, 2011 at 9:55 AM, Jeromie
Reeves<jree...@18-30chat.net>wrote:
I have left pretty much all my routers back at 3.30 because they have
been stable in my uses. Is there any compelling
fixes in 4.17/5.2??
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
-------------- next part --------------
An HTML attachment was scrubbed...
URL:<http://www.butchevans.com/pipermail/mikrotik/attachments/20110519/b44eb547/attachment.html>
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJN1TtIAAoJEC+8HUjSuDOs7gYH/RgXkR7+4RGa5NEOayTYGeI8
N2PAEJUyT640rC3uRDTJ46SIMInV2FytYQgN9qjR69yOm60638Tf02a3GMsADqri
SWHuVM2zmKVsJYUQcqVuHKhrjHGYb3E8n7RY0yqKmte+9FK/JkR/hrZCjmGquLWZ
BRRaKXSqFo7Po5lCafN375EV8dfg7aSuyxY6sKL8OTUciEET+wdizGlwxl5jzuRw
PGu3IjVVY2DgxLwlr1ufkF3rTOcz9yOhCOfKL5nKsFhEjctUR0/9lFWYDO1WBeCi
Emx2g6mIzWdMU/XGMC5BGH9T3DCvKgMVqy2BcOXzo+L5l4JjTAAbWVzKY3kUvVQ=
=M4XH
-----END PGP SIGNATURE-----
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
--
Scott Reed
Owner
NewWays Networking, LLC
Wireless Networking
Network Design, Installation and Administration
Mikrotik Advanced Certified
www.nwwnet.net
(765) 855-1060
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
--
Scott Reed
Owner
NewWays Networking, LLC
Wireless Networking
Network Design, Installation and Administration
Mikrotik Advanced Certified
www.nwwnet.net
(765) 855-1060
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
