[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Couple of questions: Scope:Compat vs. Scope:Global



Hi. I'm experimenting with IPv6. Earlier, I wrote about tunnel 
problems, the result of which is I'm waiting to establish the tunnel 
until I can put a PC in place of the router, and terminate the tunnel 
there rather than on an internal machine. NAT is a great security 
shortcut, but it does indeed have its limitations.

This morning (insomnia sucks) I've been trying v6 between my two 
debian systems, through a Linksys WAP11. The WAP11 is, as far as I 
can tell, a v4 device only, but it seems to be passing v6 traffic 
without problems:

====
$ ping6 ::192.168.1.20
PING ::192.168.1.20(::192.168.1.20) 56 data bytes
64 bytes from ::192.168.1.20: icmp_seq=1 ttl=64 time=5.01 ms
64 bytes from ::192.168.1.20: icmp_seq=2 ttl=64 time=5.98 ms
64 bytes from ::192.168.1.20: icmp_seq=3 ttl=64 time=4.05 ms
====

and

====
$ ping6 fef::192:168:1:20
PING fef::192:168:1:20(fef::192:168:1:20) 56 data bytes
64 bytes from fef::192:168:1:20: icmp_seq=1 ttl=64 time=4.94 ms
64 bytes from fef::192:168:1:20: icmp_seq=2 ttl=64 time=4.88 ms
64 bytes from fef::192:168:1:20: icmp_seq=3 ttl=64 time=7.45 ms
====

Ssh also works, but ftp doesn't. I tried command line ftp, lftp, and 
ftp://fef::192:168:1:20/ inside konqueror, as well as by hostname, 
and they all say unknown host or malformed url. I didn't find a 
"ftp6" through dselect, are the ftp clients just not v6 compatible?

Lastly, I have a technical question. I addressed the hosts not only 
with fef::192:168:1:2 and fef::192:168:1:20 but also ::192.168.1.20 
and ::192.168.1.2

====
#ifconfig
eth1  Link encap:Ethernet  HWaddr 00:02:8A:94:48:01
      inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
      inet6 addr: fe80::202:8aff:fe94:4801/64 Scope:Link
      inet6 addr: fef::192:168:1:2/120 Scope:Global
      inet6 addr: ::192.168.1.2/120 Scope:Compat
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:4107404 errors:0 dropped:0 overruns:0 frame:0
      TX packets:3082080 errors:4354 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:721410736 (687.9 MiB)  TX bytes:404624912 (385.8 MiB)
      Interrupt:177 Memory:d4006000-d4006ff
====

Does the "Scope:Compat" confir any automatic functions? Routing, NAT, 
v6 to v4 conversions? Is it treated as Global or Local address space? 
I notice that even though "fef::" is considered private, its notation 
above is "Scope:Global". Or is "Scope:Compat" just notated as 
"Compat" for human readability?

Darned Second-System syndrome.

Curt-


--- 
September 11th, 2001
The proudest day for gun control and central 
planning advocates in American history



Reply to: