Well, it looks like RIPng is broken in RouterOS, when using Vlan's on the interfaces. It has the dynamic routes within the RIPng section, but doesn't redistribute them to the kernel-routing space.
Yuk. No IGP for a while until that is fixed. I will look at the OSPFv3 stuff in the next days, but that needs extensive testing on both Quagga and Mikrotik side, before I'll deploy that.
Got a mail back, that they'll fix it in one of of the next versions.
Tuesday, October 21, 2008
Friday, October 17, 2008
Mikrotik RouterOS 3.15 release
The release of ROS 3.15 yesterday fixed quite a few bugs, that affected us.
IPv6 and IPv4 address families can now co-exist on the same BGP session (routing-test). That means, if our testing goes well, we'll be announcing IPv6 routes on INEX Vlan#2, too, very soon.
BIOS 2.18 fixes the issue, where 2.17 was killing ether3 on RB600 and ether2 and 3 on RB500 series.
The issue, that one couldn't disable dns resolving on traceroutes was really annoying for diagnostics as well.
They however broke adding static IPv4 routes via WinBox instead :( and my own RB600 router went into a non-recoverable state during upgrade. Something I haven't seen in a very long time. Netinstall and reload of backup fixed that though.
IPv6 and IPv4 address families can now co-exist on the same BGP session (routing-test). That means, if our testing goes well, we'll be announcing IPv6 routes on INEX Vlan#2, too, very soon.
BIOS 2.18 fixes the issue, where 2.17 was killing ether3 on RB600 and ether2 and 3 on RB500 series.
The issue, that one couldn't disable dns resolving on traceroutes was really annoying for diagnostics as well.
They however broke adding static IPv4 routes via WinBox instead :( and my own RB600 router went into a non-recoverable state during upgrade. Something I haven't seen in a very long time. Netinstall and reload of backup fixed that though.
Saturday, October 11, 2008
Ballindereen basestation rebuild
On wednesday evening the omni in our Ballindereen basestation failed, cause yet unknown, but the board did just not respond anymore. Unfortunatly it's been lashing down since then and until today. The roads on the Galway - Roscommon road were flooded this morning.
You'd say, what has that to do with it? Well, this is a 100ft castle tower with a 20ft pole on the roof and the board we need to replace is at the top of the pole (see left, plastic box on top of the pole). It isn't an easy job to do so and the roof is impossible to climb in wet conditions, let alone dangerous.
The majority of the customers were moved to other basestations in the meanwhile.
Some time after midnight today it stopped raining. We used the nice day to basically rip the whole base apart. It's 2 1/2 years old and needed a overhaul. A upgrade was also planned for some time, so that's what we've been at today.
The (not final) result is the picture on the right. Obviously missing the panels for the inter-base links, yet.
Also the boards aren't mounted on the pole anymore, but reside in the box on the wall with coax to the antennas. That way, we'll be able to maintain them in bad weather. This is something we changed about a year ago, but some of the older bases haven't had the rework done yet. Once finished, a battery and trickle charger move into the empty slot and that'll be it then. This base consists of 1 legacy omni, 3 sectors, and 4 point-to-point links, 4 embedded routers in total. And with the upgrades, it'll be fully MPLS capable.
Friday, October 10, 2008
Mikrotik IPv6 BGP
Ok,
it looks as it's working anyhow, but i need to create different instances with different router-id's to have two sessions between two routers. Doesn't matter that they are different address-families. What a pain.
The as-path filters that i filed a bug report in August about are still not fixed and it looks like, that I can't filter on IPv6 prefixes, either.
Looks like I'm going to kick this box to h*** soon and replace it with something decent. Mikrotik might be good at wireless, but in regards to routing, it doesn't look pretty.
it looks as it's working anyhow, but i need to create different instances with different router-id's to have two sessions between two routers. Doesn't matter that they are different address-families. What a pain.
The as-path filters that i filed a bug report in August about are still not fixed and it looks like, that I can't filter on IPv6 prefixes, either.
Looks like I'm going to kick this box to h*** soon and replace it with something decent. Mikrotik might be good at wireless, but in regards to routing, it doesn't look pretty.
GBLX IPv4 session live
Finally the last bit for our IPv4 transit falls into place: Our IPv4 session with Global Crossing got turned up today, immidiatly eating up traffic.
Thursday, October 9, 2008
Hurricane IPv6 BGP tunnel TCY <-> FFM
As IPv6 over Level3 fell flat (PacketExchange can't deliver) and I still have no second IPv6 peer for TeleCity, I did set a second tunnel up with Hurricane Electric. That finally got set up today, lads must be a bit busy at HE.net.
So for IPv6 we've now Smart Telecom (native) and Hurricane London (tunnel) in Dangan, Galway. In TeleCity we've got GlobalCrossing (native) and Hurricane Frankfurk/Main (tunnel), Germany on top of the INEX peerings on Vlan#1.
The INEX Vlan#2 is a Mikrotik router and they still can't do IPv6 BGP without mix/match :(. I've been chasing them on that since 3.10 now, it was supposed to be fixed in 3.12 and as of 3.14 routing-test it still doesn't work, if I got the configuration right.
So for IPv6 we've now Smart Telecom (native) and Hurricane London (tunnel) in Dangan, Galway. In TeleCity we've got GlobalCrossing (native) and Hurricane Frankfurk/Main (tunnel), Germany on top of the INEX peerings on Vlan#1.
The INEX Vlan#2 is a Mikrotik router and they still can't do IPv6 BGP without mix/match :(. I've been chasing them on that since 3.10 now, it was supposed to be fixed in 3.12 and as of 3.14 routing-test it still doesn't work, if I got the configuration right.
Tuesday, October 7, 2008
IPv6 and null-route
After re-organising the whole network lately, I wanted to get the null-route in place again for our IPv6 range. It's just nicer, than being looped around between two routers.
First barrier: It's not possible in Mikrotik. DOH !!! .. Well .. I raised a ticket with them on that.
Second barrier: I've added it like usual in the zebra daemon of quagga, by using "ipv6 route 2a02:278::/32 Null0". Well, so I thought. It actually does not work on Quagga 0.99.5, which reminds me, that I need to upgrade that box and then test it again.
Anyhow, we'll fix it via "ip" then. The command to archieve this is "ip route add 2a02:278::/32 dev lo"
Job done, all happy.
First barrier: It's not possible in Mikrotik. DOH !!! .. Well .. I raised a ticket with them on that.
Second barrier: I've added it like usual in the zebra daemon of quagga, by using "ipv6 route 2a02:278::/32 Null0". Well, so I thought. It actually does not work on Quagga 0.99.5, which reminds me, that I need to upgrade that box and then test it again.
Anyhow, we'll fix it via "ip" then. The command to archieve this is "ip route add 2a02:278::/32 dev lo"
Job done, all happy.
Sunday, October 5, 2008
Blog update
People that have subscribed to my blog will notice, that suddenly things have happened. Yes, I was idle updating it for a good while and yes, I've catched up on the last 2-3 months, sort of.
Well, hopefully I'll have more time in the future to keep it up to date a bit more often.
Well, hopefully I'll have more time in the future to keep it up to date a bit more often.
Friday, October 3, 2008
GBLX IPv6 and eXpress peering live
Finally, it took ages to get the details for the Globalcrossing IPv6 and the eXpress peering sessions. But they are live now and we'll just have to wait for the eXpress route-servers to pick up our prefixes. That should happen in the next 24 hours.
All we are waiting on our circuit to PacketExchange is the session for IPv4 from Globalcrossing.
Anyhow, this means, that we have 3 IPv4 and 3 IPV6 transit carriers now.
All we are waiting on our circuit to PacketExchange is the session for IPv4 from Globalcrossing.
Anyhow, this means, that we have 3 IPv4 and 3 IPV6 transit carriers now.
Subscribe to:
Posts (Atom)