2011-10-09 - Re: [GRASE-Hotspot] inquiry

Header Data

From: jb <be***s@yahoo.com>
Message Hash: 71ae709b7b5059442d9e0a6267ca5b7acfe885a961708fa50ae3dcaf8184ee56
Message ID: <1318215828.95476.YahooMailClassic@web110214.mail.gq1.yahoo.com>
Reply To: <1317978354.97400.YahooMailNeo@web161405.mail.bf1.yahoo.com>
UTC Datetime: 2011-10-09 20:03:48 UTC
Raw Date: Sun, 09 Oct 2011 20:03:48 -0700

Raw message

win 7 clients still cant access..even after regedit editing..

xp clients no problems logging in...



--- On Fri, 10/7/11, tim storey <ts***s@yahoo.com> wrote:

From: tim storey <ts***s@yahoo.com>
Subject: Re: [GRASE-Hotspot] inquiry
To: "GRASE Hotspot General Discussions" <gr***t@lists.sourceforge.net>
Date: Friday, October 7, 2011, 5:05 PM

Hi JB
I had a similar problem with a previous hotspot ATM and Windows Vista clients. The issue was actually a known Vista bug, to do with the "DHCP Broadcast flag" in the registry. This is resolved by applying a patch from MS, or manually tweaking the registry.A quick google search on the same issue for win 7 indicates that it is still a fairly widespread issue with win 7 clients.
Check out the following link for more info:http://blogs.technet.com/b/teamdhcp/archive/2009/02/12/dhcp-broadcast-flag-handling-in-windows-7.aspx
The next
 link makes reference to a cisco-related issue with a possible solution:http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/b50d628f-43c1-420f-884f-a09594517d30/

I hope this helps.
Tim S.
From: jb <be***s@yahoo.com>
To: GRASE Hotspot General Discussions <gr***t@lists.sourceforge.net>
Sent: Friday, October 7, 2011 5:59 AM
Subject: Re: [GRASE-Hotspot] inquiry


hi tim,

we're using cisco home wireless routers with dhcp disabled...windows xp clients can
connect successfully..the grase server has been working for us for more than 3 months
now and this is the first time that we encountered this problem.

i set my primary dns in /etc/resolv.conf...im using ubuntu 10.10 server edition..i have not
edited /etc/chilli/config...but i checked the config, this is the entry:

# OpenDNS Servers
#HS_DNS1=208.67.222.222
HS_DNS2=208.67.220.220
HS_DNS1=10.1.0.1


what could be the error with this?

thank you,

jb



--- On Fri, 10/7/11, Timothy White <ti***8@gmail.com> wrote:

From: Timothy White
 <ti***8@gmail.com>
Subject: Re:
 [GRASE-Hotspot] inquiry
To: "GRASE Hotspot General Discussions" <gr***t@lists.sourceforge.net>
Date: Friday, October 7, 2011, 10:16 AM

This sounds odd.If it's only happening to win7 clients that's even stranger.
You don't have any dhcp-relay style devices do you? (Routers that relay the dhcp to the hotspot).
It should be getting 10.1.0.1 for dns, plus a opendns server. I'll be releasing some changes shortly that force the clients to all use 10.1.0.1 which will be the hotspot, which will have dnsmasq on it and they you can configure dnsmasq to point to the right name servers. When you say you have set primary dns to opendns, where have you set that? If you change it in /etc/chilli/config it should hand them out via dhcp correctly.

Tim
On Thu, Oct 6, 2011 at 11:56 AM, jb <be***s@yahoo.com> wrote:

hi tim,

i just would like to inquire from you. every time a client connects to wireless or wired connection to the grase server, the assigned DNS to the client would be 192.168.254.254.

my primary DNS set up in the server is from OpenDNS which is 208.67.222.222..

what could be the problem?
thanks

jb

------------------------------------------------------------------------------


All the data continuously generated in your IT infrastructure contains a

definitive record of customers, application performance, security

threats, fraudulent activity and more. Splunk takes this data and makes

sense of it. Business sense. IT sense. Common sense.

http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________

Grase-hotspot mailing list

Gr***t@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/grase-hotspot





-----Inline Attachment Follows-----

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
-----Inline Attachment Follows-----

_______________________________________________
Grase-hotspot mailing list
Gr***t@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/grase-hotspot

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Grase-hotspot mailing list
Gr***t@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/grase-hotspot



-----Inline Attachment Follows-----

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
-----Inline Attachment Follows-----

_______________________________________________
Grase-hotspot mailing list
Gr***t@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/grase-hotspot

Thread