Modify

Opened 2 years ago

Last modified 2 years ago

#21322 reopened defect

Incorrect routing IPv6 on 15.05

Reported by: maxyamus@… Owned by: developers
Priority: normal Milestone:
Component: packages Version: Chaos Calmer 15.05
Keywords: Cc:

Description

Hello,

I have issues with ipv6 routing with freshly upgraded to stable release 15.05.

Here is my config:

interfaces: 
config interface 'wan'
        option ifname 'eth1'
        option bridge 'false'
        option proto 'dhcp'
        option broadcast '1'
        option peerdns '0'
        option dns '208.67.220.222 208.67.222.220 208.67.220.220 208.67.222.222'

config interface 'wan61'
        option ifname '@wan'
        option proto '6rd'
        option ip6prefix '2602:100::'
        option ip6prefixlen '32'
        option dns '2001:4860:4860::8888 2001:4860:4860::8844'
        option peeraddr '68.114.165.1'
        option ip4prefixlen '0'
        option auto '0'
        option ipaddr 'my ip here.. '


For some reason I get "::" in front of ipv4 gw evertywhere, though, everything set correctly in configs.

ip -6 r s
default from 2602:100:18ab:67b0::/64 via ::68.114.165.1 dev 6rd-wan61  proto static  metric 4096 
default from 2602:100::/32 via ::68.114.165.1 dev 6rd-wan61  proto static  metric 4096 
::/96 dev 6rd-wan61  proto kernel  metric 256 
2602:100:18ab:67b0::/64 dev br-lan  proto static  metric 1024 
unreachable 2602:100:18ab:67b0::/64 dev lo  proto static  metric 2147483647  error -128
2602:100::/32 dev 6rd-wan61  proto kernel  metric 256 
fe80::/64 dev eth0  proto kernel  metric 256 
fe80::/64 dev br-guest  proto kernel  metric 256 
fe80::/64 dev br-lan  proto kernel  metric 256 
fe80::/64 dev wlan0  proto kernel  metric 256 
fe80::/64 dev eth1  proto kernel  metric 256 

and ifstatus wan61, again "::" in front of ipv4 everywhere.

root@HGW:~# ifstatus wan61
{
	"up": true,
	"pending": false,
	"available": true,
	"autostart": true,
	"uptime": 85601,
	"l3_device": "6rd-wan61",
	"proto": "6rd",
	"updated": [
		"addresses",
		"routes",
		"prefixes"
	],
	"metric": 0,
	"delegation": true,
	"ipv4-address": [
		
	],
	"ipv6-address": [
		{
			"address": "2602:100:18ab:67b0::1",
			"mask": 32
		}
	],
	"ipv6-prefix": [
		{
			"address": "2602:100:18ab:67b0::",
			"mask": 64,
			"class": "wan61",
			"assigned": {
				"lan": {
					"address": "2602:100:18ab:67b0::",
					"mask": 64
				}
			}
		}
	],
	"ipv6-prefix-assignment": [
		
	],
	"route": [
		{
			"target": "::",
			"mask": 0,
			"nexthop": "::68.114.165.1",
			"metric": 4096,
			"source": "2602:100:18ab:67b0::1\/32"
		},
		{
			"target": "::",
			"mask": 0,
			"nexthop": "::68.114.165.1",
			"metric": 4096,
			"source": "2602:100:18ab:67b0::\/64"
		}
	],
	"dns-server": [
		"2001:4860:4860::8888",
		"2001:4860:4860::8844"
	],
	"dns-search": [
		
	],
	"inactive": {
		"ipv4-address": [
			
		],
		"ipv6-address": [
			
		],
		"route": [
			
		],
		"dns-server": [
			
		],
		"dns-search": [
			
		]
	},
	"data": {
		
	}
}

Please advice,

Thank you.

Attachments (0)

Change History (3)

comment:1 Changed 2 years ago by anonymous

Some additional info:

It is - CHAOS CALMER (15.05, r46767)

And interface.. my public ipv4 as inet6 addr???

root@HGW:~# ifconfig 
6rd-wan61 Link encap:IPv6-in-IPv4  
          inet6 addr: 2602:100:18ab:67b0::1/32 Scope:Global
          inet6 addr: ::24.171.xxx.xxx/96 Scope:Compat
          UP RUNNING NOARP  MTU:1280  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:173 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:15756 (15.3 KiB)

comment:2 Changed 2 years ago by jow

  • Resolution set to not_a_bug
  • Status changed from new to closed

comment:3 Changed 2 years ago by anonymous

  • Resolution not_a_bug deleted
  • Status changed from closed to reopened

Ok, didn't know about mapped IPv6, notation, though, problem still exists as I can not ping out or access any IPv6 addresses, even with firewall completely disabled.

ifconfig 
RX bytes:0 (0.0 B) TX bytes:15756 (15.3 KiB)

Thank you.

Add Comment

Modify Ticket

Action
as reopened .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.