netdev - Re: one more... iproute commands lockup whole system

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 4 Apr 2007 05:11:37 +0300
From:	"Denys" <denys@...p.net.lb>
To:	Patrick McHardy <kaber@...sh.net>, hadi@...erus.ca
Cc:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	netdev@...r.kernel.org
Subject: Re: one more... iproute commands lockup whole system

I think this highly useful feature given by jamal, difficult to be avoided 
from crash, if user not enough experienced in networking(like me). I guess 
packet can be even not ipv4/ipv6 packet, maybe it can be cloned IPX or ARP, 
so TTL field cannot be used. I checked maybe sk_buff have some fields, seems 
also bad luck, if there can be something like "internal" counter for packet, 
how much times it got redirected, it will help. But in my case of VLAN's it 
is really my own mistake and difficult to avoid it. Only bad thing - machine 
got completely locked up, and if it is remote system - it will not oops/or 
reboot even. But i dont have any idea in mind how to avoid this, only than 
big warning in DOC and internal iproute2 help :-)

On Wed, 04 Apr 2007 03:39:12 +0200, Patrick McHardy wrote
> jamal wrote:
> > On Wed, 2007-04-04 at 03:03 +0300, Denys wrote:
> > 
> >>I'm not sure it is mistake or error, but i feel it is dangerous, cause 
> >>commands locking up the system, no kernel panic, no oops, so only 
watchdog 
> >>can save poor server (and not sure this even)
> >>
> >>Commands to lockup system (just i am giving my example, i didnt sort out 
what 
> >>exactly locked up system, i guess redirecting to eth0.5, which is not 
> >>intended for that):
> > 
> > 
> > read:
> > doc/actions/mirred-usage
> 
> Are you refering to "What NOT to do if you dont want your machine to
> crash:"? I think we should make sure users can't even accidentally
> crash their box, so this should at least be caught at runtime.
> I thought the TTL stuff was intended to avoid this ..
> 
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html