On Wed, Feb 18, 2015 at 9:45 PM, Adam Carter wrote:
>>
>> If it's a static network (meaning, the computer does not usually moves
physically), why don't you use a .network unit file (man 5 systemd.network)?
>>
>>
>> I'm converting my configs over to that now. Thanks.
>
>
> Another question - i have
>
> If it's a static network (meaning, the computer does not usually moves
> physically), why don't you use a .network unit file (man 5 systemd.network)?
>
> I'm converting my configs over to that now. Thanks.
>
Another question - i have a wired interface that's always on, and wireless
interface
>
> > It looks like /etc/systemd/system/network@.service requires a gateway=
> line, however, for a second interface I wont set another default. Is there
> a standard way to so this, or do i have to copy network@.service to a new
> name and remove the 'ip route add' line?
>
> Where this service uni
On 02/13/15 22:39, Canek Peláez Valdés wrote:
On Fri, Feb 13, 2015 at 11:18 PM, Adam Carter
<[1]adamcart...@gmail.com> wrote:
>
> It looks like /etc/systemd/system/network@.service requires a
gateway= line, however, for a second interface I wont set another
default. Is there a standar
On Fri, Feb 13, 2015 at 11:18 PM, Adam Carter wrote:
>
> It looks like /etc/systemd/system/network@.service requires a gateway=
line, however, for a second interface I wont set another default. Is there
a standard way to so this, or do i have to copy network@.service to a new
name and remove the '
It looks like /etc/systemd/system/network@.service requires a gateway=
line, however, for a second interface I wont set another default. Is there
a standard way to so this, or do i have to copy network@.service to a new
name and remove the 'ip route add' line?
6 matches
Mail list logo
