My machine is connected to two networks:
192.168.100.0/24 on eth0, local ip 192.168.100.100
192.168.200.0/24 on eth1 local ip 192.168.200.1
There are some other icecc hosts on 192.168.100.0/24, some of them running their own scheduler.
The -i paramater to best of my knowledge is described in most detail in this news item:
|
- --interface option allows restricting which network interface daemons will use |
Yet my mileage seems to vary:
host ~ # icecc-scheduler -h
ICECREAM scheduler 1.4.0
usage: icecc-scheduler [options]
Options:
-n, --netname <name>
-i, --interface <net_interface>
-p, --port <port>
-h, --help
-l, --log-file <file>
-d, --daemonize
-u, --user-uid
-v[v[v]]]
-r, --persistent-client-connection
host ~ # icecc-scheduler -i eth1 -n icenet -vvv
No icecc user on system. Falling back to nobody.(Error: Success)
[3979635] 2025-04-03 11:27:23: ICECREAM scheduler 1.4.0 starting up, port 8765
[3979635] 2025-04-03 11:27:23: scheduler ready
[3979635] 2025-04-03 11:27:23: ignoring localhost lo for broadcast
[3979635] 2025-04-03 11:27:23: broadcast eth1 192.168.200.255
[3979635] 2025-04-03 11:27:23: broadcast eth0 192.168.100.255
[3979635] 2025-04-03 11:27:23: ignoring localhost lo for broadcast
[3979635] 2025-04-03 11:27:23: broadcast eth1 192.168.200.255
[3979635] 2025-04-03 11:27:23: broadcast eth0 192.168.100.255
[3979635] 2025-04-03 11:27:23: accepted 192.168.200.1
Scheduler claims to broadcast on both networks when there is only one of them on the supplied interface.
No Broadcasts are received
host ~ # icecc-scheduler -i eth0 -n icenet -vvv
No icecc user on system. Falling back to nobody.(Error: Success)
[3979585] 2025-04-03 11:26:50: ICECREAM scheduler 1.4.0 starting up, port 8765
[3979585] 2025-04-03 11:26:50: scheduler ready
[3979585] 2025-04-03 11:26:50: ignoring localhost lo for broadcast
[3979585] 2025-04-03 11:26:50: broadcast eth1 192.168.200.255
[3979585] 2025-04-03 11:26:50: broadcast eth0 192.168.100.255
[3979585] 2025-04-03 11:26:50: ignoring localhost lo for broadcast
[3979585] 2025-04-03 11:26:50: broadcast eth1 192.168.200.255
[3979585] 2025-04-03 11:26:50: broadcast eth0 192.168.100.255
Same as above, but it does not accept 192.168.100.100. (What would it be accepted for by the way?)
host ~ # icecc-scheduler -n icenet -vvv
No icecc user on system. Falling back to nobody.(Error: Success)
[3979577] 2025-04-03 11:26:29: ICECREAM scheduler 1.4.0 starting up, port 8765
[3979577] 2025-04-03 11:26:29: scheduler ready
[3979577] 2025-04-03 11:26:29: ignoring localhost lo for broadcast
[3979577] 2025-04-03 11:26:29: broadcast eth1 192.168.200.255
[3979577] 2025-04-03 11:26:29: broadcast eth0 192.168.100.255
[3979577] 2025-04-03 11:26:29: ignoring localhost lo for broadcast
[3979577] 2025-04-03 11:26:29: broadcast eth1 192.168.200.255
[3979577] 2025-04-03 11:26:29: broadcast eth0 192.168.100.255
[3979577] 2025-04-03 11:26:29: accepted 192.168.200.1
[3979577] 2025-04-03 11:26:29: Received scheduler announcement from 192.168.200.1:35128 (version 43, netname icenet)
[3979577] 2025-04-03 11:26:29: Received scheduler announcement from 192.168.100.100:35128 (version 43, netname icenet)
Without -i parameter scheduler announcements on both interfaces are reported going out and coming in.
My machine is connected to two networks:
192.168.100.0/24 on eth0, local ip 192.168.100.100
192.168.200.0/24 on eth1 local ip 192.168.200.1
There are some other icecc hosts on 192.168.100.0/24, some of them running their own scheduler.
The -i paramater to best of my knowledge is described in most detail in this news item:
icecream/NEWS
Line 37 in d680e4f
Yet my mileage seems to vary:
Scheduler claims to broadcast on both networks when there is only one of them on the supplied interface.
No Broadcasts are received
Same as above, but it does not accept 192.168.100.100. (What would it be accepted for by the way?)
Without -i parameter scheduler announcements on both interfaces are reported going out and coming in.