Mailinglist Archive: opensuse (1239 mails)

< Previous Next >
Re: [opensuse] IPv6 in Firefox: does it work? The saga continues...
On 2013-06-03 19:46, James Knott wrote:
Carlos E. R. wrote:
I have now these settings:

Status:

IPv6 LAN
IPv6 Address: fc00:0:0:0:fa1a:67ff:fe91:f422
Prefix Length:64

Autoconfiguration Type:DHCPv6


That address is automatic, I do not know where it gets it from. I would like to
set it to
"fc00::1" instead.

It looks like the DHCPv6 server is creating an address from your MAC address.
The give away is the
fffe in the middle. You can still assign an alias with fc00::1 etc., if you
desire. Otherwise just
add that address to your hosts file and give it a name. As I mentioned, I have
no experience with
that router, so can't comment on it's configuration.

That's the local IP of the router. Yes, its MAC is F8:1A:67:91:F4:22.
I can not choose the router IPv6 address, only on IPv4.
I don't see how I could assign an alias to the router address :-?

That is, I want the router to be fc00::1, I can't.

BTW, I see from a previous note your MAC address is F8:1A:67:91:F4:22. Compare
that with your IPv6
address. You should see the fffe inserted in the middle of the MAC, along with
f8 changed to fa.
This is due to that unique/local bit being inverted, as I mentioned earlier.

Ok... I see.

However, although the router has now DHCP6 enabled, the Linux computer does not obtain an IPv6 address from it. Yes, DHCP client (both 4 and 6) are enabled on the computer. I get a link local address instead.

rescate1:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:21:85:16:2D:0B
inet addr:192.168.1.31 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::221:85ff:fe16:2d0b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4271 errors:0 dropped:0 overruns:0 frame:0
TX packets:2762 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3171265 (3.0 Mb) TX bytes:379424 (370.5 Kb)



2013-06-03T20:56:46.652293+02:00 rescate1 kernel: [ 1658.041607] IPv6:
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
2013-06-03T20:56:46.673933+02:00 rescate1 ifup-dhcp[6561]: eth0
Starting DHCP4+DHCP6 client
2013-06-03T20:56:46.676635+02:00 rescate1 dhcpcd[7209]: eth0: dhcpcd 3.2.3
starting
2013-06-03T20:56:46.676654+02:00 rescate1 dhcpcd[7209]: eth0: hardware address
= 00:21:85:16:2d:0b
2013-06-03T20:56:46.677559+02:00 rescate1 dhcpcd[7209]: eth0: broadcasting for
a lease
2013-06-03T20:56:46.833487+02:00 rescate1 ifup-dhcp[6561]: .
2013-06-03T20:56:48.094410+02:00 rescate1 avahi-daemon[722]: Joining mDNS
multicast group on interface eth0.IPv6 with address fe80::221:85ff:fe16:2d0b.
2013-06-03T20:56:48.094747+02:00 rescate1 avahi-daemon[722]: New relevant
interface eth0.IPv6 for mDNS.
2013-06-03T20:56:48.094967+02:00 rescate1 avahi-daemon[722]: Registering new
address record for fe80::221:85ff:fe16:2d0b on eth0.*.
2013-06-03T20:56:49.229290+02:00 rescate1 ifup-dhcp[6561]: .
2013-06-03T20:56:49.281288+02:00 rescate1 kernel: [ 1660.670975] IPv4: martian
source 255.255.255.255 from 192.168.1.1, on dev eth0
2013-06-03T20:56:49.281301+02:00 rescate1 kernel: [ 1660.670979] ll header:
00000000: ff ff ff ff ff ff f8 1a 67 91 f4 22 08 00 ........g.."..
2013-06-03T20:56:49.682003+02:00 rescate1 dhcpcd[7209]: eth0: offered
192.168.1.31 from 192.168.1.1
2013-06-03T20:56:50.187349+02:00 rescate1 dhcpcd[7209]: eth0: checking
192.168.1.31 is available on attached networks
2013-06-03T20:56:51.194365+02:00 rescate1 dhcpcd[7209]: eth0: leased
192.168.1.31 for 86400 seconds
2013-06-03T20:56:51.194794+02:00 rescate1 dhcpcd[7209]: eth0: no renewal time
supplied, assuming 43200 seconds
2013-06-03T20:56:51.195217+02:00 rescate1 dhcpcd[7209]: eth0: no rebind time
supplied, assuming 75600 seconds
2013-06-03T20:56:51.195631+02:00 rescate1 dhcpcd[7209]: eth0: adding IP address
192.168.1.31/24
2013-06-03T20:56:51.195980+02:00 rescate1 avahi-daemon[722]: Joining mDNS
multicast group on interface eth0.IPv4 with address 192.168.1.31.
2013-06-03T20:56:51.196327+02:00 rescate1 avahi-daemon[722]: New relevant
interface eth0.IPv4 for mDNS.
2013-06-03T20:56:51.196636+02:00 rescate1 dhcpcd[7209]: eth0: adding default
route via 192.168.1.1 metric 0
2013-06-03T20:56:51.196985+02:00 rescate1 avahi-daemon[722]: Registering new
address record for 192.168.1.31 on eth0.IPv4.
2013-06-03T20:56:51.359654+02:00 rescate1 ifdown[7726]: eth0 device:
Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet
controller (rev 02)
2013-06-03T20:56:51.478278+02:00 rescate1 ifup[7821]: eth0 device:
Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet
controller (rev 02)
2013-06-03T20:56:51.548362+02:00 rescate1 SuSEfirewall2: Setting up rules from
/etc/sysconfig/SuSEfirewall2 ...
2013-06-03T20:56:51.553930+02:00 rescate1 SuSEfirewall2: using default zone
'ext' for interface eth1
2013-06-03T20:56:51.620142+02:00 rescate1 ifup-dhcp[6561]: .
2013-06-03T20:56:51.626967+02:00 rescate1 SuSEfirewall2: Firewall rules
successfully set
2013-06-03T20:56:51.655974+02:00 rescate1 dhcpcd[7209]: eth0: exiting
2013-06-03T20:56:53.993031+02:00 rescate1 ifup-dhcp[6561]: .
2013-06-03T20:57:04.618519+02:00 rescate1 ifup-dhcp[6561]: last message
repeated 4 times
2013-06-03T20:57:04.618453+02:00 rescate1 network[6148]: eth0 Starting
DHCP4+DHCP6 client. . . . . . . .
2013-06-03T20:57:04.619896+02:00 rescate1 ifup-dhcp[6561]:
2013-06-03T20:57:04.620840+02:00 rescate1 network[6148]: eth0 IP address:
192.168.1.31/24
2013-06-03T20:57:04.621691+02:00 rescate1 ifup-dhcp[6561]: eth0 IP
address: 192.168.1.31/24
2013-06-03T20:57:04.622276+02:00 rescate1 network[6148]: eth0 DHCP6
continues in background
2013-06-03T20:57:04.623284+02:00 rescate1 ifup-dhcp[6561]: eth0 DHCP6
continues in background
2013-06-03T20:57:04.702500+02:00 rescate1 network[6148]: ..done eth1
device: Realtek Semiconductor Co., Ltd. RTL8111/8168
2013-06-03T20:57:04.703128+02:00 rescate1 ifup[8861]: eth1 device:
Realtek Semiconductor Co., Ltd. RTL8111/8168
2013-06-03T20:57:04.704288+02:00 rescate1 network[6148]: No configuration found
for eth1
2013-06-03T20:57:04.704996+02:00 rescate1 ifup[8861]: No
configuration found for eth1
2013-06-03T20:57:04.726882+02:00 rescate1 network[6148]: ..unusedSetting up
service network . . . . . . . . . . . . ...done
2013-06-03T20:57:04.726903+02:00 rescate1 systemd[1]: Started LSB: Configure
network interfaces and set up routing.


