[CONTROLLER-530] Nmap scans cause erroneous switch connection messages and exceptions Created: 02/Jun/14 Updated: 25/Jul/23 Resolved: 09/Jun/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Daniel Farrell | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Linux |
||
| External issue ID: | 1124 |
| Description |
|
Process to recreate: Clone the latest version of the controller, start it (in my case, on a remote Fedora 20 VM running on an OpenStack deployment with an IP I can reach), run nmap scans against the various ports it opens. Three ports cause bug-like behavior: 6633, 1830 and 6640. When scanning 6633, ODL throws an erroneous switch connection message. *Nmap scan of 6633* $ nmap -Pn -p 6633 172.16.21.29 Starting Nmap 6.45 ( http://nmap.org ) at 2014-05-30 21:41 UTC Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds *ODL result of scanning 6633* osgi> 2014-05-30 21:41:46.451 UTC [ControllerI/O Thread] INFO o.o.c.p.o.core.internal.Controller - Switch:172.16.21.18:42889 is connected to the Controller osgi> When scanning 1830, ODL raises a SocketException. *Nmap scan of 1830* $ nmap -Pn -p 1830 172.16.21.29 Starting Nmap 6.45 ( http://nmap.org ) at 2014-05-30 21:38 UTC Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds *ODL result of scanning 1830* osgi> 2014-05-30 21:38:31.645 UTC [Thread-33] ERROR o.o.c.n.ssh.threads.SocketThread - SocketThread error osgi> When scanning 6640, ODL raises an IOException. *Nmap scan of 6640* $ nmap -Pn -p 6640 172.16.21.29 Starting Nmap 6.45 ( http://nmap.org ) at 2014-05-30 21:42 UTC Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds *ODL result of scanning 6640* osgi> 2014-05-30 21:41:46.451 UTC [ControllerI/O Thread] INFO o.o.c.p.o.core.internal.Controller - Switch:172.16.21.18:42889 is connected to the Controller osgi> 2014-05-30 21:42:50.833 UTC [nioEventLoopGroup-8-2] WARN i.n.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. osgi> I wasn't confident about filing this as one bug vs three different bugs, as well as which component to file it under. Help via Freenode/#opendaylight suggested I file it as one bug and under controller/mdsal, but I'd be happy to move it and/or split it if that turns out to be more appropriate. |
| Comments |
| Comment by Devin Avery [ 03/Jun/14 ] |
|
Some bugs needs to be split into a netconf bug and an openflow bug as the stack traces are in their relatively code bases. ... please break into multiple pieces / Tony / Rob can provide more information if you have questions |
| Comment by Daniel Farrell [ 09/Jun/14 ] |
|
This has been split, per Devin Avery's comment above. The scan of 6633 is now covered by |