Hi.
On Thu, 26 Feb 2015 13:04:14 -0600
David Wright <deb...@lionunicorn.co.uk> wrote:
> Quoting Reco (recovery...@gmail.com):
> > On Thu, Feb 26, 2015 at 08:07:46AM -0300, Renaud OLGIATI wrote:
> > > On Thu, 26 Feb 2015 11:57:39 +0100
> > > Jochen Spieker <m...@well-adjusted.de> wrote:
> > >
> > > > > Why not just connect directly RJ45 to RJ45 ?
> > >
> > > > The only reason I didn't mention that possibility is that I didn't want
> > > > to have to explain how to manually configure IP addresses. :) If the OP
> > > > has a home router, chances are that IP networking "just works".
> > >
> > > Not much of a problem: (Install and) open wicd, Wired Network Properties,
> > > click Use Static IPs, and 192.168.1.x, and 255.255.255.0
> >
> > Installing wicd would require working IP networking in the first place,
> > isn't it?
> >
> > Besides, one doesn't need to configure anything as ipv6 provides those
> > funny fe80:/64 addresses out of the box. Sure, they won't work outside
> > of a local network segment, but that's not the issue here.
>
> No configuring: great. You just have to know how to use them...
That's the trick, isn't it?
> So, I pull the cat5 cable out of a wired host, and stick into a
> wireless laptop's eth0 socket. Both were chatting happily to a router
> with ipv4 before. What do I do next to copy a file to the other host?
> Both ways please, because there's an assymetry: only the wired host
> "knows" it's been isolated from its gateway; the laptop is still happy.
> ie,
>
> wired ~$ scp a-file <fill-this-in-please>:destination-file-on-laptop
> laptop ~$ scp a-file <fill-this-in-please>:destination-file-on-wired
First, you invoke 'ip a l dev eth0' on both hosts.
In the case the interface lacks 'UP' flag, you invoke 'ip l s dev eth0
up'.
Once both interfaces are up, invoke 'ip a l dev eth0' again, and search
for the strings that look like (on both source and target hosts):
inet6 fe80::2867:acff:fef1:968d/64 scope link
valid_lft forever preferred_lft forever
In this example, 'fe80::2867:acff:fef1:968d' is so called 'link-local'
ipv6 address of the host.
Next, you invoke from source host:
ssh <target_host_user>@<target_host_ipv6>%eth0
And, if everything goes well, you should see customary 'The
authenticity of host … can't be established' message.
To copy the needed files, you invoke from the source host:
scp -r <directory_containing_your_files_here> \
<target_host_user>@[<target_host_ipv6>%eth0]:<source_dir>
I.e, to copy /home/user/Documents from one host to another, use:
scp -r /home/user/Documents \
user@[fe80::2867:acff:fef1:968d%eth0]:/home/user
The definition of 'source' and 'target' hosts is left as an exercise
for the readers.
Of course, there're more complex (but faster) ways to copy files,
but the basics are here.
Reco
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/20150226235347.c80ba110fbb235da95406...@gmail.com