The openSUSE firewall blocks it!


2013-06-03T20:57:04.158282+02:00 rescate1 kernel: [ 1675.547633]
SFW2-INext-DROP-DEFLT IN=eth0 OUT=
MAC=00:21:85:16:2d:0b:f8:1a:67:91:f4:22:86:dd
SRC=fe80:0000:0000:0000:d0fa:c7ff:fe67:4031
DST=fe80:0000:0000:0000:0221:85ff:fe16:2d0b LEN=152 TC=0 HOPLIMIT=64 FLOWLBL=0
PROTO=UDP SPT=48629 DPT=546 LEN=112
2013-06-03T20:57:21.676291+02:00 rescate1 kernel: [ 1693.065233]
SFW2-INext-DROP-DEFLT IN=eth0 OUT=
MAC=00:21:85:16:2d:0b:f8:1a:67:91:f4:22:86:dd
SRC=fe80:0000:0000:0000:d0fa:c7ff:fe67:4031
DST=fe80:0000:0000:0000:0221:85ff:fe16:2d0b LEN=152 TC=0 HOPLIMIT=64 FLOWLBL=0
PROTO=UDP SPT=48629 DPT=546 LEN=112
2013-06-03T20:57:56.000281+02:00 rescate1 kernel: [ 1727.389585]
SFW2-INext-DROP-DEFLT IN=eth0 OUT=
MAC=00:21:85:16:2d:0b:f8:1a:67:91:f4:22:86:dd
SRC=fe80:0000:0000:0000:d0fa:c7ff:fe67:4031
DST=fe80:0000:0000:0000:0221:85ff:fe16:2d0b LEN=152 TC=0 HOPLIMIT=64 FLOWLBL=0
PROTO=UDP SPT=48629 DPT=546 LEN=112
2013-06-03T20:59:07.315296+02:00 rescate1 kernel: [ 1798.704924]
SFW2-INext-DROP-DEFLT IN=eth0 OUT=
MAC=00:21:85:16:2d:0b:f8:1a:67:91:f4:22:86:dd
SRC=fe80:0000:0000:0000:d0fa:c7ff:fe67:4031
DST=fe80:0000:0000:0000:0221:85ff:fe16:2d0b LEN=152 TC=0 HOPLIMIT=64 FLOWLBL=0
PROTO=UDP SPT=48629 DPT=546 LEN=112


