Re: Help Broadcasting a UDP packet on the LAN:URGENT

From: Charles Swiger (cswiger_at_mac.com)
Date: 10/23/03

  • Next message: Barney Wolff: "Re: Help Broadcasting a UDP packet on the LAN:URGENT" 
    Date: Thu, 23 Oct 2003 15:39:53 -0400
To: net@freebsd.org

    On Thursday, October 23, 2003, at 02:45 PM, Wes Peters wrote:
    >> The all-ones broadcast is supposed to go to all physically connected
    >> network segments, regardless of whether a particular interface is
    >> ifconfig'ured with an IP that is part of a particular layer-3 subnet.
    >> You should be able to send the broadcast packet out from an interface
    >> which is up but does not have an IPv4 address assigned, right?
    >
    > So long as it IS configured with the IPv4 protocol, I'd say yes. Ditto
    > for VLANs.

    Agreed.

    Some switches use a VLAN tag of 0 to indicate a "default VLAN", so it
    perhaps might be reasonable to select that rather than all of the
    logical VLAN interfaces configured against a physical parent interface.
      However, if the capability of choosing which interfaces should
    participate in the "all ones group" is already in Bruce's code, then
    that same mechanism could also be used to manage which VLAN interfaces
    get used.

    Also, Barney's comments here:

    > On point-to-point, I've never been really happy that the two ends can
    > have addresses in different nets, but some people do it that way.
    > I always prefered to define a /30 (or /31 if the code allows) for the
    > link itself. But that difference solves the issue of whether the p2p
    > link should be treated as local or not - if the far end is on a
    > different subnet, it's remote; same subnet, it's local.

    ...make sense to me as well, for whatever that may be worth.... :-)

    Take care, 

    -- 
-Chuck
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
  • Next message: Barney Wolff: "Re: Help Broadcasting a UDP packet on the LAN:URGENT"

    Relevant Pages

    • Cisco 877w: Fa0-3 Interfaces up but no traffic passes
      ... Data Vlan101 only, no voice vlan required, WPA ... output errors, 0 collisions, 0 interface resets ... switchport trunk native vlan 101 ... bridge-group 101 subscriber-loop-control ...
      (comp.dcom.sys.cisco)
    • Re: Need help adding device to new vlan
      ... The vlan 99 ... - If I assign an ip address to the vlan 199 interface, ... switchport trunk encapsulation dot1q ... switchport trunk allowed vlan 40,51,99,199,997,998 ...
      (comp.dcom.sys.cisco)
    • Re: 2600 router + 2924 switch and vlans
      ... I can route from a port ... assigned to the def vlan, but not from any port assigned to vlan 2 ... interface FastEthernet0/0 ... switchport trunk encapsulation isl ...
      (comp.dcom.sys.cisco)
    • Need help adding device to new vlan
      ... The vlan 99 ... - If I assign an ip address to the vlan 199 interface, ... switchport trunk allowed vlan 40,51,99,199,997,998 ... no ip proxy-arp ...
      (comp.dcom.sys.cisco)
    • Re: kern/109815: wrong interface identifier at pfil_hooks for vlans + if_bridge
      ... It is cleared when an mbuf chain is passed to another entity which may consume the frame in that mbuf chain, in case the entity re-enters ether_inputwith the same mbuf chain for local delivery (e.g. bridge, netgraph, vlan). ... "logical" interface. ...
      (freebsd-net)