Jump to content

g8wcn

Active Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

698 profile views

g8wcn's Achievements

Newbie

Newbie (1/14)

  1. Hi there, I want to setup a grep tunnel in my MKIV can someone describe what I need to do, I assume from other Openwrt documenation that I need to do the basic following opkg update opkg install kmod-gre insmod ip_gre.ko ip tunnel add tunnel0 mode gre local 1.2.3.4 remote 2.3.4.5 ttl 64 ip link set tunnel0 up But what I get is "add tunnel gre0 failed: No such device" Any ideas would be extremety and gratefully appeciated!
  2. Looking back in my setup I actually put the script at the end of my 3G modem keep alive script and it looked like this and not as previously published. logger "Keep-Alive Script Executed" if ! [ -b /dev/sda1 ] ; then logger "/dev/sda1 not detected." if [ -b /dev/sda ] ; then logger "/dev/sda detected, so issuing a kick to the /dev/sda device" mount /dev/sda /usb fi fi Not the -b's and not -f
  3. Thanks for the reply, I did notice after publishing my request for help that there appears to be a few other people still suffering from the same issues in another thread on this forum. My issue in the end after tinkering around with the modem settings was down to the mass-storage part not always wanting to mount. It would always get the main device assigned to the E160G dongle mass-storage device i.e. /dev/sda but would not get the /dev/sda1 & /dev/sda2 partitions assigned to the /USB mount and swap points every time even with the time delays suggested in the modem settings in the other thread. The other people on this forum have talked about if you try to mount /dev/sda {to any point} /dev/sda1 & /dev/sda2 suddenly appear! So I added the following script to the SSH keep alive timer script which is called every 5 seconds that first checks for the existence of /dev/sda1, and if not found it the checks for the the existence of the main device /dev/sda, if found it touches /dev/sda with a duff mount, this appears enough to kick off some other process that mounts the /dev/sda1 & /dev/sda2 partitions in accordance with the USB options. if ! [ -f /dev/sda1 ] ; then logger "/dev/sda not detected." if [ -f /dev/sda ] ; then logger "/dev/sda detected, so issuing a kick to the /dev/sda device" mount /dev/sda /usb fi fi Not very nice but it does the job and ensures my mas-storage on my E160G now always mounts on reboot, would be good though to understand what is really going wrong in the boot process as I hate these work arounds.
  4. Help I am trying to get the E160G Modem ram to function so that I have 1 USB device that functions both as a modem and USB storage device. The E160G operates correctly if pluged into a windows box with the ram formated to fat32, I have reformatted the ram to Ext4 as per the instructions on this forum, but I can't see the ram? root@Pineapple:~# lsusb Bus 001 Device 005: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E230/E270/E870 HSDPA/HSUPA Modem Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I think I should be seeing 2 USB devices and I only see the Modem My current config is this *12d1:1003* | 1d6b:0002) echo "Huawei Modem (3-IRL) detected. Attempting mode switch" uci delete network.wan2 uci set network.wan2=interface uci set network.wan2.ifname=ppp0 uci set network.wan2.proto=3g uci set network.wan2.service=wcdma uci set network.wan2.device=/dev/ttyUSB0 uci set network.wan2.apn=3internet uci set network.wan2.username= uci set network.wan2.password= uci set network.wan2.defaultroute=1 uci commit network DefaultVendor=0x12d1 DefaultProduct=0x1003 TargetClass=0xff HuaweMode=1 #usb_modeswitch -v 12d1 -p 1003 -V 1d6b -P 0002 -M 5553424312345678000000000000061b000000020000000000000000000000 -n 1 -s 20 sleep 10; rmmod usbserial sleep 3; insmod usbserial vendor=0x12d1 product=0x1003 sleep 5; /etc/init.d/firewall disable; /etc/init.d/firewall stop logger "3G: firewall stopped" iptables -t nat -A POSTROUTING -s 172.16.42.0/24 -o 3g-wan2 -j MASQUERADE iptables -A FORWARD -s 172.16.42.0/24 -o 3g-wan2 -j ACCEPT iptables -A FORWARD -d 172.16.42.0/24 -m state --state ESTABLISHED,RELATED -i 3g-wan2 -j ACCEPT ;; esac I suspect I need to uncoment out the #usb part, but if I do this I get errors, any suggestions would be most welcome? Thx
  5. Is it possible to switching on logging of Karma and direct the logging to a USB drive?
  6. No need to panic, removed this line and all working, brilliant!!!! #usb_modeswitch -v 12d1 -p 1003 -V 12d1 -P 1003 -M 5553424312345678000000000000061b000000020000000000000000000000 -n 1 -s 20
  7. Hi All Reading this log with interested. I too have a Huawei E220 and can not get it to connect, tried many things suggested here on this message thread and from other places it appears to not be switching over correctly. Any additional ideas would be very welcome!!!!! , Log below!!! 01:05:24 Pineapple user.notice usb-modeswitch: 1-1:1.2: Switching seemingly failed 01:05:23 Pineapple user.notice usb-modeswitch: 1-1:1.2: Switching seemingly failed 01:05:23 Pineapple user.notice usb-modeswitch: 1-1:1.2: Selecting /etc/usb_modeswitch.d/12d1:1003 for mode switching 01:05:23 Pineapple user.notice usb-modeswitch: 1-1:1.2: Manufacturer=HUAWEI_Technologies Product=HUAWEI_Mobile Serial=? 01:05:22 Pineapple user.notice usb-modeswitch: 1-1:1.1: Switching seemingly failed 01:05:21 Pineapple user.notice usb-modeswitch: 1-1:1.1: Switching seemingly failed 01:05:21 Pineapple user.notice root: 3G: firewall stopped 01:05:20 Pineapple user.notice usb-modeswitch: 1-1:1.1: Switching seemingly failed 01:05:19 Pineapple user.notice usb-modeswitch: 1-1:1.1: Switching seemingly failed 01:05:18 Pineapple user.notice usb-modeswitch: 1-1:1.1: Switching seemingly failed 01:05:17 Pineapple user.notice usb-modeswitch: 1-1:1.1: Switching seemingly failed 01:05:16 Pineapple user.notice usb-modeswitch: 1-1:1.1: Switching seemingly failed 01:05:16 Pineapple user.notice usb-modeswitch: 1-1:1.1: Selecting /etc/usb_modeswitch.d/12d1:1003 for mode switching 01:05:16 Pineapple kern.info kernel: [ 3916.780000] usb 1-1: generic converter now attached to ttyUSB1 01:05:16 Pineapple kern.info kernel: [ 3916.770000] usbserial_generic 1-1:1.1: generic converter detected 01:05:16 Pineapple kern.info kernel: [ 3916.770000] usbserial_generic 1-1:1.1: Tell linux-usb@vger.kernel.org to add your device to a proper driver. 01:05:16 Pineapple kern.info kernel: [ 3916.750000] usbserial_generic 1-1:1.1: The "generic" usb-serial driver is only for testing and one-off prototypes. 01:05:16 Pineapple kern.info kernel: [ 3916.750000] usb 1-1: generic converter now attached to ttyUSB0 01:05:16 Pineapple kern.info kernel: [ 3916.740000] usbserial_generic 1-1:1.0: generic converter detected 01:05:16 Pineapple kern.info kernel: [ 3916.730000] usbserial_generic 1-1:1.0: Tell linux-usb@vger.kernel.org to add your device to a proper driver. 01:05:16 Pineapple kern.info kernel: [ 3916.720000] usbserial_generic 1-1:1.0: The "gen
  8. Windows Ethernet Tethering section: Ok sorry stupid me; it was late last night excited and playing with my new toy, wasn't really paying attention to the documents. You can erase this section.
  9. Where can I find the pineapple facing adaptor driver as shown in the wifi Pineapple booket?
  10. Hi Everyone I was wondering if any one knows of an open-source solution that is designed to function as a intruder deception solution? I currently have under test a commercial solution called Mykonos, but like any software nothing is perfect! I have seen that a combination of using both a open source proxy "SQUID" that support ICAP, and "GREASYSPOON" could function in this capacity by allowing the injection of deception content in the HTTP responses, but was wondering if there is any open-source community working on a dedicated project of this type that I could contribute too? Great set of very informative shows team; even as a silver hair aging hacker that has seen it all many times over the presentation style and content is excellent! G8wcn
×
×
  • Create New...