The port 546 is assigned to it:

dhcpv6-client 546/tcp # DHCPv6 Client
dhcpv6-client 546/udp # DHCPv6 Client
dhcpv6-server 547/tcp # DHCPv6 Server
dhcpv6-server 547/udp # DHCPv6 Server


So, now, after explictly opening that port, I get it:

rescate1:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:21:85:16:2D:0B
inet addr:192.168.1.31 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::221:85ff:fe16:2d0b/64 Scope:Link
inet6 addr: fc00::7fff/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4854 errors:0 dropped:0 overruns:0 frame:0
TX packets:3142 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3288751 (3.1 Mb) TX bytes:430544 (420.4 Kb)


So, I found a new bug in YaST: it forgot to open the firewall for it. Funny that a service for getting an IPv6 needs and IPv4 address first, in order to work... :-?


Now, there are other blocked packets:

2013-06-03T21:06:39.702272+02:00 rescate1 kernel: [ 2251.091036]
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=
SRC=fc00:0000:0000:0000:0000:0000:0000:7fff
DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=188 TC=0 HOPLIMIT=255 FLOWLBL=0
PROTO=UDP SPT=5353 DPT=5353 LEN=148
2013-06-03T21:06:41.840290+02:00 rescate1 kernel: [ 2253.229692]
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=
SRC=fc00:0000:0000:0000:0000:0000:0000:7fff
DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=188 TC=0 HOPLIMIT=255 FLOWLBL=0
PROTO=UDP SPT=5353 DPT=5353 LEN=148


mdns 5353/tcp # Multicast DNS
mdns 5353/udp # Multicast DNS


I wonder if I should open that one :-?

But I don't get it. The SRC is me? The log says that it is an incoming packet.
What is that destination?





And, the router address http://[fc00:0:0:0:fa1a:67ff:fe91:f422]/ is accepted by firefox, but it says the server doesn't respond (Unable to connect / Firefox can't establish a connection to the server at [fc00:0:0:0:fa1a:67ff:fe91:f422])



Now, the other post.

On 2013-06-03 19:32, James Knott wrote:> Carlos E. R. wrote:
There is absolutely no difference between fc00:: and fc00:0:0:0::, as ::
denotes a continuous string
of "0". However, they appear to want a full 64 bits specified for the site
prefix. If it works, go
with what they want.

I can change that number, it is editable. But I do not know what to write
there. O:-)

If you want to use that unique local range, then it's fc00:0.0.0::.

No, I mean the 64. I can put anything, but I don't know what to put.


That would be how computers on your network are assigned addresses. Also, link
local addresses are
not assigned with either of those methods. On my network, router
advertisements (RADVD) are used to
pass the address info to the computers. The host address is then built with
that info and the MAC
address or random number. I do not use DHCPv6.

Right, but you have an outside IPv6 address, or a tunnel. I don't have one.

It should also work with unique local addresses. Give it a try.

Yes, but there is no box to assign an IP to the router.
No outside IPv6 address means RADDV does not get a prefix from the outside, I
have to write it.

As I have never worked with that router, I really can't say much about
configuring it. However,
assigning static addresses is easy in openSUSE. Just go into the network
devices, as you would for
IPv4 and add an address alias with the desired IPv6 address and subnet mask. I
did that here and now
ifconfig shows "inet6 addr: fc00::1/64 Scope:Global". I also set up fc00::2 on
another computer and
can ping6 between them with those addresses.

If I set an static address for the computer, I would also need a static one for
the router (so
that I can write it on the computer routing table), and the router does not
allow it...

Since unique local addresses aren't allowed on the public Internet, don't worry
about it. Use the
unique local addresses for experimenting on your own network. If you want
public IPv6 addresses,
then configure your router for one of the tunnel methods it supports or use the
method I use. I get
my tunnel from gogoNET. http://www.gogo6.com. They have a few servers around
the world. I believe
Amsterdam would be the one closest to you. This service requires running
software on a computer
that acts as the tunnel end point. I run the Linux version on my firewall
computer, but you could
use any computer, Linux, Windows, Mac, etc. on your network. That software can
be configured in
either subnet or single address mode. I run subnet mode on my firewall and
single address mode on
my notebook computer, when away from home. Subnet mode requires registering
your tunnel, but single
address mode does not.

But I mean that in order to configure the networking on my computer, I need the internal IPv6 string of the router. I can not choose it, the router chooses one, automatically. And in order to know what it chooses, I need to open the page on it... using the working IPv4 stack.


This router supports an IPv6 tunnel natively, so that's what I would use, not a tunnel on my computer. It has to be DS-lite, 6RD, or 6to4.

--
Cheers / Saludos,

Carlos E. R.
(from oS 12.3 "Dartmouth" GM (rescate 1))
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >