Why are you setting MPLS MTU at 1501? Set it at 1522 if that's the highest L2 MTU you have.
Oh yea forgot about the form but yea after that your account gets enabled for the extras.Where is that?
I've emailed support, got a form to fill out that I never got around to doing.
Is this the next step after filling out the form?
Do ya know the particular controller chip?PCI-e
Do you know what specific controller/chip it is? Bus is PCI or PCI-e?None of our Pro1000's do either. We have PT and ET cards mainly.
Is there any ETA / timeline for 6.0 final?
I couldn't get the PCI-e card in the PCI slot, lolPro1000PT Quad port PCIe
Why are you using old PCI card?
Ok thanks emailed support.You can get beta3 if you contact support. Well the card is not bad, but it is quite new and drivers are not optimized in older kernel.
Is beta 3 out? Can I get a copy?It is a driver problem. Try v6beta3 there should be newer drivers. If it crashes on beta3 too then get better ethernet card.
The cards do not report L2MTU and it cannot be manually set. The values are greyed out in winbox, and at the command line you can enter the command, but it does nothing.If the card does not report L2MTU you must set MTU to desired value.
Well then how come mine dont work???We have many implementations using Intel Pro1000 cards and 1530 byte and larger frames, they work brilliantly.
So why is the card advertised as 24dbm in B mode? 25 dbm in G mode?The card will only give maximum power when both chains are in use. And that can only be if you use 802.11n (or ´mimo´) protocol.
You use ´b´ so only one chain thus 3dB less.
The futur is native Ethernet connections and FTTH fiber links, but in the meantime we need to use this old stuff because providers do not want to change their hardware to fast.
There are cases where you want to have a router distribute default routes to other routers, but you end up with a router on the network that already has a desirable default route.There is a better solution for this: set distribute-default=never
That sounds about right i see ROS 3.2 and radio name UBNT
Why is this? very strange really - would have thought the Mikrotik protocol would have been ... locked down.
upgraded to 4.3.
Config on Meta Lost.
Rebooted and config did not go away.
Now are there any problems with 4.3 we should know about
okay I have read the wiki about BCP and it works, but i can`t do a PPPOE over BCP ?
Must PPPOE Server on the local_bridge of PPTP Server?
Ya the l2tp tunnel properly is in the bridge once it connects. I spend 4 days trying, and never could get it to work, and suspect its a possible bug in newer versions of mikrotik.i dont use pppoe, just was testing it back then. does your l2tp tunnel show active in the bridge once its connected?