<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>My question is 'how much information can someone pull off of the dhcp device running behind a sole NAT that has been compromised?. As I have been running 2 wifi routers here at this dwelling, Probably alot. no need for scripts apparently the only thing needed is the ip address. So if someone gets the ipaddress of the machine they can track you?<br><br><div>> Date: Mon, 2 Feb 2015 23:37:47 -0600<br>> From: kenlynes@usa.net<br>> To: tclug-list@mn-linux.org<br>> Subject: Re: [tclug-list] tclug-list Digest, Vol 122, Issue 17<br>> <br>> Hey Ryan,<br>> When you were first discussing this sort of issue before I am not sure if you<br>> had been trying to have both of your routers assign dhcp (ip addresses) to the<br>> various network computers etc. I had that problem once and it was pointed out<br>> that only one router should be doing that. Not sure if it had any relevance to<br>> your issue, but thought I would mention it. Otherwise most of this is beyond<br>> my scope a bit.<br>> Ken<br>> <br>> ------ Original Message ------<br>> Received: Mon, 02 Feb 2015 12:00:14 PM CST<br>> From: tclug-list-request@mn-linux.org<br>> To: tclug-list@mn-linux.org<br>> Subject: tclug-list Digest, Vol 122, Issue 17<br>> <br>> > Send tclug-list mailing list submissions to<br>> > tclug-list@mn-linux.org<br>> > <br>> > To subscribe or unsubscribe via the World Wide Web, visit<br>> > http://mailman.mn-linux.org/mailman/listinfo/tclug-list<br>> > or, via email, send a message with subject or body 'help' to<br>> > tclug-list-request@mn-linux.org<br>> > <br>> > You can reach the person managing the list at<br>> > tclug-list-owner@mn-linux.org<br>> > <br>> > When replying, please edit your Subject line so it is more specific<br>> > than "Re: Contents of tclug-list digest..."<br>> > <br>> > <br>> > Today's Topics:<br>> > <br>> > 1. Re: More weird Comcast problems (Ryan Coleman)<br>> > <br>> > <br>> > ----------------------------------------------------------------------<br>> > <br>> > Message: 1<br>> > Date: Mon, 2 Feb 2015 09:06:42 -0600<br>> > From: Ryan Coleman <ryan.coleman@cwis.biz><br>> > To: TCLUG Mailing List <tclug-list@mn-linux.org><br>> > Subject: Re: [tclug-list] More weird Comcast problems<br>> > Message-ID: <3BD429F1-58CB-4D7F-BA60-A55F312D1E37@cwis.biz><br>> > Content-Type: text/plain; charset="utf-8"<br>> > <br>> > That?s overkill? Your signals outside of the superstructure are pointless in<br>> planning.<br>> > <br>> > As for 5GHz stick to the low channels, they don?t do well outside and<br>> they?re underpowered for that purpose. If someone is using those channels<br>> outside they could get nicked by the FCC - it?s not pretty when it happens<br>> (personal experience).<br>> > <br>> > <br>> > > On Feb 2, 2015, at 8:58 AM, Justin Krejci <jus@krytosvirus.com> wrote:<br>> > > <br>> > > Yes and no. It would be nice to coordinate with the neighbors but then<br>> maybe their position puts their new channel that is good for me is now bad for<br>> them or bad for their neighbors further down so if I am gently forcing them I<br>> would feel obligated to travel down the neighborhood doing channel planning.<br>> This is not something I am too keen on doing especially given that my actual<br>> wlan performance is generally fine, particularly given that I mostly use 5ghz<br>> which is mostly quiet in my immediate vicinity. I can only see one neighbor<br>> also using 5ghz so I chose a distant channel from theirs, assuming auto<br>> channel selection is not turned on in their ap; for the last several months<br>> I've never seen them change channels. <br>> > > <br>> > > <br>> > <br>> > -------------- next part --------------<br>> > An HTML attachment was scrubbed...<br>> > URL:<br>> <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20150202/be83f4a1/attachment-0001.html><br>> > <br>> > ------------------------------<br>> > <br>> > _______________________________________________<br>> > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>> > tclug-list@mn-linux.org<br>> > http://mailman.mn-linux.org/mailman/listinfo/tclug-list<br>> > <br>> > End of tclug-list Digest, Vol 122, Issue 17<br>> > *******************************************<br>> <br>> <br>> _______________________________________________<br>> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>> tclug-list@mn-linux.org<br>> http://mailman.mn-linux.org/mailman/listinfo/tclug-list<br></div> </div></body>
</html>