I have absolutely no idea how to get started

[Vegard]

I'm plugging in the USBArmory, I've tried setting the IP as 10.0.0.2 on the host for a windows machine, a linux mint, a raspbian, and still the damn usbarmory does not get a 10.0.0.1 IP and I can't ssh into the IP it has with usbarmory/usbarmory.

Can somebody please help explain this to me as you would to a child?

[Andrea Barisani]

On 27 Mar 2016 2:10 p.m., "Vegard" <vegard.pet...@gmail.com> wrote:
>
>
> I'm plugging in the USBArmory, I've tried setting the IP as 10.0.0.2 on the host for a windows machine, a linux mint, a raspbian, and still the damn usbarmory does not get a 10.0.0.1 IP and I can't ssh into the IP it has with usbarmory/usbarmory.
>
> Can somebody please help explain this to me as you would to a child?
>

First of all, does the LED blinks once the USB armory is powered up? Did your USB armory come with a pre-imaged microSD card?

> --
> You received this message because you are subscribed to the Google Groups "USB armory" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to usbarmory+...@googlegroups.com.
> To post to this group, send email to usba...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/usbarmory/a6ace991-8267-4a29-b3da-7701ff87d75b%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Vegard]

Yes, the LED blinks to indicated heartbeat.

This is the output from ifconfig:

usb0      Link encap:Ethernet  HWaddr 1a:55:89:a2:69:42
          inet addr:169.254.47.31  Bcast:169.254.255.255  Mask:255.255.0.0
          inet6 addr: fe80::c3f8:295f:9cdc:2943/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:56 errors:0 dropped:0 overruns:0 frame:0
          TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1880 (1.8 KiB)  TX bytes:23019 (22.4 KiB)

And from lsusb:

Bus 001 Device 011: ID 0525:a4a2 Netchip Technology, Inc. Linux-USB Ethernet/RNDIS Gadget

But when I do:

ssh 169.254.47.31 -l usbarmory 

 

It won't accept "usbarmory" as password and I have no idea what I am doing wrong.

This is the /etc/network/interfaces on the raspberry I'm using:

# interfaces(5) file used by ifup(8) and ifdown(8)
# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
#auto lo
#iface lo inet loopback
#iface eth0 inet manual
iface eth0 inet static
        address 10.0.0.2
        netmask 255.255.255.0
        #broadcast 10.0.0.254
        gateway 10.0.0.2
iface usb0 inet manual
        address 10.0.0.1
        netmask 255.255.255.0
        gateway 10.0.0.2

 

[Philipp Adolf]

The ifconfig output shows that your computer is using the IP address 169.254.47.31, which I think is one of the "I can't get an address automatically so I'll just use a random one" addresses. When you do ssh 169.254.47.31 you're effectively doing ssh 127.0.0.1 and trying to access your own computer.

Your iface eth0 should not use 10.0.0.2 - this one is the built-in ethernet interface of your Pi which should be connected to the internet. You'll probably want dhcp for this. For your usb0 you set manual in which case address, netmask and gateway should be ignored, I think. Set usb0 to static and use the settings you currently have for eth0. Set the address for this to 10.0.0.2 - the network config on your Pi sets the IP address the Pi uses (the host, 10.0.0.2), the USB Armory automatically sets it's address to 10.0.0.1.

