[Voyage-linux] Problem with fstab

2011-04-22 Thread ALeX
Hi,
I run Voyage 0.7.0 on a alix board. I attach two usb disk.

I add to /etc/fstab:
UUID=d2482476-9ff8-4fec-a2b6-10269065d585 /mnt/hdd1 ext4  defaults 0 0
UUID=ec240b7a-a890-44da-b84f-0e5530c0eea7 /mnt/hdd2 ext4 defaults 0 0

With the command: mount -a everything works as I expect, but when
the system don't wont to mount the device during boot.

has  someone  a solution?

Regards,
 Alessandro.

___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux


[Voyage-linux] Problem with an USB UMTS modem

2009-07-31 Thread Alex
PS This is already the fourth time I'm trying to post this message into this
f...ng mail list. First 2 times I got - The following address(es) failed:
voyage-linux@list.voyage.hk, third time the message has simply gone!!!

Hi,

I have a HUAWEI E160 UMTS modem. It is recognized by the system and works
correctly but when I disconnect it I got some error message and afterwards the
USB subsystem doesn't work any longer

Here what I have when I connect the device
--
usb 2-1: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
usb 2-1: USB disconnect, address 2
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb 2-1: new high speed USB device using ehci_hcd and address 3
usb 2-1: configuration #1 chosen from 1 choice
usb-storage: probe of 2-1:1.0 failed with error -5
usb-storage: probe of 2-1:1.1 failed with error -5
scsi3 : SCSI emulation for USB Mass Storage devices
scsi4 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usbserial
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
usbserial: USB Serial support registered for GSM modem (1-port)
option 2-1:1.0: GSM modem (1-port) converter detected
usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
option 2-1:1.1: GSM modem (1-port) converter detected
usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
usbcore: registered new interface driver option
option: USB Driver for GSM modems: v0.7.2
scsi 3:0:0:0: CD-ROMHUAWEI   Mass Storage 2.31 PQ: 0 ANSI: 2
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi-1 drive
Uniform CD-ROM driver Revision: 3.20
sr 3:0:0:0: Attached scsi generic sg0 type 5
scsi 4:0:0:0: Direct-Access HUAWEI   MMC Storage  2.31 PQ: 0 ANSI: 2
sd 4:0:0:0: [sda] Attached SCSI removable disk
sd 4:0:0:0: Attached scsi generic sg1 type 0
--



and here what I have disconnecting it
--
usb 2-1: USB disconnect, address 3
ehci_hcd :00:0f.5: HC died; cleaning up
irq 15: nobody cared (try booting with the irqpoll option)
Pid: 1486, comm: khubd Tainted: P  2.6.26-486-voyage #1
 [c0130977] __report_bad_irq+0x24/0x69
 [c013097e] __report_bad_irq+0x2b/0x69
 [c0130b9f] note_interrupt+0x1e3/0x238
 [c0130317] handle_IRQ_event+0x1a/0x3f
 [c013120d] handle_level_irq+0x8a/0xce
 [c0105162] do_IRQ+0x4b/0x61
 [c0103a73] common_interrupt+0x23/0x30
 [c01172ea] __do_softirq+0x2c/0x78
 [c0117358] do_softirq+0x22/0x26
 [c0117471] irq_exit+0x25/0x5d
 [c0105167] do_IRQ+0x50/0x61
 [c0103a73] common_interrupt+0x23/0x30
 [c0113f75] vprintk+0x249/0x26a
 [d0861e84] urb_destroy+0x0/0x19 [usbcore]
 [c01e0c8f] kref_put+0x35/0x3f
 [d08627d5] usb_start_wait_urb+0x7f/0x89 [usbcore]
 [d08629c6] usb_control_msg+0xd2/0xdc [usbcore]
 [c02bb205] printk+0xe/0x11
 [d085ed25] usb_disconnect+0x44/0xd3 [usbcore]
 [d085f7ea] hub_thread+0x43f/0xc32 [usbcore]
 [c010f6b5] __dequeue_entity+0x1f/0x71
 [c0122044] autoremove_wake_function+0x0/0x2d
 [d085f3ab] hub_thread+0x0/0xc32 [usbcore]
 [c0121cb0] kthread+0x36/0x5a
 [c0121c7a] kthread+0x0/0x5a
 [c0103c27] kernel_thread_helper+0x7/0x10
 ===
handlers:
[d08606d0] (usb_hcd_irq+0x0/0x59 [usbcore])
[d08606d0] (usb_hcd_irq+0x0/0x59 [usbcore])
Disabling IRQ #15

Message from sysl...@voyage aoption1 ttyUSB0: GSM modem (1-port) converter now d
isconnected from ttyUSB0
t Sat Jan  1 01:option 2-1:1.0: device disconnected
option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1

voyage vmunix: option 2-1:1.1: device disconnected
Disabling IRQ #1hub 2-0:1.0: hub_port_status failed (err = -19)
5
hub 2-0:1.0: connect-debounce failed, port 1 disabled
hub 2-0:1.0: cannot disable port 1 (err = -19)
--


tried booting with the irqpoll option, doesn't help
Any ideas?



___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux


[Voyage-linux] / is busy and start_led function is not called

2009-06-19 Thread Alex
Hi,

I've installed samba and that's why / cannot be remounted from the
/etc/init.d/voyage-util script. The side effect is that the start_leds function
isn't called at all. If one would call this function first in the start method
then it would work.

BTW What is the side effect of not been able to remountro? 


Thank you


___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux


[Voyage-linux] Setting countrycode in /etc/modules doesn't work on an alix

2009-06-17 Thread Alex
Hi,

I have one more question
For some reason the following record in the /etc/modules doesn't work
ath_pci xchanmode=0 outdoor=1 countrycode=276

after reboot I still have 11 channels

but calling manually

ifdown ath0
modprobe -r ath_pci
modprobe ath_pci countrycode=276
ifup ath0

does the trick.

Did I mistyped something in the /etc/modules?

Thank you


___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux


[Voyage-linux] Re: Problem starting hostapd using Voyage 0.6.1 and madwifi driver on Alix.2d3

2009-04-13 Thread Alex
Gustin Johnson gus...@... writes:

 Also, kismet is showing your AP as unsecured because hostap is not
 running.  If hostap is not running, then kismet is not detecting
 encrypted frames.

Yes, strange that Windows host shows WPA2 enabled AP

 Here are my configs:
 ** note, I have two physical devices in my ALix, which is why the
 bridged device is ath1
 

I tried your settings but it doesn't help
I had some errors though

voyage:~# hostapd /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
Line 20: unknown configuration item 'ctrl_inerface_group'
Line 23: unknown configuration item 'eapol_key_index_wokraround'
2 errors found in configuration file '/etc/hostapd/hostapd.conf'

May be you have a different version of the hostapd. My version is 0.5.10

Could it be that madwifi version of the driver does not support my card?
I have following chipset
wifi0: Atheros AR5213A chip found (MAC 5.9, PHY 2112 4.3, Radio 4.6)

Cannot find madwifi driver version though



___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux


[Voyage-linux] Re: Problem starting hostapd using Voyage 0.6.1 and madwifi driver on Alix.2d3

2009-04-12 Thread Alex
Gustin Johnson gus...@... writes:

 Has the ath0 device been created?
 
 run iwconfig with no arguments.  If you do not see ath0 then the device
 is not being created properly.
 
 I also have my athX device as part of a bridge, which I needed to
 specify in the hostapd.conf.
 
  wpa_pairwise=TKIP CCMP  
 
 Unless you are absolutely sure you need it, there is no reason to use
 TKIP.  This has nothing to do with your problem, just a security tip.
 

I already tried to reply twice but my replies are gone. Something wrong with
this forum. So I try to reply to myself


here is my iwconfig
--
voyage:~# iwconfig 
lono wireless extensions.

eth0  no wireless extensions.

eth1  no wireless extensions.

eth2  no wireless extensions.

wifi0 no wireless extensions.

br0   no wireless extensions.

ath0  IEEE 802.11g  ESSID:Voyage  Nickname:
  Mode:Master  Frequency:2.417 GHz  Access Point: 06:09:5B:D1:35:5C   
  Bit Rate:0 kb/s   Tx-Power:20 dBm   Sensitivity=1/1  
  Retry:off   RTS thr:off   Fragment thr:off
  Encryption key:off
  Power Management:off
  Link Quality=0/70  Signal level=-96 dBm  Noise level=-96 dBm
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:0   Missed beacon:0



and here is a part of my ifconfig
---
voyage:~# ifconfig 
ath0  Link encap:Ethernet  HWaddr 06:09:5b:d1:35:5c  
  inet addr:192.18.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
  inet6 addr: fe80::409:5bff:fed1:355c/64 Scope:Link
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:468 (468.0 B)

br0   Link encap:Ethernet  HWaddr 00:0d:b9:16:65:a8  
  inet addr:192.168.5.200  Bcast:192.168.5.255  Mask:255.255.255.0
  inet6 addr: fe80::20d:b9ff:fe16:65a8/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:484 errors:0 dropped:0 overruns:0 frame:0
  TX packets:482 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:39404 (38.4 KiB)  TX bytes:53787 (52.5 KiB)

wifi0 Link encap:UNSPEC  HWaddr
00-09-99-99-99-99-99-99-00-00-00-00-00-00-00-00  
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:4 errors:0 dropped:0 overruns:0 frame:3
  TX packets:10 errors:1 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:280 
  RX bytes:184 (184.0 B)  TX bytes:1320 (1.2 KiB)
  Interrupt:9 
-

I removed TKIP as was suggested but still cannot start hostapd. Neither can I
connect to the AP wrom a Windows host. Windows shows my AP and it says it is
WPA2 but it cannot connect. 

Strange but if I start a kismet on a linux host it shows my AP as non secure.

ps using wext as driver in hostapd.conf doesn't help (it says no such driver)
psps bridging lan and wlan interfaces doesn't help either




___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux


[Voyage-linux] Re: Problem starting hostapd using Voyage 0.6.1 and madwifi driver on Alix.2d3

2009-04-11 Thread Alex
here is my iwconfig
---
voyage:~# iwconfig 
lono wireless extensions.

eth0  no wireless extensions.

eth1  no wireless extensions.

eth2  no wireless extensions.

wifi0 no wireless extensions.

br0   no wireless extensions.

ath0  IEEE 802.11g  ESSID:Voyage  Nickname:
  Mode:Master  Frequency:2.432 GHz  Access Point: 06:09:5B:D1:35:5C
  Bit Rate=54 Mb/s   Tx-Power:20 dBm   Sensitivity=1/1
  Retry:off   RTS thr:off   Fragment thr:off
  Encryption key:off
  Power Management:off
  Link Quality=0/70  Signal level=-96 dBm  Noise level=-96 dBm
  Rx invalid nwid:1181  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:0   Missed beacon:0




here is part of my ifconfig

voyage:~# ifconfig 
ath0  Link encap:Ethernet  HWaddr 06:09:5b:d1:35:5c  
  inet addr:192.18.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
  inet6 addr: fe80::409:5bff:fed1:355c/64 Scope:Link
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:468 (468.0 B)

br0   Link encap:Ethernet  HWaddr 00:0d:b9:16:65:a8  
  inet addr:192.168.5.200  Bcast:192.168.5.255  Mask:255.255.255.0
  inet6 addr: fe80::20d:b9ff:fe16:65a8/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:484 errors:0 dropped:0 overruns:0 frame:0
  TX packets:482 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:39404 (38.4 KiB)  TX bytes:53787 (52.5 KiB)


so far I've fixed a typo in the interfaces - the address for the ath0 iface was
not correctly set. I also removed tkip as it was suggested. Now Windows XP shows
me my AP with the WPA2 authentication. But no matter what I do I cannot connect
to the AP and I still cannot start the hostapd. I also started kismet on my
linux machine and it shows my AP as not secured! And if I just scan access
points on my linux machine it doesn't show my AP at all! 

I do not know what to do next 


___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux


[Voyage-linux] Re: Problem starting hostapd using Voyage 0.6.1 and madwifi driver on Alix.2d3

2009-04-11 Thread Alex
Gustin Johnson gus...@... writes:

 Has the ath0 device been created?
 
 run iwconfig with no arguments.  If you do not see ath0 then the device
 is not being created properly.
 
 I also have my athX device as part of a bridge, which I needed to
 specify in the hostapd.conf.
 
  wpa_pairwise=TKIP CCMP  
 
 Unless you are absolutely sure you need it, there is no reason to use
 TKIP.  This has nothing to do with your problem, just a security tip.
 

here is my iwconfig
--
voyage:~# iwconfig 
lono wireless extensions.

eth0  no wireless extensions.

eth1  no wireless extensions.

eth2  no wireless extensions.

wifi0 no wireless extensions.

br0   no wireless extensions.

ath0  IEEE 802.11g  ESSID:Voyage  Nickname:
  Mode:Master  Frequency:2.417 GHz  Access Point: 06:09:5B:D1:35:5C   
  Bit Rate:0 kb/s   Tx-Power:20 dBm   Sensitivity=1/1  
  Retry:off   RTS thr:off   Fragment thr:off
  Encryption key:off
  Power Management:off
  Link Quality=0/70  Signal level=-96 dBm  Noise level=-96 dBm
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:0   Missed beacon:0



