- Community Home
- >
- Networking
- >
- Software Defined Networking
- >
- Re: How to wildcard Ipv4 address?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2016 12:38 PM - edited 05-24-2016 01:19 PM
05-24-2016 12:38 PM - edited 05-24-2016 01:19 PM
Can anyone help me with a flow definition containing a wildcarded ipv4 address in json. I thought it would be something like the following, but the HP VAN Controller (version 2.4.5.0614) returns:
{"error":"java.lang.IllegalArgumentException","message":"Bad address format: 192.168.0.0/16"}
----- flow.json ------
{
"flow": {
"priority": 30000,
"idle_timeout": 30,
"match": [
{"eth_type": "ipv4"},
{"ipv4_dst": "192.168.0.0/16"}
],
"instructions":[{
"apply_actions": [{"output": "NORMAL"}]}]
}}
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2016 01:39 PM
05-24-2016 01:39 PM
SolutionYou'd want to modify the flow JSON you're pushing to include a "mask" parameter along with the IPv4 address, as shown below:
{
"flow": {
"priority": 30000,
"idle_timeout": 30,
"match": [
{"eth_type": "ipv4"},
{"ipv4_dst": "192.168.0.0",
"mask": "255.255.0.0"}
],
"instructions":[{
"apply_actions": [{"output": "NORMAL"}]
}]
}
}