VB104W Modem/Router Thread

Forums › Slingshot and CallPlus › VB104W Modem/Router Thread

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17

6 posts

Wannabe Geek

Reply # 984114 11-Feb-2014 14:00

hio77:
ibman9215:
chevrolux: You just need to use a non-standard port.
Have a look in 'Management' then 'Access Controls' then 'Remote Access Control List'

The router catches traffic on all those ports. You can't change them so you will have to use a non-standard port to connect to your FTP server.

I've done that using port 1701, still gives the same "Server returned unroutable private IP address in PASV reply" response. Any other ideas?

that reads, as your ftp server is handing out the PASV response, with a private ip. this would indicate a miss configuration in the server itself.. although i would have expected it to be a little more smart about it.

From What I can see, you're right. However, what I'm left wondering is 1. Back when I was on ADSL and used a D-Link modem, everything worked fine, which makes me think the problem is modem related (possibly something to do with NAT), and 2. I'm not sure how to correct it, or even if I can because the FTP server is run by one of Linksys smart wifi routers, which have very basic configuration options.

hio77

'That VDSL Cat'
9922 posts

Uber Geek
+1 received by user: 2323

Trusted

Spark

Subscriber

Reply # 984117 11-Feb-2014 14:06

ibman9215:
hio77:
ibman9215:
chevrolux: You just need to use a non-standard port.
Have a look in 'Management' then 'Access Controls' then 'Remote Access Control List'

The router catches traffic on all those ports. You can't change them so you will have to use a non-standard port to connect to your FTP server.

I've done that using port 1701, still gives the same "Server returned unroutable private IP address in PASV reply" response. Any other ideas?

that reads, as your ftp server is handing out the PASV response, with a private ip. this would indicate a miss configuration in the server itself.. although i would have expected it to be a little more smart about it.

From What I can see, you're right. However, what I'm left wondering is 1. Back when I was on ADSL and used a D-Link modem, everything worked fine, which makes me think the problem is modem related (possibly something to do with NAT), and 2. I'm not sure how to correct it, or even if I can because the FTP server is run by one of Linksys smart wifi routers, which have very basic configuration options.

what server are you using?

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

ibman9215

6 posts

Wannabe Geek

Reply # 984122 11-Feb-2014 14:14

hio77:
ibman9215:
hio77:
ibman9215:
chevrolux: You just need to use a non-standard port.
Have a look in 'Management' then 'Access Controls' then 'Remote Access Control List'

The router catches traffic on all those ports. You can't change them so you will have to use a non-standard port to connect to your FTP server.

I've done that using port 1701, still gives the same "Server returned unroutable private IP address in PASV reply" response. Any other ideas?

that reads, as your ftp server is handing out the PASV response, with a private ip. this would indicate a miss configuration in the server itself.. although i would have expected it to be a little more smart about it.

From What I can see, you're right. However, what I'm left wondering is 1. Back when I was on ADSL and used a D-Link modem, everything worked fine, which makes me think the problem is modem related (possibly something to do with NAT), and 2. I'm not sure how to correct it, or even if I can because the FTP server is run by one of Linksys smart wifi routers, which have very basic configuration options.

what server are you using?

The FTP is run by my Linksys EA6500 router.

hio77

'That VDSL Cat'
9922 posts

Uber Geek
+1 received by user: 2323

Trusted

Spark

Subscriber

Reply # 984138 11-Feb-2014 14:26

ibman9215:
hio77:
ibman9215:
hio77:
ibman9215:
chevrolux: You just need to use a non-standard port.
Have a look in 'Management' then 'Access Controls' then 'Remote Access Control List'

The router catches traffic on all those ports. You can't change them so you will have to use a non-standard port to connect to your FTP server.

I've done that using port 1701, still gives the same "Server returned unroutable private IP address in PASV reply" response. Any other ideas?

that reads, as your ftp server is handing out the PASV response, with a private ip. this would indicate a miss configuration in the server itself.. although i would have expected it to be a little more smart about it.

From What I can see, you're right. However, what I'm left wondering is 1. Back when I was on ADSL and used a D-Link modem, everything worked fine, which makes me think the problem is modem related (possibly something to do with NAT), and 2. I'm not sure how to correct it, or even if I can because the FTP server is run by one of Linksys smart wifi routers, which have very basic configuration options.

what server are you using?

The FTP is run by my Linksys EA6500 router.

ah. check around for ip detection methods..

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

ibman9215

6 posts

Wannabe Geek

Reply # 984179 11-Feb-2014 15:10

hio77:
ibman9215:
hio77:
ibman9215:
hio77:
ibman9215:
chevrolux: You just need to use a non-standard port.
Have a look in 'Management' then 'Access Controls' then 'Remote Access Control List'

The router catches traffic on all those ports. You can't change them so you will have to use a non-standard port to connect to your FTP server.

I've done that using port 1701, still gives the same "Server returned unroutable private IP address in PASV reply" response. Any other ideas?

that reads, as your ftp server is handing out the PASV response, with a private ip. this would indicate a miss configuration in the server itself.. although i would have expected it to be a little more smart about it.

From What I can see, you're right. However, what I'm left wondering is 1. Back when I was on ADSL and used a D-Link modem, everything worked fine, which makes me think the problem is modem related (possibly something to do with NAT), and 2. I'm not sure how to correct it, or even if I can because the FTP server is run by one of Linksys smart wifi routers, which have very basic configuration options.

