- DALnet-services - nomad.dal.net

How do or can I join DALNet and get the opportunity to use or utilize the products and/or services?
by Henry Udoye 20 Aug '14

20 Aug '14

-- Henry Udoye. 4165 Whiteplains Road. P. O. Box 1290. Bronx. N. Y. 10466 Phone : 914-316-1854. Fax : 206-350-3803 hudoye1979(a)gmail.com Dear Sir/Madam: If you don’t mind, I visited or went to php.net to get help from php or other code experts and I was referred or ask or advised to visit IRC. Please how do I contact or reach or get in touch with php experts according to or as stated in the paragraph below? How do or can I join DALNet and get the opportunity to use or utilize the products and/or services? Instant Resource Center Otherwise known as IRC or Internet Relay Chat. Here you can usually find experienced PHP people sitting around doing nothing on various channels with php in their names. Note that there is no official IRC channel. Check OFTC <http://oftc.net/> or any other major network (EFNet <http://www.efnet.org/>, IRCNet <http://www.ircnet.com/>, QuakeNet <http://www.quakenet.org/>, IrCQNet <http://www.icq.com/>, DALNet <http://www.dal.net/> and freenode <http://www.freenode.net/>).

1 0

Peering instability betwen Dalnet and Florida Lambda Rail at NOTA in Miami
by Bruce H McIntosh 20 Jun '14

20 Jun '14

We have noted several instances of interruptions in BGP peering betewen Dalnet and Florida Lambda Rail at the NAP of The Americas in Miami. Each time we monitored a loss of peering we attempted to contact Dalnet at the listed contact address on your PeeringDB page: http://www.peeringdb.com/view.php?asn=31800 . We have received no answers to any of our queries about the outages. Is there any information available on the series of peering glitches between our organizations over the past several weeks? Our AS 11096 Our IPv4 198.32.124.143 Your AS 31800 Your IPv4 198.32.124.111 -- ------------------------------------------------------------------------ Bruce H. McIntosh bhm(a)flrnet.edu Senior Network Engineer http://www.flrnet.org Floirda Lambda Rail NOC 352-294-3571

3 2

RE: [DALnet-src] User hostmasking
by Andreas 20 Jul '13

20 Jul '13

I think this should be two different points to review here; - Hiding the real IP/hostnames of users like it's being done on LinkNet and other networks. This would be a good feature for DALnet and Bahamut. - Spoofing of hostnames for regular users, like done in hybrid and on EFNet/LinkNet. This is a bad idea for many of the reasons mentioned by oldcrow. This is already implemented for the trusted parts of users, namely IRC Operators with the regular oper host masking on connects. Perhaps this could be improved to start hiding your host when you oper up instead of when connecting. Regards, Andreas aka ph0x From: dalnet-src-bounces(a)lists.dal.net [mailto:dalnet-src-bounces@lists.dal.net] On Behalf Of oldcrow Sent: Friday, July 19, 2013 8:23 PM Cc: dalnet-src(a)dal.net; dalnet-services(a)dal.net Subject: Re: [DALnet-src] User hostmasking One concern that I would have is for the potential impersonation of representatives from businesses, like PayPal or (in the case of gaming) XBox Live or whatever. If someone could set their hostmask to CSR(a)paypal.com, or support(a)apple.com, it's not difficult to imagine that some users might be fooled into handing over sensitive account information. oldcrow On Fri, Jul 19, 2013 at 2:47 AM, Holbrook Bunting <holbrook(a)dal.net> wrote: (If any of you got this twice, apologies, sent it from the wrong address the first go) So, the idea of user hostmasking was brought up on the dalnet-src@ mailing list a few weeks ago and since we already have the ability in bahamut (via SVSHOST) to have services change a usershostname at anytime, I am thinking why not do this on a global scale? efnet (and others using the same ircd) have the ability to give specific users their own custom host,on a server level, like handing out I:lines. We already have infrastructure setup for management of things in different areas via services (nickname/channel ownership, akill, etc). On a small network I had running, I built into my services a way to allow users to set a "custom" hostname into NickServ done on the nick level, which worked a little like the /ns set url - command. To create a new host for nick xyz (whilst using that nick), I would use; /ns set host some.random.hostname. To turn off that option: /ns set host - To minimise potential abuse, a list of hostmasks would say no you can't set your hostname to havethe word "dalnet" or "staff" or "*.dal.net <http://dal.net/> " in it. If the user tried to set their host to be the same as another users host or ip, it would deny the request. Finally, once a hostname was set, services would not allow them to change the hostname for that nick again for 1 week (unless it was to turn it off). For any other potential abuse problems that someone might cause, there was a kill switch which a CSOp could use to disallow the user from setting a custom host (kinda like freeze), remove any existing host already set. This automated system looked beneficial in that any user could create their own unique hostname without having a bureaucratic system of having a specific team of opers having to grant or deny any request on a one-by-one basis. So, with my system, when does services issue the SVSHOST command (aside from when using /ns set host)? The answer is it would happen when they /identify to their nickname (or another nickname that they aren't currently using) with a separate NOHOST option at the end for if they don't want the host applied at that time. Does a system like this sound of interest to anyone? Does anyone think something like that would be too open for potential abuse? Does anyone have any differing views on how to best setup a user hostmasking system for the network? Thanks,Holbrook aka zort aka srd _______________________________________________ DALnet-src mailing list DALnet-src(a)lists.dal.net https://lists.dal.net/mailman/listinfo/dalnet-src

