Re: [gentoo-user] systemd net interfaces always want a default route?

2015-02-18 Thread Adam Carter

 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 that doesnt start at boot and it not always running. I used to
just run the openrc init script to start and stop it, since openrc used per
interface scripts. With systemd the wired interface is fine using
/etc/systemd/network/interface.network, but AFAIK I wont be able to use a
*.network file for the wireless interface because then its status will be
tied to the wired interface.

What's the standard systemd way for me to control the wireless interface?


Re: [gentoo-user] systemd net interfaces always want a default route?

2015-02-18 Thread Canek Peláez Valdés
On Wed, Feb 18, 2015 at 9:45 PM, Adam Carter adamcart...@gmail.com 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 a wired interface that's always on, and
wireless interface that doesnt start at boot and it not always running. I
used to just run the openrc init script to start and stop it, since openrc
used per interface scripts. With systemd the wired interface is fine using
/etc/systemd/network/interface.network, but AFAIK I wont be able to use a
*.network file for the wireless interface because then its status will be
tied to the wired interface.

 What's the standard systemd way for me to control the wireless interface?

There isn't one. networkd is only for really simple networks, and wireless
networks are not considered as such.

You can use wpa_supplicant.service, or wpa_supplicant@interface.service,
or just go to a full fledged network management program like wicd,
NetworkManager, or several others.

I use networkd in all my wired machines. For  wireless machines, I use
NetworkManager.

I believe you can use wpa_supplicant to handle all your wireless (and even
wired) needs. Check out man 5 wpa_supplicant.conf, and then just enable
and start wpa_supplicant@interface.service.

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México


Re: [gentoo-user] systemd net interfaces always want a default route?

2015-02-14 Thread Adam Carter

  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 unit file came from? Did you write it yourself?


I had assumed it was part of systemd, but now i remember I copied it from a
wiki that explained how to setup static networking.


 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.


Re: [gentoo-user] systemd net interfaces always want a default route?

2015-02-13 Thread Canek Peláez Valdés
On Fri, Feb 13, 2015 at 11:18 PM, Adam Carter 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 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 unit file came from? Did you write it yourself?

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)?

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México


Re: [gentoo-user] systemd net interfaces always want a default route?

2015-02-13 Thread Joseph

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 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 unit file came from? Did you write it yourself?
  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)?
  Regards.
  --
  Canek Peláez Valdés
  Profesor de asignatura, Facultad de Ciencias
  Universidad Nacional Autónoma de México

References

  1. mailto:adamcart...@gmail.com


I did mange to make it to work but, when I printed a pdf file or an OpenOffice document the job is being transmitted from client to server and being held, 
when I release it; it didn't get printed. The job just disappeared.


---configuration-
My setting on server:
/etc/cups/cupsd.conf
...
Port 631
Listen /run/cups/cups.sock

# Restrict access to the server...
Location /
 Order allow,deny
 Allow localhost
 Allow 192.168.151.*

On a eeepc client:
/etc/openvpn/eeepc.conf
...
push route 192.168.151.0  255.255.255.0

/etc/cups/client.conf
ServerName 192.168.151.1:631

---end configuration--

With the above setting when I open Fedora - Printer Setting (eeepc is running 
Fedora) I was able to see all the printers that I have installed on a server.
But the result was strange, jobs disappearing, slow etc.  Text file printed OK

In addition my connection to the client was VERY, VERY slow when I ssh to it.  I don't know if the cups had something to do with it.  I disable the configuration 
and the response is much faster.


--
Joseph