Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 39 subscribers
  • Views 3067 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

What is raclient and what triggers raclient running raclient.sh?

cwynn

I have an XGS firewall that requires a monthly reboot via the front panel power switch because raclient is spawning multiple sh processes per second that become zombies until SFOS runs out of handles to create new process IDs. 

What is the purpose of package raclient in SFOS? What triggers raclient to run the shell script raclient.sh?  Where in SFOS is the configuration that tells networkd to run raclient -s /scripts/network/raclient.sh?



This thread was automatically locked due to age.
Parents
  • 0

    Hi cwynn,

    Thank you for reaching out to Sophos Community.

    Upon checking your case 06983464, As per the update. The development team has accepted your case. However, being unable to access the device where the issue occurs impedes the investigation process.

    Also, the case handler queries the following:

    • How has the unit been since disabling IPv6?
    • Is it still stable?
    • Do you see any zombie SH processes still?

    Erick Jan
    Community Support Engineer | Sophos Technical Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.

  • 0 in reply to Erick Jan

    Hi Erick, my name is Chris.  Your response doesn't answer my question.  I'm hoping a Sophos Community member can tell me what is raclient and what triggers raclient running raclient.sh?

  • 0 in reply to cwynn

    Hi Chris,

    My bad, for your queries.

    The raclient package is responsible for the following:

    • Generating DHCP requests
    • Updating the link information with IP in ipv6 when the request comes in
    • DHCP Options

    That is, whenever a change happens, the ISP sends an extra option, new options, etc it’ll run.

    Erick Jan
    Community Support Engineer | Sophos Technical Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.

  • 0 in reply to Erick Jan

    Thank you for responding Erick.  I can see in networkd.log that networkd is running udhcpc and dhclient as the IPv4 and IPv6 DHCP clients.  networkd also starts raclient as a DHCP client when an interface is configured to get a IPv6 DHCP address but dhclient is logging it finds the DHCP server, requests and binds to a lease which all fall under "Generating DHCP requests".  raclient does not run when interfaces are configured for only DHCP IPv4 addresses.

    raclient does run the raclient.sh script with DHCP lease changes but it also runs the script based on other triggers.  What are the other triggers?

    Here is a portion of networkd.log from a SFOS instance I created in a VM for testing.  It is getting a DHCP lease from another test SFOS VM instance.  Please let me know if another log shows the trigger or action causing raclient to run raclinet.sh

    INFO    ; Oct 13 13:38:49  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 13:48:16  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 13:54:27  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
PRC: Renewing lease on Port2.
XMT: Forming Renew, 0 ms elapsed.
XMT:  X-- IA_NA 5d:00:0a:0a
XMT:  | X-- Requested renew  +3600
XMT:  | X-- Requested rebind +5400
XMT:  | | X-- IAADDR fd00::9
XMT:  | | | X-- Preferred lifetime +7200
XMT:  | | | X-- Max lifetime +7500
XMT:  V IA_NA appended.
XMT: Renew on Port2, interval 9850ms.
PRC: Address fd00::9 depreferred.
PRC: Rebind event scheduled in 600 seconds, to run for 600 seconds.
PRC: Expiration scheduled in 1200 seconds.
RCV: Reply message on Port2 from fe80::215:5dff:fe00:a07.
RCV:  X-- IA_NA 5d:00:0a:0a
RCV:  | X-- starts 1697230669
RCV:  | X-- t1 - renew  +0
RCV:  | X-- t2 - rebind +0
RCV:  | X-- [Options]
RCV:  | | X-- IAADDR fd00::9
RCV:  | | | X-- Preferred lifetime 1200.
RCV:  | | | X-- Max lifetime 2400.
RCV:  X-- Server ID: 00:01:00:01:2c:b8:43:40:00:15:5d:00:0a:07
PRC: Bound to lease 00:01:00:01:2c:b8:43:40:00:15:5d:00:0a:07.
Success
PRC: Renewal event scheduled in 1200 seconds, to run for 600 seconds.
PRC: Depreference scheduled in 1200 seconds.
PRC: Expiration scheduled in 2400 seconds.
INFO    ; Oct 13 13:58:16  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 14:07:41  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 14:13:36  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
PRC: Renewing lease on Port2.
XMT: Forming Renew, 0 ms elapsed.
XMT:  X-- IA_NA 5d:00:0a:0a
XMT:  | X-- Requested renew  +3600
XMT:  | X-- Requested rebind +5400
XMT:  | | X-- IAADDR fd00::9
XMT:  | | | X-- Preferred lifetime +7200
XMT:  | | | X-- Max lifetime +7500
XMT:  V IA_NA appended.
XMT: Renew on Port2, interval 10120ms.
PRC: Address fd00::9 depreferred.
PRC: Rebind event scheduled in 599 seconds, to run for 600 seconds.
PRC: Expiration scheduled in 1199 seconds.
RCV: Reply message on Port2 from fe80::215:5dff:fe00:a07.
RCV:  X-- IA_NA 5d:00:0a:0a
RCV:  | X-- starts 1697231870
RCV:  | X-- t1 - renew  +0
RCV:  | X-- t2 - rebind +0
RCV:  | X-- [Options]
RCV:  | | X-- IAADDR fd00::9
RCV:  | | | X-- Preferred lifetime 240240.
RCV:  | | | X-- Max lifetime 542580.
RCV:  X-- Server ID: 00:01:00:01:2c:b8:43:40:00:15:5d:00:0a:07
PRC: Bound to lease 00:01:00:01:2c:b8:43:40:00:15:5d:00:0a:07.
Success
PRC: Renewal event scheduled in 271290 seconds, to run for 135645 seconds.
PRC: Depreference scheduled in 240240 seconds.
PRC: Expiration scheduled in 542580 seconds.
INFO    ; Oct 13 14:18:02  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 14:23:16  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 14:28:47  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 14:37:50  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 14:46:07  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;

Reply
  • 0 in reply to Erick Jan

    Thank you for responding Erick.  I can see in networkd.log that networkd is running udhcpc and dhclient as the IPv4 and IPv6 DHCP clients.  networkd also starts raclient as a DHCP client when an interface is configured to get a IPv6 DHCP address but dhclient is logging it finds the DHCP server, requests and binds to a lease which all fall under "Generating DHCP requests".  raclient does not run when interfaces are configured for only DHCP IPv4 addresses.

    raclient does run the raclient.sh script with DHCP lease changes but it also runs the script based on other triggers.  What are the other triggers?

    Here is a portion of networkd.log from a SFOS instance I created in a VM for testing.  It is getting a DHCP lease from another test SFOS VM instance.  Please let me know if another log shows the trigger or action causing raclient to run raclinet.sh

    INFO    ; Oct 13 13:38:49  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 13:48:16  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 13:54:27  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
PRC: Renewing lease on Port2.
XMT: Forming Renew, 0 ms elapsed.
XMT:  X-- IA_NA 5d:00:0a:0a
XMT:  | X-- Requested renew  +3600
XMT:  | X-- Requested rebind +5400
XMT:  | | X-- IAADDR fd00::9
XMT:  | | | X-- Preferred lifetime +7200
XMT:  | | | X-- Max lifetime +7500
XMT:  V IA_NA appended.
XMT: Renew on Port2, interval 9850ms.
PRC: Address fd00::9 depreferred.
PRC: Rebind event scheduled in 600 seconds, to run for 600 seconds.
PRC: Expiration scheduled in 1200 seconds.
RCV: Reply message on Port2 from fe80::215:5dff:fe00:a07.
RCV:  X-- IA_NA 5d:00:0a:0a
RCV:  | X-- starts 1697230669
RCV:  | X-- t1 - renew  +0
RCV:  | X-- t2 - rebind +0
RCV:  | X-- [Options]
RCV:  | | X-- IAADDR fd00::9
RCV:  | | | X-- Preferred lifetime 1200.
RCV:  | | | X-- Max lifetime 2400.
RCV:  X-- Server ID: 00:01:00:01:2c:b8:43:40:00:15:5d:00:0a:07
PRC: Bound to lease 00:01:00:01:2c:b8:43:40:00:15:5d:00:0a:07.
Success
PRC: Renewal event scheduled in 1200 seconds, to run for 600 seconds.
PRC: Depreference scheduled in 1200 seconds.
PRC: Expiration scheduled in 2400 seconds.
INFO    ; Oct 13 13:58:16  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 14:07:41  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 14:13:36  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
PRC: Renewing lease on Port2.
XMT: Forming Renew, 0 ms elapsed.
XMT:  X-- IA_NA 5d:00:0a:0a
XMT:  | X-- Requested renew  +3600
XMT:  | X-- Requested rebind +5400
XMT:  | | X-- IAADDR fd00::9
XMT:  | | | X-- Preferred lifetime +7200
XMT:  | | | X-- Max lifetime +7500
XMT:  V IA_NA appended.
XMT: Renew on Port2, interval 10120ms.
PRC: Address fd00::9 depreferred.
PRC: Rebind event scheduled in 599 seconds, to run for 600 seconds.
PRC: Expiration scheduled in 1199 seconds.
RCV: Reply message on Port2 from fe80::215:5dff:fe00:a07.
RCV:  X-- IA_NA 5d:00:0a:0a
RCV:  | X-- starts 1697231870
RCV:  | X-- t1 - renew  +0
RCV:  | X-- t2 - rebind +0
RCV:  | X-- [Options]
RCV:  | | X-- IAADDR fd00::9
RCV:  | | | X-- Preferred lifetime 240240.
RCV:  | | | X-- Max lifetime 542580.
RCV:  X-- Server ID: 00:01:00:01:2c:b8:43:40:00:15:5d:00:0a:07
PRC: Bound to lease 00:01:00:01:2c:b8:43:40:00:15:5d:00:0a:07.
Success
PRC: Renewal event scheduled in 271290 seconds, to run for 135645 seconds.
PRC: Depreference scheduled in 240240 seconds.
PRC: Expiration scheduled in 542580 seconds.
INFO    ; Oct 13 14:18:02  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 14:23:16  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 14:28:47  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 14:37:50  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;
INFO    ; Oct 13 14:46:07  ; RA_CLIENT      ; dev [Port2]	 Flags: Managed = 1 , Otherconf = 1;

Children
No Data
Unfiltered HTML