Modify

Opened 4 years ago

Closed 4 years ago

#14208 closed enhancement (fixed)

wan doesnt configure when ip6gw is link-local

Reported by: Lars Schotte <gustik@…> Owned by: developers
Priority: response-needed Milestone: Chaos Calmer 15.05
Component: base system Version: Trunk
Keywords: Cc:

Description

hi folks,

i ve noticed that when i tried to set the ip6gw on static ipv6 configuration of the wan port, it does not configure at all and completely ignores all configuration on that network interface (also ipv4) getting it inaccessible from that port (what can be dangerous when it happens on br-lan).

so my suggestion would consist of two parts:
1.) change the scripts so that a misconfiguration of one parameter does not tear down all configuration getting the router inaccessible from the net.
so that would mean finer granularity.
2.) then it would be nice to be able to configure ip6gw with a parameter like "fe80::XXX:XXX:XXX:XXXX%eth1".

OK?

Attachments (0)

Change History (9)

comment:1 Changed 4 years ago by Lars Schotte <gustik@…>

hi folks,

i ve noticed that when i tried to set the ip6gw to a link local address in static ipv6 configuration of the wan port, it does not configure at all and completely ignores all configuration on that network interface (also ipv4) getting it inaccessible from that port (what can be dangerous when it happens on br-lan).

so my suggestion would consist of two parts:
1.) change the scripts so that a misconfiguration of one parameter does not tear down all configuration getting the router inaccessible from the net.
so that would mean finer granularity.
2.) then it would be nice to be able to configure ip6gw with a parameter like "fe80::XXX:XXX:XXX:XXXX%eth1".

OK?

comment:2 follow-up: Changed 4 years ago by jow

  • Priority changed from lowest to response-needed

Please paste the offending configuration.

comment:3 in reply to: ↑ 2 Changed 4 years ago by Lars Schotte <gustik@…>

Replying to jow:

Please paste the offending configuration.

sorry, but i am not in that country any more where that router is standing, so all i can do is to try to reproduce that on my router here and paste that conf then, when that would be fine for you?

comment:4 Changed 4 years ago by anonymous

As long as it reproduces the issue its fine for me, but tbh what you describe here sounds awkward and I suspect a more general configuration mistake.

comment:5 Changed 4 years ago by Lars Schotte <gustik@…>

OK, i pulled this out of my ass and put it into /etc/config/networks (you can try it on your own if you wish to):

config interface dsl
        option ifname   eth1
        option proto    static
        option ipaddr   192.168.41.1
        option netmask  255.255.255.0
        option ip6addr  '20a1::43:43'
        # option ip6gw  'fe80::55:56:32%eth1'

configuration works -> configures with ipv6 and ipv4.
but as soon as you do:

config interface dsl
        option ifname   eth1
        option proto    static
        option ipaddr   192.168.41.1
        option netmask  255.255.255.0
        option ip6addr  '20a1::43:43'
        option ip6gw  'fe80::55:56:32%eth1'

neither ipv6 nor ipv4 works.

btw. "general configuration mistake" is part of the bug report.

comment:6 Changed 4 years ago by Lars Schotte <gustik@…>

btw. that reproduced configuration on that fictional "dsl" interface was done on ATTITUDE ADJUSTMENT (12.09, r36088) on a WNDR3800, so you can consider this a general issue on ALL versions, not just trunk.

comment:7 Changed 4 years ago by cyrus

The scope-id (%eth1) seems redundant to me as the interface is already specified elsewhere (e.g. "option ifname eth1" in your example) so supporting this doesn't really make sense I guess.

I don't agree with the "single parameter wrong" as well. If you fear breaking your IPv4 config, you could easily add a second interface and make it an alias with option ifname "@dsl" and configure your IPv6 settings there. I would find it rather surprising if a (partly) misconfigured interface would come up and so something undefined.

comment:8 Changed 4 years ago by Lars Schotte <gustik@…>

OK, i could reproduce that without %eth1 it works and automatically adds the eth1 as dev.
so that could be marked as resolved.

that solution with alias did not come up to my mind, of course, that would be a solution.
then it would be advisable to have ipv6 and ipv4 configured apart from each other as different aliases.

not exactly how i expected it, but i see your point.

comment:9 Changed 4 years ago by cyrus

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

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


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

 
Note: See TracTickets for help on using tickets.