2011-06-29 - [GRASE-Hotspot] Error Connection

Header Data

From: Jesse Cofie <bo***d@gmail.com>
Message Hash: 6ee79c38daf63ee40d3049a254c2050f215db808e138e2e9bac415b72495d8a4
Message ID: <BANLkTik-Yu0k-bRet0FFZ6oRasnzRf52rQ@mail.gmail.com>
Reply To: N/A
UTC Datetime: 2011-06-29 05:05:49 UTC
Raw Date: Wed, 29 Jun 2011 12:05:49 +0000

Raw message 

Hello everyone,

I installed the Bazaar frontend for Fedora and am trying to connect to the
Branch source and I keep getting this error(using the checkout command):


Run command: bzr checkout --lightweight
http://grase.bzr.sourceforge.net/bzr/grase/grase-www-portal/ /home/Agent089

bzr: ERROR: Connection error: Couldn't resolve host '
grase.bzr.sourceforge.net' [Errno -2] Name or service not known


What could be the problem? What's the fix?



I also get this error when i use the branch command:

Run command: bzr branch
http://grase.bzr.sourceforge.net/bzr/grase/grase-www-portal//home/Agent089/grase-www-portal
--revision 132 --use-exi...

bzr: ERROR: Server sent an unexpected error: ('error', 'No repository
present: "chroot-334421648:///"')


On Tue, Jun 28, 2011 at 4:20 AM, <
gr***t@lists.sourceforge.net> wrote:

> Send Grase-hotspot mailing list submissions to
>        gr***t@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.sourceforge.net/lists/listinfo/grase-hotspot
> or, via email, send a message with subject or body 'help' to
>        gr***t@lists.sourceforge.net
>
> You can reach the person managing the list at
>        gr***r@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Grase-hotspot digest..."
>
>
> Today's Topics:
>
>   1. DNS fix proposal (Timothy White)
>   2. Re: DNS fix proposal (Timothy White)
>   3. problem with admin login (????? ??????)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 26 Jun 2011 20:18:49 +1000
> From: Timothy White <ti***8@gmail.com>
> Subject: [GRASE-Hotspot] DNS fix proposal
> To: GRASE Hotspot <gr***t@lists.sourceforge.net>
> Message-ID: <BANLkTinUH=1p-hq2cKU5SYCUF=qu***Q@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I've realised that a component I took out of the hotspot system before
> releasing it to the public last year, probably needs to be added back
> in.
> Simply, dnsmasq.
>
> Currently the coovachilli config file gives out 2 IP's for DNS, one is
> an OpenDNS one, and the other is 10.1.0.1 which will timeout if the
> server doesn't have a DNS server as well. I don't want to go back to
> OpenDNS (as I don't aggree with their idea of redirecting NX to their
> search page).
> What I am going to do is have both DNS's ips (because coovachilli
> needs 2) to point to 10.1.0.1 and depend on dnsmasq. Through a simple
> script we can allow the admin to change which dns servers dnsmasq
> looks at by writing a file to /etc/dnsmasq.d/ with the server=x.y.z.a
> lines as required.
> The default options that I'll install with grase-www-portal will include:
> * strict-order so that the computers default dns (as in
> /etc/resolv.conf) will be tried first
> * server=opendnsipaddress
> * server=googlednsipaddress
> * bogus-nxdomain=x.y.z
>
> What this will do is allow us to try the users default dns server
> first (need for example here on an iinet connection to ensure freezone
> traffic is actually free). Failing that we can try OpenDNS and Google
> DNS without them redirecting NX to their search page (the
> bogus-nxdomain stuff). What it'll also allow us to do, is have the
> hotspot write another file that will be loaded before the defaults, so
> that the admin can override the options with their own server= lines
> (i.e. OpenDNS Family Filter) and with no-resolv to not use the default
> DNS provided by the system.
>
> The only issue I can see currently is if the admin wants to run
> another DNS server on the machine as well. We can tell dnsmasq to only
> bind to the coova chilli interfaces, however I'm inclined to add that
> option commented out and leave it to the system admin to uncomment it
> if they wish to run another DNS server as well.
>
> Any thoughts on all of this? Using dnsmasq may also open up the door
> for Layer 3 coovachilli, however until such a time that I need Layer 3
> coova chilli, I'm probably not going to work on it.
>
> All thoughts are welcomed. If people object to using OpenDNS or Google
> DNS as fallbacks, please speak up.
>
> Tim
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 26 Jun 2011 21:45:48 +1000
> From: Timothy White <ti***8@gmail.com>
> Subject: Re: [GRASE-Hotspot] DNS fix proposal
> To: GRASE Hotspot <gr***t@lists.sourceforge.net>
> Message-ID: <BANLkTi=c3***Q@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Following up more on this. I'm probably going to implement an
> interface to the blacklists maintained at
> http://cri.univ-tlse1.fr/blacklists/index_en.php (and any others
> people nominate) to allow us to use both dnsmasq as a dns blacklister,
> and squidguard as a url blacklister.
>
> Suggestions are welcome for more blacklists and filtering ideas. (i.e.
> I'm even thinking of writing a custom squid redirector that looks up
> domains on a variety of "dns blacklists" that aren't strictly designed
> for black listing.)
>
> Tim
>
> On Sun, Jun 26, 2011 at 8:18 PM, Timothy White <ti***8@gmail.com>
> wrote:
> > I've realised that a component I took out of the hotspot system before
> > releasing it to the public last year, probably needs to be added back
> > in.
> > Simply, dnsmasq.
> >
> > Currently the coovachilli config file gives out 2 IP's for DNS, one is
> > an OpenDNS one, and the other is 10.1.0.1 which will timeout if the
> > server doesn't have a DNS server as well. I don't want to go back to
> > OpenDNS (as I don't aggree with their idea of redirecting NX to their
> > search page).
> > What I am going to do is have both DNS's ips (because coovachilli
> > needs 2) to point to 10.1.0.1 and depend on dnsmasq. Through a simple
> > script we can allow the admin to change which dns servers dnsmasq
> > looks at by writing a file to /etc/dnsmasq.d/ with the server=x.y.z.a
> > lines as required.
> > The default options that I'll install with grase-www-portal will include:
> > * strict-order so that the computers default dns (as in
> > /etc/resolv.conf) will be tried first
> > * server=opendnsipaddress
> > * server=googlednsipaddress
> > * bogus-nxdomain=x.y.z
> >
> > What this will do is allow us to try the users default dns server
> > first (need for example here on an iinet connection to ensure freezone
> > traffic is actually free). Failing that we can try OpenDNS and Google
> > DNS without them redirecting NX to their search page (the
> > bogus-nxdomain stuff). What it'll also allow us to do, is have the
> > hotspot write another file that will be loaded before the defaults, so
> > that the admin can override the options with their own server= lines
> > (i.e. OpenDNS Family Filter) and with no-resolv to not use the default
> > DNS provided by the system.
> >
> > The only issue I can see currently is if the admin wants to run
> > another DNS server on the machine as well. We can tell dnsmasq to only
> > bind to the coova chilli interfaces, however I'm inclined to add that
> > option commented out and leave it to the system admin to uncomment it
> > if they wish to run another DNS server as well.
> >
> > Any thoughts on all of this? Using dnsmasq may also open up the door
> > for Layer 3 coovachilli, however until such a time that I need Layer 3
> > coova chilli, I'm probably not going to work on it.
> >
> > All thoughts are welcomed. If people object to using OpenDNS or Google
> > DNS as fallbacks, please speak up.
> >
> > Tim
> >
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 26 Jun 2011 19:29:26 -0700 (PDT)
> From: ????? ?????? <pa***s@yahoo.com>
> Subject: [GRASE-Hotspot] problem with admin login
> To: gr***t@lists.sourceforge.net
> Message-ID:
>        <13***C@web161619.mail.bf1.yahoo.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi member of grase hotspot mailing list. I'm new here.
> right now i'm having problem when login admin page.
> it just showing blank page after entered username and password for admin.
> and there is no login page for internet use from client computer..
>
> can you help me?
> i attach apache error and access log and my chilli configutration for
> reference..
> tkanks
> -------------- next part --------------
> An HTML attachment was scrubbed...
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: image/jpeg
> Size: 12322 bytes
> Desc: not available
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: chilli.conf
> Type: application/octet-stream
> Size: 791 bytes
> Desc: not available
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: error.log
> Type: application/octet-stream
> Size: 11470 bytes
> Desc: not available
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: access.log
> Type: application/octet-stream
> Size: 61132 bytes
> Desc: not available
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> 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-d2d-c2
>
> ------------------------------
>
> _______________________________________________
> Grase-hotspot mailing list
> Gr***t@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/grase-hotspot
>
>
> End of Grase-hotspot Digest, Vol 1, Issue 2
> *******************************************
>

Thread