If you really want to split into records with a regex:

/^(BSS.*?)(?=^BSS|\z)/smg

But I don't know why you want the records at all. This format seems easiest to parse line-by-line.

my @essids;
for (qx| sudo iw dev wlan0 scan |) {
   /^\s*SSID:\s*(.*)/ and push @essids, $1;
}

[download]

If you need other information besides the ssid, maybe you can just do something like this:

my @records;
for (qx| sudo iw dev wlan0 scan |) {
  if (/^BSS\s*(.*)/) { push @records, { BSS=>$1 } }
  elsif (/^\s*(\w+):\s*(.*)/) { $records[-1]{$1} = $2 if @records }
}
foreach my $record (@records) {
  print "$record->{SSID}\n";
}

[download]

In reply to Re: more elegant way to parse this? by Anonymous Monk
in thread more elegant way to parse this? by morgon

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.