1 0

User hostmasking
by Holbrook Bunting 20 Jul '13

20 Jul '13

(If any of you got this twice, apologies, sent it from the wrong address the first go) So, the idea of user hostmasking was brought up on the dalnet-src@ mailing list a few weeks ago and since we already have the ability in bahamut (via SVSHOST) to have services change a users hostname at anytime, I am thinking why not do this on a global scale? efnet (and others using the same ircd) have the ability to give specific users their own custom host, on a server level, like handing out I:lines. We already have infrastructure setup for management of things in different areas via services (nickname/channel ownership, akill, etc). On a small network I had running, I built into my services a way to allow users to set a "custom" hostname into NickServ done on the nick level, which worked a little like the /ns set url - command. To create a new host for nick xyz (whilst using that nick), I would use; /ns set host some.random.hostname. To turn off that option: /ns set host - To minimise potential abuse, a list of hostmasks would say no you can't set your hostname to have the word "dalnet" or "staff" or "*.dal.net" in it. If the user tried to set their host to be the same as another users host or ip, it would deny the request. Finally, once a hostname was set, services would not allow them to change the hostname for that nick again for 1 week (unless it was to turn it off). For any other potential abuse problems that someone might cause, there was a kill switch which a CSOp could use to disallow the user from setting a custom host (kinda like freeze), remove any existing host already set. This automated system looked beneficial in that any user could create their own unique hostname without having a bureaucratic system of having a specific team of opers having to grant or deny any request on a one-by-one basis. So, with my system, when does services issue the SVSHOST command (aside from when using /ns set host)? The answer is it would happen when they /identify to their nickname (or another nickname that they aren't currently using) with a separate NOHOST option at the end for if they don't want the host applied at that time. Does a system like this sound of interest to anyone? Does anyone think something like that would be too open for potential abuse? Does anyone have any differing views on how to best setup a user hostmasking system for the network? Thanks, Holbrook aka zort aka srd

4 9

Re: [DALnet-src] User hostmasking
by Holbrook Bunting 19 Jul '13

19 Jul '13

On 19 July 2013 11:22, oldcrow <oldcrow(a)dal.net> wrote: > **One concern that I would have is for the potential impersonation of > representatives from businesses, like PayPal or (in the case of gaming) > XBox Live or whatever. If someone could set their hostmask to > CSR(a)paypal.com, or support(a)apple.com, it's not difficult to imagine that > some users might be fooled into handing over sensitive account information. > ** > Indeed. Under my system: A file contained a list of hostmasks (line by line) which users couldn't pick for a host, so: apple.com - would disallow apple.com but allow uses.apple.com *dal.net - Would deny anything ending in dal.net and so on. Perhaps make that list dynamic with a separate OperServ autokill like command to place temporary/perm bans of changing to certain hosts. The other issue I had considered was multiple people using the same hostname. Under mine, services would not allow them to use: - Someone elses exact hostname (real or with /ns set host) - ipv6 or ipv4 ip address - hostname matching something in the deny list holbrook / zort / srd

1 0

User hostmasking
by Holbrook Bunting 19 Jul '13

19 Jul '13