Once you have done that and restarted the interfaces (or just the whole Pi if you don't know how to - I don't usually use Raspbian so I can't tell you) you should be able to 'ssh usba...@10.0.0.1' and log in with password 'usbarmory'.

Hope this helps,

Philipp Adolf

P.S.: I think using ssh $IP -l usbarmory won't work. SSH arguments usually have to come before the address you're trying to log into or they will be sent as a command to execute on the server. So use ssh -l usbarmory $IP or just ssh usbarmory@$IP.

--
You received this message because you are subscribed to the Google Groups "USB armory" group.
To unsubscribe from this group and stop receiving emails from it, send an email to usbarmory+...@googlegroups.com.
To post to this group, send email to usba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/usbarmory/1258490c-9ba3-4d4b-a485-ec1a4d513e09%40googlegroups.com.

[Andrea Barisani]

Hello Vegard,

please let me know if you have further issues, you might also find our FAQ to be helpful: https://github.com/inversepath/usbarmory/wiki/Frequently-Asked-Questions-(FAQ)

Cheers

To view this discussion on the web visit https://groups.google.com/d/msgid/usbarmory/CAOG%2BsoG8MXGtH8i1S5cpBEWnOs7daP-c0bmyXDocg3SiN226YQ%40mail.gmail.com.

[Vegard]

Yeah I do have further issues.

Let's take this from the start and not be complete autists assuming that everybody can read our minds and / or knows exactly what we know, shall we?

Step 1: I purchase a USBArmory and receive it in the mail
Step 2: I download an image onto a MicroSD-card and put it into the damn thing
Step 3: I shove the USB-connector into the USB-slot of a computer - for simplicity's sake, let's assume it's a popular linux-distribution such as debian and that it has no other network set up

Step 4: What files do I edit and what do I write in them in order to be able to ssh into the USBArmory?


Seriously, is it really that difficult to write a guide to get things up and running?

[Andrea Barisani]

On Thu, Mar 31, 2016 at 11:03 AM, Vegard <vegard.pet...@gmail.com> wrote:

Yeah I do have further issues.

Let's take this from the start and not be complete autists assuming that everybody can read our minds and / or knows exactly what we know, shall we?

Step 1: I purchase a USBArmory and receive it in the mail
Step 2: I download an image onto a MicroSD-card and put it into the damn thing

Which image? There are several available.

 

Step 3: I shove the USB-connector into the USB-slot of a computer - for simplicity's sake, let's assume it's a popular linux-distribution such as debian and that it has no other network set up

Step 4: What files do I edit and what do I write in them in order to be able to ssh into the USBArmory?


Seriously, is it really that difficult to write a guide to get things up and running?

Setting networking up on Linux distributions is a very common tasks that pretty much all of the USB armory users are able to undertake using standard Linux distribution documentation as the task is not specific to the USB armory. The network interface exposed by the USB armory works just like any other.

I am sorry that you can't get the USB armory running but we are here precisely to help you in getting that sorted out.

For now I will assume that you are running Debian on the USB armory and not other images such as Kali. Also, before going in modifying your system configuration, I will suggest that you manually configure your network to see if things are up and running correctly.

1. Ensure that your existing network connections do not use/overlap with subnet 10.0.0.0/24

2. Ensure that the USB armory LED is blinking and that you see a "usb0" network interface after plugging your USB armory, depending on the Debian version you might see different names, if so and if certain that the interface was added after plugging the USB armory then replace "usb0" in my instructions with your interface name.

3. Set 10.0.0.2/24 to your "usb0" interface as follows:

sudo ip addr add 10.0.0.2/24 dev usb0

4. Your network is now configured and you should be able to ssh to the USB armory as follows:

ssh usba...@10.0.0.1

The default password is "usbarmory" for the Debian image.

If this works, and you can SSH to the USB armory, then we can worry about configuring this persistently in your distribution configuration and enable Internet connection sharing.

I hope this helps.

Cheers

 

To view this discussion on the web visit https://groups.google.com/d/msgid/usbarmory/22ccc17c-87af-4f76-87f6-a5c10fb875ca%40googlegroups.com.

[Vegard]

Yeah that worked, thanks.
Now at least I know there isn't anything wrong anywhere.

[Andrea Barisani]

On Thu, Mar 31, 2016 at 4:03 PM, Vegard <vegard.pet...@gmail.com> wrote:

Yeah that worked, thanks.
Now at least I know there isn't anything wrong anywhere.

Making this configuration permanent highly depends on the specific Linux distribution that you are using and its version. If you would communicate the OS details on your USB host I can help you in setting this configuration and have it automatically activated once you plug in your USB armory.

Cheers

 

--
You received this message because you are subscribed to the Google Groups "USB armory" group.
To unsubscribe from this group and stop receiving emails from it, send an email to usbarmory+...@googlegroups.com.
To post to this group, send email to usba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/usbarmory/e5e3bc8f-4a55-47ab-99aa-96941be45dc4%40googlegroups.com.

[Vegard]

I'm just playing with it on a Raspi1 (with raspian jessie I guess) for now, uname -a gives "Linux raspberrypi 4.1.19+ #858 Tue Mar 15 15:52:03 GMT 2016 armv6l GNU/Linux".

So I'm guessing I need to do something to /etc/init.d/network or somesuch?

I'm still getting the wrong IP-address assigned for the USBArmory:
---

pi@raspberrypi:~ $ ifconfig

eth0      Link encap:Ethernet  HWaddr b8:27:eb:4f:23:70

          inet addr:192.168.1.11  Bcast:192.168.1.255  Mask:255.255.255.0

          inet6 addr: fe80::536f:6006:7688:3194/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:15773 errors:0 dropped:5124 overruns:0 frame:0

          TX packets:4916 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:3985328 (3.8 MiB)  TX bytes:689445 (673.2 KiB)

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:256 errors:0 dropped:0 overruns:0 frame:0

          TX packets:256 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:20016 (19.5 KiB)  TX bytes:20016 (19.5 KiB)

usb0      Link encap:Ethernet  HWaddr 1a:55:89:a2:69:42

          inet addr:169.254.47.31  Bcast:169.254.255.255  Mask:255.255.0.0

          inet6 addr: fe80::c3f8:295f:9cdc:2943/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:244 errors:0 dropped:0 overruns:0 frame:0

          TX packets:379 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:20727 (20.2 KiB)  TX bytes:42743 (41.7 KiB)

---

And I'm kind of messing with /etc/network/interfaces:
---

pi@raspberrypi:~ $ cat /etc/network/interfaces

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd

# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:

source-directory /etc/network/interfaces.d

auto lo

iface lo inet loopback

iface eth0 inet manual

#iface eth0 inet static

#       address 10.0.0.2

#       netmask 255.255.255.0

        #broadcast 10.0.0.254

#       gateway 10.0.0.2

iface usb0 inet static

        address 10.0.0.1

        netmask 255.255.255.0

        gateway 10.0.0.2

allow-hotplug wlan0

iface wlan0 inet manual

    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug wlan1

iface wlan1 inet manual

    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

---

[Vegard]

I just wanted to say I got it working by following the instructions from this topic: https://groups.google.com/d/topic/usbarmory/SZCN2WxOo60/discussion

Thanks for your help, Andrea! :)

