Can't transfer files via FTP through VPN after switch to new router (with identical network and port-forwarding settings) Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Come Celebrate our 10 Year Anniversary!How to route all traffic over site to site VPN tunnel?Passive mode for FileZilla FTP isn't workingCisco ASA VPN - Route all internet traffic from remote site through main site's ISPopenvpn tunnel- tunnel is up but issues with routingOpenVPN Site2Site using PFSenseSetting up a server that routes local traffic through vpn, while still being able to access internet directlyDual-Stack Lite and FTP connection via IPv4 - How?Same routes under VPN - how to workaround?Shorewall: VPN clients can access LAN resources, but not the InternetWhy should I use VPN in this scenario?
Caught masturbating at work
Most effective melee weapons for arboreal combat? (pre-gunpowder technology)
Flight departed from the gate 5 min before scheduled departure time. Refund options
How can I save and copy a screenhot at the same time?
Is openssl rand command cryptographically secure?
One-one communication
What is the difference between a "ranged attack" and a "ranged weapon attack"?
Project Euler #1 in C++
Resize vertical bars (absolute-value symbols)
Random body shuffle every night—can we still function?
Is there public access to the Meteor Crater in Arizona?
New Order #6: Easter Egg
Did any compiler fully use 80-bit floating point?
Why is it faster to reheat something than it is to cook it?
What does the writing on Poe's helmet say?
Why complex landing gears are used instead of simple,reliability and light weight muscle wire or shape memory alloys?
Wrapping text with mathclap
Why shouldn't this prove the Prime Number Theorem?
How to align enumerate environment inside description environment
Does the Black Tentacles spell do damage twice at the start of turn to an already restrained creature?
How many time has Arya actually used Needle?
Google .dev domain strangely redirects to https
After Sam didn't return home in the end, were he and Al still friends?
Does the Mueller report show a conspiracy between Russia and the Trump Campaign?
Can't transfer files via FTP through VPN after switch to new router (with identical network and port-forwarding settings)
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Come Celebrate our 10 Year Anniversary!How to route all traffic over site to site VPN tunnel?Passive mode for FileZilla FTP isn't workingCisco ASA VPN - Route all internet traffic from remote site through main site's ISPopenvpn tunnel- tunnel is up but issues with routingOpenVPN Site2Site using PFSenseSetting up a server that routes local traffic through vpn, while still being able to access internet directlyDual-Stack Lite and FTP connection via IPv4 - How?Same routes under VPN - how to workaround?Shorewall: VPN clients can access LAN resources, but not the InternetWhy should I use VPN in this scenario?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have a problem with the following setup: A friendly local business has a time stamp clock on site A. This clock provides data via an integrated ftp server. Also on site A: a Raspberry Pi 3 running Debian Wheezy acting as OpenVPN server. Port forwarding on the router was set to enable VPN and SSH connections from the internet via a dynamic DNS address. This enabled users from site B, where the payroll accounting magic is happening, to first establish a tunnel to site A's network and then fetch time stamp clock data with the help of a proprietary Windows software using the (active) FTP protocol.
It all worked fine until they switched their internet provider. The new router (to which I don't have access) was set up identical to the old one with all clients on the network having the same IPs – and the same port forwarding settings as well. After the switch, I still can SSH into the raspberry, open a tunnel to site A's network, and ping the time stamp clock. But whenever I try to fetch the data via FTP (no matter if I try it with the proprietary software from the manufacturer or with a standard FTP client), I errors like "LIST requested action not taken" or something similar.
My guess is that this somehow is an active FTP protocol problem where the answers from the time stamp clock are not routed back through the tunnel properly. But this is just a guess – and I have no idea how to debug and fix this. Maybe anyone here does? Anything that hints me in the right direction is highly appreciated!
Thank you and greetings from Germany!
networking vpn routing openvpn ftp
asked Apr 15 at 5:19
JürgenJürgen
61
New contributor
Jürgen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
|
show 1 more comment
I have a problem with the following setup: A friendly local business has a time stamp clock on site A. This clock provides data via an integrated ftp server. Also on site A: a Raspberry Pi 3 running Debian Wheezy acting as OpenVPN server. Port forwarding on the router was set to enable VPN and SSH connections from the internet via a dynamic DNS address. This enabled users from site B, where the payroll accounting magic is happening, to first establish a tunnel to site A's network and then fetch time stamp clock data with the help of a proprietary Windows software using the (active) FTP protocol.
It all worked fine until they switched their internet provider. The new router (to which I don't have access) was set up identical to the old one with all clients on the network having the same IPs – and the same port forwarding settings as well. After the switch, I still can SSH into the raspberry, open a tunnel to site A's network, and ping the time stamp clock. But whenever I try to fetch the data via FTP (no matter if I try it with the proprietary software from the manufacturer or with a standard FTP client), I errors like "LIST requested action not taken" or something similar.
My guess is that this somehow is an active FTP protocol problem where the answers from the time stamp clock are not routed back through the tunnel properly. But this is just a guess – and I have no idea how to debug and fix this. Maybe anyone here does? Anything that hints me in the right direction is highly appreciated!
Thank you and greetings from Germany!
networking vpn routing openvpn ftp
asked Apr 15 at 5:19
JürgenJürgen
61
New contributor
Jürgen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
The new router, contrary to the claims made, is almost certainly not setup identically to the old one. Have the ISP, or whoever did the setup and made the false claim, to fix it.
– womble♦
Apr 15 at 6:45
But how can FTP be blocked if the tunnel is otherwise working? I just don't get my head around that.
– Jürgen
Apr 15 at 8:13
1
The information you have provided is not enough to troubleshoot the issue. If it was working before, and not working now, there must be something that changed. Comparing the new settings with old one would be the first step to start troubleshooting.
– Abu Zaid
Apr 15 at 10:29
OpenVPN and FTP settings are identical (as they haven't changed). All I did was updating the raspberry in the hope that this would fix things. I have no router access; I assumed – as SSH and VPN tunnels are working – that the configuration here is okay. But I don't know how I could possibly verify that. Is it technically possible that the router forwards the tunnel correctly but prevents FTP from working? How? As you might have already guessed, I'm not an expert, so sorry if these are dumb questions – I just don't understand what is going on here.
– Jürgen
Apr 15 at 13:34
That would be difficult to answer. FTP is complicated than ssh. Without router access, your options are limited. You can try to run Wireshark/tcpdump and analyze the traffic, see if the connection is established, authentication is working, and so on. You will need to have good understanding of a working ftp session, and then if you see the issue is with Network (traffic is not making through), present it to your new service provider.
– Abu Zaid
Apr 15 at 16:34
|
show 1 more comment
I have a problem with the following setup: A friendly local business has a time stamp clock on site A. This clock provides data via an integrated ftp server. Also on site A: a Raspberry Pi 3 running Debian Wheezy acting as OpenVPN server. Port forwarding on the router was set to enable VPN and SSH connections from the internet via a dynamic DNS address. This enabled users from site B, where the payroll accounting magic is happening, to first establish a tunnel to site A's network and then fetch time stamp clock data with the help of a proprietary Windows software using the (active) FTP protocol.
It all worked fine until they switched their internet provider. The new router (to which I don't have access) was set up identical to the old one with all clients on the network having the same IPs – and the same port forwarding settings as well. After the switch, I still can SSH into the raspberry, open a tunnel to site A's network, and ping the time stamp clock. But whenever I try to fetch the data via FTP (no matter if I try it with the proprietary software from the manufacturer or with a standard FTP client), I errors like "LIST requested action not taken" or something similar.
My guess is that this somehow is an active FTP protocol problem where the answers from the time stamp clock are not routed back through the tunnel properly. But this is just a guess – and I have no idea how to debug and fix this. Maybe anyone here does? Anything that hints me in the right direction is highly appreciated!
Thank you and greetings from Germany!
networking vpn routing openvpn ftp
asked Apr 15 at 5:19
JürgenJürgen
61
New contributor
Jürgen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have a problem with the following setup: A friendly local business has a time stamp clock on site A. This clock provides data via an integrated ftp server. Also on site A: a Raspberry Pi 3 running Debian Wheezy acting as OpenVPN server. Port forwarding on the router was set to enable VPN and SSH connections from the internet via a dynamic DNS address. This enabled users from site B, where the payroll accounting magic is happening, to first establish a tunnel to site A's network and then fetch time stamp clock data with the help of a proprietary Windows software using the (active) FTP protocol.
It all worked fine until they switched their internet provider. The new router (to which I don't have access) was set up identical to the old one with all clients on the network having the same IPs – and the same port forwarding settings as well. After the switch, I still can SSH into the raspberry, open a tunnel to site A's network, and ping the time stamp clock. But whenever I try to fetch the data via FTP (no matter if I try it with the proprietary software from the manufacturer or with a standard FTP client), I errors like "LIST requested action not taken" or something similar.
My guess is that this somehow is an active FTP protocol problem where the answers from the time stamp clock are not routed back through the tunnel properly. But this is just a guess – and I have no idea how to debug and fix this. Maybe anyone here does? Anything that hints me in the right direction is highly appreciated!
Thank you and greetings from Germany!
networking vpn routing openvpn ftp
networking vpn routing openvpn ftp
asked Apr 15 at 5:19
JürgenJürgen
61
New contributor
Jürgen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 15 at 5:19
JürgenJürgen
61
New contributor
Jürgen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 15 at 5:19
JürgenJürgen
61
New contributor
Jürgen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 15 at 5:19
JürgenJürgen
61
asked Apr 15 at 5:19
JürgenJürgen
61
61
New contributor
Jürgen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jürgen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jürgen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
The new router, contrary to the claims made, is almost certainly not setup identically to the old one. Have the ISP, or whoever did the setup and made the false claim, to fix it.
– womble♦
Apr 15 at 6:45
But how can FTP be blocked if the tunnel is otherwise working? I just don't get my head around that.
– Jürgen
Apr 15 at 8:13
1
The information you have provided is not enough to troubleshoot the issue. If it was working before, and not working now, there must be something that changed. Comparing the new settings with old one would be the first step to start troubleshooting.
– Abu Zaid
Apr 15 at 10:29
OpenVPN and FTP settings are identical (as they haven't changed). All I did was updating the raspberry in the hope that this would fix things. I have no router access; I assumed – as SSH and VPN tunnels are working – that the configuration here is okay. But I don't know how I could possibly verify that. Is it technically possible that the router forwards the tunnel correctly but prevents FTP from working? How? As you might have already guessed, I'm not an expert, so sorry if these are dumb questions – I just don't understand what is going on here.
– Jürgen
Apr 15 at 13:34
That would be difficult to answer. FTP is complicated than ssh. Without router access, your options are limited. You can try to run Wireshark/tcpdump and analyze the traffic, see if the connection is established, authentication is working, and so on. You will need to have good understanding of a working ftp session, and then if you see the issue is with Network (traffic is not making through), present it to your new service provider.
– Abu Zaid
Apr 15 at 16:34
|
show 1 more comment
1
The new router, contrary to the claims made, is almost certainly not setup identically to the old one. Have the ISP, or whoever did the setup and made the false claim, to fix it.
– womble♦
Apr 15 at 6:45
But how can FTP be blocked if the tunnel is otherwise working? I just don't get my head around that.
– Jürgen
Apr 15 at 8:13
1
The information you have provided is not enough to troubleshoot the issue. If it was working before, and not working now, there must be something that changed. Comparing the new settings with old one would be the first step to start troubleshooting.
– Abu Zaid
Apr 15 at 10:29
OpenVPN and FTP settings are identical (as they haven't changed). All I did was updating the raspberry in the hope that this would fix things. I have no router access; I assumed – as SSH and VPN tunnels are working – that the configuration here is okay. But I don't know how I could possibly verify that. Is it technically possible that the router forwards the tunnel correctly but prevents FTP from working? How? As you might have already guessed, I'm not an expert, so sorry if these are dumb questions – I just don't understand what is going on here.
– Jürgen
Apr 15 at 13:34
That would be difficult to answer. FTP is complicated than ssh. Without router access, your options are limited. You can try to run Wireshark/tcpdump and analyze the traffic, see if the connection is established, authentication is working, and so on. You will need to have good understanding of a working ftp session, and then if you see the issue is with Network (traffic is not making through), present it to your new service provider.
– Abu Zaid
Apr 15 at 16:34
1
1
The new router, contrary to the claims made, is almost certainly not setup identically to the old one. Have the ISP, or whoever did the setup and made the false claim, to fix it.
– womble♦
Apr 15 at 6:45
The new router, contrary to the claims made, is almost certainly not setup identically to the old one. Have the ISP, or whoever did the setup and made the false claim, to fix it.
– womble♦
Apr 15 at 6:45
But how can FTP be blocked if the tunnel is otherwise working? I just don't get my head around that.
– Jürgen
Apr 15 at 8:13
But how can FTP be blocked if the tunnel is otherwise working? I just don't get my head around that.
– Jürgen
Apr 15 at 8:13
1
1
The information you have provided is not enough to troubleshoot the issue. If it was working before, and not working now, there must be something that changed. Comparing the new settings with old one would be the first step to start troubleshooting.
– Abu Zaid
Apr 15 at 10:29
The information you have provided is not enough to troubleshoot the issue. If it was working before, and not working now, there must be something that changed. Comparing the new settings with old one would be the first step to start troubleshooting.
– Abu Zaid
Apr 15 at 10:29
OpenVPN and FTP settings are identical (as they haven't changed). All I did was updating the raspberry in the hope that this would fix things. I have no router access; I assumed – as SSH and VPN tunnels are working – that the configuration here is okay. But I don't know how I could possibly verify that. Is it technically possible that the router forwards the tunnel correctly but prevents FTP from working? How? As you might have already guessed, I'm not an expert, so sorry if these are dumb questions – I just don't understand what is going on here.
– Jürgen
Apr 15 at 13:34
OpenVPN and FTP settings are identical (as they haven't changed). All I did was updating the raspberry in the hope that this would fix things. I have no router access; I assumed – as SSH and VPN tunnels are working – that the configuration here is okay. But I don't know how I could possibly verify that. Is it technically possible that the router forwards the tunnel correctly but prevents FTP from working? How? As you might have already guessed, I'm not an expert, so sorry if these are dumb questions – I just don't understand what is going on here.
– Jürgen
Apr 15 at 13:34
That would be difficult to answer. FTP is complicated than ssh. Without router access, your options are limited. You can try to run Wireshark/tcpdump and analyze the traffic, see if the connection is established, authentication is working, and so on. You will need to have good understanding of a working ftp session, and then if you see the issue is with Network (traffic is not making through), present it to your new service provider.
– Abu Zaid
Apr 15 at 16:34
That would be difficult to answer. FTP is complicated than ssh. Without router access, your options are limited. You can try to run Wireshark/tcpdump and analyze the traffic, see if the connection is established, authentication is working, and so on. You will need to have good understanding of a working ftp session, and then if you see the issue is with Network (traffic is not making through), present it to your new service provider.
– Abu Zaid
Apr 15 at 16:34
|
show 1 more comment
1 Answer
1
active
oldest
votes
The problem that happens sometime is the following: say that:
Site A's LAN is 192.168.1.x and
RaspberryPi's LAN address is 192.168.1.10
Time clock's LAN address is 192.168.1.11
Now RaspberryPi hands out OpenVPN addresses to it's clients (site B, say using 10.1.2.0) so:
SiteB's client has 10.1.2.5 and RaspberryPi itself is set as a server as 10.1.2.1
What happens now is that RaspberryPi routes the 10.1.2.0 traffic to 192.168.1.0 network allowing you to access the time clock. So far so good (i assume this was never touched). This 192.168 traffic is then handled by the LAN router to reach the time clock.
The problem happens when the LAN router sometimes see the packets as coming from RaspberryPi's 10.1.2.0 address instead of 192.168.1.10 address. So, it sends the packet to the time-clock but the responses are routed to the regular Internet gateway instead.
The solution for that is to have a static route on the LAN router which sets RaspberryPi 192.168.1.10. as the gateway for all 10.1.2.0 traffic.
The other solution which i hate to suggest is to setup an open VPN client on the time clock that connects to the RaspberryPi bypassing the LAN router issues altogether.
answered Apr 17 at 18:17
ElkadyElkady
1263
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
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
);
);
Jürgen is a new contributor. Be nice, and check out our Code of Conduct.
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%2fserverfault.com%2fquestions%2f963060%2fcant-transfer-files-via-ftp-through-vpn-after-switch-to-new-router-with-identi%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The problem that happens sometime is the following: say that:
Site A's LAN is 192.168.1.x and
RaspberryPi's LAN address is 192.168.1.10
Time clock's LAN address is 192.168.1.11
Now RaspberryPi hands out OpenVPN addresses to it's clients (site B, say using 10.1.2.0) so:
SiteB's client has 10.1.2.5 and RaspberryPi itself is set as a server as 10.1.2.1
What happens now is that RaspberryPi routes the 10.1.2.0 traffic to 192.168.1.0 network allowing you to access the time clock. So far so good (i assume this was never touched). This 192.168 traffic is then handled by the LAN router to reach the time clock.
The problem happens when the LAN router sometimes see the packets as coming from RaspberryPi's 10.1.2.0 address instead of 192.168.1.10 address. So, it sends the packet to the time-clock but the responses are routed to the regular Internet gateway instead.
The solution for that is to have a static route on the LAN router which sets RaspberryPi 192.168.1.10. as the gateway for all 10.1.2.0 traffic.
The other solution which i hate to suggest is to setup an open VPN client on the time clock that connects to the RaspberryPi bypassing the LAN router issues altogether.
answered Apr 17 at 18:17
ElkadyElkady
1263
add a comment |
The problem that happens sometime is the following: say that:
Site A's LAN is 192.168.1.x and
RaspberryPi's LAN address is 192.168.1.10
Time clock's LAN address is 192.168.1.11
Now RaspberryPi hands out OpenVPN addresses to it's clients (site B, say using 10.1.2.0) so:
SiteB's client has 10.1.2.5 and RaspberryPi itself is set as a server as 10.1.2.1
What happens now is that RaspberryPi routes the 10.1.2.0 traffic to 192.168.1.0 network allowing you to access the time clock. So far so good (i assume this was never touched). This 192.168 traffic is then handled by the LAN router to reach the time clock.
The problem happens when the LAN router sometimes see the packets as coming from RaspberryPi's 10.1.2.0 address instead of 192.168.1.10 address. So, it sends the packet to the time-clock but the responses are routed to the regular Internet gateway instead.
The solution for that is to have a static route on the LAN router which sets RaspberryPi 192.168.1.10. as the gateway for all 10.1.2.0 traffic.
The other solution which i hate to suggest is to setup an open VPN client on the time clock that connects to the RaspberryPi bypassing the LAN router issues altogether.
answered Apr 17 at 18:17
ElkadyElkady
1263
add a comment |
The problem that happens sometime is the following: say that:
Site A's LAN is 192.168.1.x and
RaspberryPi's LAN address is 192.168.1.10
Time clock's LAN address is 192.168.1.11
Now RaspberryPi hands out OpenVPN addresses to it's clients (site B, say using 10.1.2.0) so:
SiteB's client has 10.1.2.5 and RaspberryPi itself is set as a server as 10.1.2.1
What happens now is that RaspberryPi routes the 10.1.2.0 traffic to 192.168.1.0 network allowing you to access the time clock. So far so good (i assume this was never touched). This 192.168 traffic is then handled by the LAN router to reach the time clock.
The problem happens when the LAN router sometimes see the packets as coming from RaspberryPi's 10.1.2.0 address instead of 192.168.1.10 address. So, it sends the packet to the time-clock but the responses are routed to the regular Internet gateway instead.
The solution for that is to have a static route on the LAN router which sets RaspberryPi 192.168.1.10. as the gateway for all 10.1.2.0 traffic.
The other solution which i hate to suggest is to setup an open VPN client on the time clock that connects to the RaspberryPi bypassing the LAN router issues altogether.
answered Apr 17 at 18:17
ElkadyElkady
1263
The problem that happens sometime is the following: say that:
Site A's LAN is 192.168.1.x and
RaspberryPi's LAN address is 192.168.1.10
Time clock's LAN address is 192.168.1.11
Now RaspberryPi hands out OpenVPN addresses to it's clients (site B, say using 10.1.2.0) so:
SiteB's client has 10.1.2.5 and RaspberryPi itself is set as a server as 10.1.2.1
What happens now is that RaspberryPi routes the 10.1.2.0 traffic to 192.168.1.0 network allowing you to access the time clock. So far so good (i assume this was never touched). This 192.168 traffic is then handled by the LAN router to reach the time clock.
The problem happens when the LAN router sometimes see the packets as coming from RaspberryPi's 10.1.2.0 address instead of 192.168.1.10 address. So, it sends the packet to the time-clock but the responses are routed to the regular Internet gateway instead.
The solution for that is to have a static route on the LAN router which sets RaspberryPi 192.168.1.10. as the gateway for all 10.1.2.0 traffic.
The other solution which i hate to suggest is to setup an open VPN client on the time clock that connects to the RaspberryPi bypassing the LAN router issues altogether.
answered Apr 17 at 18:17
ElkadyElkady
1263
answered Apr 17 at 18:17
ElkadyElkady
1263
answered Apr 17 at 18:17
ElkadyElkady
1263
answered Apr 17 at 18:17
ElkadyElkady
1263
1263
add a comment |
add a comment |
Jürgen is a new contributor. Be nice, and check out our Code of Conduct.
Jürgen is a new contributor. Be nice, and check out our Code of Conduct.
Jürgen is a new contributor. Be nice, and check out our Code of Conduct.
Jürgen is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f963060%2fcant-transfer-files-via-ftp-through-vpn-after-switch-to-new-router-with-identi%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
The new router, contrary to the claims made, is almost certainly not setup identically to the old one. Have the ISP, or whoever did the setup and made the false claim, to fix it.
– womble♦
Apr 15 at 6:45
But how can FTP be blocked if the tunnel is otherwise working? I just don't get my head around that.
– Jürgen
Apr 15 at 8:13
1
The information you have provided is not enough to troubleshoot the issue. If it was working before, and not working now, there must be something that changed. Comparing the new settings with old one would be the first step to start troubleshooting.
– Abu Zaid
Apr 15 at 10:29
OpenVPN and FTP settings are identical (as they haven't changed). All I did was updating the raspberry in the hope that this would fix things. I have no router access; I assumed – as SSH and VPN tunnels are working – that the configuration here is okay. But I don't know how I could possibly verify that. Is it technically possible that the router forwards the tunnel correctly but prevents FTP from working? How? As you might have already guessed, I'm not an expert, so sorry if these are dumb questions – I just don't understand what is going on here.
– Jürgen
Apr 15 at 13:34
That would be difficult to answer. FTP is complicated than ssh. Without router access, your options are limited. You can try to run Wireshark/tcpdump and analyze the traffic, see if the connection is established, authentication is working, and so on. You will need to have good understanding of a working ftp session, and then if you see the issue is with Network (traffic is not making through), present it to your new service provider.
– Abu Zaid
Apr 15 at 16:34