Watch videos with subtitles in your language, upload your videos, create your own subtitles! Click here to learn more on "how to Dotsub"

IOL INTACT Webinar

0 (0 Likes / 0 Dislikes)
Today we are going to cover the release of INTACT 6.2 it came out last week if you haven't received an update or email about it please feel free to contact us hopefully some of you have tried to download it we're going to go over the new features about that and also going to talk to you about the multiple package updates we made over the last year one thing, there is a Q&A window, if you type Q&A please type your question for the end of the presentation so, lets talk about what we're here to talk about today we are going to talk about 3.2.6.2 the releases major things that are in the release of INTACT - we added cloud licensing support which we are going to demonstrate its pretty straight forward, we will talk a little about how that works and how it will help people we added IPv6 router advertisement options, a lot of this has to do with future support of packages but it also included DNS options in router advertisements we also added TCP support for our new BGP conformance testing, so we will talk a little bit about that and one thing we are going to want to recommend is always new packages that I'm about to talk about we are going to recommend that you update to 6.2 there's a couple of, there will be a couple of warnings if you don't update, so we are recommended to everyone to update to 6.2 to be able to use the newest play as they are available I also want to remind everybody that there is a poll that we have up about some of the new INTACT features please feel free to fill it out and give us your feedback, we find that very valuable the first thing we want to talk about a little bit is the IPv6 Ready test plan updates the last revision of the test plan was 4.0.7 - this is considered a minor revision for the ready logo, what that means is that it becomes available immediately in updates typically this is to address to bug fixes, or in this cases, you will see several of the bugs that I'm going to talk about were to allow devices that supported newer RFC's to be able to continue to get the Ready Logo the first one is to allow devices to not process the hop-by-hop options this is an update in RFC 8200 we're going to roll-out new test cases for the RFC which Ill talk about later for right now I wanted to make sure that if device chooses not to support those options, then it's optional obviously we still recommend it as most implementations will process them, but for the moment if you don't process them then you will still be able to get the Ready Logo, that also includes the US Government test cases as well we also added the ability for a device not to send a packet to a message with MTU less than 1280 for atomic fragments we also allowed the transmission of more than 3 RS due to RFC 7559 which has to do with RS resiliency in particular around wireless or lossy networks the only other update that was important to that was test case 4.1.8 was updated to support separate destinations and this is because destination caches we had a couple of the implementations that failed this test case and it wasn't against the standard so we updated it to make sure that it met all the implementations which changed the source address to one of the pages those are all actually in the test document and that was released in September of this year, so that's available and online. Its on the Ready Logo website its also on the IOL website if you're looking for the actual document the actual tech bits so that was the test document updated. In this case these are the test cases that we addressed in the core update 4.0.8_2 this was released to of this includes all these fixes. Several of them were filed by you guys, users of INTACT directly and a couple of them we found internally. Couple of them were just fixes and some minor issues the 3.3 was one we had to override a variable that allows you to specify how long it takes your device to bind that DAD address that test case gives you an address of only 20 seconds. We set it so you can't try to set that variable higher, a lot of people would inadvertently set the variable too high and that would show up as a fail, when it was really just, needed to be overwritten. We took care of that and the rest of the fixes are right here, most of them were minor fixes that were affecting test cases one exception probably was 1.2.4d it had an issue processing perimeter problems when the fragment header was included so we made an update, several people were reporting failures on that and 1.1.07 was, you may have run into a race condition where, depending on when the packets were sent if a device went just transmitted Unicast then switched to Multicast then it would come up as a fail but the next time you ran it, if the Multicast NS came out at the right time, it would respond so it looked like the device was passing and failing we resolved that issue so it should always come up with the correct result we also updated 5.1 the last one on this list. It was actually just checking for, I think global addresses, so we updated it so you can send it source address from link-local or global, so we fixed those these are all what we consider minor bug updates. Address architecture package also got an update. This one is very minor, it was actual just that a lot of people get confused about all the test cases that are included, so we added all the test cases into that release to show what they are but then most of the new ones that weren't there before will just display a message to why they don't run. Two of them are support for IPv6 mobility, which we are not aware of anyone supporting and the third one is for a test case that uses link global and DNS, which isn't recommended. DHCP got similar updates to Core in that there we a couple of test cases that were missing individual message sites so we made some updates here. Checking DNS queries, some of them, 1.3.3, it was missing an IANA. We updated all of these, again if you find any of these issues, at the end we're going to have a section for your guys to talk about how to fill out bugs with us or how to let us know that something is going wrong So these are just minor bug fixes that we made to DHCP. A new one that we wanted to make everyone of is we now have BGP conformance testing I will note, everything else we've talked about up to this point was IPv6 this is actually the IPv4 flavor of BGP, we've gotten slightly more requests for that down the road we'll do the v6 version, but for right now this is an IPv4 version. Its fully automated with device configuration, so it will configure the router for the individual test cases. It covers all of those RFCs, its available for companies to purchase and use just like any other INTACT package. Looking forward, these are a couple of the new things we will be rolling out in the next six months to a year. We're looking into docker support, in particular this allows people to deploy things in a docker environment. We currently have virtual machines for most of our deployments, we've had some customers express interest in using a docker format. We're also going to release some updates for IPv6 Ready Core, in particular, for the new test cases for RFC 8200 and RFC 8201 In general, we're probably going to add a couple more test cases based on the new IETF node requirements document That includes some updates for security purposes, in particular around neighbor discovery with dealing with fragmentation headers, we're going to add those too. We're also in the near future going to role out NPD, this is for the US Government firewall test cases We're going to roll those out in INTACT, the exception is we're not going to be testing the CVEs It will be all the other packets that go through the firewall that need to be testing. So we'll be adding that package shortly for people who want it. We'll also as the USG revision 1 becomes available, we're going to update all the packages AA, DHCP, IPsec and IKEv2 One thing to note, if you already have these packages, you will be given the updates automatically. There's no separate fee, its just included. So if you have a Core package or a DHCP package today, you will get the new test cases included with that. INTACT 3.3.0.0, we are planning on releasing this on June 14th. The major features, there are a couple of things going on under the hood in particular, around packet processing for the newest RFC stuff, but we're also going to have an updated GUI The GUI the Java, the GUI going to be updated this go around. The CLI will support configuration. And what this means is that the current CLI, you can run testing in but you have to set-up the device configuration through the GUI The next revision of the CLI, the 3.3.0.0 version, you can do it all through CLI, so people who want to script it can script the entire thing from start to finish through the CLI. We're also going to have a RESTful API available to people. We got a lot of requests for CI type of environments where people want to run the tool. This kind of goes to our docker solution where people want to real quickly set-up INTACT to run the tests if they do that, they want to be able to control it, so we're going to add a RESTful API in 3.3.0.0 Another feature we've added is, we have DPDK support. And this in particular is for high speed interfaces, it will obviously work on any DPDK interface But we started using this to do a little bit more on the performance testing side but also just to support the higher speeds So we'll have DPDK support, you'll obviously need to get a DPDK NIC in your system if you want to use that, but we'll support it. We'll obviously continue to support the generic packet generator interfaces that we've been supporting. I'm going to demo this in a minute with the cloud feature, but I wanted to talk about this. This is the MyIOL, now has support for directly putting tickets into our system. Right now one thing I want to clarify is it just puts it into the system, in the future we're going to allow you guys to track what's going on with those how updates are going so you can directly see them and puts them into the system, it does take the file information which I'll show you and Ill display all of that It's a little bit easier from our end to make sure it gets into our system and its not just through an email. Contact information, as always, its [email protected] But first let me go ahead and demo and then we'll take some of your questions. Please while I do this next part, please feel free to shoot us some questions inside the box Right now I gave you guys a link that if you go to the UNH-IOL site, you'll see a report tools issue button that show up on top of the website So up here you can manage your devices, manage your testing. Over here when your logged into the site, you just click on report a tool issue, our case, we're INTACT You want to select INTACT. Severity, this allows you to give us an idea of what's going on critical, can't use the tool, not loading, I've run into some issue. Summary, just give a little information. Big things that we want to know is, environment, where you're running it, how you're running it. Affected test cases definitely help us, but also in our case, there is a debug zip you can attach that. We find that very helpful, in this case it's for our records. Any one of our technicians, student engineers, staff members can go through and look at the issues if you attach them. Please use this system, it will put it directly into our system and get you a faster response time. Again, just log into the MyIOL site and click on the report a tool issue. Lastly, I wanted to show the cloud support. Right now I just installed a new version of 3.2.6.2 This is the message you will get that will pop up if you don't have a license. It's throwing me a product error message, I want to select the cloud license In this case, I have a cloud license instead of using the license manager click the cloud license button Someone from the IOL, probably Michayla or myself will send you a file; we'll give you access to this. You click on the little link file, you choose it, you put it right in there, you click okay and INTACT will connect directly up to the cloud. The upside to here is this allows us to better control the licenses. A lot of people have had issues where licenses have updated underneath you on the license manager You do an update to the hardware, you do an update to the RAM, the cloud service allows us to get around all those issues. The one catch is you do have to have the app online, so the app has to be accessible and connect back to the cloud service. We're still going to continue to support the license manager for those who are in isolated networks, but we found it a lot easier to be able to control and help people support and debug using this cloud license feature. I also just want to remind everyone when you have an issue and you need our help, you go right under the help menu and you click the make debug zip and it will go and create a zip file and then you attach that to us. That gives us all the logs and all the information we might need. If you ever need to update you're installer or your changing for whatever reason, under the help button there is also the license installer which gives you that same window we just had a second ago. Just a reminder, the new feature we added was cloud licensing. Some of you will start to get this from us on renewals, just know when we say cloud license thats where we want it to go into the system. If anyone has any questions, feel free to pop them in now. The main things we've talked about today included the cloud licensing for 6.2, the GUI is mostly the same we did update several issues that existed in the test cases One thing I see we have a question about is US Gov revision 1, one thing to note about that is we're hoping to have that available but due to government shut down its been a bit slower than we originally anticipated, we're hoping it will be available in the next 90 days and we expect that one more revision and that 30 days after that to have it finalized. We got a question, "cloud licensing means we don't need to maintain license manager", YES you would not need the license manager This is in particular we found this helpful for deployments where license managers sitting at one site and they trouble getting VPN access or to other departments the cloud license sits outside and is available to anybody that's on a web server that is in that Amazon cloud We got a question "when to expect the RFC 8200 test cases to be available," we envision those to be available probably right before the newer version of the profile. The new revision isn't going to change for the Core specs So we're working with the Ready Logo to update the test cases. One thing for everyone to remember is when the Ready Logo updates it will only be available for six months where you can still apply with the old scripts and then you'll have to update to the new ones I just want to remind everyone we have a poll, helps us understand what new features and next things we're going to be added to INTACT We also envision a survey coming out to several of you to get an idea of how many people are running INTACT apps on things like Microsoft Windows, MAC OS, we don't want to be supporting features people aren't using. We are going to send out the survey to get a usage idea, you should be getting that from us in the next two weeks. We got a question, "is this presentation available for download," we have a wonderful website that has all of our webinars on it. If you go to our website www.iol.unh.edu and under IPv6 Testing Software, at the bottom you will see the latest webinars. We also post on our youtube site. Those who are interested, we have the past ones on here, we have one for DHCPv6, automate your testing, and we have one BGP that's currently available. So you can click on all of those and it will give you all the information that you need. One thing to note, someone asked about the version of Java, currently we support Java 8 We're looking at 3.3 to possibly support Java 11, but this is just a reminder that this version is Java 8. We don't have anymore questions, so I'll give you another minute to submit those One thing we didn't talk about is we haven't had a whole lot of updates for CE Router or IPsec In CE Routers case, there hasn't been a whole lot of changes. We probably will have a release in the next two months with minor fixes for CE Router for those out there listening for that test program For IPsec and IKEv2 we have been waiting for revision of the profile before doing an update as a lot of the algorithms have changed, so we'll be updating that after the new revision. The release plan for CE Router will be short, we consider it very minor. Only bug fixes, there's now actual change in the test spec and for IPsec we're waiting on the new revision because we didn't want to put a lot of work into supporting the old revision of the profile. If you have any questions about any of this stuff, please email [email protected] I want to thank everyone for attending today!

Video Details

Duration: 21 minutes and 12 seconds
Country:
Language: English
License: Dotsub - Standard License
Genre: None
Views: 1
Posted by: mbernazzani on May 15, 2019

Join Timothy Winters, Senior Executive, Software and IP Networking, as he discusses what's new with the IOL INTACT® Release 3.2.6.2 and how to get your device ready for the latest Core #IPv6 Ready Logo update. Also a live Q&A! Enjoy.

Caption and Translate

    Sign In/Register for Dotsub above to caption this video.