So, the idea of user hostmasking was brought up on the dalnet-src@ mailing list a few weeks ago and since we already have the ability in bahamut (via SVSHOST) to have services change a users hostname at anytime, I am thinking why not do this on a global scale? efnet (and others using the same ircd) have the ability to give specific users their own custom host, on a server level, like handing out I:lines. We already have infrastructure setup for management of things in different areas via services (nickname/channel ownership, akill, etc). On a small network I had running, I built into my services a way to allow users to set a "custom" hostname into NickServ done on the nick level, which worked a little like the /ns set url - command. To create a new host for nick xyz (whilst using that nick), I would use; /ns set host some.random.hostname. To turn off that option: /ns set host - To minimise potential abuse, a list of hostmasks would say no you can't set your hostname to have the word "dalnet" or "staff" or "*.dal.net" in it. If the user tried to set their host to be the same as another users host or ip, it would deny the request. Finally, once a hostname was set, services would not allow them to change the hostname for that nick again for 1 week (unless it was to turn it off). For any other potential abuse problems that someone might cause, there was a kill switch which a CSOp could use to disallow the user from setting a custom host (kinda like freeze), remove any existing host already set. This automated system looked beneficial in that any user could create their own unique hostname without having a bureaucratic system of having a specific team of opers having to grant or deny any request on a one-by-one basis. So, with my system, when does services issue the SVSHOST command (aside from when using /ns set host)? The answer is it would happen when they /identify to their nickname (or another nickname that they aren't currently using) with a separate NOHOST option at the end for if they don't want the host applied at that time. Does a system like this sound of interest to anyone? Does anyone think something like that would be too open for potential abuse? Does anyone have any differing views on how to best setup a user hostmasking system for the network? Thanks, Holbrook aka zort aka srd

1 0

Re: [DALnet-src] MemoServ msg limits adjustment
by Holbrook Bunting 10 Mar '12

10 Mar '12

As per discussion on irc. The maximum length of a message over irc is 510 characters, that's incuding the sender, command and recipient, thus if you are using say a 30 character nick: :somereallylongnickname PRIVMSG MemoServ(a)services.dal.net :SEND visigoth some message that right there is 76 characters minus the 510 limit, so the max length memo there would be roughly 434 characters. srd On 9 March 2012 16:59, Bradley Claghorn <visigoth(a)mysterial.org> wrote: > I imagine this has probably been requested before, but I am curious to > how people feel these days about the option of having a longer memo > limit. Say, double, like 512 characters instead of 255, or 511. > > Discuss... > > Thank you! > -- > Bradley Claghorn > Visigoth @ IRC > punch.dal.net outpost > _______________________________________________ > DALnet-src mailing list > DALnet-src(a)lists.dal.net > https://lists.dal.net/mailman/listinfo/dalnet-src >

2 1

Channel Mode Request
by PapaSmurf 21 Feb '12

21 Feb '12

Would it be possible to create a new channel mode to disallow channel notices (via Bahamut and ChanServ with mlock)? Popular channels and some help channels are getting bombarded with bots sending channel notices (en mass). If possible, it would be a nice tool to have. Thanks, PapaSmurf

5 4

Bug with ChanServ UNBAN?
by Craig Walder 06 Jun '11

06 Jun '11

Hi there, I just tried to join a restricted channel that I own before identifying to my nick. Obviously, I got banned by ChanServ. My bot sits in this channel for me to test, as well as my main channel. Here is a log of what happened: 1. Firstly, I tried to join the channel before identifying: ========================================== * You were kicked by ChanServ (Sorry, this is a restricted channel.) * Attempting to rejoin channel #yodatest * Unable to join channel (address is banned) ========================================== 2. So as anyone else would, I issue /chanserv unban #yodatest ========================================== -ChanServ- There are no bans against you on #yodatest. * Attempting to rejoin channel #yodatest * Unable to join channel (address is banned) ========================================== 3. Still banned even though there are no bans? I issue a /chanserv invite #yodatest ========================================== * ChanServ (service(a)dal.net) invites you to join #yodatest * Rejoined channel #yodatest * ChanServ sets mode: +o bleepy ========================================== 4. Decide to have a look at the ban list and unban myself: ========================================== * bleepy sets mode: -b *!bleepy(a)*bleepy.org ========================================== 5. Out of interest, I ban myself and then try /chanserv unban again: ========================================== * bleepy sets mode: +b *!bleepy(a)*bleepy.org -ChanServ- There are no bans against you on #yodatest. ========================================== My usermask: bleepy!bleepy(a)bleepy.org I am able to recreate this several times, and it works as above constantly. Regards [ E ] <mailto:bleepy@gmail.com> bleepy(a)gmail.com [ W ] www.bleepy.org This email may contain confidential information intended only for the named addressee(s). If you are not named, you must not retain, print or share any information contained within it.

2 1

Suggestion!
by rugal＠ptcl.net 22 Mar '11

22 Mar '11

Hello! I have a suggestion here about NickServ: Please re-adding the old GCOS code ( full name ) or free space that can be use as description to services. It was allowed in around 1998. But later disable. Regards RuGaL

2 1