noop

Forum Replies Created

Viewing 30 posts - 61 through 90 (of 92 total)
  • 10. Januar 2016 at 21:26 #17689

    there’s a command „iw“ which might be helpful.

    apt-get install iw    <--install the iw software if not already installed
    iw list           <-- returns lots of info on the dongle capabilities

    If it returns an error that’s a clue

    iw wlan0 info

    Interface wlan0
            ifindex 3
            type AP
            wiphy 0

    type AP is what you want.

    10. Januar 2016 at 19:51 #17687

    Alex:

    Are you starting with the latest max2play image download? 2.22 (I think?).
    If not, do that.

    10. Januar 2016 at 16:32 #17682

    Hi Alex:

    for your dongle rt1871x may be correct and expected to be different.
    Look through the output for errors and warnings.

    I would expect that the command

    lsusb

    confirms that your dongle has a realtech „rt“ chip

    You should try (if you are not already using it) the edimax dongle as it is supported by MAX2PLAY according the the change logs.

    On a separate note:
    What release of max2play are you starting with? Have your tried downloading the latest?

    • This reply was modified 8 years, 11 months ago by noop.
    10. Januar 2016 at 4:18 #17677

    No problemo get some sleep! I’m 5 hours behind you.

    OK there’s a problem…mode „Managed“ is client not „Master“.

    i’m guessing that hostapd is not able to set mode master for some reason.
    stop hostapd and run manually…

    sudo /etc/init.d/hostapd stop
    sudo /usr/sbin/hostapd /etc/hostapd/hostapd.conf -d | less

    this will display one page of the output at a time, you can use the <return> key to advance one
    more line at a time, <space> key one page at time. These lines in my output show the interface
    being set to mode „AP“ (access point)

    Configuration file: /etc/hostapd/hostapd.conf
    nl80211: interface wlan0 in phy phy0
    rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
    nl80211: Using driver-based off-channel TX
    nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
    nl80211: Register frame match - hexdump(len=2): 04 0a
    nl80211: Failed to register Action frame processing - ignore for now
    nl80211: Add own interface ifindex 3
    nl80211: Set mode ifindex 3 iftype 3 (AP)        <----- HERE
    nl80211: Create interface iftype 6 (MONITOR)
    .
    .
    .
    Using interface wlan0 with hwaddr 00:0f:60:05:50:82 and ssid 'max2play'
    Deriving WPA PSK based on passphrase

    What does your output look like? Look at the output for problems/errors.
    BTW: to exit the program type: q followed by ctrl-c

    • This reply was modified 8 years, 11 months ago by noop.
    • This reply was modified 8 years, 11 months ago by noop.
    10. Januar 2016 at 2:06 #17668

    So everything looks good with info you sent. Do you have another wireless device to check for the accesspoint with? say a laptop?
    It should be working.

    ALSO:
    command:
    iwconfig

    look for „Mode:Master“ in wlan0

    mon.wlan0  IEEE 802.11bgn  Mode:Monitor  Tx-Power=20 dBm
              Retry short limit:7   RTS thr:off   Fragment thr:off
              Power Management:off
    
    wlan0     IEEE 802.11bgn  Mode:Master  Tx-Power=20 dBm
              Retry short limit:7   RTS thr:off   Fragment thr:off
              Power Management:off
    
    lo        no wireless extensions.
    
    eth0      no wireless extensions.
    
    • This reply was modified 8 years, 11 months ago by noop.
    10. Januar 2016 at 1:46 #17666

    in your response to the what the command ifconfig wlan0 you said

    Yes it looks nearly exactly the same as yours, all but the addresses

    was the inet addr 192.168.189.1 ?

    10. Januar 2016 at 1:02 #17663

    your IP addresses should be the same…what do you see?

    Assuming they were the same, I’d be interested in knowing the contents of your file:
    /etc/hostapd/hostapd.conf, it’s not too long.

    cat /etc/hostapd/hostapd.conf

    • This reply was modified 8 years, 11 months ago by noop.
    10. Januar 2016 at 0:18 #17660

    OK the start command does generate a lot of output.
    now the command
    ifconfig wlan0
    should confirm the static IP address 192.168.189.1 something like

    wlan0     Link encap:Ethernet  HWaddr 00:0f:60:xx:xx:xx
              inet addr:192.168.189.1  Bcast:192.168.189.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:20305 errors:0 dropped:9758 overruns:0 frame:0
              TX packets:20859 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:3953760 (3.7 MiB)  TX bytes:5779163 (5.5 MiB)
    

    If so can you then see the network SSID from your IOS device?

    9. Januar 2016 at 20:59 #17658

    That looks ok, and the other commands?

    9. Januar 2016 at 19:19 #17655

    Sorry I guess that’s an alias I have

    ls -al /usr/sbin/hostapd

    9. Januar 2016 at 18:03 #17652

    Alex:

    You are correct in that the setup of the „wifi“ interface will be changed by the „accesspoint“ setup.

    So you do not see the „max2play“ SSID correct?

    You get the info that you provided how? By connecting the hardwire ethernet? or hdmi/keyboard?

    Please provide the response to these commands:

    ll /usr/sbin/hostapd
    sudo /etc/init.d/hostapd stop
    sudo /etc/init.d/hostapd start
    ps -efl | grep hostapd
    9. Januar 2016 at 2:32 #17645

    Here’s something to try…using your previous recipe modified…to help debug the issue.

    1. Burn a new image.
    2. Expand it.
    3. Update M2P.
    4. Increase the USB current via the raspberry plug in (not really necessary yet)
    5. Plug in the wifi dongle.
    6. install wifi.
    7. install access-point.
    8. remove power and then remove all connections, except wifi dongle, then apply power.

    Wait a few minutes for the PI to boot then test the access point functionally:
    1. on your IOS device, set-up -> wifi should show an available network with SSID „max2play“ (or whatever you set it to)
    2. Try to connect to this network, if you get an error, „forget“ the network, and re-try (you will prompted for password in this case).
    3. If connected, on the IOS device use safari or chrome and browse the PI at: http://192.168.189.1/ , you should see the max2play page.

    If you see the web page then access point is successfully installed.

    • This reply was modified 8 years, 11 months ago by noop.
    • This reply was modified 8 years, 11 months ago by noop.
    8. Januar 2016 at 22:08 #17639

    Alex:

    what is the current output (in amps) of your power supply? Are you testing without the USB disk connected?

    8. Januar 2016 at 22:05 #17638

    This is the one I have that works with M2P as an access point

    http://www.canakit.com/raspberry-pi-wifi.html

    It id’s as this with the command „lsusb“:

    Bus 001 Device 004: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter

    Alex: do any of your dongles match this?

    8. Januar 2016 at 2:39 #17626

    here is the url to my „run Command“ plugin:

    https://www.dropbox.com/s/vld2dmovyfjlmoo/run_command.tar?dl=0

    English only, sorry.

    8. Januar 2016 at 2:17 #17625

    OMG!!! congrats Alex „way to stick with it“. Your tenacity has been rewarded.

    7. Januar 2016 at 4:54 #17596

    Alex:

    I found this recipe for setting up access point. I have not tried this myself. You could try if you wish.

    Use the RT8188CUS dongle. I would recommend installing the minimum addons (not accesspoint of course), then running this.

    Then test if the accesspoint is working.

    1 you see the ssid
    2 you can connect to the ssid
    3 you can get access to the m2p webpage on the PI

    wget "http://raspberry-at-home.com/files/ap_setup.sh"
    chmod +x ap_setup.sh
    sudo ./ap_setup.sh

    The reference web site is: http://raspberry-at-home.com/hotspot-wifi-access-point/`

    • This reply was modified 8 years, 11 months ago by noop.
    6. Januar 2016 at 4:49 #17588

    Alex:

    As a long shot…have you tried your setup without the hard drive? Marginal power can cause strange problems.

    5. Januar 2016 at 17:42 #17585

    dmesg prints a time based log of system messages. The most recent messages are at the bottom of the file. You could for any errors/warning/info regarding hostapd or wireless authentication, etc, that might be useful. The stuff that flies by at the beginning are older messages.
    An alternate command to try is: tail /var/log/messages which should print similar info. „tail“ prints the end of the the file.
    tail -50 filename prints the last 50 lines etc… tail -f filename monitors the file and dynamcially prints the end of the file as it grows.
    Cntl-C to terminate. /var/log/messages is the file where system messages are logged.

    • This reply was modified 8 years, 11 months ago by noop.
    4. Januar 2016 at 1:02 #17572

    I suppose that it could be a defective dongle, things do seem weird.

    Running the command dmesg on the PI might yield something useful.

    3. Januar 2016 at 23:45 #17569

    hrmm… I cannot see what might be causing the issue, of apparently not being able to load the web interface when connect wireless to the PI running as an access-point.

    I’m assuming that you are entering the URL ->

    http://192.168.189.1/

    Be sure that your iPod or iPhone is not dropping the max2play network and reconnecting to your home hub.

    3. Januar 2016 at 22:06 #17566

    Hi Alex:

    I have to admit that I am confused, as to what you are trying to accomplish at this point and specifically what is not working.

    With the PI disconnected from the wired interface, you should see it’s wireless SSID and be able to connected to it with, either the iPod or iPhone or other wireless device. While connected you should be able to point your browser to http://192.168.189.1 and see the M2P interface. Is this not the case? If so, you should be able to check the status of any pluggins. With the hardwired interface disconnected you will not have internet access from the PI, so things like internet radio will not function. You should however have access to your music library assuming it is local to the PI, say on an external hard-disk, or even on the SDCARD.

    3. Januar 2016 at 19:56 #17562

    With the iPod connected to the PI’s SSID, IPeng on the iPod, should see the squeezebox server if it is also running on the PI (check that).

    Assuming your music library is local to the PI, everything should be working at this point.

    3. Januar 2016 at 17:23 #17542

    Hi Alex:

    That is good news…sounds like you are there. With hostapd running on the PI, another wireless device you should now see the new wireless network with the SSID you setup in the form. You should then be able to connect to that new network, providing the password you had setup (default mypasscode).
    For his new network the PI will provide IP addresses in the 192.168.189.X range, with the PI acting as a router at address 192.168.189.1 (by default). This network will be independent of your other networks unless you clear the „Standalone“ box and connect the hardwire ethernet. In that case the PI will route packets to your the other connected network. You WILL NOT see devices connected to the new wireless network, show up on your home router as clients, because they are on a subnetwork managed by the PI. Only the PI’s hardwire interface will be client on your home router’s network (which is what you see, I think). I hope this make sense.

    You will find max2play at: http://192.168.189.1

    • This reply was modified 8 years, 12 months ago by noop.
    • This reply was modified 8 years, 12 months ago by noop.
    • This reply was modified 8 years, 12 months ago by noop.
    3. Januar 2016 at 5:00 #17537

    Yes I have access point running…if i click „Debug Informations“ near the bottom of the „ACCESS POINT“ setup screen, I see:

    #### DNSMASQ Installed ####
    Status: install ok installed
     
    
    #### HOSTAPD Installed ####
    Status: install ok installed
     
    
    #### WiFi Interface Installed ####
    2
     
    
    #### DNSMASQ Running ####
    5 S   110  4525     1  0  80   0 -  1612 poll_s ?        00:00:00 dnsmasq
     
    
    #### HOSTAPD Running ####
    5 S     0  4508     1  0  80   0 -  1294 poll_s ?        00:00:00 hostapd
     

    Notice that hostapd is running… what do you see now?
    I would expect that a recommended dongle from M2P should work out of the box, and they are inexpensive so you can certainly go that way.

    2. Januar 2016 at 4:05 #17527

    Happy New year Alex:

    You should have completed and submitted the form to complete the access point installation, then run the commands to replace the „hostapd“ program. You should not need to start over again, just run the commands again now.

    • This reply was modified 8 years, 12 months ago by noop.
    31. Dezember 2015 at 5:57 #17521

    Hi Alex:

    You would install the access point plugin to get to the point where the supplied hostapd is failing.
    Then you would issue the commands provided at a shell prompt. Then reboot.

    Yes the wired and wireless network connections would have different IP addresses. Accessing the same data/computer.

    Don’t be discouraged, as long as you learn something the time is not wasted. Keep your chin up.

    30. Dezember 2015 at 17:57 #17518

    Alex:

    I don’t know how adventurous you are but there is a pre-compiled hostapd binary available that supports the RTL8188CUS chipset.
    It’s up to you if you want to try it out.

    Here is how to try it out… it looks complicated but what it essentially does is: download a new hostapd file, move the current one aside, and creates a link to the new hostapd program.

    After going through the Max2Play Access point setup, then replace the hostapd binary…

    cd /tmp
    wget http://www.daveconroy.com/wp3/wp-content/uploads/2013/07/hostapd.zip
    unzip hostapd.zip 
    sudo mv /usr/sbin/hostapd /usr/sbin/hostapd.bak
    sudo mv hostapd /usr/sbin/hostapd.edimax 
    sudo ln -sf /usr/sbin/hostapd.edimax /usr/sbin/hostapd 
    sudo chown root.root /usr/sbin/hostapd 
    sudo chmod 755 /usr/sbin/hostapd

    Then reboot, and see if this version of hostapd runs for your dongle.

    30. Dezember 2015 at 4:43 #17513

    The RLT8188CUS chip does apparently support access point according to what I read.
    .
    Perhaps the coders here can comment.

    • This reply was modified 9 years ago by noop.
    29. Dezember 2015 at 20:31 #17510

    from a command line shell prompt, you can type:

    lsusb

    with the dongle plugged in, it should list some infomation.

    i.e.:

    
    pi@max2play ~ $ lsusb
    Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
    Bus 001 Device 005: ID 1058:1010 Western Digital Technologies, Inc. Elements External HDD
    Bus 001 Device 004: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
    
Viewing 30 posts - 61 through 90 (of 92 total)