The time now is Fri 24 May 2013, 06:06
All times are UTC - 4 |
| Author |
Message |
richard.a

Joined: 15 Aug 2006 Posts: 510 Location: Adelaide, South Australia
|
Posted: Mon 29 Mar 2010, 17:42 Post subject:
practical example of Mi-Fi usefulness (if I had one) Subject description: (slightly off topic) |
|
| Quote: | Regarding the MiFi device mentioned, it may very well prove useful anyway, for demo-ing a combination of Linux, wifi hotspots, and 3G connectivity among friends and business owners with whom I'm acquainted. (I'm retired from the work force)
We need more hotspots after all, and imho the internode hotspot system is possibly the best Australian one for minimal investment by businesses. |
I wrote that in my last post, and this is a little off topic.
Since then, at 2001 yesterday (according to IRC logs) my main ADSL service went down due to a line fault. Australia's phone lines are all owned by just one telco. We are hamstrung here.
It's now almost 12 hours since the failure. I've been using 3G wireless connectivity to keep IRC bots and channel (chat room) logging going via a laptop with the 3G dongle mentioned previously.
If I had the MiFi I described - instead of the USB dongle - at least parts of my LAN could be operational to the outside world, allowing more than one computer access
UPDATED
I have the MiFi unit - a dash into Adelaide to pick up the unit from Internode.
A very simple job to transfer the SIM card, there is an instruction book.
I tested it out, and while a little iffy first up to recognise the unit on 4.3.1 vanilla, it did after 3 attempts. Also on 2.14X15 (nicely) as well as superbly on 4.2.1
This was on a Toshiba Satellite 1800, 896 Celeron processor, 256, and a D-Link PCMCIA AirPlus-G NIC.
Richard in Adelaide -
although my whois on 3G often says I'm in Sydney, 1000 miles away lol. Today it says Melbourne, 800 miles away:)
_________________ Have you noticed editing is always needed for the inevitable typos that weren't there when you hit the "post" button?

Last edited by richard.a on Tue 30 Mar 2010, 06:31; edited 1 time in total
|
|
Back to top
|
|
 |
cthisbear
Joined: 29 Jan 2006 Posts: 2943 Location: Sydney Australia
|
Posted: Mon 29 Mar 2010, 18:16 Post subject:
|
|
richard.a
Whirlpool forum...same problem.
" Im trying to get a huawei E160E USB modem to work with Puppy Linux. "
http://forums.whirlpool.net.au/forum-replies.cfm?t=1413253&p=-1#bottom
Chris.
|
|
Back to top
|
|
 |
01micko

Joined: 11 Oct 2008 Posts: 7019 Location: qld
|
Posted: Tue 30 Mar 2010, 00:31 Post subject:
|
|
richard.a
You may find this interesting so you can share you 3G internet, I have done it and know it works with ethernet, but should work with a wireless adapter too.
http://www.murga-linux.com/puppy/viewtopic.php?search_id=1899807111&t=37520
It is a great little program and it has documentation included.
______________
cthisbear
Posted a reply on whirlpool for your mate over there.
Cheers
_________________ keep the faith .. 
|
|
Back to top
|
|
 |
cthisbear
Joined: 29 Jan 2006 Posts: 2943 Location: Sydney Australia
|
Posted: Tue 30 Mar 2010, 04:02 Post subject:
|
|
01micko:
Good work mate...........Chris.
|
|
Back to top
|
|
 |
Aitch

Joined: 04 Apr 2007 Posts: 6825 Location: Chatham, Kent, UK
|
Posted: Wed 31 Mar 2010, 20:46 Post subject:
|
|
Richard a.
Which Mifi device did you get?
I'm curious, as I posted a link earlier for the Huawei E5830 one used by Three in UK
Good to see you got it working on 4.2.1, 4.3.1, and 2.14X - my 3 favourite puppies at the moment, but some tips on what you did would be useful
Do you have full web admin access? - the Three version seems crippled, [?] and seemingly doesn't allow wep ar wpa/2 security, though there are reports of updating the firmware, and unlocking the device to get around this - I only have mine [very new acquisition] working on Windoze, atm
thanks
Aitch
|
|
Back to top
|
|
 |
richard.a

