Re: dhclient and wpa_supplicant

From: Sam Leffler (sam_at_errno.com)
Date: 07/30/05

  • Next message: Greg 'groggy' Lehey: "Re: Growisofs seg faults with DVD-RAM. Anybody else seen this?" 
    Date: Sat, 30 Jul 2005 14:58:36 -0700
To: Eric Schuele <e.schuele@computer.org>

    Eric Schuele wrote:
    > Sam Leffler wrote:
    >
    >> Eric Schuele wrote:
    >>
    >
    > <big-snip>
    >
    >>> dhclient.conf contains
    >>> ===========================
    >>> interface "ath0" {
    >>> #send option host-name "myhost";
    >>> #send option domain-name "nxdomain.org";
    >>> send dhcp-client-identifier "myhost";
    >>>
    >>> media
    >>> ### Home
    >>> "ssid <home_ssid> mode 11b channel 11 wepmode on weptxkey 1 wepkey
    >>> 0x<home_wepkey>",
    >>> ### Office
    >>> "ssid <office_ssid mode 11b channel 6 wepmode on weptxkey 1 wepkey
    >>> 0x<office_wepkey>";
    >>> request subnet-mask, broadcast-address, routers,
    >>> domain-name-servers, domain-name;
    >>> }
    >>
    >>
    >>
    >> Do not use media statements to setup wireless parameters; this does
    >> not work. You need to run wpa_supplicant and let it identify the
    >> network and setup the key parameters.
    >
    >
    > How do I tell wpa_supplicant about the network media? I had found an
    > older post of yours regarding NOT doing it in dhclient.conf.... but I've
    > found no other way to accomplish it.

    The above dhclient.conf lists media settings that are all handled by
    wpa_supplicant so you don't specify any of them. Specifically you set
    ssid, band, channel, and wep parameters; all these are handled by
    wpa_supplicant.

    The intent is that dhclient deal only with the dhcp protocol and stop
    being involved in the discovery and selection of wireless networks (a
    job wpa_supplicant is better equipped to handle).

    >
    >>
    >>>
    >>> wpa_supplicant.conf
    >>> =============================
    >>> ctrl_interface=/var/run/wpa_supplicant
    >>> ctrl_interface_group=wheel
    >>>
    >>> # Home Network
    >>> network={
    >>> ssid="<home_ssid>"
    >>> scan_ssid=1
    >>> key_mgmt=NONE
    >>> wep_tx_keyidx=0
    >>> wep_key0="<home_wepkey>"
    >>> }
    >>>
    >>> # Office Network
    >>> network={
    >>> ssid="<office_ssid>"
    >>> scan_ssid=1
    >>> key_mgmt=NONE
    >>> wep_tx_keyidx=0
    >>> wep_key0="<office_wepkey>"
    >>> }
    >>>
    >>
    >> Not sure you need scan_ssid set, I'd leave it out.
    >>
    >> If you have problems try disabling auto-startup of ath0 and run
    >> wpa_supplicant by hand with the -d flag to see what it's doing. Once
    >> that's going then enable startup in rc.conf. If you continue to have
    >> problems provide the output wpa_supplicant -d -i ath0 -c
    >> /etc/wpa_supplicant.conf (or similar) when you have trouble. There is
    >> also a pending issue with locating some ap's that are setup to hide
    >> their ssid. If one of the ap's is configured in this way contact me
    >> directly--I've been trying to collect the info I need to identify
    >> what's going on.
    >
    >
    > Both my APs (home and office) hide their ssids. One is a wrt54g (home),
    > the other is linksys as well... though I forget the model at the moment
    > (FWIW its a/b/g). What can I do to provide the info you need?

    These should work; I've had reports of problems with certain Cisco ap's.
      Note however that configuring an ap to hide it's ssid adds no real
    security.

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

  • Next message: Greg 'groggy' Lehey: "Re: Growisofs seg faults with DVD-RAM. Anybody else seen this?"

    Relevant Pages

    • RE: Securing a Local Network
      ... Show the Management of your company the insecurity of the Peer to Peer ... setup and discuss what risks are they willing to accept. ... -Cost of getting the web server and the mail server internally versus having ... -Use an older box for Intrusion Detection on the internal network as well. ...
      (Security-Basics)
    • Re: Client computer wont connect to internet ATTN: Joe Crown
      ... for my host/client setup. ... >When I supported Windows 98 & Windows ME the most common cause of ... >> When I try to connect to the internet using Firefox or Internet ... >> 7) In the Manufacturers box, click Microsoft, in the Network Protocols ...
      (microsoft.public.windowsxp.network_web)
    • Re: Network Connections x 2 PCs
      ... The setup is quite ... >>> If you have a broadband router, run XP's Network Setup Wizard on both ... tell it that the computers connect to the ... >>> If you have a hub, the setup depends on how many IP addresses you get ...
      (microsoft.public.windowsxp.general)
    • RE: Site-to-Site VPN not working
      ... I was looking through my documentation on this setup. ... In ISA on the remote server, add a site-to-site VPN using the name of the ... add a Network Rule called REMOTEOFFICE to route ...
      (microsoft.public.isa)
    • Re: Need help setting up a wireless network btwn 2 computers via router
      ... In fact, insult away as long ... instructions on how to set up this network. ... One is "Network Setup Wizard" and the other is ... "Wireless Network Setup Wizard," will either of these two walk me ...
      (microsoft.public.windowsxp.network_web)