On 2016-02-18 17:53, Bruno Randolf wrote:
> On 02/18/2016 04:43 PM, John Crispin wrote:
>> ideally this gets handled generically, which wont be easy as these are
>> all virtual interfaces. maybe if we just add the code in a generic place
>> rather than duplicate it lots of times.
>
> Ideally -
On 02/18/2016 04:43 PM, John Crispin wrote:
> ideally this gets handled generically, which wont be easy as these are
> all virtual interfaces. maybe if we just add the code in a generic place
> rather than duplicate it lots of times.
Ideally - yes... but where?
Also I don't understand why these
On 18/02/2016 17:36, Bruno Randolf wrote:
> On 02/18/2016 02:00 PM, Jakub Jančo wrote:
>> You should add all important options to networking:
>> metric
>> defaultroute
>> peerdns
>> These are important for remote management and dns resolving.
>>
>> You can see my not yet applied patch
>>
On 02/18/2016 02:00 PM, Jakub Jančo wrote:
> You should add all important options to networking:
> metric
> defaultroute
> peerdns
> These are important for remote management and dns resolving.
>
> You can see my not yet applied patch http://patchwork.ozlabs.org/patch/581065/
> It works for me.
You should add all important options to networking:
metric
defaultroute
peerdns
These are important for remote management and dns resolving.
You can see my not yet applied patch http://patchwork.ozlabs.org/patch/581065/
It works for me.
--
S pozdravom Jakub Janco
On Wed, Feb 17, 2016 at 7:21
Same as for other network interfaces, the option 'metric' should be respected.
(Unfortunately I could not test these changes, since I don't have these modems
and QMI is broken on trunk for me... But the same method is used in the
"HiLink" script I just added before.)
Signed-off-by: Bruno Randolf
