https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226688
--- Comment #5 from Dave Eckhardt <de0u+fbb...@andrew.cmu.edu> --- (In reply to Rodney W. Grimes from comment #4) I agree that workarounds are possible. For example, if some values won't fit into a table, it is possible to handle those values via a separate rule check. But firewall rule systems are hard enough to understand if they work the way they are documented as working. Random misbehaviors, even if survivable, make the system much harder to understand. Again please see bug #180731 which is a different problem with the same "odd" value (it seems as if on amd64 machines you can get the value into the table but you can't see it once it's there). I guess I would argue against closing either bug, on the grounds that it/they might make a nice starter project for somebody looking to do serious work on ipfw. Thanks for looking at my report so quickly! -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-ipfw@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ipfw To unsubscribe, send any mail to "freebsd-ipfw-unsubscr...@freebsd.org"
