Modify

Opened 3 years ago

#19138 new defect

6to4 INVALID_LOCAL_ADDRESS

Reported by: admin@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Barrier Breaker 14.07
Keywords: ipv6, 6to4 Cc:

Description

After upgrading to Barrier Breaker, my 6to4 on Time Warner stopped working.

root@Gateway:~# ifstatus wan6
{
        "up": false,
        "pending": true,
        "available": true,
        "autostart": true,
        "proto": "6to4",
        "data": {

        },
        "errors": [
                {
                        "subsystem": "6to4",
                        "code": "INVALID_LOCAL_ADDRESS"
                }
        ]
}

When I hard code the Local IPv4 address to my WAN address (which is assigned by DHCP), I get a proper IPv6 address:

root@Gateway:/etc# ifstatus wan6
{
        "up": true,
        "pending": false,
        "available": true,
        "autostart": true,
        "uptime": 1,
        "l3_device": "6to4-wan6",
        "proto": "6to4",
        "updated": [
                "addresses",
                "routes",
                "prefixes"
        ],
        "metric": 0,
        "delegation": true,
        "ipv4-address": [

        ],
        "ipv6-address": [
                {
                        "address": "2002:41be:a2c1::1",
                        "mask": 16
                }
        ],
        "ipv6-prefix": [
                {
                        "address": "2002:41be:a2c1::",
                        "mask": 48,
                        "class": "wan6",
                        "assigned": {
                                "lan": {
                                        "address": "2002:41be:a2c1::",
                                        "mask": 60
                                }
                        }
                }
        ],
        "ipv6-prefix-assignment": [

        ],
        "route": [
                {
                        "target": "::",
                        "mask": 0,
                        "nexthop": "::192.88.99.1",
                        "source": "2002:41be:a2c1::1\/16"
                },
                {
                        "target": "::",
                        "mask": 0,
                        "nexthop": "::192.88.99.1",
                        "source": "2002:41be:a2c1::\/48"
                },
                {
                        "target": "::",
                        "mask": 0,
                        "nexthop": "::192.88.99.1",
                        "source": "::\/128"
                }
        ],
        "dns-server": [

        ],
        "dns-search": [

        ],
        "inactive": {
                "ipv4-address": [

                ],
                "ipv6-address": [

                ],
                "route": [

                ],
                "dns-server": [

                ],
                "dns-search": [

                ]
        },
        "data": {

        }
}

This isn't ideal, because my IP could change. "Leave empty to use the current WAN address" feature isn't working for me?

Attachments (0)

Change History (0)

Add Comment

Modify Ticket

Action
as new .
Author


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

 
Note: See TracTickets for help on using tickets.