How can I configure pfSense to allow traffic from LAN to WAN?
up vote
0
down vote
favorite
My topology is as the picture above.
I've configure to allow incoming traffic into each pfSense interface, include 3 LAN and 1 WAN.
Ex: I can ping from DC to pfSense interface in the same network.
I used default Manual Outbound NAT rule generation but still can't ping from inside network to outside and receive this message "PING: transmit failed. General failure."
Help me fixing this please.
networking firewall lan wan pfsense
edited Oct 23 '16 at 14:50
Journeyman Geek♦
111k43216364
asked Oct 22 '16 at 12:31
Nguyen Khanh
1111
add a comment |
up vote
0
down vote
favorite
My topology is as the picture above.
I've configure to allow incoming traffic into each pfSense interface, include 3 LAN and 1 WAN.
Ex: I can ping from DC to pfSense interface in the same network.
I used default Manual Outbound NAT rule generation but still can't ping from inside network to outside and receive this message "PING: transmit failed. General failure."
Help me fixing this please.
networking firewall lan wan pfsense
edited Oct 23 '16 at 14:50
Journeyman Geek♦
111k43216364
asked Oct 22 '16 at 12:31
Nguyen Khanh
1111
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
My topology is as the picture above.
I've configure to allow incoming traffic into each pfSense interface, include 3 LAN and 1 WAN.
Ex: I can ping from DC to pfSense interface in the same network.
I used default Manual Outbound NAT rule generation but still can't ping from inside network to outside and receive this message "PING: transmit failed. General failure."
Help me fixing this please.
networking firewall lan wan pfsense
edited Oct 23 '16 at 14:50
Journeyman Geek♦
111k43216364
asked Oct 22 '16 at 12:31
Nguyen Khanh
1111
My topology is as the picture above.
I've configure to allow incoming traffic into each pfSense interface, include 3 LAN and 1 WAN.
Ex: I can ping from DC to pfSense interface in the same network.
I used default Manual Outbound NAT rule generation but still can't ping from inside network to outside and receive this message "PING: transmit failed. General failure."
Help me fixing this please.
networking firewall lan wan pfsense
networking firewall lan wan pfsense
edited Oct 23 '16 at 14:50
Journeyman Geek♦
111k43216364
asked Oct 22 '16 at 12:31
Nguyen Khanh
1111
edited Oct 23 '16 at 14:50
Journeyman Geek♦
111k43216364
asked Oct 22 '16 at 12:31
Nguyen Khanh
1111
edited Oct 23 '16 at 14:50
Journeyman Geek♦
111k43216364
edited Oct 23 '16 at 14:50
Journeyman Geek♦
111k43216364
edited Oct 23 '16 at 14:50
Journeyman Geek♦
111k43216364
111k43216364
asked Oct 22 '16 at 12:31
Nguyen Khanh
1111
asked Oct 22 '16 at 12:31
Nguyen Khanh
1111
asked Oct 22 '16 at 12:31
Nguyen Khanh
1111
1111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Okay, by default the first LAN connection should be able to ping from the LAN to WAN (Outbound rules) but the rest of the LAN interfaces do not have rules automatically created: You will need to add rules under Firewall > Rules > [LAN*] and Firewall > NAT > Outbound.
Clarifying the LAN rules again, you will need a rule to say certain traffic is allowed in and out.
I do not know exactly what you have configured - IP address wise - from your original post.
If you require further assistance, could you send a screen-shot of the above tabs.
I hope the above helps.
Kind regards,
Andre Morton
answered Oct 22 '16 at 15:56
A. Morton
413
This is detailed topology with IP address:
– Nguyen Khanh
Oct 23 '16 at 13:21
Sorry, this is detailed topology with IP address: imgur.com/a/dOWqz Sorry if it's hard to see. The default LAN network is 192.168.1.0, as you said, it should be able to ping to WAN. But it can't, this is the result: imgur.com/fERsTfM Configuration for each interface: imgur.com/zhXgVCv Thank's for your help.
– Nguyen Khanh
Oct 23 '16 at 13:29
Can you also send a screen shot of the Firewall > Rules > [LAN*] tab please. The other settings look correct.
– A. Morton
Oct 23 '16 at 15:50
Also, have you unchecked the 'Block private networks' check box under Interfaces > WAN? As this blocks all private RFC1918 addresses: 192.168.*.* 10.*.*.* 172.16.*.*
– A. Morton
Oct 23 '16 at 15:56
1
Sorry, I fixed this haha, I forgot to add default gateway in each machine.
– Nguyen Khanh
Oct 24 '16 at 14:06
|
show 7 more comments
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Okay, by default the first LAN connection should be able to ping from the LAN to WAN (Outbound rules) but the rest of the LAN interfaces do not have rules automatically created: You will need to add rules under Firewall > Rules > [LAN*] and Firewall > NAT > Outbound.
Clarifying the LAN rules again, you will need a rule to say certain traffic is allowed in and out.
I do not know exactly what you have configured - IP address wise - from your original post.
If you require further assistance, could you send a screen-shot of the above tabs.
I hope the above helps.
Kind regards,
Andre Morton
answered Oct 22 '16 at 15:56
A. Morton
413
This is detailed topology with IP address:
– Nguyen Khanh
Oct 23 '16 at 13:21
Sorry, this is detailed topology with IP address: imgur.com/a/dOWqz Sorry if it's hard to see. The default LAN network is 192.168.1.0, as you said, it should be able to ping to WAN. But it can't, this is the result: imgur.com/fERsTfM Configuration for each interface: imgur.com/zhXgVCv Thank's for your help.
– Nguyen Khanh
Oct 23 '16 at 13:29
Can you also send a screen shot of the Firewall > Rules > [LAN*] tab please. The other settings look correct.
– A. Morton
Oct 23 '16 at 15:50
Also, have you unchecked the 'Block private networks' check box under Interfaces > WAN? As this blocks all private RFC1918 addresses: 192.168.*.* 10.*.*.* 172.16.*.*
– A. Morton
Oct 23 '16 at 15:56
1
Sorry, I fixed this haha, I forgot to add default gateway in each machine.
– Nguyen Khanh
Oct 24 '16 at 14:06
|
show 7 more comments
up vote
0
down vote
Okay, by default the first LAN connection should be able to ping from the LAN to WAN (Outbound rules) but the rest of the LAN interfaces do not have rules automatically created: You will need to add rules under Firewall > Rules > [LAN*] and Firewall > NAT > Outbound.
Clarifying the LAN rules again, you will need a rule to say certain traffic is allowed in and out.
I do not know exactly what you have configured - IP address wise - from your original post.
If you require further assistance, could you send a screen-shot of the above tabs.
I hope the above helps.
Kind regards,
Andre Morton
answered Oct 22 '16 at 15:56
A. Morton
413
This is detailed topology with IP address:
– Nguyen Khanh
Oct 23 '16 at 13:21
Sorry, this is detailed topology with IP address: imgur.com/a/dOWqz Sorry if it's hard to see. The default LAN network is 192.168.1.0, as you said, it should be able to ping to WAN. But it can't, this is the result: imgur.com/fERsTfM Configuration for each interface: imgur.com/zhXgVCv Thank's for your help.
– Nguyen Khanh
Oct 23 '16 at 13:29
Can you also send a screen shot of the Firewall > Rules > [LAN*] tab please. The other settings look correct.
– A. Morton
Oct 23 '16 at 15:50
Also, have you unchecked the 'Block private networks' check box under Interfaces > WAN? As this blocks all private RFC1918 addresses: 192.168.*.* 10.*.*.* 172.16.*.*
– A. Morton
Oct 23 '16 at 15:56
1
Sorry, I fixed this haha, I forgot to add default gateway in each machine.
– Nguyen Khanh
Oct 24 '16 at 14:06
|
show 7 more comments
up vote
0
down vote
up vote
0
down vote
Okay, by default the first LAN connection should be able to ping from the LAN to WAN (Outbound rules) but the rest of the LAN interfaces do not have rules automatically created: You will need to add rules under Firewall > Rules > [LAN*] and Firewall > NAT > Outbound.
Clarifying the LAN rules again, you will need a rule to say certain traffic is allowed in and out.
I do not know exactly what you have configured - IP address wise - from your original post.
If you require further assistance, could you send a screen-shot of the above tabs.
I hope the above helps.
Kind regards,
Andre Morton
answered Oct 22 '16 at 15:56
A. Morton
413
Okay, by default the first LAN connection should be able to ping from the LAN to WAN (Outbound rules) but the rest of the LAN interfaces do not have rules automatically created: You will need to add rules under Firewall > Rules > [LAN*] and Firewall > NAT > Outbound.
Clarifying the LAN rules again, you will need a rule to say certain traffic is allowed in and out.
I do not know exactly what you have configured - IP address wise - from your original post.
If you require further assistance, could you send a screen-shot of the above tabs.
I hope the above helps.
Kind regards,
Andre Morton
answered Oct 22 '16 at 15:56
A. Morton
413
edited Oct 22 '16 at 16:08
answered Oct 22 '16 at 15:56
A. Morton
413
answered Oct 22 '16 at 15:56
A. Morton
413
answered Oct 22 '16 at 15:56
A. Morton
413
413
This is detailed topology with IP address:
– Nguyen Khanh
Oct 23 '16 at 13:21
Sorry, this is detailed topology with IP address: imgur.com/a/dOWqz Sorry if it's hard to see. The default LAN network is 192.168.1.0, as you said, it should be able to ping to WAN. But it can't, this is the result: imgur.com/fERsTfM Configuration for each interface: imgur.com/zhXgVCv Thank's for your help.
– Nguyen Khanh
Oct 23 '16 at 13:29
Can you also send a screen shot of the Firewall > Rules > [LAN*] tab please. The other settings look correct.
– A. Morton
Oct 23 '16 at 15:50
Also, have you unchecked the 'Block private networks' check box under Interfaces > WAN? As this blocks all private RFC1918 addresses: 192.168.*.* 10.*.*.* 172.16.*.*
– A. Morton
Oct 23 '16 at 15:56
1
Sorry, I fixed this haha, I forgot to add default gateway in each machine.
– Nguyen Khanh
Oct 24 '16 at 14:06
|
show 7 more comments
This is detailed topology with IP address:
– Nguyen Khanh
Oct 23 '16 at 13:21
Sorry, this is detailed topology with IP address: imgur.com/a/dOWqz Sorry if it's hard to see. The default LAN network is 192.168.1.0, as you said, it should be able to ping to WAN. But it can't, this is the result: imgur.com/fERsTfM Configuration for each interface: imgur.com/zhXgVCv Thank's for your help.
– Nguyen Khanh
Oct 23 '16 at 13:29
Can you also send a screen shot of the Firewall > Rules > [LAN*] tab please. The other settings look correct.
– A. Morton
Oct 23 '16 at 15:50
Also, have you unchecked the 'Block private networks' check box under Interfaces > WAN? As this blocks all private RFC1918 addresses: 192.168.*.* 10.*.*.* 172.16.*.*
– A. Morton
Oct 23 '16 at 15:56
1
Sorry, I fixed this haha, I forgot to add default gateway in each machine.
– Nguyen Khanh
Oct 24 '16 at 14:06
This is detailed topology with IP address:
– Nguyen Khanh
Oct 23 '16 at 13:21
This is detailed topology with IP address:
– Nguyen Khanh
Oct 23 '16 at 13:21
Sorry, this is detailed topology with IP address: imgur.com/a/dOWqz Sorry if it's hard to see. The default LAN network is 192.168.1.0, as you said, it should be able to ping to WAN. But it can't, this is the result: imgur.com/fERsTfM Configuration for each interface: imgur.com/zhXgVCv Thank's for your help.
– Nguyen Khanh
Oct 23 '16 at 13:29
Sorry, this is detailed topology with IP address: imgur.com/a/dOWqz Sorry if it's hard to see. The default LAN network is 192.168.1.0, as you said, it should be able to ping to WAN. But it can't, this is the result: imgur.com/fERsTfM Configuration for each interface: imgur.com/zhXgVCv Thank's for your help.
– Nguyen Khanh
Oct 23 '16 at 13:29
Can you also send a screen shot of the Firewall > Rules > [LAN*] tab please. The other settings look correct.
– A. Morton
Oct 23 '16 at 15:50
Can you also send a screen shot of the Firewall > Rules > [LAN*] tab please. The other settings look correct.
– A. Morton
Oct 23 '16 at 15:50
Also, have you unchecked the 'Block private networks' check box under Interfaces > WAN? As this blocks all private RFC1918 addresses: 192.168.*.* 10.*.*.* 172.16.*.*
– A. Morton
Oct 23 '16 at 15:56
Also, have you unchecked the 'Block private networks' check box under Interfaces > WAN? As this blocks all private RFC1918 addresses: 192.168.*.* 10.*.*.* 172.16.*.*
– A. Morton
Oct 23 '16 at 15:56
1
1
Sorry, I fixed this haha, I forgot to add default gateway in each machine.
– Nguyen Khanh
Oct 24 '16 at 14:06
Sorry, I fixed this haha, I forgot to add default gateway in each machine.
– Nguyen Khanh
Oct 24 '16 at 14:06
|
show 7 more comments
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%2f1137753%2fhow-can-i-configure-pfsense-to-allow-traffic-from-lan-to-wan%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
