Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kali App Network Issue #3656

Closed
Sicks3c opened this issue Nov 10, 2018 · 1 comment
Closed

Kali App Network Issue #3656

Sicks3c opened this issue Nov 10, 2018 · 1 comment
Labels

Comments

@Sicks3c
Copy link

Sicks3c commented Nov 10, 2018

Hello Community
Before proceeding to the issue , I'd like to thank all the team for their effort to make kali available on win 10

As a part of penetration testing , I used to run my vulnerable machines in virtualbox with kali and put them on the same network in order to practice now with this kali app I found some issue

Information about my system

Linux DESKTOP-3S31BKC 4.4.0-17134-Microsoft #345-Microsoft Wed Sep 19 17:47:00 PST 2018 x86_64 GNU/Linux

1 - I have inserted my vulnerable machine on virtualbox like this : vuln

2 - Then I have installed Kali linux via microsoft store and xfce4 like this :
image

When I try host discovery I dont find the IP Adress of the vulnerable machine , I can't figure out in what interface kali is connected and how to make it at the same network as my vulnerable machine in virtualbox

I tried this

ryq7yue
there is a lot of interfaces that came from no where ... I cant figure out which one kali is connected on

Another thing

I can ping websites and stuff but NetworkManager is not working properly
lrehfia

Please advise me what to do
Have a great day

@therealkenc
Copy link
Collaborator

therealkenc commented Nov 10, 2018

Please advise me what to do

Took a look on a lark; non-exhaustive hard fails on NetworkManager below. Spiritually dupe #69 (with a nod to #3337). WSL has incomplete AF_NETLINK support.

You could, in principle, if you are feeling highly motivated, pick up the torch from #3337 and reboot the NETLINK_EXT_ACK fail into a CLI scenario following the issue template instead of deleting it. If you go this route, make sure you're on at least 1809 (or better still Insiders), and running with WSL elevated. Bonne chance.

1774  socket(AF_NETLINK, SOCK_RAW|SOCK_CLOEXEC|SOCK_NONBLOCK, NETLINK_KOBJECT_UEVENT) = 6
1774  setsockopt(6, SOL_SOCKET, SO_ATTACH_FILTER, {len=8, filter=0x7fffe6f54ae0}, 16) = -1 EINVAL (Invalid argument)
1774  bind(6, {sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000}, 12) = 0
1774  getsockname(6, {sa_family=AF_NETLINK, nl_pid=1774, nl_groups=00000000}, [12]) = 0
1774  setsockopt(6, SOL_SOCKET, SO_PASSCRED, [1], 4) = -1 EINVAL (Invalid argument)
1774  fstat(6, {st_mode=S_IFSOCK|0777, st_size=0, ...}) = 0
1774  fcntl(6, F_GETFL)                 = 0x80802 (flags O_RDWR|O_NONBLOCK|O_CLOEXEC)
1774  write(3, "\1\0\0\0\0\0\0\0", 8)   = 8
1774  time(NULL)                        = 1541871637 (2018-11-10T09:40:37-0800)
1774  socket(AF_NETLINK, SOCK_RAW|SOCK_CLOEXEC, NETLINK_ROUTE) = 7
1774  setsockopt(7, SOL_SOCKET, SO_SNDBUF, [32768], 4) = 0
1774  setsockopt(7, SOL_SOCKET, SO_RCVBUF, [32768], 4) = 0
1774  bind(7, {sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000}, 12) = 0
1774  getsockname(7, {sa_family=AF_NETLINK, nl_pid=-2147483640, nl_groups=00000000}, [12]) = 0
1774  setsockopt(7, SOL_SOCKET, SO_PASSCRED, [1], 4) = 0
1774  fcntl(7, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
1774  setsockopt(7, SOL_SOCKET, SO_SNDBUF, [32768], 4) = 0
1774  setsockopt(7, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
1774  setsockopt(7, SOL_NETLINK, NETLINK_EXT_ACK, [1], 4) = -1 EINVAL (Invalid argument)
1774  setsockopt(7, SOL_NETLINK, NETLINK_ADD_MEMBERSHIP, [1], 4) = -1 EINVAL (Invalid argument)
1774  write(2, "**\nNetworkManager:ERROR:src/plat"..., 107) = 107

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants