So today has been somewhat of a long day. The girlfriend has been over going through all of my things in preparation of us moving in together. And by going through my things, I mean, me begging to keep things so they aren't thrown out.
But in the meantime, I have been really having some issues with getting this VM of Windows Server 2003 setup. I'm using VMWare to run the guest VM. My host OS is Windows 7 Ultimate x64. Everything seems to be running fine, but for the life of me, I cannot get this VM to maintain a connection to the internet.
The way the networking is currently setup at my place, is upstairs in the house I am in, is where the cable modem is located. Currently (although only for 1 more month) I live in the basement. I have two routers in this house. One router is a standard WRT54G router broadcasting the internet. The router in the basement is flashed with DD-WRT acting as a repeater bridge. My desktop is connecting to the repeater bridge for internet. There is no DHCP server running on the repeater bridge, so any machine connecting to that needs to have a statically assigned IP address.
My host machine is able to connect to the internet fine. However, the VM just keeps losing connectivity after 5 minutes or so. It's currently setup as having a bridged connection, and this is where it is losing its connectivity. However, this is odd, whenever I setup the VM to have NAT networking, the VM does not have any connectivity at all.
This isn't making sense to me. I could understand that incoming connections would have issues and not connect to the VM, but all outgoing connections from the VM should go through. I've also tried setting up another laptop to connect wirelessly, and then share its connection with an ethernet cord, and that does not work either. All the same issues.
For the time being, looks like I will only be able to update this very slowly. Hopefully the new networking (where I have direct access to the network) environment when I move to my new place will help solve this issue. Any ideas on the current situation though? Let me know.
Sunday, January 31, 2010
Saturday, January 30, 2010
TCL Me Silly
So today has been a debugging day for myself it seems. I help run a couple channels on IRC. Or really, the bots that I manage run it. On the bots, I have a couple of scripts running that help to make the channel management easier. All scripts are written in tcl. These scripts help manage FAQs, key word triggering, and managing ops, voiced users, etc.
Now anyone who is on IRC knows that there are many types of bots that can be and are used to help manage channels. These bots that are currently being used (and running these scripts) are eggdrops. The one script in question is for managing oped users, voiced users, and the actions that they can perform.
The way eggdrops work (if you don't know) is you can set flags for users. For example, if a user is an operator, you can give them the +o flag (attribute). If a user is voiced, you can give them the +v flag. One basic check that the script should be performing, is that opped users should be able to kick voiced users from a room, but not the other way around.
I'll give you one guess as to what I'm trying to debug.
So, since voiced users do somehow have the ability I'm trying to figure out why. I've also narrowed down that it seems to only be happening in this one specific channel, and I think I just discovered why.
When you set flags for the user in the bot, you can set them on two different levels. You can set a flag (like +o) on a per channel level (where the flag is only for that channel) or on a global level. So what's happening, is the script is doing a check on the user's (who is being kicked) flags. It also compares those flags to the flags of the "kickee".
In this channel specifically, I've set the flags for the operators at the channel level, not the global level, and I think that is why this issue is happening. When the script does the check on the flags, it is doing a check on the global flags for the user being kicked, not at the channel level. Since the opped users in here have their flags set at the channel level, not global level, the script isn't seeing the "o" flag. It then thinks it is not set, and then kicks and bans the user from the specified channel.
So, right now, it looks like my (hopefully temporary) work around is that I have to set the flags at the global level for the ops so that they do not get kicked. In the meantime, I have to try to figure out how to make the script also check on the channel level.
Here is the script that I am working on at the moment. If anyone happens to be great with tcl, or even better, a guru with eggdrop scripting, take a look at it and let me know if you know how to make it do a channel check.
Now anyone who is on IRC knows that there are many types of bots that can be and are used to help manage channels. These bots that are currently being used (and running these scripts) are eggdrops. The one script in question is for managing oped users, voiced users, and the actions that they can perform.
The way eggdrops work (if you don't know) is you can set flags for users. For example, if a user is an operator, you can give them the +o flag (attribute). If a user is voiced, you can give them the +v flag. One basic check that the script should be performing, is that opped users should be able to kick voiced users from a room, but not the other way around.
I'll give you one guess as to what I'm trying to debug.
So, since voiced users do somehow have the ability I'm trying to figure out why. I've also narrowed down that it seems to only be happening in this one specific channel, and I think I just discovered why.
When you set flags for the user in the bot, you can set them on two different levels. You can set a flag (like +o) on a per channel level (where the flag is only for that channel) or on a global level. So what's happening, is the script is doing a check on the user's (who is being kicked) flags. It also compares those flags to the flags of the "kickee".
In this channel specifically, I've set the flags for the operators at the channel level, not the global level, and I think that is why this issue is happening. When the script does the check on the flags, it is doing a check on the global flags for the user being kicked, not at the channel level. Since the opped users in here have their flags set at the channel level, not global level, the script isn't seeing the "o" flag. It then thinks it is not set, and then kicks and bans the user from the specified channel.
So, right now, it looks like my (hopefully temporary) work around is that I have to set the flags at the global level for the ops so that they do not get kicked. In the meantime, I have to try to figure out how to make the script also check on the channel level.
Here is the script that I am working on at the moment. If anyone happens to be great with tcl, or even better, a guru with eggdrop scripting, take a look at it and let me know if you know how to make it do a channel check.
Friday, January 29, 2010
In the Words of Bill Gates
"Hello World"
I've been thinking about documenting everything that I do with technology. Regardless if people read this, it will be a good source for myself to reference when it comes to problems/issues/anything I've done in the past that I'm doing at the time. I think this could be a good resource for many people.
To give a little info on myself, I am currently a Systems Administrator in a Windows environment for a large company. I love my work. I love being hands on with technology. I couldn't do anything different.
I'm also a pretty big gamer. At the moment, I currently have a Xbox 360, Xbox, Playstation 3, Nintendo Wii, and Nintendo DS Lite. All have been hacked and modified in one way or another, except for the PS3. But hopefully, that will be coming soon (will be a future article).
I enjoy collaborating with people to work on projects. I'm active on IRC, forums, and many other mediums. I think the point of this blog will be to just talk about what I'm doing when it comes to hacking consoles, setting up servers, installing services, creating networks, and really, just anything technology related.
I'd love to hear any and all input, thoughts, and anything else you want to send my way. But for now, I'll call it a night. I'm looking forward to keeping this going.
I've been thinking about documenting everything that I do with technology. Regardless if people read this, it will be a good source for myself to reference when it comes to problems/issues/anything I've done in the past that I'm doing at the time. I think this could be a good resource for many people.
To give a little info on myself, I am currently a Systems Administrator in a Windows environment for a large company. I love my work. I love being hands on with technology. I couldn't do anything different.
I'm also a pretty big gamer. At the moment, I currently have a Xbox 360, Xbox, Playstation 3, Nintendo Wii, and Nintendo DS Lite. All have been hacked and modified in one way or another, except for the PS3. But hopefully, that will be coming soon (will be a future article).
I enjoy collaborating with people to work on projects. I'm active on IRC, forums, and many other mediums. I think the point of this blog will be to just talk about what I'm doing when it comes to hacking consoles, setting up servers, installing services, creating networks, and really, just anything technology related.
I'd love to hear any and all input, thoughts, and anything else you want to send my way. But for now, I'll call it a night. I'm looking forward to keeping this going.
Subscribe to:
Posts (Atom)