It's clearly being invoked in this scenario, as evidenced by the fact I had to add a rule to pass all traffic inwards to my LAN.

I have no forward rules and UPnP works just fine for me with just the auto-added dst-nat rules.

What I can't quite wrap my brain around is that now my forward chain doesn't seem like it's adding any value. Either I'm right - and it isn't; or it's achieving something I can't think of - which I'd like to understand. Well, the forward chain is for routed packets. You're using NAT for UPnP device...

Has anyone used the RouterBOARD 1100/1200 devices for LACP?

LACP works, but you can't bridge that interface. The bridging disables the LACPDU packets and the bond fails. Or so all my testing seems to show.

It's been suggested that it's not sensible to rely solely on NAT to secure the inside hosts. At the same time, if the inside hosts *request* an incoming port forwarding via uPnP, then the firewall should allow it. But is that then not exactly equivalent to just using NAT as your firewall? UPnP is a...

Adding address from pool to interface is in our TODO list.

Now that I'm already on RouterOS 5.10rc2, I'd be happy to test the update that includes this functionality as well.

Ok, I now have IPv6 working correctly. I'm still not sure I should be setting the IPv6 address on the internal LAN interfaces manually, but otherwise it seems to work OK.

If you know what the range allocated is then yes you should be able to simply add an IPv6 address to the interface of your choice, seeing as you have the upstream gateway and Internode knows to route back to you for that range. Yeah, but how do I work out what a valid IPv6 address for that interfac...

RouterOS is not configuring the local interface with a proper IPv6 address from the pool received via the DHCPv6-PD request. On Linux, the LAN interface upon which RADVD runs gets an IPv6 address. Anyone know if it's possible to manually apply an address? All I have now are link-local addresses and ...

I can't seem to find the right configuration for /ipv6 nd prefix -- everything I try just comes up as Invalid.

I've noticed a difference in the debug outputs for connecting with username@ipv6.internode.on.net vs enabling IPv6 from the internode web portal and using your regular username. Testing with the new 5.10rc2 from Mikrotik results in a valid PD coming from Internode: [admin@MikroTik] /ipv6 dhcp-clien...

So how am I supposed to pass prefixes to other routers on my network?

This is done by RADVD not by DHCPv6-PD. Mikrotik have found the problem and provided me with a test version of RouterOS, which I'm about to download. Will report back.

http://wiki.mikrotik.com/wiki/Manual:PPP_AAA#User_Profiles dhcpv6-pd-pool (string; Default: ) Name of the IPv6 pool which will be used by dynamically created DHCPv6-PD server when client connects. But we're not running a DHCPv6-PD server, just a client. So we don't need to configure a DHCPv6-PD pre...

Is this section required to be configured on the client device? In the same way?

No, that's for the server side. It's under the big Server heading and everything.

I'd hit up node support, see what they see their end.

Yeah, I'll try that today when Internode's NetOps team are online.

also just for kicks, try NODE-PD instead of Internode-IPv6 for your pool name.

Nope, doesn't work without any firewall or using NODE-PD as the pool name. Just gets stuck on "Searching..."

it definitely works - I've labbed it against a cisco 7200 LNS and I get a prefix fine. I'm glad someone got it to work! Can you post the IPv6 firewall rules you used on the Mikrotik as well? Also, Internode presents a /56 prefix. Are you able to configure your Cisco to present that and see if it st...

Turns out that Packet Sniffer on RouterOS can't sniff pppoe connections. You have to point it to the ethernet interface that the pppoe-client is running on and set the filter-mac-protocol=pppoe instead. I've now sent the packet trace from the (working) wide-dhcpv6-client and (non-working) RouterOS 5...

(I decided to start a new topic on this as not to clutter up the RouterOS 5.9 announcement thread) I have done further testing. I cannot get packet sniffer on RouterOS to see any DHCPv6-PD packets at all. I have re-tested my connection with Ubuntu Server running a pppoe client and it can happily get...

You should be able to set up a mirror port on the Routerboard under the Switch section and run the capture on your PC.

Sadly, this doesn't work, as I don't see the packets traveling over the PPPoE link. Will have to try and get RouterOS's packet sniffer to work instead.

You should be able to set up a mirror port on the Routerboard under the Switch section and run the capture on your PC.

Thanks, that's a great suggestion.

There is some other problem why dhcp-pd client does not get the prefix from your dhcp-pd server. And that should not be connected to fact that SLAAC address is not set on the router pppoe client interface. Yup, so further research has shown me as well. It was just a guess. :) I'm trying to grab pac...

I'm having some issues with IPv6 over PPP. I put require IPv6 in the profile, PPP connects however DHCP client never joins. This is on Internode http://ipv6.internode.on.net/ . Yeah, I'm with Internode as well, same problem. I've already emailed support and will enable DHCP debug logging and send t...

Here is the working configuration example: http://wiki.mikrotik.com/wiki/Manual:IPv6_PD_over_PPP This doesn't work -- my configuration is identical and my RB client never received a prefix nor created the IPv6 pool. This works with other routers, e.g Linux running wide-dhcpv6-client on the same PPP...

I get exactly the same, just sits on "Searching..." If I open IPv6 outbound udp/567 and inbound udp/546 I can see packets leaving the RouterOS, but nothing coming back. I know that DHCPv6-PD works, as I've tested it with a generic Linux-based router and a Fritz!Box device. I'm not sure wh...

Anyone got a dual-stacked IPv4/IPv6 PPPoE connection up and running yet?

Nope. I've added the dhcp-client entry, but it's just stuck on "Searching...". I suspect a firewall issue somewhere.

Right, so LACP uses multicast for the LACPDU packets, so do bridges not pass multicast traffic by default, perhaps? If there are no filter rules configured, should a bridge pass all traffic or no traffic?

I've got a weird problem I hope someone can help me with. I'm trying to create a LACP 2-port bond between an RB1100AH and a Netgear GS716Tv2. Everything works ok until I add the bond into a bridge. At that point, the Netgear sees the bond as down and stops load-balancing/failover. I've experimented ...

Normis You forgot to mention that UPnP has been updated slightly in v4.6 (Xbox360 Live).

Still doesn't seem to work with Back to My Mac, though.