How to disable AP isolation in Linux bridge?
up vote
2
down vote
favorite
Context: I am trying to set up a WiFi hotspot on a Raspberry Pi by bridging my ethernet connection.
Question: How do I disable AP isolation or client isolation?
Pre-work: Here is what I have done yet.
Install the following modules.
apt-get install hostapd bridge-utils
Stop hostapd service.
systemctl stop hostapd
Prevent eth0/wlan0 ports from being allocated by DHCP.
vi /etc/dhcpcd.conf
Add the following lines towards the end of the file, but above any interface blocks.
denyinterfaces wlan0
denyinterfaces eth0
Add the bridge.
brctl addbr br0
Connect
eth0
tobr0
.
brctl addif br0 eth0
Add to interfaces.
vi /etc/network/interfaces
auto br0
iface br0 inet manual
bridge_ports eth0 wlan0
Configure access point.
vi /etc/hostapd/hostapd.conf
interface=wlan0
ssid=wifi-ssid
hw_mode=g
channel=7
wmm_enabled=0
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=passphrase
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
Point system to use this file.
vi /etc/default/hostapd
DAEMON_CONF="/etc/hostapd/hostapd.conf"
Reboot
systemctl start hostapd
reboot
linux networking wireless-access-point bridge hostapd
add a comment |
up vote
2
down vote
favorite
Context: I am trying to set up a WiFi hotspot on a Raspberry Pi by bridging my ethernet connection.
Question: How do I disable AP isolation or client isolation?
Pre-work: Here is what I have done yet.
Install the following modules.
apt-get install hostapd bridge-utils
Stop hostapd service.
systemctl stop hostapd
Prevent eth0/wlan0 ports from being allocated by DHCP.
vi /etc/dhcpcd.conf
Add the following lines towards the end of the file, but above any interface blocks.
denyinterfaces wlan0
denyinterfaces eth0
Add the bridge.
brctl addbr br0
Connect
eth0
tobr0
.
brctl addif br0 eth0
Add to interfaces.
vi /etc/network/interfaces
auto br0
iface br0 inet manual
bridge_ports eth0 wlan0
Configure access point.
vi /etc/hostapd/hostapd.conf
interface=wlan0
ssid=wifi-ssid
hw_mode=g
channel=7
wmm_enabled=0
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=passphrase
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
Point system to use this file.
vi /etc/default/hostapd
DAEMON_CONF="/etc/hostapd/hostapd.conf"
Reboot
systemctl start hostapd
reboot
linux networking wireless-access-point bridge hostapd
1
FYI: To create code sections in a list, use 2*4=8 spaces in front of the code.
– zx485
Nov 12 at 23:30
Thanks for editing it as well!
– sid
Nov 13 at 1:04
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Context: I am trying to set up a WiFi hotspot on a Raspberry Pi by bridging my ethernet connection.
Question: How do I disable AP isolation or client isolation?
Pre-work: Here is what I have done yet.
Install the following modules.
apt-get install hostapd bridge-utils
Stop hostapd service.
systemctl stop hostapd
Prevent eth0/wlan0 ports from being allocated by DHCP.
vi /etc/dhcpcd.conf
Add the following lines towards the end of the file, but above any interface blocks.
denyinterfaces wlan0
denyinterfaces eth0
Add the bridge.
brctl addbr br0
Connect
eth0
tobr0
.
brctl addif br0 eth0
Add to interfaces.
vi /etc/network/interfaces
auto br0
iface br0 inet manual
bridge_ports eth0 wlan0
Configure access point.
vi /etc/hostapd/hostapd.conf
interface=wlan0
ssid=wifi-ssid
hw_mode=g
channel=7
wmm_enabled=0
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=passphrase
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
Point system to use this file.
vi /etc/default/hostapd
DAEMON_CONF="/etc/hostapd/hostapd.conf"
Reboot
systemctl start hostapd
reboot
linux networking wireless-access-point bridge hostapd
Context: I am trying to set up a WiFi hotspot on a Raspberry Pi by bridging my ethernet connection.
Question: How do I disable AP isolation or client isolation?
Pre-work: Here is what I have done yet.
Install the following modules.
apt-get install hostapd bridge-utils
Stop hostapd service.
systemctl stop hostapd
Prevent eth0/wlan0 ports from being allocated by DHCP.
vi /etc/dhcpcd.conf
Add the following lines towards the end of the file, but above any interface blocks.
denyinterfaces wlan0
denyinterfaces eth0
Add the bridge.
brctl addbr br0
Connect
eth0
tobr0
.
brctl addif br0 eth0
Add to interfaces.
vi /etc/network/interfaces
auto br0
iface br0 inet manual
bridge_ports eth0 wlan0
Configure access point.
vi /etc/hostapd/hostapd.conf
interface=wlan0
ssid=wifi-ssid
hw_mode=g
channel=7
wmm_enabled=0
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=passphrase
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
Point system to use this file.
vi /etc/default/hostapd
DAEMON_CONF="/etc/hostapd/hostapd.conf"
Reboot
systemctl start hostapd
reboot
linux networking wireless-access-point bridge hostapd
linux networking wireless-access-point bridge hostapd
edited Nov 12 at 23:36
zx485
548313
548313
asked Nov 12 at 23:20
sid
111
111
1
FYI: To create code sections in a list, use 2*4=8 spaces in front of the code.
– zx485
Nov 12 at 23:30
Thanks for editing it as well!
– sid
Nov 13 at 1:04
add a comment |
1
FYI: To create code sections in a list, use 2*4=8 spaces in front of the code.
– zx485
Nov 12 at 23:30
Thanks for editing it as well!
– sid
Nov 13 at 1:04
1
1
FYI: To create code sections in a list, use 2*4=8 spaces in front of the code.
– zx485
Nov 12 at 23:30
FYI: To create code sections in a list, use 2*4=8 spaces in front of the code.
– zx485
Nov 12 at 23:30
Thanks for editing it as well!
– sid
Nov 13 at 1:04
Thanks for editing it as well!
– sid
Nov 13 at 1:04
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
Looking at hostapd.conf, it says
# Client isolation can be used to prevent low-level bridging of frames between
# associated stations in the BSS. By default, this bridging is allowed.
#ap_isolate=1
So client isolation (WLAN clients on the same AP can talk to each other) is disabled by default. Unless your built of hostapd
has it enabled by default, clients should be able to talk to each other. If that is the case, enable it in the config file.
How did you determine that WLAN clients can't talk to each other, and client isolation is enabled? Have two WLAN clients ping each other?
In case your question is not about client isolation, but about the bridge between eth0
and wlan0
not working: Again, how did you test that it doesn't work? Have a host on LAN and a host on WLAN ping each other? Did you check the IP configuration on each of those hosts? How do the hosts get their IP addresses (from which DHCP server? Or static?) Did you check routes? You can debug with tcpdump -ni interface_name
in a terminal window for each important interface, and see where your packets get stuck.
To actually isolate LAN from WLAN one usually uses ebtables
rules, and it's unlikely you accidentally inserted the correct ones... So pretty sure something in your setup is just not working.
It makes sense that client isolation is disabled by default.
– sid
Nov 14 at 4:01
Full disclosure - one of the devices is a cast speaker and the other is a phone. I tried pairing the device and the phone, and I got an error message saying it could not talk to the speaker. You got the question right. It was abou client isolation. Hosts are assigned IPs via DHCP.
– sid
Nov 14 at 4:06
So things to test: (1) Connect two devices you fully control to the AP, like two laptops, see if they can ping each other. (2) Run wireshark onwlan0
on the AP to debug the "pairing" attempt. I don't remember if inter-client communication shows up; if it doesn't, (3a) replace one device with one you control and run wireshark on that device to at least debug half of the "pairing", or (3b) use two APs bridged via LAN if you have the hardware, run wireshark on LAN port. My money is on "pairing" making assumptions that are not given, like link-local IP address, or multicast stuff.
– dirkt
Nov 14 at 6:30
I was able to figure out that the speaker could not connect to the hotspot. Which is why the phone and the speaker were unable to talk to each other. I set up a hotspot from my Windows laptop and I was able to get things set up properly. But, I wanted the hotspot to run from the Raspberry Pi. So, I looked for other OS's that natively supported hotspots instead of manually using hostapd. I installed Ubuntu MATE and it works now.
– sid
yesterday
I bet Ubuntu MATE is also using hostapd, just with a different configuration, and possibly different wifi drivers. So in your place, and to learn something, I'd closely look at what Ubuntu MATE is doing differently. "I'll just install different 'OS' (rather, distros) until one will work" is hit or miss, because all distros are using more or less the same software, just configured a bit differently.
– dirkt
yesterday
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Looking at hostapd.conf, it says
# Client isolation can be used to prevent low-level bridging of frames between
# associated stations in the BSS. By default, this bridging is allowed.
#ap_isolate=1
So client isolation (WLAN clients on the same AP can talk to each other) is disabled by default. Unless your built of hostapd
has it enabled by default, clients should be able to talk to each other. If that is the case, enable it in the config file.
How did you determine that WLAN clients can't talk to each other, and client isolation is enabled? Have two WLAN clients ping each other?
In case your question is not about client isolation, but about the bridge between eth0
and wlan0
not working: Again, how did you test that it doesn't work? Have a host on LAN and a host on WLAN ping each other? Did you check the IP configuration on each of those hosts? How do the hosts get their IP addresses (from which DHCP server? Or static?) Did you check routes? You can debug with tcpdump -ni interface_name
in a terminal window for each important interface, and see where your packets get stuck.
To actually isolate LAN from WLAN one usually uses ebtables
rules, and it's unlikely you accidentally inserted the correct ones... So pretty sure something in your setup is just not working.
It makes sense that client isolation is disabled by default.
– sid
Nov 14 at 4:01
Full disclosure - one of the devices is a cast speaker and the other is a phone. I tried pairing the device and the phone, and I got an error message saying it could not talk to the speaker. You got the question right. It was abou client isolation. Hosts are assigned IPs via DHCP.
– sid
Nov 14 at 4:06
So things to test: (1) Connect two devices you fully control to the AP, like two laptops, see if they can ping each other. (2) Run wireshark onwlan0
on the AP to debug the "pairing" attempt. I don't remember if inter-client communication shows up; if it doesn't, (3a) replace one device with one you control and run wireshark on that device to at least debug half of the "pairing", or (3b) use two APs bridged via LAN if you have the hardware, run wireshark on LAN port. My money is on "pairing" making assumptions that are not given, like link-local IP address, or multicast stuff.
– dirkt
Nov 14 at 6:30
I was able to figure out that the speaker could not connect to the hotspot. Which is why the phone and the speaker were unable to talk to each other. I set up a hotspot from my Windows laptop and I was able to get things set up properly. But, I wanted the hotspot to run from the Raspberry Pi. So, I looked for other OS's that natively supported hotspots instead of manually using hostapd. I installed Ubuntu MATE and it works now.
– sid
yesterday
I bet Ubuntu MATE is also using hostapd, just with a different configuration, and possibly different wifi drivers. So in your place, and to learn something, I'd closely look at what Ubuntu MATE is doing differently. "I'll just install different 'OS' (rather, distros) until one will work" is hit or miss, because all distros are using more or less the same software, just configured a bit differently.
– dirkt
yesterday
add a comment |
up vote
1
down vote
Looking at hostapd.conf, it says
# Client isolation can be used to prevent low-level bridging of frames between
# associated stations in the BSS. By default, this bridging is allowed.
#ap_isolate=1
So client isolation (WLAN clients on the same AP can talk to each other) is disabled by default. Unless your built of hostapd
has it enabled by default, clients should be able to talk to each other. If that is the case, enable it in the config file.
How did you determine that WLAN clients can't talk to each other, and client isolation is enabled? Have two WLAN clients ping each other?
In case your question is not about client isolation, but about the bridge between eth0
and wlan0
not working: Again, how did you test that it doesn't work? Have a host on LAN and a host on WLAN ping each other? Did you check the IP configuration on each of those hosts? How do the hosts get their IP addresses (from which DHCP server? Or static?) Did you check routes? You can debug with tcpdump -ni interface_name
in a terminal window for each important interface, and see where your packets get stuck.
To actually isolate LAN from WLAN one usually uses ebtables
rules, and it's unlikely you accidentally inserted the correct ones... So pretty sure something in your setup is just not working.
It makes sense that client isolation is disabled by default.
– sid
Nov 14 at 4:01
Full disclosure - one of the devices is a cast speaker and the other is a phone. I tried pairing the device and the phone, and I got an error message saying it could not talk to the speaker. You got the question right. It was abou client isolation. Hosts are assigned IPs via DHCP.
– sid
Nov 14 at 4:06
So things to test: (1) Connect two devices you fully control to the AP, like two laptops, see if they can ping each other. (2) Run wireshark onwlan0
on the AP to debug the "pairing" attempt. I don't remember if inter-client communication shows up; if it doesn't, (3a) replace one device with one you control and run wireshark on that device to at least debug half of the "pairing", or (3b) use two APs bridged via LAN if you have the hardware, run wireshark on LAN port. My money is on "pairing" making assumptions that are not given, like link-local IP address, or multicast stuff.
– dirkt
Nov 14 at 6:30
I was able to figure out that the speaker could not connect to the hotspot. Which is why the phone and the speaker were unable to talk to each other. I set up a hotspot from my Windows laptop and I was able to get things set up properly. But, I wanted the hotspot to run from the Raspberry Pi. So, I looked for other OS's that natively supported hotspots instead of manually using hostapd. I installed Ubuntu MATE and it works now.
– sid
yesterday
I bet Ubuntu MATE is also using hostapd, just with a different configuration, and possibly different wifi drivers. So in your place, and to learn something, I'd closely look at what Ubuntu MATE is doing differently. "I'll just install different 'OS' (rather, distros) until one will work" is hit or miss, because all distros are using more or less the same software, just configured a bit differently.
– dirkt
yesterday
add a comment |
up vote
1
down vote
up vote
1
down vote
Looking at hostapd.conf, it says
# Client isolation can be used to prevent low-level bridging of frames between
# associated stations in the BSS. By default, this bridging is allowed.
#ap_isolate=1
So client isolation (WLAN clients on the same AP can talk to each other) is disabled by default. Unless your built of hostapd
has it enabled by default, clients should be able to talk to each other. If that is the case, enable it in the config file.
How did you determine that WLAN clients can't talk to each other, and client isolation is enabled? Have two WLAN clients ping each other?
In case your question is not about client isolation, but about the bridge between eth0
and wlan0
not working: Again, how did you test that it doesn't work? Have a host on LAN and a host on WLAN ping each other? Did you check the IP configuration on each of those hosts? How do the hosts get their IP addresses (from which DHCP server? Or static?) Did you check routes? You can debug with tcpdump -ni interface_name
in a terminal window for each important interface, and see where your packets get stuck.
To actually isolate LAN from WLAN one usually uses ebtables
rules, and it's unlikely you accidentally inserted the correct ones... So pretty sure something in your setup is just not working.
Looking at hostapd.conf, it says
# Client isolation can be used to prevent low-level bridging of frames between
# associated stations in the BSS. By default, this bridging is allowed.
#ap_isolate=1
So client isolation (WLAN clients on the same AP can talk to each other) is disabled by default. Unless your built of hostapd
has it enabled by default, clients should be able to talk to each other. If that is the case, enable it in the config file.
How did you determine that WLAN clients can't talk to each other, and client isolation is enabled? Have two WLAN clients ping each other?
In case your question is not about client isolation, but about the bridge between eth0
and wlan0
not working: Again, how did you test that it doesn't work? Have a host on LAN and a host on WLAN ping each other? Did you check the IP configuration on each of those hosts? How do the hosts get their IP addresses (from which DHCP server? Or static?) Did you check routes? You can debug with tcpdump -ni interface_name
in a terminal window for each important interface, and see where your packets get stuck.
To actually isolate LAN from WLAN one usually uses ebtables
rules, and it's unlikely you accidentally inserted the correct ones... So pretty sure something in your setup is just not working.
answered Nov 13 at 7:44
dirkt
8,48231120
8,48231120
It makes sense that client isolation is disabled by default.
– sid
Nov 14 at 4:01
Full disclosure - one of the devices is a cast speaker and the other is a phone. I tried pairing the device and the phone, and I got an error message saying it could not talk to the speaker. You got the question right. It was abou client isolation. Hosts are assigned IPs via DHCP.
– sid
Nov 14 at 4:06
So things to test: (1) Connect two devices you fully control to the AP, like two laptops, see if they can ping each other. (2) Run wireshark onwlan0
on the AP to debug the "pairing" attempt. I don't remember if inter-client communication shows up; if it doesn't, (3a) replace one device with one you control and run wireshark on that device to at least debug half of the "pairing", or (3b) use two APs bridged via LAN if you have the hardware, run wireshark on LAN port. My money is on "pairing" making assumptions that are not given, like link-local IP address, or multicast stuff.
– dirkt
Nov 14 at 6:30
I was able to figure out that the speaker could not connect to the hotspot. Which is why the phone and the speaker were unable to talk to each other. I set up a hotspot from my Windows laptop and I was able to get things set up properly. But, I wanted the hotspot to run from the Raspberry Pi. So, I looked for other OS's that natively supported hotspots instead of manually using hostapd. I installed Ubuntu MATE and it works now.
– sid
yesterday
I bet Ubuntu MATE is also using hostapd, just with a different configuration, and possibly different wifi drivers. So in your place, and to learn something, I'd closely look at what Ubuntu MATE is doing differently. "I'll just install different 'OS' (rather, distros) until one will work" is hit or miss, because all distros are using more or less the same software, just configured a bit differently.
– dirkt
yesterday
add a comment |
It makes sense that client isolation is disabled by default.
– sid
Nov 14 at 4:01
Full disclosure - one of the devices is a cast speaker and the other is a phone. I tried pairing the device and the phone, and I got an error message saying it could not talk to the speaker. You got the question right. It was abou client isolation. Hosts are assigned IPs via DHCP.
– sid
Nov 14 at 4:06
So things to test: (1) Connect two devices you fully control to the AP, like two laptops, see if they can ping each other. (2) Run wireshark onwlan0
on the AP to debug the "pairing" attempt. I don't remember if inter-client communication shows up; if it doesn't, (3a) replace one device with one you control and run wireshark on that device to at least debug half of the "pairing", or (3b) use two APs bridged via LAN if you have the hardware, run wireshark on LAN port. My money is on "pairing" making assumptions that are not given, like link-local IP address, or multicast stuff.
– dirkt
Nov 14 at 6:30
I was able to figure out that the speaker could not connect to the hotspot. Which is why the phone and the speaker were unable to talk to each other. I set up a hotspot from my Windows laptop and I was able to get things set up properly. But, I wanted the hotspot to run from the Raspberry Pi. So, I looked for other OS's that natively supported hotspots instead of manually using hostapd. I installed Ubuntu MATE and it works now.
– sid
yesterday
I bet Ubuntu MATE is also using hostapd, just with a different configuration, and possibly different wifi drivers. So in your place, and to learn something, I'd closely look at what Ubuntu MATE is doing differently. "I'll just install different 'OS' (rather, distros) until one will work" is hit or miss, because all distros are using more or less the same software, just configured a bit differently.
– dirkt
yesterday
It makes sense that client isolation is disabled by default.
– sid
Nov 14 at 4:01
It makes sense that client isolation is disabled by default.
– sid
Nov 14 at 4:01
Full disclosure - one of the devices is a cast speaker and the other is a phone. I tried pairing the device and the phone, and I got an error message saying it could not talk to the speaker. You got the question right. It was abou client isolation. Hosts are assigned IPs via DHCP.
– sid
Nov 14 at 4:06
Full disclosure - one of the devices is a cast speaker and the other is a phone. I tried pairing the device and the phone, and I got an error message saying it could not talk to the speaker. You got the question right. It was abou client isolation. Hosts are assigned IPs via DHCP.
– sid
Nov 14 at 4:06
So things to test: (1) Connect two devices you fully control to the AP, like two laptops, see if they can ping each other. (2) Run wireshark on
wlan0
on the AP to debug the "pairing" attempt. I don't remember if inter-client communication shows up; if it doesn't, (3a) replace one device with one you control and run wireshark on that device to at least debug half of the "pairing", or (3b) use two APs bridged via LAN if you have the hardware, run wireshark on LAN port. My money is on "pairing" making assumptions that are not given, like link-local IP address, or multicast stuff.– dirkt
Nov 14 at 6:30
So things to test: (1) Connect two devices you fully control to the AP, like two laptops, see if they can ping each other. (2) Run wireshark on
wlan0
on the AP to debug the "pairing" attempt. I don't remember if inter-client communication shows up; if it doesn't, (3a) replace one device with one you control and run wireshark on that device to at least debug half of the "pairing", or (3b) use two APs bridged via LAN if you have the hardware, run wireshark on LAN port. My money is on "pairing" making assumptions that are not given, like link-local IP address, or multicast stuff.– dirkt
Nov 14 at 6:30
I was able to figure out that the speaker could not connect to the hotspot. Which is why the phone and the speaker were unable to talk to each other. I set up a hotspot from my Windows laptop and I was able to get things set up properly. But, I wanted the hotspot to run from the Raspberry Pi. So, I looked for other OS's that natively supported hotspots instead of manually using hostapd. I installed Ubuntu MATE and it works now.
– sid
yesterday
I was able to figure out that the speaker could not connect to the hotspot. Which is why the phone and the speaker were unable to talk to each other. I set up a hotspot from my Windows laptop and I was able to get things set up properly. But, I wanted the hotspot to run from the Raspberry Pi. So, I looked for other OS's that natively supported hotspots instead of manually using hostapd. I installed Ubuntu MATE and it works now.
– sid
yesterday
I bet Ubuntu MATE is also using hostapd, just with a different configuration, and possibly different wifi drivers. So in your place, and to learn something, I'd closely look at what Ubuntu MATE is doing differently. "I'll just install different 'OS' (rather, distros) until one will work" is hit or miss, because all distros are using more or less the same software, just configured a bit differently.
– dirkt
yesterday
I bet Ubuntu MATE is also using hostapd, just with a different configuration, and possibly different wifi drivers. So in your place, and to learn something, I'd closely look at what Ubuntu MATE is doing differently. "I'll just install different 'OS' (rather, distros) until one will work" is hit or miss, because all distros are using more or less the same software, just configured a bit differently.
– dirkt
yesterday
add a comment |
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%2f1374862%2fhow-to-disable-ap-isolation-in-linux-bridge%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
1
FYI: To create code sections in a list, use 2*4=8 spaces in front of the code.
– zx485
Nov 12 at 23:30
Thanks for editing it as well!
– sid
Nov 13 at 1:04