and here is a part of my ifconfig
---
voyage:~# ifconfig 
ath0  Link encap:Ethernet  HWaddr 06:09:5b:d1:35:5c  
  inet addr:192.18.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
  inet6 addr: fe80::409:5bff:fed1:355c/64 Scope:Link
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:468 (468.0 B)

br0   Link encap:Ethernet  HWaddr 00:0d:b9:16:65:a8  
  inet addr:192.168.5.200  Bcast:192.168.5.255  Mask:255.255.255.0
  inet6 addr: fe80::20d:b9ff:fe16:65a8/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:484 errors:0 dropped:0 overruns:0 frame:0
  TX packets:482 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:39404 (38.4 KiB)  TX bytes:53787 (52.5 KiB)

wifi0 Link encap:UNSPEC  HWaddr
00-09-99-99-99-99-99-99-00-00-00-00-00-00-00-00  
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:4 errors:0 dropped:0 overruns:0 frame:3
  TX packets:10 errors:1 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:280 
  RX bytes:184 (184.0 B)  TX bytes:1320 (1.2 KiB)
  Interrupt:9 
-

I removed TKIP as was suggested but still cannot start hostapd. Neither can I
connect to the AP wrom a Windows host. Windows shows my AP and it says it is
WPA2 but it cannot connect. 

Strange but if I start a kismet on a linux host it shows my AP as non secure.


___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux


[Voyage-linux] Problem starting hostapd using Voyage 0.6.1 and madwifi driver on Alix.2d3

2009-04-10 Thread Alex
Hi,

I'm having problem trying to start hostapt on an Alix.2d3 board with an Atheros
wifi card (AR5213 chipset)

I'm able to turn the wifi interface into managed mode and I can see the unsecure
Access Point (canno't connect to it though). But when I try to start the hostapd
I always get the following message:

voyage:~# hostapd -dd -K -t /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
ioctl(SIOCGIFINDEX): No such device
madwifi driver initialization failed.
946687574.419793: ath0 : Unable to setup interface.
946687574.419854: Flushing old station entries
946687574.419875: Deauthenticate all stations

my hostapd.conf is here
--
interface=ath0 
driver=madwifi
ssid=Voyage
hw_mode=g
channel=1

logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=1

# Debugging: 0 = no, 1 = minimal, 2 = verbose, 3 = msg dumps, 4 = excessive
debug=4

# Dump file for state information (on SIGUSR1)
dump_file=/tmp/hostapd.dump


#macaddr_acl=0
#auth_algs=1
#ignore_broadcast_ssid=0
wpa=2
wpa_psk=57602025b05e9c5765f3d68c8949598473143f3ece66dd0f96ae4b4869b99bd4
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP CCMP  
---

my interfaces are here
---
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.
auto lo
iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

#auto eth0
#iface eth0 inet static
#   address 192.168.5.200
#   netmask 255.255.255.0
#   broadcast 192.168.5.255
#   gateway 192.168.5.1

auto br0
iface br0 inet static
address 192.168.5.200
netmask 255.255.255.0
broadcast 192.168.5.255
gateway 192.168.5.1
bridge_ports eth0 eth1 eth2 eth3

auto ath0
iface ath0 inet static
pre-up wlanconfig ath0 destroy || true
pre-up wlanconfig ath0 create wlandev wifi0 wlanmode ap
post-down wlanconfig ath0 destroy  
address 192.18.4.1   
netmask 255.255.255.0
broadcast 192.168.4.255
#network 192.168.4.0   
madwifi-base wifi0
madwifi-mode Master
wireless-channel 2
wireless-essid Voyage
wireless-txpower 18dBm
#wireless-rate 54M
up iwpriv ath0 mode 3
#up iwconfig ath0 channel 2
#up iwconfig ath0 essid Voyage
#up iwconfig ath0 txpower 18
#up iwconfig ath0 rate auto 
--

I tried to compile the newest version of the hostapd (0.6.8) but it didn't help
either. Some help would be appreciated



___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux


[Voyage-linux] Centralized management system (WUMPST) Mesh Networking

2008-10-11 Thread Alex Jonceski
Hi, 

Does anybody can make a comment about centralized management system
(WUMPST)  Mesh Networking solution Voyage Web Store offers. Is the
software and centralized management system for sale. I have tried to
reach anybody from voyage web store but I have not received reply email.

Any information is welcomed.

Thank you
Alex


___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux