On Thu, Jun 06, 2002 at 11:34:18AM -0400, Kunal Trivedi wrote: > > That's because br_pass_frame_up is called from several spots (promisc, bcast, and > > local). That way, if it's not a bcast packet, the pkt_type will survive as > > PACKET_HOST. If it is bcast, it will be replaced with PACKET_BROADCAST. If it > > got there because of promisc, pkt_type gets PACKET_OTHERHOST. Works all around > > ;-) > > Yes, I agree, that br_pass_frame_up is called for promisc, bcast, and > local. But, the questions was, 'If pkt. is bcast pkt., then does it come > back again to bridge code, from net_rx_action ?
skb->dev is set to the BRIDGE device. and net_rx_action will not call bridge hooks for BRIDGE devices, only for ENSLAVED devices. i.e. net_rx_action will not touch it. hth --L _______________________________________________ Bridge mailing list [EMAIL PROTECTED] http://www.math.leidenuniv.nl/mailman/listinfo/bridge
