Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 May 2007 12:15:18 +1000
From:      "Murray Taylor" <>
To:        "Gunther Mayer" <>, <>
Subject:   RE: Spaces in SSID in /etc/rc.conf
Message-ID:  <04E232FDCD9FBE43857F7066CAD3C0F12DF4B1@svmailmel.bytecraft.internal>

Next in thread | Raw E-Mail | Index | Archive | Help

> -----Original Message-----
> From:
> [] On Behalf Of=20
> Gunther Mayer
> Sent: Tuesday, 15 May 2007 5:46 AM
> To:
> Subject: Spaces in SSID in /etc/rc.conf
> Hi there,
> I got a low key server who is wirelessly connected to the net=20
> using an=20
> SSID that contains a space. In rc.conf I define the ifconfig line for=20
> configuration of my wireless interface upon bootup, but the=20
> entire line=20
> reads something like
> ifconfig_ath0=3D' inet ssid "my network" '
> No matter how I tweak the quotes (single then double, other=20
> way round,=20
> with lots of \\) I never get my interface to configure properly upon=20
> bootup and I need to get to the console to fix it up. I=20
> thought I knew=20
> shell syntax but this is beyond me or manpages...
> What's the right way to do this?
> Gunther

Have you tried this (I havent, its just a suggestion)...

I use this construct to get around scp transfers and the
file names windoze users love to create with heaps of spaces...

ifconfig_ath0=3D' inet ssid "my\ network" '

If there are multiple spaces then you need to slash each one, i.e.

> ifconfig_ath0=3D' inet ssid "my\ \ network" '

Give it a shot ;-)

The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material.=20

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.

### This e-mail message has been scanned for Viruses by Bytecraft ###

Want to link to this message? Use this URL: <>