Re: FreeBSD 4.9 / VRRP / vlan

From: Spyou (root_at_spyou.org)
Date: 11/28/03

  • Next message: Pawel Malachowski: "Re: FreeBSD 4.9 / VRRP / vlan" 
    Date: Fri, 28 Nov 2003 00:00:01 +0100
To: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl>

    At 23:54 27/11/2003, Pawel Malachowski wrote:
    >On Thu, Nov 27, 2003 at 11:38:40PM +0100, Spyou wrote:
    >
    > > Damn ! The mac address of you vlan (and, i suppose, of you ether card) has
    > > changed ...
    >
    >Ether card MAC and other vlans are unchanged. Thats what we are expecting. :)

    According to your last mail, before you run freevrrpd, your vlan says ether
    00:00:e8:41:cd:10 (probably the mac addr of your eth card)

    After, i see ether 00:00:5e:00:01:01 on your dump ... wich seems to be a
    typical freevrrpd virtual mac address.

    mine stays unchanged before, during and after running freevrrpd (parent
    ether & vlan managed by freevrrpd) .. that's why i was thinking this is a
    problem with the FXP driver ...

    >What version are You running with?

    4.9 right now

    >What says freevrrpd in syslog?

    nothing relevant ..
    When launching :
    Nov 26 23:22:20 f1 freevrrpd[409]: launching daemon in background mode
    Nov 26 23:22:20 f1 freevrrpd[410]: initializing threads and all VRID
    Nov 26 23:22:20 f1 freevrrpd[410]: reading configuration file
    /usr/local/etc/freevrrpd.conf
    Nov 26 23:22:20 f1 freevrrpd[410]: send ip = 10.42.42.42, eth = 0:0:5e:0:1:1
    Nov 26 23:22:20 f1 freevrrpd[410]: server state vrid 1: master

    When killing :
    Nov 26 23:23:42 f1 freevrrpd[410]: restoring real MAC address:
    00:B0:D0:E1:32:D8 for interface fxp1

    Regards,

    _______________________________________________
    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: Pawel Malachowski: "Re: FreeBSD 4.9 / VRRP / vlan"

    Relevant Pages

    • Re: arp-proxy
      ... address allocated by DHCP ... the MAC address for cust1 must never appear as a source MAC ... a broadcast from the service subnet should appear on all customer VLANs ... to the correct customer VLAN ...
      (freebsd-net)
    • Re: arp-proxy
      ... Not a big fan of Linux though. ... >> separate vlan trunked. ... > IIUC, you want to do some kind of NAT of MAC addresses, this is not ... > simple router which has one route for each customer pointing to the ...
      (freebsd-net)
    • RE: Dhcp security
      ... One way "depending on how many clients you are servicing" would be to ... create MAC (layer 2) based reservations, ... MAC reservation). ... aforementioned would be VLAN membership rubbish. ...
      (Focus-Microsoft)
    • Re: 2950 empty mac address table
      ... >>One other VLAN was configured, but no interfaces were bound to it. ... > for the attached switches all look correct? ... > and do the replies have the expected MAC? ... config and full mac tables. ...
      (comp.dcom.sys.cisco)
    • Re: Blocking by MAC Address -
      ... Again an attacker could still bypass 802.1x with this configuration. ... Switch will only see one MAC. ... > the ideia is to change dynamicaly the VLAN of the port. ...
      (microsoft.public.windows.server.networking)