Does Microsoft WSL have full support for network and devices?
I have been testing Microsoft's Windows Subsystem for Linux (WSL) which is available on the Windows Store.
Does WSL have full support for networking and devices? For instance, can I expect commands like iptables, arp, lsusb or the /dev system to work as they do on a full Linux installation?
linux networking windows-subsystem-for-linux
edited Dec 12 '18 at 13:10
DavidPostill♦
103k25223257
asked Dec 12 '18 at 9:41
lukassz
18010
migrated from unix.stackexchange.com Dec 12 '18 at 13:00
This question came from our site for users of Linux, FreeBSD and other Un*x-like operating systems.
add a comment |
I have been testing Microsoft's Windows Subsystem for Linux (WSL) which is available on the Windows Store.
Does WSL have full support for networking and devices? For instance, can I expect commands like iptables, arp, lsusb or the /dev system to work as they do on a full Linux installation?
linux networking windows-subsystem-for-linux
edited Dec 12 '18 at 13:10
DavidPostill♦
103k25223257
asked Dec 12 '18 at 9:41
lukassz
18010
migrated from unix.stackexchange.com Dec 12 '18 at 13:00
This question came from our site for users of Linux, FreeBSD and other Un*x-like operating systems.
add a comment |
I have been testing Microsoft's Windows Subsystem for Linux (WSL) which is available on the Windows Store.
Does WSL have full support for networking and devices? For instance, can I expect commands like iptables, arp, lsusb or the /dev system to work as they do on a full Linux installation?
linux networking windows-subsystem-for-linux
edited Dec 12 '18 at 13:10
DavidPostill♦
103k25223257
asked Dec 12 '18 at 9:41
lukassz
18010
I have been testing Microsoft's Windows Subsystem for Linux (WSL) which is available on the Windows Store.
Does WSL have full support for networking and devices? For instance, can I expect commands like iptables, arp, lsusb or the /dev system to work as they do on a full Linux installation?
linux networking windows-subsystem-for-linux
linux networking windows-subsystem-for-linux
edited Dec 12 '18 at 13:10
DavidPostill♦
103k25223257
asked Dec 12 '18 at 9:41
lukassz
18010
edited Dec 12 '18 at 13:10
DavidPostill♦
103k25223257
asked Dec 12 '18 at 9:41
lukassz
18010
edited Dec 12 '18 at 13:10
DavidPostill♦
103k25223257
edited Dec 12 '18 at 13:10
DavidPostill♦
103k25223257
edited Dec 12 '18 at 13:10
DavidPostill♦
103k25223257
103k25223257
asked Dec 12 '18 at 9:41
lukassz
18010
asked Dec 12 '18 at 9:41
lukassz
18010
asked Dec 12 '18 at 9:41
lukassz
18010
18010
migrated from unix.stackexchange.com Dec 12 '18 at 13:00
This question came from our site for users of Linux, FreeBSD and other Un*x-like operating systems.
migrated from unix.stackexchange.com Dec 12 '18 at 13:00
This question came from our site for users of Linux, FreeBSD and other Un*x-like operating systems.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
By "full suport" of network you will have a limited or even obscure scope here. I don't think you will be able to do advanced things like ipv4 forwarding on 2 NICs with a WSL Linux running, but 2 issues got solved related to iptables allowing the use of this firewall inside WSL Linux instances indicating that it could work.
iptables related issues:
- iptables v1.6.0: can't initialize iptables table `filter': Table does not exist (do you need to insmod?) #3634
- Command: " iptable -L " is not working #767
Same will apply to arp and usb related problems. Check if the issues are closed or not:
arp related issues:
- arp command not working at all - /proc/net/arp: No such file or directory #2279
- "ip neigh" command dosne't work #2998
usb related issues:
- Unable to execute lsusb or lsblk #2287
td,dr: You will have to crawl through the WSL repository to see if the feature you want is implemented.
answered Dec 12 '18 at 13:04
nwildner
21519
add a comment |
Generally no.
One of the most glaring examples of this is the inability to do anything whatsoever with the system's block devices from inside WSL, which unfortunately appears to be a side-effect of how Windows itself is designed, and means you can't use WSL to access disks that use filesystems which Linux supports but Windows doesn't.
You can find similar issues with almost any Linux program which interacts directly with the hardware, and the same is largely true of things that do things with the network other than the common cases of just opening a TCP or UDP socket and talking over it.
answered Dec 12 '18 at 20:09
Austin Hemmelgarn
2,53918
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1382950%2fdoes-microsoft-wsl-have-full-support-for-network-and-devices%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
By "full suport" of network you will have a limited or even obscure scope here. I don't think you will be able to do advanced things like ipv4 forwarding on 2 NICs with a WSL Linux running, but 2 issues got solved related to iptables allowing the use of this firewall inside WSL Linux instances indicating that it could work.
iptables related issues:
- iptables v1.6.0: can't initialize iptables table `filter': Table does not exist (do you need to insmod?) #3634
- Command: " iptable -L " is not working #767
Same will apply to arp and usb related problems. Check if the issues are closed or not:
arp related issues:
- arp command not working at all - /proc/net/arp: No such file or directory #2279
- "ip neigh" command dosne't work #2998
usb related issues:
- Unable to execute lsusb or lsblk #2287
td,dr: You will have to crawl through the WSL repository to see if the feature you want is implemented.
answered Dec 12 '18 at 13:04
nwildner
21519
add a comment |
By "full suport" of network you will have a limited or even obscure scope here. I don't think you will be able to do advanced things like ipv4 forwarding on 2 NICs with a WSL Linux running, but 2 issues got solved related to iptables allowing the use of this firewall inside WSL Linux instances indicating that it could work.
iptables related issues:
- iptables v1.6.0: can't initialize iptables table `filter': Table does not exist (do you need to insmod?) #3634
- Command: " iptable -L " is not working #767
Same will apply to arp and usb related problems. Check if the issues are closed or not:
arp related issues:
- arp command not working at all - /proc/net/arp: No such file or directory #2279
- "ip neigh" command dosne't work #2998
usb related issues:
- Unable to execute lsusb or lsblk #2287
td,dr: You will have to crawl through the WSL repository to see if the feature you want is implemented.
answered Dec 12 '18 at 13:04
nwildner
21519
add a comment |
By "full suport" of network you will have a limited or even obscure scope here. I don't think you will be able to do advanced things like ipv4 forwarding on 2 NICs with a WSL Linux running, but 2 issues got solved related to iptables allowing the use of this firewall inside WSL Linux instances indicating that it could work.
iptables related issues:
- iptables v1.6.0: can't initialize iptables table `filter': Table does not exist (do you need to insmod?) #3634
- Command: " iptable -L " is not working #767
Same will apply to arp and usb related problems. Check if the issues are closed or not:
arp related issues:
- arp command not working at all - /proc/net/arp: No such file or directory #2279
- "ip neigh" command dosne't work #2998
usb related issues:
- Unable to execute lsusb or lsblk #2287
td,dr: You will have to crawl through the WSL repository to see if the feature you want is implemented.
answered Dec 12 '18 at 13:04
nwildner
21519
By "full suport" of network you will have a limited or even obscure scope here. I don't think you will be able to do advanced things like ipv4 forwarding on 2 NICs with a WSL Linux running, but 2 issues got solved related to iptables allowing the use of this firewall inside WSL Linux instances indicating that it could work.
iptables related issues:
- iptables v1.6.0: can't initialize iptables table `filter': Table does not exist (do you need to insmod?) #3634
- Command: " iptable -L " is not working #767
Same will apply to arp and usb related problems. Check if the issues are closed or not:
arp related issues:
- arp command not working at all - /proc/net/arp: No such file or directory #2279
- "ip neigh" command dosne't work #2998
usb related issues:
- Unable to execute lsusb or lsblk #2287
td,dr: You will have to crawl through the WSL repository to see if the feature you want is implemented.
answered Dec 12 '18 at 13:04
nwildner
21519
edited Dec 12 '18 at 13:09
answered Dec 12 '18 at 13:04
nwildner
21519
answered Dec 12 '18 at 13:04
nwildner
21519
answered Dec 12 '18 at 13:04
nwildner
21519
21519
add a comment |
add a comment |
Generally no.
One of the most glaring examples of this is the inability to do anything whatsoever with the system's block devices from inside WSL, which unfortunately appears to be a side-effect of how Windows itself is designed, and means you can't use WSL to access disks that use filesystems which Linux supports but Windows doesn't.
You can find similar issues with almost any Linux program which interacts directly with the hardware, and the same is largely true of things that do things with the network other than the common cases of just opening a TCP or UDP socket and talking over it.
answered Dec 12 '18 at 20:09
Austin Hemmelgarn
2,53918
add a comment |
Generally no.
One of the most glaring examples of this is the inability to do anything whatsoever with the system's block devices from inside WSL, which unfortunately appears to be a side-effect of how Windows itself is designed, and means you can't use WSL to access disks that use filesystems which Linux supports but Windows doesn't.
You can find similar issues with almost any Linux program which interacts directly with the hardware, and the same is largely true of things that do things with the network other than the common cases of just opening a TCP or UDP socket and talking over it.
answered Dec 12 '18 at 20:09
Austin Hemmelgarn
2,53918
add a comment |
Generally no.
One of the most glaring examples of this is the inability to do anything whatsoever with the system's block devices from inside WSL, which unfortunately appears to be a side-effect of how Windows itself is designed, and means you can't use WSL to access disks that use filesystems which Linux supports but Windows doesn't.
You can find similar issues with almost any Linux program which interacts directly with the hardware, and the same is largely true of things that do things with the network other than the common cases of just opening a TCP or UDP socket and talking over it.
answered Dec 12 '18 at 20:09
Austin Hemmelgarn
2,53918
Generally no.
One of the most glaring examples of this is the inability to do anything whatsoever with the system's block devices from inside WSL, which unfortunately appears to be a side-effect of how Windows itself is designed, and means you can't use WSL to access disks that use filesystems which Linux supports but Windows doesn't.
You can find similar issues with almost any Linux program which interacts directly with the hardware, and the same is largely true of things that do things with the network other than the common cases of just opening a TCP or UDP socket and talking over it.
answered Dec 12 '18 at 20:09
Austin Hemmelgarn
2,53918
answered Dec 12 '18 at 20:09
Austin Hemmelgarn
2,53918
answered Dec 12 '18 at 20:09
Austin Hemmelgarn
2,53918
answered Dec 12 '18 at 20:09
Austin Hemmelgarn
2,53918
2,53918
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1382950%2fdoes-microsoft-wsl-have-full-support-for-network-and-devices%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown