...
| Feature | Status |
|---|---|
| CAPsMAN | OK |
| Interfaces | OK |
Wireless | |
| Bridge/Switching | OK |
| Tunnels/PPP | OK |
| IPv6 | OK |
BGP | |
| OSPF | OK, but attention required * |
| MPLS | OK, but attention required * |
Routing filter | OK, but attention required * |
| Tools | OK |
Queues | OK |
| Firewall | OK |
| HotSpot | OK |
| Static Routing | OK |
| User Manager | See caveats |
| Dude | |
Caveats
BGP
Anchor bgp bgp
All known configurations will upgrade from 6.x to 7.x sucessfully. But keep in mind that there is complete redesign of the configuration. v7 BGP implementation provides with connection, template and session menus.
Template contains all BGP protocol-related configuration options. It can be used as a template for dynamic peers and apply a similar config to a group of peers. Most of the parameters are similar to previous implementatiob except that some are grouped in the output and input section making the config more readable and easier to understand whether the option is applied on input or output.
BGP connection minimal set of parameters are remote.address, template, connect, listen and local.role
Connect and listen to parameters specify whether peers will try to connect and listen to a remote address or just connect or just listen. It is possible that in setups where peer uses the multi-hop connection local.address must be configured too. Peer role is now a mandatory parameter, for basic setups, you can just use ibgp, ebgp.
Now you can monitor the status of all connected and disconnected peers from /routing bgp session menu.
Other great debugging information on all routing processes can be monitored from /routing stats menu.
Networks are added to the firewall address-list and referenced in the BGP connection configuration.
...