pfsense: Connection between two lans drops after 30s Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!pfsense: connection between two internal lans dropped after 20 secondspfSense with a bridge as a LAN interface : traffic blocked between interfacesUsing PFSense to securely connect two networkspfSense router on a LAN with two gatewayspfSense routing between two routers with shared networkpfsense: connection between two internal lans dropped after 20 secondsPfSense box not passing traffic between WAN and LANpfSense on Hyper-V random package dropsRunning pfsense on a xenserver - Random network drops?pfSense LAN ConfigurationpFsense drops packets between 2 LAN interfaces - sometimes
How does the math work when buying airline miles?
Significance of Cersei's obsession with elephants?
Is grep documentation about ignoring case wrong, since it doesn't ignore case in filenames?
Source for Esri sample data from 911 Hot Spot Analysis
How to install press fit bottom bracket into new frame
Did Deadpool rescue all of the X-Force?
What do you call the main part of a joke?
Most bit efficient text communication method?
AppleTVs create a chatty alternate WiFi network
Question about debouncing - delay of state change
How come Sam didn't become Lord of Horn Hill?
Why is it faster to reheat something than it is to cook it?
Do I really need to have a message in a novel to appeal to readers?
Using et al. for a last / senior author rather than for a first author
Are all finite dimensional hilbert spaces isomorphic to spaces with Euclidean norms?
As a beginner, should I get a Squier Strat with a SSS config or a HSS?
Is it fair for a professor to grade us on the possession of past papers?
Is there any word for a place full of confusion?
Chinese Seal on silk painting - what does it mean?
Sum letters are not two different
How do I make this wiring inside cabinet safer?
Time to Settle Down!
Hangman Game with C++
A term for a woman complaining about things/begging in a cute/childish way
pfsense: Connection between two lans drops after 30s
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!pfsense: connection between two internal lans dropped after 20 secondspfSense with a bridge as a LAN interface : traffic blocked between interfacesUsing PFSense to securely connect two networkspfSense router on a LAN with two gatewayspfSense routing between two routers with shared networkpfsense: connection between two internal lans dropped after 20 secondsPfSense box not passing traffic between WAN and LANpfSense on Hyper-V random package dropsRunning pfsense on a xenserver - Random network drops?pfSense LAN ConfigurationpFsense drops packets between 2 LAN interfaces - sometimes
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
Problem Solved
It was an asymetric routing problem. It occured because i had two NICs on the server, one wired and one wireless. When connecting to the server via wlan-ap-wire, the packets took another way back. The solution was pretty easy, just disabled one NIC (the one for wlan, only used when testing...).
Original question
I have the following setup on my lan.
LAN: 192.168.1.0/24 (LAN for clients)
DMZ: 192.168.20.0/25 (LAN for server)
WAN: X.X.X.X
One router acting AP (192.168.1.200) on the LAN interface for WLAN access.
Scheme:
WAN - router with pfsense - LAN - (dd wrt as AP, WLAN) - clients
- DMZ (wired)
When i ssh from a client connected to the WLAN to the server on the DMZ interface the connection drops out after ~30s.
EDIT: i get the same problem with ftp, the tcp connection drops out after ~30s. Probably a asymmetric routing problem...
For debug purpose i tested to connect the DMZ to the WLAN, and then it works perfect.
One solution is of course to connect the server to the LAN interface instead of the DMZ interface.
I googled and found a similar thread: pfsense: connection between two internal lans dropped after 20 seconds
I think the problem is what tleding is speaking about:
"... As you probably already realize, because the switch had an IP in the same subnet as my machine, return packets from the switch would go direct to my machine rather than following the same path as packets from my machine. The switch would essentially just side-step the PFSENSE box...."
But i cant solve the issue.
For debug purpose i added allow all rules on both the LAN and the DMZ interface, and the initial connection works.
Sorry,i’m a bit unclear.
My wlan is just an AP plugged into the lan using an old netgear router as an access point, so the wlan and lan is the same net. All clients is getting their IP from 192.168.1.1 (pfsense). The ap is configured as https://wiki.dd-wrt.com/wiki/index.php/Wireless_Access_Point
nat pfsense access-point
asked Apr 12 at 19:48
joxxejoxxe
32
New contributor
joxxe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Problem Solved
It was an asymetric routing problem. It occured because i had two NICs on the server, one wired and one wireless. When connecting to the server via wlan-ap-wire, the packets took another way back. The solution was pretty easy, just disabled one NIC (the one for wlan, only used when testing...).
Original question
I have the following setup on my lan.
LAN: 192.168.1.0/24 (LAN for clients)
DMZ: 192.168.20.0/25 (LAN for server)
WAN: X.X.X.X
One router acting AP (192.168.1.200) on the LAN interface for WLAN access.
Scheme:
WAN - router with pfsense - LAN - (dd wrt as AP, WLAN) - clients
- DMZ (wired)
When i ssh from a client connected to the WLAN to the server on the DMZ interface the connection drops out after ~30s.
EDIT: i get the same problem with ftp, the tcp connection drops out after ~30s. Probably a asymmetric routing problem...
For debug purpose i tested to connect the DMZ to the WLAN, and then it works perfect.
One solution is of course to connect the server to the LAN interface instead of the DMZ interface.
I googled and found a similar thread: pfsense: connection between two internal lans dropped after 20 seconds
I think the problem is what tleding is speaking about:
"... As you probably already realize, because the switch had an IP in the same subnet as my machine, return packets from the switch would go direct to my machine rather than following the same path as packets from my machine. The switch would essentially just side-step the PFSENSE box...."
But i cant solve the issue.
For debug purpose i added allow all rules on both the LAN and the DMZ interface, and the initial connection works.
Sorry,i’m a bit unclear.
My wlan is just an AP plugged into the lan using an old netgear router as an access point, so the wlan and lan is the same net. All clients is getting their IP from 192.168.1.1 (pfsense). The ap is configured as https://wiki.dd-wrt.com/wiki/index.php/Wireless_Access_Point
nat pfsense access-point
asked Apr 12 at 19:48
joxxejoxxe
32
New contributor
joxxe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Problem Solved
It was an asymetric routing problem. It occured because i had two NICs on the server, one wired and one wireless. When connecting to the server via wlan-ap-wire, the packets took another way back. The solution was pretty easy, just disabled one NIC (the one for wlan, only used when testing...).
Original question
I have the following setup on my lan.
LAN: 192.168.1.0/24 (LAN for clients)
DMZ: 192.168.20.0/25 (LAN for server)
WAN: X.X.X.X
One router acting AP (192.168.1.200) on the LAN interface for WLAN access.
Scheme:
WAN - router with pfsense - LAN - (dd wrt as AP, WLAN) - clients
- DMZ (wired)
When i ssh from a client connected to the WLAN to the server on the DMZ interface the connection drops out after ~30s.
EDIT: i get the same problem with ftp, the tcp connection drops out after ~30s. Probably a asymmetric routing problem...
For debug purpose i tested to connect the DMZ to the WLAN, and then it works perfect.
One solution is of course to connect the server to the LAN interface instead of the DMZ interface.
I googled and found a similar thread: pfsense: connection between two internal lans dropped after 20 seconds
I think the problem is what tleding is speaking about:
"... As you probably already realize, because the switch had an IP in the same subnet as my machine, return packets from the switch would go direct to my machine rather than following the same path as packets from my machine. The switch would essentially just side-step the PFSENSE box...."
But i cant solve the issue.
For debug purpose i added allow all rules on both the LAN and the DMZ interface, and the initial connection works.
Sorry,i’m a bit unclear.
My wlan is just an AP plugged into the lan using an old netgear router as an access point, so the wlan and lan is the same net. All clients is getting their IP from 192.168.1.1 (pfsense). The ap is configured as https://wiki.dd-wrt.com/wiki/index.php/Wireless_Access_Point
nat pfsense access-point
asked Apr 12 at 19:48
joxxejoxxe
32
New contributor
joxxe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Problem Solved
It was an asymetric routing problem. It occured because i had two NICs on the server, one wired and one wireless. When connecting to the server via wlan-ap-wire, the packets took another way back. The solution was pretty easy, just disabled one NIC (the one for wlan, only used when testing...).
Original question
I have the following setup on my lan.
LAN: 192.168.1.0/24 (LAN for clients)
DMZ: 192.168.20.0/25 (LAN for server)
WAN: X.X.X.X
One router acting AP (192.168.1.200) on the LAN interface for WLAN access.
Scheme:
WAN - router with pfsense - LAN - (dd wrt as AP, WLAN) - clients
- DMZ (wired)
When i ssh from a client connected to the WLAN to the server on the DMZ interface the connection drops out after ~30s.
EDIT: i get the same problem with ftp, the tcp connection drops out after ~30s. Probably a asymmetric routing problem...
For debug purpose i tested to connect the DMZ to the WLAN, and then it works perfect.
One solution is of course to connect the server to the LAN interface instead of the DMZ interface.
I googled and found a similar thread: pfsense: connection between two internal lans dropped after 20 seconds
I think the problem is what tleding is speaking about:
"... As you probably already realize, because the switch had an IP in the same subnet as my machine, return packets from the switch would go direct to my machine rather than following the same path as packets from my machine. The switch would essentially just side-step the PFSENSE box...."
But i cant solve the issue.
For debug purpose i added allow all rules on both the LAN and the DMZ interface, and the initial connection works.
Sorry,i’m a bit unclear.
My wlan is just an AP plugged into the lan using an old netgear router as an access point, so the wlan and lan is the same net. All clients is getting their IP from 192.168.1.1 (pfsense). The ap is configured as https://wiki.dd-wrt.com/wiki/index.php/Wireless_Access_Point
nat pfsense access-point
nat pfsense access-point
asked Apr 12 at 19:48
joxxejoxxe
32
New contributor
joxxe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 12 at 19:48
joxxejoxxe
32
New contributor
joxxe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Apr 13 at 20:53
joxxe
asked Apr 12 at 19:48
joxxejoxxe
32
New contributor
joxxe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 12 at 19:48
joxxejoxxe
32
asked Apr 12 at 19:48
joxxejoxxe
32
32
New contributor
joxxe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
joxxe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
joxxe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Your LAN subnet is 192.168.1.0/24 and from your question it looks like your WLAN is a router with an IP of 192.168.1.200 and a 192.168.1.0/24 subnet, that's not going to work. You need to change your WLAN subnet to be different than your LAN subnet if you want to keep routing between them, or just attach your LAN port on your WLAN router to an available LAN port on your client pfsense network.
answered Apr 12 at 22:19
Bob DoleBob Dole
763
New contributor
Bob Dole is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
protected by Community♦ Apr 13 at 11:46
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your LAN subnet is 192.168.1.0/24 and from your question it looks like your WLAN is a router with an IP of 192.168.1.200 and a 192.168.1.0/24 subnet, that's not going to work. You need to change your WLAN subnet to be different than your LAN subnet if you want to keep routing between them, or just attach your LAN port on your WLAN router to an available LAN port on your client pfsense network.
answered Apr 12 at 22:19
Bob DoleBob Dole
763
New contributor
Bob Dole is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your LAN subnet is 192.168.1.0/24 and from your question it looks like your WLAN is a router with an IP of 192.168.1.200 and a 192.168.1.0/24 subnet, that's not going to work. You need to change your WLAN subnet to be different than your LAN subnet if you want to keep routing between them, or just attach your LAN port on your WLAN router to an available LAN port on your client pfsense network.
answered Apr 12 at 22:19
Bob DoleBob Dole
763
New contributor
Bob Dole is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your LAN subnet is 192.168.1.0/24 and from your question it looks like your WLAN is a router with an IP of 192.168.1.200 and a 192.168.1.0/24 subnet, that's not going to work. You need to change your WLAN subnet to be different than your LAN subnet if you want to keep routing between them, or just attach your LAN port on your WLAN router to an available LAN port on your client pfsense network.
answered Apr 12 at 22:19
Bob DoleBob Dole
763
New contributor
Bob Dole is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Your LAN subnet is 192.168.1.0/24 and from your question it looks like your WLAN is a router with an IP of 192.168.1.200 and a 192.168.1.0/24 subnet, that's not going to work. You need to change your WLAN subnet to be different than your LAN subnet if you want to keep routing between them, or just attach your LAN port on your WLAN router to an available LAN port on your client pfsense network.
answered Apr 12 at 22:19
Bob DoleBob Dole
763
New contributor
Bob Dole is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Apr 12 at 22:19
Bob DoleBob Dole
763
New contributor
Bob Dole is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Apr 12 at 22:19
Bob DoleBob Dole
763
answered Apr 12 at 22:19
Bob DoleBob Dole
763
763
New contributor
Bob Dole is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Bob Dole is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Bob Dole is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
protected by Community♦ Apr 13 at 11:46
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
