Did anyone ever find out about this wargame computer? I want to try my had at it :-) But, im not going to be trapped in a honeypot either. Muahahahaha
Printable View
Did anyone ever find out about this wargame computer? I want to try my had at it :-) But, im not going to be trapped in a honeypot either. Muahahahaha
Personally I don't want to participate in something that just seems suspicious. I'm not saying it's not for real or anything, I'm just saying that I'd rather play it safe.
I simply find the fact that wargame.mine.nu is actually an AOL computer to be somewhat alarming. You'd think that you would at least use a "real" server rather than dyndns for a wargame... that, and there is always a possibility that someone has set up a DNS entry that they control so that it would point to a machine that isn't theirs...
Come to think of it, wouldn't it be possible for someone in control of the right servers to set it up so that any requests to HTTP ports would be taken care of by one computer, but all else would be sent to a victim? I can't think of anything foolproof that could be used to create that effect at the moment... Hmm... communication between network monitor and DNS server... telling it when to route what based on past recieved packets to certain ports... hmmm. Then you have any local cache problems... bleh. I'm too tired to muse about it at the moment.
I think this could probably be done quite simply with a router. You can set a router to say port 80 goes to 192.168.1.10, port 23 goes to 192.168.1.5, port 25 goes to 192.168.1.15, and so on. So couldn't you just say, port 80 goes to 192.168.1.10, else go to xxx.xxx.xxx.xxx (victim). With the router performing NAT, I believe it would still appear transparent to everyone else....Quote:
Come to think of it, wouldn't it be possible for someone in control of the right servers to set it up so that any requests to HTTP ports would be taken care of by one computer, but all else would be sent to a victim? I can't think of anything foolproof that could be used to create that effect at the moment... Hmm... communication between network monitor and DNS server... telling it when to route what based on past recieved packets to certain ports... hmmm. Then you have any local cache problems... bleh. I'm too tired to muse about it at the moment.
Question.....this may sound dumb, but, I work supporting cable and dsl connections.....Please clear something up for me. If you use a router, how would you set up the router to send info to one ip. Is that the same thing as port forwarding? I think it is, but i just want to clear the waters up a little bit :-)
Yes....Quote:
Is that the same thing as port forwarding?
You have to use it if your network uses unrouteable IP addys (NAT). Same thing though...
doh gotta read these posts more often sounds like this was kinda fun!!
lol, it got kinda hairy after {p2p} and others found something fishy about it, some are trying it, others are not. I am leaning on the side of caution, and am not gonna try it cuz if AOL does indeed not allow it, I do not wanna be on their **** list.Quote:
doh gotta read these posts more often sounds like this was kinda fun!!
thnx soulman
I was thinking of something different, but it's not workable or important enough to elaborate on. :)Quote:
Originally posted here by souleman
I think this could probably be done quite simply with a router. You can set a router to say port 80 goes to 192.168.1.10, port 23 goes to 192.168.1.5, port 25 goes to 192.168.1.15, and so on. So couldn't you just say, port 80 goes to 192.168.1.10, else go to xxx.xxx.xxx.xxx (victim). With the router performing NAT, I believe it would still appear transparent to everyone else....