No `pppd`: HOW can install ?

And in this case you can do blinkenlight debugging. If there is link then there is light on the nics.

Insert cable. If the link light fires up there is a connection. Otherwise, you need another cable.

This should take all of 10 seconds to find out.

-- mrr

The Pi has Auto-MDIX. You don't need a crossover cable.

The LEDs are labelled on the board. However, just for clarity:

FDX = Full-Duplex connection LNK = Link established (also flashes when data is received or transmitted)

Dom

Whilst you're right about it not supporting gigabit, I'd like to know why you are only seeing 25Mb/sec through the Ethernet...

I ask as I regularly see 95+Mb/sec into (or out of) a Pi in the tests I've done.

Thats with max sized packets (ie. 1500 bytes) - e.g. simple FTP test: (ftp is running on a Pi)

ftp> get test100 /dev/null local: /dev/null remote: test100 200 PORT command successful 150 Opening BINARY mode data connection for test100 (104857600 bytes) 226 Transfer complete 104857600 bytes received in 8.91 secs (11490.2 kB/s) ftp>

Running iperf between a Pi (fuzepi) and my desktop (yakko):

gordon @ fuzepi: iperf -c yakko ------------------------------------------------------------ Client connecting to yakko, TCP port 5001 TCP window size: 21.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.254.38 port 54013 connected with 192.168.254.2 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 96.5 MBytes 80.8 Mbits/sec

So even on the rather small transfer size iperf uses, I'm still seeing much more than your 25Mb/sec.

If I take the packet size down to about 60 bytes then yes, I do see much reduced throughput, but thats not entirely unnexpected on lower power processors:

gordon @ fuzepi: iperf -c yakko -l 60 ------------------------------------------------------------ Client connecting to yakko, TCP port 5001 TCP window size: 21.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.254.38 port 54017 connected with 192.168.254.2 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 34.4 MBytes 28.9 Mbits/sec

So a bit confused about your 25Mb/sec figure...

Gordon

OK, Thanks, I've filed that. So far I've resisted using a national-railway-system to connect ONE rPi to ONE PC, plus the fact that fiddling with eth-settings on the PC, screwed the existing inet capability.

People don't want minimalism. They encourage feature creep. Soon the rPi will need it's own air-conditioner-on-its-back, like the WinTel monopolists.

Good, thanks.

Following:- ]So just plug this cable in and configure your computers to static IPs ] ]PC: ]ifconfig eth0 192.168.0.1 ]rPI: ]ifconfig eth0 192.168.0.2 ] ]and you are done. If you persist on a connection between 2 computers...

all the LEDs came on! Including at the PC's eth0 socket. And I lost keybrd: on one terminal.

What are the simplest commands for the 2-ends to see each other?

==TIA.

In order to use RPi's installer, which knows the: current-fetchURL, all dependencies ...etc. I started 2 approaches:

1. apparently the popular: RpI -> PC -> Inet
2. RPi+pppd -> 3Gdongle -> Inet

AFAIK ethernet is efficient for rapid communications between MANY devices. For one-to-one communication, it's an absurdity, like phoning your spouse who is sitting next to you!

Someone posted the commands for the PC & RPi sides to . But I still don't know how to transfer data: PC RPi. Nor will I surrender to investigating the adsurdity.

RPi+pppd -> 3Gdongle -> Inet works beyond expecations !

There are two ways to do it:

1. Get a SD card adapter to the PC, mount the RPi card in Linux running on the PC and just maintain the mounted RPi filesystem to your heart's content.
2. If you have a TCP/IP connection to both the RPi and PC, get WinSCP to the PC and connect to SSH server on the RPi.