<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFCC">
<br>
<div class="moz-cite-prefix">On 19/12/12 15:35, Simon Hobson wrote:<br>
</div>
<blockquote
cite="mid:052E7ACEB0F730A82F2EBA743F574FB7@thehobsons.co.uk"
type="cite">
<pre wrap="">perl-list wrote:
</pre>
<blockquote type="cite">
<pre wrap="">bah - that is what I feared. The problem I have is not knowing what will be received at each site (depends on vendor) and hoping to find a solution that works with all to prevent re-configsevery timesomeone somewhere adds some new equipment, and worse yet, matching things in a multi-vendor environment when you aren't sure what will come from where.
</pre>
</blockquote>
<pre wrap="">
Sorry, I don't understand what the problem is.
If you are having to match on <some option> then presumably you have some idea what is in the option. In all cases, if you are using something like "option blah = <something>" then there's no problem. If you expect <something> to look like a string then specify the string in quotes :
option option-82 = "Switch 0 Port 3"
If you expect it to be "non text" then specify it as a hex string :
option option-82 = "00:03" # if, for example, the equipment just sent two octets with switch and port number</pre>
</blockquote>
Shouldn't this be: option option-82 = 00:03 --> no quotes?<br>
<blockquote
cite="mid:052E7ACEB0F730A82F2EBA743F574FB7@thehobsons.co.uk"
type="cite">
<pre wrap="">
This will work with all sites, using a common config format. All it requires is that you put quotes in your database round text values, and not around hex representations.
If this doesn't cover your problem, then perhaps you'd better expand on what your problem is.
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>