2013-09-26 - Re: [GRASE-Hotspot] An idea for Grase hardware (Drazen)

Header Data

From: darnalis <da***s@gmail.com>
Message Hash: 791b2b831192104df2da3db959b3c0ec9f75e816fa2de4b20b18ced351d610bd
Message ID: <CAKDTiad=GZ2TkSgDjSE44VsR_LNx6Bbgw4J0Tr4hH8cnGHQ=Ww@mail.gmail.com>
Reply To: N/A
UTC Datetime: 2013-09-26 23:59:57 UTC
Raw Date: Fri, 27 Sep 2013 14:59:57 +0800

Raw message 

Wow drazen, you really read my mind.  I am also working on this on my own
but not yet being able to purchase a reliable usb lan ethernet adapter.
 Would love to hear more about the stability and the performance of your
setup. Thanks

regards,
darnalis


On Fri, Sep 27, 2013 at 2:00 PM, <
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. An idea for Grase hardware (Drazen)
>    2. Hotspot don't redirect (Oscar Saiz)
>    3. Issues during installation (Sam Clore)
>    4. Re: Issues during installation (Drazen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 15 Sep 2013 10:12:20 +0200
> From: Drazen <dr***a@radez.hr>
> Subject: [GRASE-Hotspot] An idea for Grase hardware
> To: Gr***t@lists.sourceforge.net
> Message-ID: <52***3@radez.hr>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I have decided to share an idea here with other grase users.
> Hope Tim will have nothing against.
>
> There is well known wisdom using old PCs for different linux projects.
> So Grase is not exception of this.
>
> Well, why not reuse old notebook too?
>
> Main reason why this is not widely used is fact that 99% of
> notebook/laptop devices have one wired interface only.
> In theory we could use wireless interface as second one, but this is not
> practical for several reasons. Speed and radio covering to mention two
> important ones.
>
> Well, today it is possible to get USB to Ethernet adapter which can play
> very well. It is quite cheap and performs well. According my short
> investigation, seems that ones which are designed for MAC computers will
> work upon connecting with most Linuxes . Ubuntu as well.
> So I did purchased one and tried to push it at several of my Linux
> desktop machines. They all recognized new hardware upon connecting it to
> USB and it was ready in a second. I ordered mine from eBay.
>
> Another reason why someone may decide to go this way is power
> consumption. If you are running your hotspot server at home for family
> and maybe neighbors, when server have to work 24/7, using any PC class
> machine, power consumption may affect your electric bill.
> If you can't invest in low power Atom or similar integrated mini-itx
> board, an old notebook can help.
>
> It is possible to find more or less old notebook which is partially
> cracked, non-working screen or several other malfunctioning why owner
> already bought new one. What only important is that board boots up, and
> recognize memory, LAN adapter, USB, and hard disk. Often is possible to
> find perfectly working machine just it is outdated and running modern
> windows very slow. In fact modern content becoming main reason while
> older computers getting slow.
>
>
> Main trick in preparing such machine is to take out everything what we
> don't need  and what drains power.
> Those are: screen, wireless card if any, modem card, sound card,
> blue-tooth /IR card, optical drive, touch-pad and keyboard. It is
> recommended to not putting back up-cover due to better cooling.
>
> Additional tweaking may include passive cooling and custom made housing.
>
> Final result should bring less power consumption and less heating,
> giving CPU more free cycles to do main job.
> CD/DVD drive we use for first installation then will never need it
> again. so it goes out.
> For installation is used external VGA display. Keyboard is essential for
> installation and then take it out.
> Later if necessary we can plug external display and usb keyboard to
> access console what is really rare case.
> I recommend to pass trough BIOS and disable everything there we don't
> need, set final boot sekvence.
> Some NB BIOS has no option to allow to set automatic start after loosing
> power. So, after electric power outage, we need to power-on server
> manually.
>
> Some illustration you can see here:
>
> https://plus.google.com/photos/108215489267527604536/albums/5923511266866501809
> This is HP nx6110. Which was pretty much cracked at all corners, display
> hinges where broken, display itself starts showing lines but main reason
> was disk self locking what made this machine unusable.
>
> Have a fun
> Drazen
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 23 Sep 2013 12:20:23 +0200
> From: "Oscar Saiz" <os***z@telefonica.net>
> Subject: [GRASE-Hotspot] Hotspot don't redirect
> To: <gr***t@lists.sourceforge.net>
> Message-ID: <DF800B616D624FDDBC459653029E5133@PC>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Tim,
> I installed your hotspot for long time ago.
> I?ve never had any problem, but recently I?ve seen that the hotspot can't
> redirect the browser to the main page (identification page)
> I?ve to put 172.16.0.1/grase/uam
> ?Do you know what could be the problem?
> I?d installed the 3.7.7.6 version in debian 6.
>
> Thanks a lot
>
> Oscar
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 3
> Date: Thu, 26 Sep 2013 19:50:00 +0000
> From: Sam Clore <sc***e@microsoft.com>
> Subject: [GRASE-Hotspot] Issues during installation
> To: "gr***t@lists.sourceforge.net"
>         <gr***t@lists.sourceforge.net>
> Message-ID:
>         <
> 7e***d@BL2PR03MB259.namprd03.prod.outlook.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi all!
>
> I had some problems running the installation of Grase today.
>
> I followed the server installation steps to the letter and encountered no
> problems there.
>
> When I ran the installation of Grase however, it got to the point where it
> said "Starting Chilli..." and then hung.  At this point I also lost my
> internet connection.
>
> So my question is regarding the hardware set up.
>
> My current set up is:
>
> *         Ubuntu server 12.04.3 LTS
>
> *         Two NICs
>
> o   Eth1 is connected via Ethernet cable to a switch which is then
> connected to my LAN
>
> o   Eth0 isn't connected to anything
>
> *         According to the server setup, my internet interface is on eth1
>
> I was looking at the hardware setup picture located here:
> http://grasehotspot.org/documentation/hardware-setup/ and am a little
> confused.
>
> The picture seems to indicate three things:
>
> 1.       That the wireless AP is connected to a switch
>
> 2.       That the server is connected directly to the internet
>
> 3.       That the server is also connected to a switch
>
> Is #2 from above correct?  Must the server be directly connected to the
> internet or can it be connected to the LAN via a switch?
>
> Is it required that I have eth0 connected to something during installation?
>
> Thanks!
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 4
> Date: Fri, 27 Sep 2013 07:59:54 +0200
> From: Drazen <dr***a@radez.hr>
> Subject: Re: [GRASE-Hotspot] Issues during installation
> To: gr***t@lists.sourceforge.net
> Message-ID: <52***3@radez.hr>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Sam
> I guess your issue is here
>
> "?Two NICs
>
> oEth1 is connected via Ethernet cable to a switch which is then
> connected to my LAN
>
> oEth0 isn't connected to anything
>
> ?According to the server setup, my internet interface is on eth1
>
>   "
>
> This should be reversed. While installing Ubuntu it will take any
> interface which you say is default for the server (from linux side of
> mind default is one which will be connected to network and Internet. At
> that one linux expects to get DHCP address from your router first. )
> So whichever one you set Deafult and there is cable connected to router
> and internet will be fine for Ubuntu installation.
> However, Grase installation expects that eth0 is internet one, and eth1
> is one Grase will manage. That is why chilly crashed.
> As seen from your post you did switch those two.
> It should be changed in Ubuntu installation first. Connect cable to eth0
> . It will reconfigure eth0 itself or will ask.
> Also check /etc/network/interfaces . There you should change eth1 to eth0
> No any mention of eth1 should be here.
> "....
> # The primary network interface
> auto eth0
> iface eth0 inet dhcp
> ..."
>
> Should be command to do this from CL  which honestly I don't know.
> Reboot Ubuntu here to clean up mess.
> Then try to install grase again.
> Hope this help
> Drazen
>
> On 26.9.2013 21:50, Sam Clore wrote:
> >
> > Hi all!
> >
> > I had some problems running the installation of Grase today.
> >
> > I followed the server installation steps to the letter and encountered
> > no problems there.
> >
> > When I ran the installation of Grase however, it got to the point
> > where it said "Starting Chilli..." and then hung.  At this point I
> > also lost my internet connection.
> >
> > So my question is regarding the hardware set up.
> >
> > My current set up is:
> >
> > ?Ubuntu server 12.04.3 LTS
> >
> > ?Two NICs
> >
> > oEth1 is connected via Ethernet cable to a switch which is then
> > connected to my LAN
> >
> > oEth0 isn't connected to anything
> >
> > ?According to the server setup, my internet interface is on eth1
> >
> > I was looking at the hardware setup picture located here:
> > http://grasehotspot.org/documentation/hardware-setup/
> > <http://grasehotspot.org/documentation/hardware-setup/> and am a
> > little confused.
> >
> > The picture seems to indicate three things:
> >
> > 1.That the wireless AP is connected to a switch
> >
> > 2.That the server is connected directly to the internet
> >
> > 3.That the server is also connected to a switch
> >
> > Is #2 from above correct?  Must the server be directly connected to
> > the internet or can it be connected to the LAN via a switch?
> >
> > Is it required that I have eth0 connected to something during
> > installation?
> >
> > Thanks!
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > October Webinars: Code for Performance
> > Free Intel webinars can help you accelerate application performance.
> > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> > the latest Intel processors and coprocessors. See abstracts and register
> >
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
> >
> >
> > _______________________________________________
> > Grase-hotspot mailing list
> > Gr***t@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/grase-hotspot
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
>
> ------------------------------
>
> _______________________________________________
> Grase-hotspot mailing list
> Gr***t@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/grase-hotspot
>
>
> End of Grase-hotspot Digest, Vol 28, Issue 3
> ********************************************
>

Thread