Re: --resend-on-iif status

> If I get it right, bridge code doesn't send packets back to same physical
> interface, which is ok for most of cases but alas not for wireless,

I am also interested in this issue for the madwifi driver.  Currently, the
driver does packet rebroadcasting between STAs within the driver, bypassing
the kernel bridging code (eg. bridge_packets 1 always).  It would be nice to
have some way for the bridge code and the wireless driver code to coordinate
who is supposed to resend the packets and such.  If Bart is willing to
implement and publish the recommended method for doing this coordination, I
can create a patch for the madwifi driver and submit it.

> +inline int isWlan(char *ifname) {
> +  char *c = ifname + 4;
> +  if (ifname == NULL) return 0;
> +  if (strncmp(ifname, "wlan", 4)) return 0;
> +  while (*c) {
> +    if ((*c < '0') || (*c > '9')) return 0;
> +    ++c;
> +  }
> +  return 1;
> +}

It seems to me that detecting interfaces by name is a Very Bad Idea.  There
should be (if there is not already) a way to detect wireless devices without
relying on the device name.  The wireless extension code manages.

-- 
I used to think I was a child; now I think I am an adult -- not because
I no longer do childish things, but because those I call adults are no
more mature than I am.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAkDAe8cACgkQFMm9uvwPXW7e+wCeLVMZhL9LhKQMhhUazpqT1NcG
cQ0AnjpK8P4erRszO0SBk18f0bFYhMGd
=bi/R
-----END PGP SIGNATURE-----