Not that anyone appears to have ever cared about this. But it's only a small problem with IO::Socket. I read in Lincoln Stiens book that IO::Socket will handle the hard part of setsockopt for you, that is, the packed part. So Technically you could proably do
$socket->sockopt("25", pack("Z*", "eth0"));
Still though, the sockopt should fail when done the easier way. I've patched IO::Socket;
sub SO_BINDTODEVICE{25};
+ if(exists $arg->{Interface}){
+ my $unit = $arg->{Interface};
+ my $int = pack("Z*",$unit);
+ setsockopt($sock,SOL_SOCKET,SO_BINDTODEVICE,$int)|| die "er
+ror $!\n";
+ }
Or whatever, it just gives you the option of giving interface as an arg much like Net::Ping does. I'm sure it's not useful to most of the world. Remember your milage may vary as SO_BINDTODEVICE is platform specific int as far as i know.
I've also begun to document setsockopt pack formats. If anyone knows if this has already been done i'd greatly appreciate it.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.