[muntea...@gmail.com]

I have the same problem . How do you solved ?

[Andrea Barisani]

On Wednesday, February 22, 2017 at 1:41:37 PM UTC+1, muntea...@gmail.com wrote:

I have the same problem . How do you solved ?

Which image are you using on the USB armory and is the LED blinking?

Thanks

[muntea...@gmail.com]

image from SD card received together with USB Armory from Crowd Supply

[Andrea Barisani]

On Wednesday, February 22, 2017 at 2:19:28 PM UTC+1, muntea...@gmail.com wrote:

image from SD card received together with USB Armory from Crowd Supply

Does the LED blink and which OS is it used on the host side?

[muntea...@gmail.com]

Yes , the led is blinking , on network panel RNDIS Gadget is connected

[Andrea Barisani]

On Wednesday, February 22, 2017 at 2:21:32 PM UTC+1, muntea...@gmail.com wrote:

Yes , the led is blinking , on network panel RNDIS Gadget is connected

Assign IP address 10.0.0.2 with netmask 255.255.255.0 to the RNDIS Gadget, once you have done that you should be able to SSH to the USB armory at its IP address (10.0.0.1, user usbarmory password usbarmory)

[muntea...@gmail.com]

I am using MacBook with macOS Sierra 10.12.3

[muntea...@gmail.com]

Yes , led is blinking , on network panel shows connected , using macOS Sierra 10.12.3

[muntea...@gmail.com]

I set this ten times but can't connect with 10.0.0.1 . I'm not very experienced but this looks simple settings .

IPv4 : manually

IP adress : 10.0.0.2

Subnet mask : 255.255.255.0

Router : 192.168.0.1

" 10.0.0.1 refused to connect. "

[Andrea Barisani]

On Wed, Feb 22, 2017 at 2:34 PM, <muntea...@gmail.com> wrote:

I set this ten times but can't connect with 10.0.0.1 . I'm not very experienced but this looks simple settings .

IPv4 : manually

IP adress : 10.0.0.2

Subnet mask : 255.255.255.0

Router : 192.168.0.1

1) Leave Router blank.

2) Ensure that your other interface addresses are not conflicting with network 10.0.0.0/24

3) Kindly show the SSH command you are using.

Thanks

 

" 10.0.0.1 refused to connect. "

On Wednesday, February 22, 2017 at 3:23:49 PM UTC+2, muntea...@gmail.com wrote:

I am using MacBook with macOS Sierra 10.12.3

On Wednesday, February 22, 2017 at 3:21:32 PM UTC+2, muntea...@gmail.com wrote:

Yes , the led is blinking , on network panel RNDIS Gadget is connected

On Wednesday, February 22, 2017 at 3:19:28 PM UTC+2, muntea...@gmail.com wrote:

image from SD card received together with USB Armory from Crowd Supply

On Wednesday, February 22, 2017 at 2:48:44 PM UTC+2, Andrea Barisani wrote:

On Wednesday, February 22, 2017 at 1:41:37 PM UTC+1, muntea...@gmail.com wrote:

I have the same problem . How do you solved ?

Which image are you using on the USB armory and is the LED blinking?

Thanks

--
You received this message because you are subscribed to the Google Groups "USB armory" group.

To unsubscribe from this group and stop receiving emails from it, send an email to usbarmory+unsubscribe@googlegroups.com.

To post to this group, send email to usba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/usbarmory/227c4899-4408-4eec-b87d-6b19354d3ad9%40googlegroups.com.

[muntea...@gmail.com]

thanks I think I found the problem . I will ask later if have any issues . Thanks again .

To unsubscribe from this group and stop receiving emails from it, send an email to usbarmory+...@googlegroups.com.