EAP: Can't run ping from inside (logged in via SSH)

EAP: Can't run ping from inside (logged in via SSH)
EAP: Can't run ping from inside (logged in via SSH)
2019-04-06 15:45:14
Model: EAP245
Hardware Version: V3
Firmware Version: 2.1.0 Build 20181107 Rel. 39421

Hi all,

 

Anyone got ping working from inside EAP's Busybox? Because it asks for being executed with root permisions.

 

Thanks in advance,

Olivia

0
0
#1
Options
3 Reply
Re:EAP: Can't run ping from inside (logged in via SSH)
2019-04-08 01:40:17

Hi Olivia,

 

Now we cannot use the ping command from inside(logged in via SSH), but we have plan to optimize the feature, thank you for your feedback.

0
0
#2
Options
Re:Re:EAP: Can't run ping from inside (logged in via SSH)
2019-04-08 07:14:36 - last edited 2019-04-08 07:31:40

forrest wrote

Now we cannot use the ping command from inside(logged in via SSH), but we have plan to optimize the feature, thank you for your feedback.

 

Hello @forrest,

 

ping requiring root permissions was a bug introduced into some Linux distros due to the package maintainers not updating the ping/busybox packages when kernel policy did change.

 

You can correct this by replacing busybox ping with the standard command and either setting the SETUID bit for ping or by granting ping the right to use raw sockets if your Linux version running on EAP supports extended file attributes. Newer Linux distros have corrected this bug in the ping package already.

 

See https://superuser.com/questions/1035977/why-does-ping-require-the-setuid-bit for more info on this.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
1
1
#3
Options
Re:Re:Re:EAP: Can't run ping from inside (logged in via SSH)
2019-04-09 07:55:47

R1D2 wrote

forrest wrote

Now we cannot use the ping command from inside(logged in via SSH), but we have plan to optimize the feature, thank you for your feedback.

 

Hello @forrest,

 

ping requiring root permissions was a bug introduced into some Linux distros due to the package maintainers not updating the ping/busybox packages when kernel policy did change.

 

You can correct this by replacing busybox ping with the standard command and either setting the SETUID bit for ping or by granting ping the right to use raw sockets if your Linux version running on EAP supports extended file attributes. Newer Linux distros have corrected this bug in the ping package already.

 

See https://superuser.com/questions/1035977/why-does-ping-require-the-setuid-bit for more info on this.

Hi R1D2,

 

Thanks for your suggestion. Now we have a limit for the ping command in our EAP products; we will consider opening this feature up.

 

0
0
#4
Options