what server are you using?

The FTP is run by my Linksys EA6500 router.

ah. check around for ip detection methods..

I think the problem may be the VB104W isn't translating the LAN IP to the WAN IP, therefore causing the Unroutable Private IP. I just need to figure out how to configure it to do that,

hio77

'That VDSL Cat'
9922 posts

Uber Geek
+1 received by user: 2323

Trusted

Spark

Subscriber

Reply # 984183 11-Feb-2014 15:16

yes, exactly what im getting at.

i havent used very many router ftp servers though, so directing you to the option might be a bit hard...

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

Countryman98

9 posts

Wannabe Geek
+1 received by user: 2

Reply # 984251 11-Feb-2014 16:25

There is currently an updated firmware for the VB104W in Beta testing that will address the port forwarding and some of the other bugs with the current firmware. I have heard that they hope to release it in the next few weeks.

chevrolux

3909 posts

Uber Geek
+1 received by user: 1624

Subscriber

Reply # 984288 11-Feb-2014 16:58

One person supports this post

Linksys EA6500 router.

There's your problem. Throw it away and get a NAS lol. They are the most terrible things... in the world (said in your best Jeremy Clarkson voice).

chevrolux

3909 posts

Uber Geek
+1 received by user: 1624

Subscriber

Reply # 984289 11-Feb-2014 16:58

Linksys EA6500 router.

There's your problem. Throw it away and get a NAS lol. They are the most terrible things... in the world (said in your best Jeremy Clarkson voice).

NZCrusader

646 posts

Ultimate Geek
+1 received by user: 228

Reply # 984534 11-Feb-2014 21:20

One person supports this post

Countryman98: There is currently an updated firmware for the VB104W in Beta testing that will address the port forwarding and some of the other bugs with the current firmware. I have heard that they hope to release it in the next few weeks.

Would rather SS invest in fritz box. ;)

Btw anyone finding AUS traffic is very slow?

https://www.speedtest.net/my-result/3298039233

Perhaps SS need to purchase some more bandwidth?

NZ / AU Battlefield 4 Gaming Community
http://www.sonsofvalour.net/forums/forum.php

hamish225

1312 posts

Uber Geek
+1 received by user: 171

Reply # 984551 11-Feb-2014 21:48

NZCrusader:
Countryman98: There is currently an updated firmware for the VB104W in Beta testing that will address the port forwarding and some of the other bugs with the current firmware. I have heard that they hope to release it in the next few weeks.

Would rather SS invest in fritz box. ;)

Btw anyone finding AUS traffic is very slow?

https://www.speedtest.net/my-result/3298039233

Perhaps SS need to purchase some more bandwidth?

yeah mines slow too, thats weird. i usually get line speed.

fritz boxes cost way too much, i think snap charged like $400 for them, as opposed to $20 for the one slingshot have.

the modem being a cheap one doesn't at all justify its faults though, they should fix those with all haste.

Salad

10 posts

Wannabe Geek
+1 received by user: 1

Reply # 993242 24-Feb-2014 12:04

VDSL bridging with this modem.

Have tried and failed to get it to work. I've tried two different routers (one running Tomato, and a friends Asus running stock firmware). Neither can sign into the VB104W with PPPoE.

I hit the factory reset button and now it's bricked.

Serves me right for expecting the factory reset button to work on a modem that can't even forward ports.

alexcc

151 posts

Master Geek
+1 received by user: 17

Reply # 993250 24-Feb-2014 12:17

Salad: VDSL bridging with this modem.

Have tried and failed to get it to work. I've tried two different routers (one running Tomato, and a friends Asus running stock firmware). Neither can sign into the VB104W with PPPoE.

I hit the factory reset button and now it's bricked.

Serves me right for expecting the factory reset button to work on a modem that can't even forward ports.

Bridging works fine for me, got the modem connected to an Asus N66u right now.

hamish225

1312 posts

Uber Geek
+1 received by user: 171

Reply # 993253 24-Feb-2014 12:21

alexcc:
Salad: VDSL bridging with this modem.

Have tried and failed to get it to work. I've tried two different routers (one running Tomato, and a friends Asus running stock firmware). Neither can sign into the VB104W with PPPoE.

I hit the factory reset button and now it's bricked.

Serves me right for expecting the factory reset button to work on a modem that can't even forward ports.

Bridging works fine for me, got the modem connected to an Asus N66u right now.

if you bridge it to another router, does that mean things like firewall, port forwarding and dhcp are the responsibility of the other router? (is that a way to get port forwarding to work?)

shacknasty

29 posts

Geek
+1 received by user: 2

Reply # 993262 24-Feb-2014 12:36

Salad: VDSL bridging with this modem.

Have tried and failed to get it to work. I've tried two different routers (one running Tomato, and a friends Asus running stock firmware). Neither can sign into the VB104W with PPPoE.

I hit the factory reset button and now it's bricked.

Serves me right for expecting the factory reset button to work on a modem that can't even forward ports.

How bricked is it? I've had two of these modems now, and one of them resets the password to admin/admin instead of admin/macaddress on factory reset.

I've been following this thread for a fix/update to the port forwarding problem with these modems, haven't tried bridging but will give that a go today if that is an effective work around to the issue, which is getting pretty annoying (the only reason I wanted to upgrade to VDSL was for using plex remotely, which now doesnt work at all).

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17