I'm not trying to help you not upgrade but my 4.9 box says Starting Nmap 5.21 ( http://nmap.org ) at 2012-01-24 15:13 CST Failed to resolve given hostname/IP: 10.20.0. Note that you can't use '/mask' AND '1-4,7,100-' style IP ranges WARNING: No targets were specified, so 0 hosts scanned. Nmap done: 0 IP addresses (0 hosts up) scanned in 0.13 seconds
I'm pretty sure what you're giving nmap is invalid in your old version too, so unless this is an excercise in interesting ways to crash old software, I'd check my nmap input, in addition to upgrading my box. On Tue, Jan 24, 2012 at 2:32 PM, goodb0fh <[email protected]> wrote: > Doc, > It hurts when I do that... > > Sent from my iPhone > > On Jan 24, 2012, at 1:27 PM, Philip Guenther <[email protected]> wrote: > > > On Tue, Jan 24, 2012 at 10:35 AM, R0me0 *** <[email protected]> > wrote: > >> It is a GENERIC kernel, the name is only copy of GENERIC.MP :) . As I > said, > >> it is a complex setup and I'm planning an upgrade. > > > > Well, you're doing the right thing. There have been *MANY* fixes to > > the network stack since 4.4, so updating to 5.0 as you plan is very > > very likely to resolve it. > > > > I'm not sure, though, if you're looking for something besides > > encouragement in doing that. With no information from the crash, > > there's no way anyone can say "oh yeah, that was fixed in version > > 4.x", and even with that information it would just serve to confirm > > that you should do what you're already planning on doing and should do > > for other reasons. Even if it was a completely new bug and the crash > > trace proved it, the volume of changes in the code between 4.4 and > > current is such that reproducing it on a -current setup would be the > > first step... > > > > So, are you looking for something else? > > > > > > Philip Guenther
