HOw do I Give VLANs internet access?
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
The challenge that I am faced with is as follows.
I need to give internet access to several VLANs via a single Ubuntu 16.04 router.
The VLANs are 8021q tagged and arrive at the router on interface ens1f1.
VLANs are named vlan10, vlan20, vlan30, and vlan40.
The internet uplink is connected to enp0s25.
Enp0s25 has a static public IP address assigned by the ISP.
The upstream device connected to Enp0s25 is not VLAN capable.
I ask you sage and wizened engineers or packet manglers out there if you would please explain to me how I can route, bridge, NAT, or catapult packets between those VLANs and that great tangle of plumbing we call the internet.
In the meantime, I shall retreat to my cupboard muttering error 418 (RFC 2324).
Regards,
Kevin
networking server internet iptables
asked Feb 6 at 15:53
Kevin Anderson
1
add a comment |Â
up vote
0
down vote
favorite
The challenge that I am faced with is as follows.
I need to give internet access to several VLANs via a single Ubuntu 16.04 router.
The VLANs are 8021q tagged and arrive at the router on interface ens1f1.
VLANs are named vlan10, vlan20, vlan30, and vlan40.
The internet uplink is connected to enp0s25.
Enp0s25 has a static public IP address assigned by the ISP.
The upstream device connected to Enp0s25 is not VLAN capable.
I ask you sage and wizened engineers or packet manglers out there if you would please explain to me how I can route, bridge, NAT, or catapult packets between those VLANs and that great tangle of plumbing we call the internet.
In the meantime, I shall retreat to my cupboard muttering error 418 (RFC 2324).
Regards,
Kevin
networking server internet iptables
asked Feb 6 at 15:53
Kevin Anderson
1
Do you use any type of firewall?iptables,ufw, etc.? I have to ask because if you are usingufwit'll be a little bit trickier, if you're usingiptablesit won't be as hard, but if you're not using any firewall you're already breaking the cardinal rule of server admin.
– Thomas Ward♦
Feb 6 at 15:59
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
The challenge that I am faced with is as follows.
I need to give internet access to several VLANs via a single Ubuntu 16.04 router.
The VLANs are 8021q tagged and arrive at the router on interface ens1f1.
VLANs are named vlan10, vlan20, vlan30, and vlan40.
The internet uplink is connected to enp0s25.
Enp0s25 has a static public IP address assigned by the ISP.
The upstream device connected to Enp0s25 is not VLAN capable.
I ask you sage and wizened engineers or packet manglers out there if you would please explain to me how I can route, bridge, NAT, or catapult packets between those VLANs and that great tangle of plumbing we call the internet.
In the meantime, I shall retreat to my cupboard muttering error 418 (RFC 2324).
Regards,
Kevin
networking server internet iptables
asked Feb 6 at 15:53
Kevin Anderson
1
The challenge that I am faced with is as follows.
I need to give internet access to several VLANs via a single Ubuntu 16.04 router.
The VLANs are 8021q tagged and arrive at the router on interface ens1f1.
VLANs are named vlan10, vlan20, vlan30, and vlan40.
The internet uplink is connected to enp0s25.
Enp0s25 has a static public IP address assigned by the ISP.
The upstream device connected to Enp0s25 is not VLAN capable.
I ask you sage and wizened engineers or packet manglers out there if you would please explain to me how I can route, bridge, NAT, or catapult packets between those VLANs and that great tangle of plumbing we call the internet.
In the meantime, I shall retreat to my cupboard muttering error 418 (RFC 2324).
Regards,
Kevin
networking server internet iptables
networking server internet iptables
asked Feb 6 at 15:53
Kevin Anderson
1
asked Feb 6 at 15:53
Kevin Anderson
1
asked Feb 6 at 15:53
Kevin Anderson
1
asked Feb 6 at 15:53
Kevin Anderson
1
asked Feb 6 at 15:53
Kevin Anderson
1
1
Do you use any type of firewall?iptables,ufw, etc.? I have to ask because if you are usingufwit'll be a little bit trickier, if you're usingiptablesit won't be as hard, but if you're not using any firewall you're already breaking the cardinal rule of server admin.
– Thomas Ward♦
Feb 6 at 15:59
add a comment |Â
Do you use any type of firewall?iptables,ufw, etc.? I have to ask because if you are usingufwit'll be a little bit trickier, if you're usingiptablesit won't be as hard, but if you're not using any firewall you're already breaking the cardinal rule of server admin.
– Thomas Ward♦
Feb 6 at 15:59
Do you use any type of firewall?
iptables, ufw, etc.? I have to ask because if you are using ufw it'll be a little bit trickier, if you're using iptables it won't be as hard, but if you're not using any firewall you're already breaking the cardinal rule of server admin.– Thomas Ward♦
Feb 6 at 15:59
Do you use any type of firewall?
iptables, ufw, etc.? I have to ask because if you are using ufw it'll be a little bit trickier, if you're using iptables it won't be as hard, but if you're not using any firewall you're already breaking the cardinal rule of server admin.– Thomas Ward♦
Feb 6 at 15:59
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
This answer assumes you use an
iptablesfirewall on your 'router', and not something 'easier' likeufw, and that you have properly set up the router to handle VLANs on the given interface.
What you're looking for is called "NAT". This is done by default on many routers, however by default isn't done on Linux systems.
You'll need to enable IPv4 forwarding also in the system to make it work. Add this to the end of /etc/sysctl.conf:
net.ipv4.ip_forward = 1
You can get that to apply by doing sudo sysctl -p afterwards. This enables the ability to forward traffic through.
Since your default Internet route is out to the Public Internet, but you want to set up NAT so that the other VLAN machines can go out to the Internet via your system, you would need to set up something like this in iptables:
iptables -t nat -A POSTROUTING -s ip.add.re.ss/24 ! -d ip.add.re.ss/24 -m comment --comment "Allow vlanXX to go to the Internet, masquerade as the public IP." -j MASQUERADE
This is a rule in the NAT table for how to route traffic after it's arrived at the system. You'll need three of these rules, one for each subnet of each VLAN. Adjust ip.add.re.ss and vlanXX accordingly to match the information for your network specifically.
You also need to have an ACCEPT rule in the filter table of iptables for FORWARD, and you would typically do this by interface, like this, updating the XX items to be the vlan number:
iptables -t filter -A FORWARD -o ens1f1.XX -m comment --comment "NAT for vlanXX" -j ACCEPT
iptables -t filter -A FORWARD -i ens1f1.XX -m comment --comment "NAT for vlanXX" -j ACCEPT
Once you've done this, you need to make sure you save the iptables rules. Ideally you would do this if you didn't have it installed first, and tell it "Yes" when it asks to save your rules:
sudo apt-get install iptables-persistent
... and that would set up the iptables rules at boot properly as well as save the rules. If you already have iptables-persistent, then you need to update the rules it loads:
sudo su -c 'iptables-save > /etc/iptables/rules.v4'
... and now the NAT MASQUERADE rule will be in place every time you boot.
answered Feb 6 at 16:26
Thomas Ward♦
41.9k23115167
Dear Thomas, Thank you so much for your rapid and thorough reply. So I don't need any bridges to solve this? The router in question still lives in my development lab, I would never let anything attach to the wild without a firewall. Although I looked into ufw, I couldn't see it helping me. Even so, my attempts using IPtables didn't get far either. I shall brew up a solution according to your recipe and report back. Regards, Kevin
– Kevin Anderson
Feb 6 at 17:13
@KevinAnderson You don't need a bridge, no. Especially if the VLANs are directly linked to the port itself. You just need simple NAT. (This NAT only lets it go out, it doesn't let unrelated traffic back into the systems, so if you are running a webserver on 1.2.3.4 on vlan30, you can't access the webserver from the public IP address without much more complicated NAT rules)
– Thomas Ward♦
Feb 6 at 17:45
@KevinAnderson Also you need to have the machine set up properly for 802.1Q VLAN tagging, per the linked "VLAN" help article from the Ubuntu Help documentation in order for all this to work properly. Without knowing more about your setup though, and assuming it's just straight VLANs and this is a dedicated 'gateway' box, there shouldn't be an issue. If the VLANs are internal virtual ethernet interfaces or something, though, that makes it more complex. The basics are here, though.
– Thomas Ward♦
Feb 6 at 17:46
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
This answer assumes you use an
iptablesfirewall on your 'router', and not something 'easier' likeufw, and that you have properly set up the router to handle VLANs on the given interface.
What you're looking for is called "NAT". This is done by default on many routers, however by default isn't done on Linux systems.
You'll need to enable IPv4 forwarding also in the system to make it work. Add this to the end of /etc/sysctl.conf:
net.ipv4.ip_forward = 1
You can get that to apply by doing sudo sysctl -p afterwards. This enables the ability to forward traffic through.
Since your default Internet route is out to the Public Internet, but you want to set up NAT so that the other VLAN machines can go out to the Internet via your system, you would need to set up something like this in iptables:
iptables -t nat -A POSTROUTING -s ip.add.re.ss/24 ! -d ip.add.re.ss/24 -m comment --comment "Allow vlanXX to go to the Internet, masquerade as the public IP." -j MASQUERADE
This is a rule in the NAT table for how to route traffic after it's arrived at the system. You'll need three of these rules, one for each subnet of each VLAN. Adjust ip.add.re.ss and vlanXX accordingly to match the information for your network specifically.
You also need to have an ACCEPT rule in the filter table of iptables for FORWARD, and you would typically do this by interface, like this, updating the XX items to be the vlan number:
iptables -t filter -A FORWARD -o ens1f1.XX -m comment --comment "NAT for vlanXX" -j ACCEPT
iptables -t filter -A FORWARD -i ens1f1.XX -m comment --comment "NAT for vlanXX" -j ACCEPT
Once you've done this, you need to make sure you save the iptables rules. Ideally you would do this if you didn't have it installed first, and tell it "Yes" when it asks to save your rules:
sudo apt-get install iptables-persistent
... and that would set up the iptables rules at boot properly as well as save the rules. If you already have iptables-persistent, then you need to update the rules it loads:
sudo su -c 'iptables-save > /etc/iptables/rules.v4'
... and now the NAT MASQUERADE rule will be in place every time you boot.
answered Feb 6 at 16:26
Thomas Ward♦
41.9k23115167
Dear Thomas, Thank you so much for your rapid and thorough reply. So I don't need any bridges to solve this? The router in question still lives in my development lab, I would never let anything attach to the wild without a firewall. Although I looked into ufw, I couldn't see it helping me. Even so, my attempts using IPtables didn't get far either. I shall brew up a solution according to your recipe and report back. Regards, Kevin
– Kevin Anderson
Feb 6 at 17:13
@KevinAnderson You don't need a bridge, no. Especially if the VLANs are directly linked to the port itself. You just need simple NAT. (This NAT only lets it go out, it doesn't let unrelated traffic back into the systems, so if you are running a webserver on 1.2.3.4 on vlan30, you can't access the webserver from the public IP address without much more complicated NAT rules)
– Thomas Ward♦
Feb 6 at 17:45
@KevinAnderson Also you need to have the machine set up properly for 802.1Q VLAN tagging, per the linked "VLAN" help article from the Ubuntu Help documentation in order for all this to work properly. Without knowing more about your setup though, and assuming it's just straight VLANs and this is a dedicated 'gateway' box, there shouldn't be an issue. If the VLANs are internal virtual ethernet interfaces or something, though, that makes it more complex. The basics are here, though.
– Thomas Ward♦
Feb 6 at 17:46
add a comment |Â
up vote
1
down vote
This answer assumes you use an
iptablesfirewall on your 'router', and not something 'easier' likeufw, and that you have properly set up the router to handle VLANs on the given interface.
What you're looking for is called "NAT". This is done by default on many routers, however by default isn't done on Linux systems.
You'll need to enable IPv4 forwarding also in the system to make it work. Add this to the end of /etc/sysctl.conf:
net.ipv4.ip_forward = 1
You can get that to apply by doing sudo sysctl -p afterwards. This enables the ability to forward traffic through.
Since your default Internet route is out to the Public Internet, but you want to set up NAT so that the other VLAN machines can go out to the Internet via your system, you would need to set up something like this in iptables:
iptables -t nat -A POSTROUTING -s ip.add.re.ss/24 ! -d ip.add.re.ss/24 -m comment --comment "Allow vlanXX to go to the Internet, masquerade as the public IP." -j MASQUERADE
This is a rule in the NAT table for how to route traffic after it's arrived at the system. You'll need three of these rules, one for each subnet of each VLAN. Adjust ip.add.re.ss and vlanXX accordingly to match the information for your network specifically.
You also need to have an ACCEPT rule in the filter table of iptables for FORWARD, and you would typically do this by interface, like this, updating the XX items to be the vlan number:
iptables -t filter -A FORWARD -o ens1f1.XX -m comment --comment "NAT for vlanXX" -j ACCEPT
iptables -t filter -A FORWARD -i ens1f1.XX -m comment --comment "NAT for vlanXX" -j ACCEPT
Once you've done this, you need to make sure you save the iptables rules. Ideally you would do this if you didn't have it installed first, and tell it "Yes" when it asks to save your rules:
sudo apt-get install iptables-persistent
... and that would set up the iptables rules at boot properly as well as save the rules. If you already have iptables-persistent, then you need to update the rules it loads:
sudo su -c 'iptables-save > /etc/iptables/rules.v4'
... and now the NAT MASQUERADE rule will be in place every time you boot.
answered Feb 6 at 16:26
Thomas Ward♦
41.9k23115167
Dear Thomas, Thank you so much for your rapid and thorough reply. So I don't need any bridges to solve this? The router in question still lives in my development lab, I would never let anything attach to the wild without a firewall. Although I looked into ufw, I couldn't see it helping me. Even so, my attempts using IPtables didn't get far either. I shall brew up a solution according to your recipe and report back. Regards, Kevin
– Kevin Anderson
Feb 6 at 17:13
@KevinAnderson You don't need a bridge, no. Especially if the VLANs are directly linked to the port itself. You just need simple NAT. (This NAT only lets it go out, it doesn't let unrelated traffic back into the systems, so if you are running a webserver on 1.2.3.4 on vlan30, you can't access the webserver from the public IP address without much more complicated NAT rules)
– Thomas Ward♦
Feb 6 at 17:45
@KevinAnderson Also you need to have the machine set up properly for 802.1Q VLAN tagging, per the linked "VLAN" help article from the Ubuntu Help documentation in order for all this to work properly. Without knowing more about your setup though, and assuming it's just straight VLANs and this is a dedicated 'gateway' box, there shouldn't be an issue. If the VLANs are internal virtual ethernet interfaces or something, though, that makes it more complex. The basics are here, though.
– Thomas Ward♦
Feb 6 at 17:46
add a comment |Â
up vote
1
down vote
up vote
1
down vote
This answer assumes you use an
iptablesfirewall on your 'router', and not something 'easier' likeufw, and that you have properly set up the router to handle VLANs on the given interface.
What you're looking for is called "NAT". This is done by default on many routers, however by default isn't done on Linux systems.
You'll need to enable IPv4 forwarding also in the system to make it work. Add this to the end of /etc/sysctl.conf:
net.ipv4.ip_forward = 1
You can get that to apply by doing sudo sysctl -p afterwards. This enables the ability to forward traffic through.
Since your default Internet route is out to the Public Internet, but you want to set up NAT so that the other VLAN machines can go out to the Internet via your system, you would need to set up something like this in iptables:
iptables -t nat -A POSTROUTING -s ip.add.re.ss/24 ! -d ip.add.re.ss/24 -m comment --comment "Allow vlanXX to go to the Internet, masquerade as the public IP." -j MASQUERADE
This is a rule in the NAT table for how to route traffic after it's arrived at the system. You'll need three of these rules, one for each subnet of each VLAN. Adjust ip.add.re.ss and vlanXX accordingly to match the information for your network specifically.
You also need to have an ACCEPT rule in the filter table of iptables for FORWARD, and you would typically do this by interface, like this, updating the XX items to be the vlan number:
iptables -t filter -A FORWARD -o ens1f1.XX -m comment --comment "NAT for vlanXX" -j ACCEPT
iptables -t filter -A FORWARD -i ens1f1.XX -m comment --comment "NAT for vlanXX" -j ACCEPT
Once you've done this, you need to make sure you save the iptables rules. Ideally you would do this if you didn't have it installed first, and tell it "Yes" when it asks to save your rules:
sudo apt-get install iptables-persistent
... and that would set up the iptables rules at boot properly as well as save the rules. If you already have iptables-persistent, then you need to update the rules it loads:
sudo su -c 'iptables-save > /etc/iptables/rules.v4'
... and now the NAT MASQUERADE rule will be in place every time you boot.
answered Feb 6 at 16:26
Thomas Ward♦
41.9k23115167
This answer assumes you use an
iptablesfirewall on your 'router', and not something 'easier' likeufw, and that you have properly set up the router to handle VLANs on the given interface.
What you're looking for is called "NAT". This is done by default on many routers, however by default isn't done on Linux systems.
You'll need to enable IPv4 forwarding also in the system to make it work. Add this to the end of /etc/sysctl.conf:
net.ipv4.ip_forward = 1
You can get that to apply by doing sudo sysctl -p afterwards. This enables the ability to forward traffic through.
Since your default Internet route is out to the Public Internet, but you want to set up NAT so that the other VLAN machines can go out to the Internet via your system, you would need to set up something like this in iptables:
iptables -t nat -A POSTROUTING -s ip.add.re.ss/24 ! -d ip.add.re.ss/24 -m comment --comment "Allow vlanXX to go to the Internet, masquerade as the public IP." -j MASQUERADE
This is a rule in the NAT table for how to route traffic after it's arrived at the system. You'll need three of these rules, one for each subnet of each VLAN. Adjust ip.add.re.ss and vlanXX accordingly to match the information for your network specifically.
You also need to have an ACCEPT rule in the filter table of iptables for FORWARD, and you would typically do this by interface, like this, updating the XX items to be the vlan number:
iptables -t filter -A FORWARD -o ens1f1.XX -m comment --comment "NAT for vlanXX" -j ACCEPT
iptables -t filter -A FORWARD -i ens1f1.XX -m comment --comment "NAT for vlanXX" -j ACCEPT
Once you've done this, you need to make sure you save the iptables rules. Ideally you would do this if you didn't have it installed first, and tell it "Yes" when it asks to save your rules:
sudo apt-get install iptables-persistent
... and that would set up the iptables rules at boot properly as well as save the rules. If you already have iptables-persistent, then you need to update the rules it loads:
sudo su -c 'iptables-save > /etc/iptables/rules.v4'
... and now the NAT MASQUERADE rule will be in place every time you boot.
answered Feb 6 at 16:26
Thomas Ward♦
41.9k23115167
edited Feb 6 at 18:25
answered Feb 6 at 16:26
Thomas Ward♦
41.9k23115167
answered Feb 6 at 16:26
Thomas Ward♦
41.9k23115167
answered Feb 6 at 16:26
Thomas Ward♦
41.9k23115167
41.9k23115167
Dear Thomas, Thank you so much for your rapid and thorough reply. So I don't need any bridges to solve this? The router in question still lives in my development lab, I would never let anything attach to the wild without a firewall. Although I looked into ufw, I couldn't see it helping me. Even so, my attempts using IPtables didn't get far either. I shall brew up a solution according to your recipe and report back. Regards, Kevin
– Kevin Anderson
Feb 6 at 17:13
@KevinAnderson You don't need a bridge, no. Especially if the VLANs are directly linked to the port itself. You just need simple NAT. (This NAT only lets it go out, it doesn't let unrelated traffic back into the systems, so if you are running a webserver on 1.2.3.4 on vlan30, you can't access the webserver from the public IP address without much more complicated NAT rules)
– Thomas Ward♦
Feb 6 at 17:45
@KevinAnderson Also you need to have the machine set up properly for 802.1Q VLAN tagging, per the linked "VLAN" help article from the Ubuntu Help documentation in order for all this to work properly. Without knowing more about your setup though, and assuming it's just straight VLANs and this is a dedicated 'gateway' box, there shouldn't be an issue. If the VLANs are internal virtual ethernet interfaces or something, though, that makes it more complex. The basics are here, though.
– Thomas Ward♦
Feb 6 at 17:46
add a comment |Â
Dear Thomas, Thank you so much for your rapid and thorough reply. So I don't need any bridges to solve this? The router in question still lives in my development lab, I would never let anything attach to the wild without a firewall. Although I looked into ufw, I couldn't see it helping me. Even so, my attempts using IPtables didn't get far either. I shall brew up a solution according to your recipe and report back. Regards, Kevin
– Kevin Anderson
Feb 6 at 17:13
@KevinAnderson You don't need a bridge, no. Especially if the VLANs are directly linked to the port itself. You just need simple NAT. (This NAT only lets it go out, it doesn't let unrelated traffic back into the systems, so if you are running a webserver on 1.2.3.4 on vlan30, you can't access the webserver from the public IP address without much more complicated NAT rules)
– Thomas Ward♦
Feb 6 at 17:45
@KevinAnderson Also you need to have the machine set up properly for 802.1Q VLAN tagging, per the linked "VLAN" help article from the Ubuntu Help documentation in order for all this to work properly. Without knowing more about your setup though, and assuming it's just straight VLANs and this is a dedicated 'gateway' box, there shouldn't be an issue. If the VLANs are internal virtual ethernet interfaces or something, though, that makes it more complex. The basics are here, though.
– Thomas Ward♦
Feb 6 at 17:46
Dear Thomas, Thank you so much for your rapid and thorough reply. So I don't need any bridges to solve this? The router in question still lives in my development lab, I would never let anything attach to the wild without a firewall. Although I looked into ufw, I couldn't see it helping me. Even so, my attempts using IPtables didn't get far either. I shall brew up a solution according to your recipe and report back. Regards, Kevin
– Kevin Anderson
Feb 6 at 17:13
Dear Thomas, Thank you so much for your rapid and thorough reply. So I don't need any bridges to solve this? The router in question still lives in my development lab, I would never let anything attach to the wild without a firewall. Although I looked into ufw, I couldn't see it helping me. Even so, my attempts using IPtables didn't get far either. I shall brew up a solution according to your recipe and report back. Regards, Kevin
– Kevin Anderson
Feb 6 at 17:13
@KevinAnderson You don't need a bridge, no. Especially if the VLANs are directly linked to the port itself. You just need simple NAT. (This NAT only lets it go out, it doesn't let unrelated traffic back into the systems, so if you are running a webserver on 1.2.3.4 on vlan30, you can't access the webserver from the public IP address without much more complicated NAT rules)
– Thomas Ward♦
Feb 6 at 17:45
@KevinAnderson You don't need a bridge, no. Especially if the VLANs are directly linked to the port itself. You just need simple NAT. (This NAT only lets it go out, it doesn't let unrelated traffic back into the systems, so if you are running a webserver on 1.2.3.4 on vlan30, you can't access the webserver from the public IP address without much more complicated NAT rules)
– Thomas Ward♦
Feb 6 at 17:45
@KevinAnderson Also you need to have the machine set up properly for 802.1Q VLAN tagging, per the linked "VLAN" help article from the Ubuntu Help documentation in order for all this to work properly. Without knowing more about your setup though, and assuming it's just straight VLANs and this is a dedicated 'gateway' box, there shouldn't be an issue. If the VLANs are internal virtual ethernet interfaces or something, though, that makes it more complex. The basics are here, though.
– Thomas Ward♦
Feb 6 at 17:46
@KevinAnderson Also you need to have the machine set up properly for 802.1Q VLAN tagging, per the linked "VLAN" help article from the Ubuntu Help documentation in order for all this to work properly. Without knowing more about your setup though, and assuming it's just straight VLANs and this is a dedicated 'gateway' box, there shouldn't be an issue. If the VLANs are internal virtual ethernet interfaces or something, though, that makes it more complex. The basics are here, though.
– Thomas Ward♦
Feb 6 at 17:46
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1003592%2fhow-do-i-give-vlans-internet-access%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
Do you use any type of firewall?
iptables,ufw, etc.? I have to ask because if you are usingufwit'll be a little bit trickier, if you're usingiptablesit won't be as hard, but if you're not using any firewall you're already breaking the cardinal rule of server admin.– Thomas Ward♦
Feb 6 at 15:59