egghelp/eggheads community

using mashost/getchanhost

2010-04-09T18:47:03-04:00

The manpages for regexp, regsub and re_syntax (regular expression syntax) would be a good start.

Statistics: Posted by nml375 — Fri Apr 09, 2010 6:47 pm

using mashost/getchanhost

2010-04-09T18:19:52-04:00

Ah.. I didn't see that *. mssing, lol. Thanks so much for your help, you've been so patient with my newbiness. Looks like I really need to study up on regexp/regsub next... are there any pages you would recommend?

Statistics: Posted by Luminous — Fri Apr 09, 2010 6:19 pm

using mashost/getchanhost

2010-04-09T17:33:48-04:00

Then you are not using the code I posted. I did notice another typo in my earlier post, missing a *. in one of the hostmasks... Update posted now...

Statistics: Posted by nml375 — Fri Apr 09, 2010 5:33 pm

using mashost/getchanhost

2010-04-09T17:25:54-04:00

Oh.. no, I hadn't seen your pastebin until now. :\ Okay, I see what you were saying now...

That is still giving me the same mask type though... @*.something.something.

Statistics: Posted by Luminous — Fri Apr 09, 2010 5:25 pm

using mashost/getchanhost

2010-04-09T16:55:27-04:00

Now you've got unbalanced brackets... Did you check my last post on the pastebin?

Let me separate the various components:

Code:

set expression {@.*(\.[[:alnum:]]+\.[[:alnum:]]{2,4})$}set string $hostset option1 -nocaseset option2 --set var1 aset var2 bif {[regexp $option1 $option2 $expression $string $var1 $var2]} {...#the same as this, which is exactly what I posted on the pastebin:if {[regexp -nocase -- {@.*(\.[[:alnum:]]+\.[[:alnum:]]{2,4})$} $host a b]} {}

Obviously, you don't need to put each parameter in a variable, I simply did this to illustrate which part of the command is what... As I've already mentioned, in my later posts I only spoke of the regular expression (pattern), not the whole regexp command. The pattern should NOT include the variable $host, in fact, since it's enclosed with braces {}, there will in fact be no variable substitution (or command substitution for that matter), which further emphasize that you should not add $host to the pattern. As I said, within the pattern the $-sign is used to indicate the end of line, nothing else.

Statistics: Posted by nml375 — Fri Apr 09, 2010 4:55 pm

using mashost/getchanhost

2010-04-09T10:17:54-04:00

I don't understand what to do with $host then... http://paste.tclhelp.net/?id=6gb Adding it anywhere doesn't seem to work...

Statistics: Posted by Luminous — Fri Apr 09, 2010 10:17 am

using mashost/getchanhost

2010-04-09T07:56:03-04:00

No, that dollar-sign is a part of the regular expression, and represents the end of line. In your code, you've removed it, making the pattern match anything containing two to four digits after a dot, anywhere in the string - not the end of it. The $host should not be a part of the pattern, but a separate parameter to regexp.

Statistics: Posted by nml375 — Fri Apr 09, 2010 7:56 am

using mashost/getchanhost

2010-04-09T00:07:00-04:00

I assume there should be a "$host" where $ is... this seems to work so far for normal hosts so far. Wanted to run the script by you and make sure all looked good. There were a few bracket issues I had to work out, hehe: http://paste.tclhelp.net/?id=6fv

Edit: perhaps I did that wrong because it still adds the "scrambled" hosts the same way as it before; retrieving two slots.

Statistics: Posted by Luminous — Fri Apr 09, 2010 12:07 am

using mashost/getchanhost

2010-04-08T16:44:42-04:00

Well, that's because it matches {@[[:alnum:]]+\.[[:alnum:]]+(\..+)}

I'd believe the best way to find a positive match for a real domain, is to look for a valid tld (2-4 alnum characters). Probably something along these lines:
{@.*(\.[[:alnum:]]+\.[[:alnum:]]{2,4})$}

If it matches, it's a "real" hostname, if it does not, it's a "scrambled" one. In the latter, split on . and get the last list item [lindex [split $host .] end]

Statistics: Posted by nml375 — Thu Apr 08, 2010 4:44 pm

using mashost/getchanhost

2010-04-08T16:38:28-04:00

Ah... thanks.

I will fix that.... in the meantime, I have noticed an issue with the regexp...

[!!Me] !voice Rancho
~!~ mode/#mychan [+v Rancho] by Mybot

Address of Rancho is: webchat@d1cf996.23e86861.3682fb09.18377e3cX

Now, when I .match Rancho, I get this:

HANDLE PASS NOTES FLAGS LAST
Rancho no 0 g never (nowhere)
HOSTS: *Rancho*!*@*.3682fb09.18377e3cX
] --- Found 1 match.

That @*.3682fb09.18377e3cX part is a problem, because the 3682fb09 part will change... I need it to be @*.18377e3cX, just the last part, when the address looks like that.

Statistics: Posted by Luminous — Thu Apr 08, 2010 4:38 pm

using mashost/getchanhost

2010-04-08T12:16:18-04:00

I noticed some improper/poor list operations in the code in the pastebin as well, posted an update with corrections and comments..

Statistics: Posted by nml375 — Thu Apr 08, 2010 12:16 pm

using mashost/getchanhost

2010-04-07T19:10:13-04:00

Update: so far, so good. I got to test it on an @*.domain.net type of address earlier. So that part definitely works.

Now that I got this working, my !devoice proc is now valid and I can hopefully get this mode +q simulation trigger to work... I will likely need help with that though, having trouble with the details...

Statistics: Posted by Luminous — Wed Apr 07, 2010 7:10 pm

using mashost/getchanhost

2010-04-07T16:07:43-04:00

Aha, lol. Thank you very much. I'll test it here in a bit, hope it works.

Statistics: Posted by Luminous — Wed Apr 07, 2010 4:07 pm

using mashost/getchanhost

2010-04-07T15:21:21-04:00

Ahh, seems a space got lost in cyberspace...
Add a space between -- and {[... I'll update my post in a sec or two (fix also posted on the pastebin you linked)

Statistics: Posted by nml375 — Wed Apr 07, 2010 3:21 pm

using mashost/getchanhost

2010-04-07T14:40:22-04:00

All right, that all makes pretty good sense, thanks. Here's my updated code. paste.tclhelp.net does complain about that regsub: http://paste.tclhelp.net/?id=6f7

Something else I can try there, I hope?

Will that first regexp actually do what I want? I need one adduser proc that will make a mask like: *nick*!*@*29655c0fX for addresses like someone@3d344119.1377149a.189efabc.29655c0fX and then one that does a more traditional *nick*!*@*.domain.com for others' addresses that do not have just that one last scrambled IP block.

Statistics: Posted by Luminous — Wed Apr 07, 2010 2:40 pm