On Fri, Sep 09, 2011 at 05:17:55PM -0700, Bill Prince wrote:
> Well, the old AP is on ether2, and all the old SMs are there too and
> on the /26 subnet.
>
> The new AP is on ether7, and the new SMs will not talk to the old AP.
> So they will have to go somewhere, and I don't have enough spare IP
>
rotik@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/20110
chevans.com/ for tutorials related to Mikrotik
RouterOS
-- next part ------
An HTML attachment was scrubbed...
URL:
<http://www.butchevans.com/pipermail/mikrotik/attachments/20110909/1a1c01b2/attachment.html>
___
Mikro
On Fri, 2011-09-09 at 17:03 -0400, Josh Luthman wrote:
> DNS was changed in 4.x I think. That's one that's been most obnoxious for
> me.
Yes, it was 4.x where this changed. I agree, it was pointless to change
it for no real benefit.
--
**
Well, the old AP is on ether2, and all the old SMs are there too and on
the /26 subnet.
The new AP is on ether7, and the new SMs will not talk to the old AP.
So they will have to go somewhere, and I don't have enough spare IP
addresses to just plunk down a new subnet on the new AP.
We're in
You can not have 2 ports on the same device in the same subnet. It won't
know which to use.
But, with what you are saying, why can't you just split the /26 into 2
/27s and be done?
Here is maybe the thing that is getting you. If you split the /26 into
2 /27s and put them on separate interfaces
My thinking was that all the lower addresses (1-30) will be in the /26,
and all the upper addresses (33-62) will be in the /27. Once they're
moved, then I can go back and switch all the lowers to a /27.
This will all be on the same router (RB493). The /26 is on ether 2, and
the /27 will be o
Has anyone else seen the RB493 problem?
Mine become completely unresponsive and require a site trip to power
cycle (they run the network card for the UPS which makes it extra painful)
Dropped everything back to 4.17 and been solid
--
Simon Westlake
si...@powercode.com
(920) 351-1010
Powerco
Would anything from 32-63 overlap with the old subnet? If not, it should
work, as the more specific route will take precedence (assuming you are
running some kind of routing protocol or will have routes between the
two routers statically)
Hard to answer for sure without more information but it
Routing will be a problem.
How are you going to tell a router customer .1 is here, .5 is there, etc.?
There are thousands of /26 networks available that are non-routing. What
about creating a new /26 out of 10.x.x.x and NAT it until you get
everyone moved?
On 9/9/2011 5:34 PM, Bill Prince wrot
> 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/
I have found this on RB493 as well as RB435G
It appears to happen during the load of the configuration on the new
version. What I have found works, is to export the config to a .rsc,
edit it and change the first line to "delay 30" then for the upgrade do:
/system reset-configuration run-aft
We put up a new AP on a POP where we already have 6 operating APs. The
plan is to split off about 25 existing subscribers on one of the old APs
and put them on this new AP.
So we have all the subs (about 50) in one /26 (x.y.x.0/26). The ones
we're going to move I need to put on a separat
On 09/09/2011 02:05 PM, Scott Lambert wrote:
Lots of us have. I think concensus is that it occurs more often when
ether1 is in use.
I've been looking for references to this so I know when it's "safe" to
resume upgrades. Is there a thread on the MT forum? Does anyone have a
ticket open with
attachment was scrubbed...
URL:<http://www.butchevans.com/**pipermail/mikrotik/**
attachments/20110909/9b319c1e/**attachment.html<http://www.butchevans.com/pipermail/mikrotik/attachments/20110909/9b319c1e/attachment.html>
__**_
Mikrotik mailing list
Mikrotik@
On Fri, Sep 09, 2011 at 01:12:11PM -0700, Kristian Hoffmann wrote:
> On 09/09/2011 10:47 AM, Dave Crim wrote:
> >This probably doesn't apply to you, but we had nothing but problems
> >running 5.x on 493G's. The Ethernet ports would flap up and down at
> >random intervals, causing it to stop passin
d NAT rules are pretty basic. Only one or two simple queues
>>>>>> in a few circumstances and Butch's QoS script (the old one that
>>>>>> doesn't
>>>>>> support per-interface configuration).
>>>>>>
>>>
e
upgraded firmware as well. See
http://blog.butchevans.com/2010/08/routeros-upgrade-process/ for
detailed steps.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://www.butchevans.com/pipermail/mikrotik/attachments/20110909/9
il/mikrotik/attachments/20110909/9b319c1e/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
-
On 09/09/2011 10:47 AM, Dave Crim wrote:
This probably doesn't apply to you, but we had nothing but problems
running 5.x on 493G's. The Ethernet ports would flap up and down at
random intervals, causing it to stop passing traffic momentarily.
Mikrotik Support suggested we upgrade to 5.6, which I
tchevans.com/2010/08/routeros-upgrade-process/ for
detailed steps.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://www.butchevans.com/pipermail/mikrotik/attachments/20110909/9b319c1e/attachment.html>
___
Mikr
I went from 3.30 to 5.4 with no issues.
Be aware, the upgrade works, but you can not just import 3.x or 4.x .rsc
files into 5.x. They changed some of the words again. Some of it is to
support 802.11n.
On 9/9/2011 12:09 PM, Butch Evans wrote:
On Fri, 2011-09-09 at 10:46 -0500, Rory McCann wr
An HTML attachment was scrubbed...
URL:
<http://www.butchevans.com/pipermail/mikrotik/attachments/20110909/f97ab
ccc/attachment.html>
___
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
V
Keeping people from stealing service, that's pretty actually easy these
days for hotspot. Anything from Chillispot to Bluesocket will do that,
with a moderate amount of effort. It just a balance of customer ease
vs. effort tot to steal.
Providing security to the end user is difficult, and l
On Fri, 2011-09-09 at 10:46 -0500, Rory McCann wrote:
> Most of my routers are running 4.10 or 4.11. I'm planning on upgrading
> them to 5.6 and am wondering if there are any major changes I should be
> aware of that may break functionality. I have one RB1000 and the rest
> are RB750 or RB750G.
ucts
P*: 701-403-4877*| C*: 701-640-8999
*E*: r...@mkap.com*| W*: support.mkap.com
-- next part --
An HTML attachment was scrubbed...
URL:
<http://www.butchevans.com/pipermail/mikrotik/attachments/20110909/f97abccc/attachment.html>
__
26 matches
Mail list logo
