Re: More dhclient gayness

From: Mateusz Jędrasik (imachine_at_toya.net.pl)
Date: 07/26/05

  • Next message: Yamada Ken Takeshi: "firefox 1.0.6 on -current crashes"
    To: freebsd-current@freebsd.org
    Date: Tue, 26 Jul 2005 14:03:01 +0200
    
    

    Dnia wtorek 26 lipca 2005 02:29, Mike Jakubik napisał:
    > xl0: link state changed to UP
    > DHCPREQUEST on xl0 to 255.255.255.255 port 67
    > DHCPREQUEST on xl0 to 255.255.255.255 port 67
    > DHCPACK from x.x.x.1
    > bound to x.x.x.195 -- renewal in 43200 seconds.
    > xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    > options=9<RXCSUM,VLAN_MTU>
    > inet x.x.x.195 netmask 0xffffff80 broadcast x.x.x.255
    > ether 00:01:03:d4:4c:07
    > media: Ethernet autoselect (100baseTX <full-duplex>)
    > status: active
    > Creating and/or trimming log files:.
    > Starting syslogd.
    > Additional routing options: IP gateway=YES.
    > Starting devd.
    > dhclient xl0: already running?
    > Mounting NFS file systems:.
    >
    > ---
    >
    > Why is dhclient being run again? Can someone tell me why this openbsd
    > version was brought in anyways? The old one worked just fine, this seems
    > like yet another reinvention of a wheel, and a broken one at that.
    >

    I have a very similar issue on 6.0-BETA, it starts once, then again during the
    boot process similarly at the same place You mentioned, with
    ifconfig_fxp0="DHCP" in rc.conf.

    Eh. ;-)

    Btw, is it possible to have two interfaces? I have w wi0 and fxp0 card, the
    wi0 being dynamically switchable on or off with a switch on the laptop's
    side. I would ideally like both of them to do DHCP, however, first trying the
    currently working/available interface - that is, fxp0 - then, if the fxp0
    link goes down, and nothing is up, cancelling the DHCP request, later, when
    the wi0 gets switched ON, FreeBSD automatically picking up DHCP from the
    associated wireless network - is that possible, without manually needing to
    start DHCP every time?

    Cheers,

    /m.
    > _______________________________________________
    > freebsd-current@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-current
    > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

    -- 
    Mateusz Jędrasik
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    

  • Next message: Yamada Ken Takeshi: "firefox 1.0.6 on -current crashes"

    Relevant Pages

    • Re: (OT) vlans and cisco switches and dhcp to my system
      ... You can configure the dhcp server to ... separate VLAN despite the proper address being "passed through" to the ... were port-specific on the switch. ...
      (Ubuntu)
    • Re: 802.1x howto ias computer only authentication
      ... Windows XP because no dhcp can be found. ... User authentication based on certificates works ok but thats not ... access permission by your remote access policy. ... the way the 802.1X switch works is to ...
      (microsoft.public.internet.radius)
    • Re: DHCP Strangest Problem I ever Seen in my life
      ... What you describe is classic behavior of spanning tree being enabled on the ... Every last time I've seen this behavior it was a switch issue, ... 168455 - DHCP Renewal Failures on Switched Networks ...
      (microsoft.public.win2000.networking)
    • Re: Event ID 1003 -> DHCP problem
      ... I don't think it's switch related, because it's the external nic that's ... this is an expected behavior while DHCP Client failed to ... Considering your scenario that the affected network adapter is ... I suggest that you replace the external network adapter on the SBS ...
      (microsoft.public.windows.server.sbs)
    • Re: Multiple access points to flood an area.
      ... But yes, in general, you put an access point where you want coverage and run wire back to the switch. ... It has been chosen because the native IP range 192.168.0.X of the D-Link does not overlap the 192.168.1.X IP address range of the router built into the 2WIRE2701 modem (wireless option disabled) ... They can be on the same subnet, just make one of the run DHCP and disable it on the other. ...
      (alt.internet.wireless)