Joined: 15 Aug 2006 Posts: 510 Location: Adelaide, South Australia
|
Posted: Wed 31 Mar 2010, 22:49 Post subject:
Mi-Fi does work, and nicely Subject description: Still possibly off-topic |
|
| Aitch wrote: | | Which Mifi device did you get? |
The natty little black box says it's a 2352, and the manual says it could have been a 2372. Not sure what the difference is. I did read somewhere that it has Huawei E5830 internals rather than those of the E160E dongle which I have.
It also appears to have been available in black or silver. Mine is black.
| Aitch wrote: | | I'm curious, as I posted a link earlier for the Huawei E5830 one used by Three in UK |
Oh... I must have missed that
| Aitch wrote: | | Good to see you got it working on 4.2.1, 4.3.1, and 2.14X - my 3 favourite puppies at the moment, but some tips on what you did would be useful |
While it was running for the next few hours, I also tried an Aspire1 on which I have the four OS's I mentioned so I know it supports at least two WiFi connections nicely.
I didn't wish to waste time with the security stuff, particularly because I have found with a Netgear WG614 (v9) that there were difficulties in getting the three puppy versions mentioned connecting encrypted. 4.21 was more iffy than 4.31 in that regard.
| Aitch wrote: | Do you have full web admin access? - the Three version seems crippled, [?] and seemingly doesn't allow wep ar wpa/2 security, though there are reports of updating the firmware, and unlocking the device to get around this - I only have mine [very new acquisition] working on Windoze, atm |
As mentioned, I didn't explore what I can do with it; almost all of my ISP's Adelaide customers had DSLAM failure which nobody has explained yet... but one suspects it was a problem associated with what is referred to as "the last mile" here - the length of copper conductor from the phone exchange mainframe to the customers, administered by "the only game in town" so to speak.
The chat rooms in which I'm an admin (in my spare time!) were having to be supervised by bots and personal clients on an old Toshiba laptop running WindowsXP SP2. So, hence my extremely fast "get-it-running-at-all costs" saga because of this situation which didn't need downtime longer than a few minutes.
I charged the battery (without inserting the SIM because the latter was in use) - the book says 4hrs initial charge - and it showed a solid LED charged indication after 2 hours.
About 30mins later (to ensure it was fully charged), I shut down the charger, shut down bots and chat clients, and pulled the 3G dongle from the WindowsXP home SP2 ancient Toshiba Satellite 1800 laptop, leaving the laptop idling.
Then removed the SIM from the dongle, removed the (now charged) battery from the MiFi, plugged SIM and then battery into MiFi (SIM sits under the battery), and pressed the power on button on the MiFi.
As soon as the MiFi LEDs announced its search had located a 3G signal and locked on (this is described in detail in the instruction booklet provided by manufacturer Novatel), I told the (Windows) laptop to go looking and it was quickly located and set as default, I restarted the bots and chat clients
It really was as simple as that!
Comments
I wrote to Internode later that evening giving them an update, and said a maximum of 15mins to do the change-over, but I suspect it was far, far, less.
Setting up to use the hotspot on the puppies mentioned was only slightly longer in duration than on WindowsXP... and was about the same length of time as in accessing a regular "proper" hotspot!
Actually it IS a proper hotspot lol
Once my regular ADSL connection was restored considerably later that night, I tried the same puppies on the Toshiba laptop and they performed similarly. Interestingly the D-Link PCMCIA WiFi identifies in puppies and PCLinuxOS as Atheros, which is what the Aspire1's claims to be. So that isn't as good a check as it might be.
The instruction book also tells you how to go about using it as a regular 3G device, but the WiFi side is disabled if you do that - which I thought was pretty pointless.
The ability exists to configure the device by both web browser and alternatively via a USB cable, but I didn't use either method as it self-configures nicely and quickly (without any security of course) on its own. WPA etc needs to be set up with either web or USB access.
There is a miniature card slot on the back which can be for any capacity up to 16Gb for storage of downloads etc - very useful when the 3G provider charges for the bandwidth in both directions. My ISP (who doesn't count uploads on its regular ADSL plans) have little choice but to pass on the charges from Optus who is the 3G carrier they use. So the card can be removed later and its contents copied across a regular LAN, etc.
I'm impressed actually at the simplicity of operation. A plus for non technical users, and it is ideally suited for converts to alternative OS's who could be discouraged if it wasn't simple. I've seen the expressions on their faces when something is sufficiently "different" to be a worry factor .
_________________ Have you noticed editing is always needed for the inevitable typos that weren't there when you hit the "post" button?

|
|
Back to top
|
|
 |
Aitch

Joined: 04 Apr 2007 Posts: 6825 Location: Chatham, Kent, UK
|
Posted: Thu 01 Apr 2010, 22:14 Post subject:
|
|
Richard a.
Thanks, good feedback!
Here's the link I posted [I since bought one],
http://www.murga-linux.com/puppy/viewtopic.php?p=394490#394490
...and like you, hooked it up really easily - haven't done much more experimenting with it yet, as I have broadband, and it's fairly expensive to use, but I bought it for my camper & narrowboat, though I'm still trying to get a good 12v Car PC rig in the boat - having a problem with the right power supply - blown 2 cheapies already, and I'm still experimenting with powered USB extension cables for the remote DVD player/writer, as it plays up on standard extensions, and getting a low power screen to work, cheaply [I'd really like a 15" touchscreen that uses about 25watts or less! ] - not enough 'leisure' battery reserve amps is the real problem, so I'm also trying to get better charging output from the main engine alternator....and maybe a solar panel
Meanwhile, mobile I have an Edubook running XP Fundamentals[?] slowly..., and an IBM T21 running XP/214X, using a standard 3G E220 and a 300w inverter to recharge the batteries
Aitch
|
|
Back to top
|
|
 |
Baldronicus
Joined: 25 Apr 2008 Posts: 8
|
Posted: Fri 02 Apr 2010, 19:52 Post subject:
Internode 3G access Puppy 4.3.1 standard E160E (or X) |
|
Hi rerwin et al,
Thanks very much for all the effort and information with the dial up and Mobile Broadband modems.
Hopefully the following might be of assistance with the Internode connection problem (at least it seems to work- not sure if there might be hidden rough edges, or whether I might unknowingly have done something else to get it to work).
Edit (again- cut out too much): As Richard (rerwin) points out in another post below, the description that originally followed is not really the best way to approach the connection. At this stage, updating /etc/resolv.conf with the DNS info on the sheet provided with the modem (by Internode), looks a much better way to go.
Best to have the latest backend and modem update pets loaded (you may need to use a pupsave or a remastered 4.3.1- if remastering 4.3.1 see the threads in the forum-as there may be a problem unless you use one of the various fixes). Reboot with the modem attached (initial run), and follow Richard's (rerwin's) advice for detecting the modem.
Set up PupDial with:
Phone Number: *99#
Username: (as per Smokey01's advice this can be anything- I used "a"
Password: (as per Username)
APN: internode
Open /etc/resolv.conf. (I don't know if you would need to uncomment and overwrite the first line with the following, but it may not hurt). Key in the word "nameserver" (without quotes), leave a space, then enter the Primary DNS info as given on the sheet. On the next line do the same for the Secondary DNS info. Save the file (in place) and hopefully it should work when you try connecting through PupDial..
The initial connection may still seem a bit slow, but it seems to work pretty well after that.
Edit:paragraphs removed as redundant.
Hope this helps, and I haven't botched anything (no, I don't know what I am doing).
Thanks.
Baldronicus
Edit: forgot to note modem type: Huawei E160E (possibly E160X in documentation)
Last edited by Baldronicus on Sun 02 May 2010, 20:53; edited 3 times in total
|
|
Back to top
|
|
 |
kazzamozz

Joined: 25 Jul 2009 Posts: 61 Location: Melbourne, Australia
|
Posted: Thu 08 Apr 2010, 06:57 Post subject:
3Gwireless modem autodetection Subject description: 214 puppies |
|
Hi Rerwin
I know this forum is for 4.1.2 and upwards but I
just thought I would update you on recent events.
Have installed your latest 3g 13.pet
and Istandish's mt-gprs-2.6.21.7-12.pet
Success with a Vodafone 3Gk3715
using ttuxxxs 214r5 puppy and also mini-sys-linux mini 008.4c-En & Muppy
kernel 2.6.21.7
New Years Pup 4.11 base not sure of the kernel
I know this is only supposed to work on 4.1.2 and later but this is working on the early puppies and also updating the menus for gprs connect. It works very well too.
once you install this plug in the modem reboot
Click on gprs connect I get a connection. I still cannot get this modem to actually work under pupdial, it can see it but it just sits there waiting for a response, but as stated previously for some reason it's very happy to connect with gprs connect I only have to enter.
Vfinternet.au
guest
guest
and it works.
I am currently testing on growler and teenpup but am having problems as they won't create the save file. This is related to the Toshiba L300 keeps going to a dead screen when rebooting so will be testing on the desktop tomorrow.
Just thought this may be of interest with all the work you have been doing on this. Personally I am wrapt I can get a 3G modem to work on the older pups as some of them are pretty cool. I didn't have to do any mucking around either they just installed. So whatever magic you have created seems to work on any puppy so far !!
Cheers
Kazzamozz
|
|
Back to top
|
|
 |
rerwin

Joined: 24 Aug 2005 Posts: 1318 Location: Maine, USA
|
Posted: Thu 08 Apr 2010, 14:24 Post subject:
|
|
I am pleased to see you making such progress on your own. I have been preoccupied with the upgrade to usb_modeswitch in time for 4.3.2. Now I need some of you to test out the new packages so we don't get an ugly surprise in 4.3.2.
First, install the updated pup_event_backend_modprobe_fix_to_p43x-4.pet:
http://www.murga-linux.com/puppy/viewtopic.php?mode=attach&id=27883
Then, if you already have modem_fix_pack_to_431-5 installed, just install modem_fix_pack_delta-5-to-6.pet:
http://www.murga-linux.com/puppy/viewtopic.php?mode=attach&id=27884
Otherwise, if you start with a fresh 4.3.1 or 4.3.2 puppy and new pupsave, just install modem_fix_pack_to_431-6.pet:
http://www.murga-linux.com/puppy/viewtopic.php?mode=attach&id=27882
Please report your results ASAP so I can recommend that ttuuxxx add the fix pack delta to his official 4.3.2 (or make a quick fix)..
Regarding the possible need for the "-chap" workaround: there is a way to avoid the editing of the /ppp/options file. In anticipation of a need for it for other ISPs, I implemented an easy way to add new providers. However, I see that the instance I created for whoever-raised-the-issue did not make it into 4.3.1 as I had intended. But it is easy to add yourselves. Given your actual APN string, which I show here as (APN), enter the command:
echo "-chap" > /etc/wvdial_options/APN-(APN)
Pupdial will then insert the "-chap" automatically. You need do that only once, since it is retained. Please post the new files that are needed so I can add them to an update. Thanks
With the completion of the fix-pack-6, I am ready to resume work on details for particular modem models. So, when trying the latest implementation, please tell me of any problems. I admit that my progress on the ones I have been working has been frustrating. But we need to press on with what can be resolved.
Thank you for all of your help with this.
Richard
Baldronicus,
I am fascinated by your experimentation with your E160. You are the first I know of to utilize the extra Init statements I built into wvdial.conf. Your Init4 entry tells me you need to force your provider to use only 3G, and not 2G. Is that because they give you 2G by default? Or will 2G not work if they have to "fall back" to it? I am surprised it is necessary in your case.
Regarding commenting out the line with 115200: all the feedback I see is that the speed value is irrelevant for wireless modems, so any value can be set and will be ignored. One less thing to mess with.
Richard
Greatnessguru,
Regarding your Motorola VE465 mobile phone in USB modem mode: I have something to help you along. Although we won't be able to get the Connect Wizard to detect your phone (because it requires the generic usbserial driver/module), we can automate the loading of that module, so that you can simply probe for the modem in Pupdial.
Modems commonly use a driver (e.g., option, sierra) that has an associated initialization script that finds the ttyUSB- device. Those drivers actually invoke usbserial, so having a script for usbserial gets tricky. But these cases are rare and the probe step is at least straightforward.
The latest modem fix pack (-6) has a file: /etc/udev/rules.d/50-modprobe-usbserial.rules, which can be expanded to include your phone/modem. The file currently has one special case in it, More can be added in the following format: | Code: | # #################################################
# Modem name...
SUBSYSTEM=="usb", ACTION=="add", \
ATTRS{idVendor}=="vvvv", ATTRS{idproduct}=="pppp", \
RUN+="/sbin/modprobe usbserial %s{idVendor} %s{idProduct}"
| where you change the vvvv to the vendor ID and pppp to the product ID. Adding the modem name would be good, too.
Your entry should be this: | Code: | #################################################
# Motorola VE465
SUBSYSTEM=="usb", ACTION=="add", \
ATTRS{idVendor}=="22b8", ATTRS{idproduct}=="2b24", \
RUN+="/sbin/modprobe usbserial %s{idVendor} %s{idProduct}"
| Please try the new update packages and try this out. There may be more things to adjust, but this is a start.
Richard
|
|
Back to top
|
|
 |
Greatnessguru

Joined: 09 Jul 2007 Posts: 104 Location: rural McBain MI USA (near Cadillac MI)
|
Posted: Sat 10 Apr 2010, 02:15 Post subject:
Class attribute? |
|
rerwin,
| Code: | ...
# Modem name...
...
ATTRS{idproduct}...
... %s{idProduct}" |
Upper case "P", or lower?
Also, the idea is to _not_ special case phone modems,
but to _general case_ them.
Something like, I suppose:
| Code: | #################################################
# Cls=ff(vend.)
SUBSYSTEM=="usb", ACTION=="add", \
ATTRS{idCls}=="ff(vend.)", \
RUN+="/sbin/modprobe usbserial %s{idCls}" |
Is "idCls" correct for the "Cls" attribute?
Thanks,
Eddie Maddox
|
|
Back to top
|
|
 |
Greatnessguru

Joined: 09 Jul 2007 Posts: 104 Location: rural McBain MI USA (near Cadillac MI)
|
Posted: Sat 10 Apr 2010, 14:07 Post subject:
|
|
rerwin,
I tried much testing with Puppy 431, pfix=ram,
and your -4/-6 PETs.
No success ever.
I am very frustrated by the great inconsistency between the
/etc/udev/rules.d/50-modprobe-usbserial.rules code for the
existing special case and the code you supplied for the VE465.
Please supply links to docs on that file.
Thanks,
Eddie Maddox
|
|
Back to top
|
|
 |
rerwin

Joined: 24 Aug 2005 Posts: 1318 Location: Maine, USA
|
Posted: Sat 10 Apr 2010, 17:09 Post subject:
|
|
Greatnessguru,
That file was an experiment for someone with a Chinese cellphone, I think, but the user never responded. I have now concluded that you might be better off trying the 'option' driver, which apparently supports more than you would think.
There is a rules file:
50-modprobe-option.rules
to which you could add the following entry: | Code: | # Motorola VE465
ACTION=="add", SUBSYSTEMS=="usb", \
ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="2b24", \
ATTRS{bInterfaceClass}=="ff", \
RUN+="/usr/sbin/pmodprobeoption.sh %s{idVendor} %s{idProduct}"
| (Yes, it should be "idP..."; my typo before. And that is the attribute for class, too.)
Regarding your generic technique: modprobe expects vendor and product as keyword parameters, so the class would not work. And class ff probably has multiple meanings, depending on the device, which could be anything.
When you try the option idea, please get a diag file (with pmodemdiag) and PM it to me, so I can see what happened. I need clues as to why it is not working. If we have to go back to the usbserial angle, we will be blazing a trail. So I hope the option driver works here.
Richard
|
|
Back to top
|
|
 |
Greatnessguru

Joined: 09 Jul 2007 Posts: 104 Location: rural McBain MI USA (near Cadillac MI)
|
Posted: Sun 11 Apr 2010, 08:17 Post subject:
|
|
rerwin,
| Quote: | | please get a diag file (with pmodemdiag) and PM it to me, |
pmodemdiag hung, never creating the file.
| Code: | Running PupScan silently to get hardware IDs and drivers.
Collecting various modem-related files into an archive tarball:
pmodemdiag-20100411.tar.gz. |
Eddie Maddox
|
|
Back to top
|
|
 |
Greatnessguru

Joined: 09 Jul 2007 Posts: 104 Location: rural McBain MI USA (near Cadillac MI)
|
Posted: Sun 11 Apr 2010, 09:14 Post subject:
|
|
rerwin,
| Quote: | Regarding your generic technique:
modprobe expects vendor and product as keyword parameters,
so the class would not work.
And class ff probably has multiple meanings,
depending on the device, which could be anything. |
So, the natural thing to do is:
- probe for the Class "ff"
- for each Class "ff" found:
-- show the info in a dialog box
-- ask the user if it is a "modem" or is set to "modem mode"
-- if so:
--- extract the Vendor and Product for modprobe
Correct?
My Motorola VE465, via menus on the phone, can be set to either:
- Mass Storage
- Modem
for USB.
For Bluetooth it can be set to several different things.
Eddie Maddox
|
|
Back to top
|
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|