Forum Home
Press F1
 
Thread ID: 138935 2015-02-12 18:10:00 VDSL modem/router suggestions please Tony (4941) Press F1
Post ID Timestamp Content User
1394259 2015-02-20 13:54:00 I'm not a network expert by a long shot, but would increasing the lease time setting in the router stop that? Or should it already be long enough to prevent this and the router is playing silly buggers. (lease time is how long the router reserves an allocated IP address for a particular device as I understand it)

My Asus router defaults to a fairly long lease time of several days and devices tend to keep the same address through modem resets, internet crashes, pc restarts, etc. In fact when I look at the network map it shows connected devices from months back as still being there unless I do a refresh.

I used to manually set IP adresses for everything but I find using DHCP is easier when it's working right, saves having to reset everything if I connect to a different network or router or whatever.

Indeed, when it works right, it's fantastic.
When routers keep crashing, it's not so much.

Unfortunately changing the lease time won't fix this, and on some routers it's not even possible (Or buried under an abysmal interface like the Technicolor routers).

We've given Tony a "bandaid" as it work, not addressing the cause of the issue, but enough to fix it at least to save some sanity I would hope. Could do it for all the other devices if you really wanted, but I suspect they don't get used quite as much as your primary computer? ;)
Chilling_Silence (9)
1394260 2015-02-23 21:29:00 Still having problems. :angry. The setup is totally unreliable. It will be OK for a while, then stop. Sometimes I can kick-start it by disabling/enabling the network adapter, sometimes not. Rebooting the router usually starts everything up, but not necessarily for very long.

If ping the router I get a response (not surprising). If I ping past the router (8.8.8.8) the results are mixed. If I do the standard 4 pings, it will either work, give me "destination unreachable", or a timeout, or some combination. For instance it may return one value, then 2 unreachable and one timeout. I have found that if it's working and I do continuous pings (ping 8.8.8.8 -t) then it will stay up for as long as the pings continue. Once I interrupt the pings it goes back to the usual unpredictable state.

I've located another VDSL modem to borrow, so it will be interesting to see how that goes. It is the Spark free one that a neighbour doesn't use any more.

Aaaaaargh!
Tony (4941)
1394261 2015-02-23 21:56:00 That sounds like the Zyxel is playing up *terribly*!!
Ensure you're lodging this with your ISP immediately in case you need to pursue a refund for the router.
Chilling_Silence (9)
1394262 2015-02-23 22:04:00 Hang on that reminds me of a router I used back in the day at a customers, like years back. It was something screwy going on like with the state table filling up or whatever, so existing connections would stay up but nothing knew would work... Cached DNS would still resolve, pings would work, skype calls would carry on, but opening a new page in the browser would just go "Nup, not interested, I'm going to sulk in the corner" sorta thing.

Definitely lodge that with your ISP, they may suggest a firmware upgrade.
Chilling_Silence (9)
1394263 2015-02-23 22:14:00 Hang on that reminds me of a router I used back in the day at a customers, like years back . It was something screwy going on like with the state table filling up or whatever, so existing connections would stay up but nothing knew would work . . . Cached DNS would still resolve, pings would work, skype calls would carry on, but opening a new page in the browser would just go "Nup, not interested, I'm going to sulk in the corner" sorta thing .

Definitely lodge that with your ISP, they may suggest a firmware upgrade . I've been spending a lot of time with the Actrix helpdesk; they definitely know what's going on . Yesterday we did discuss the possibility of a dodgy router which is why I'm going to be trying the loaner from Spark . I've also already upgraded the firmware, to no avail .

We also discussed the possibility of a dodgy line, but I'm less and less convinced that is the issue . The reason it was raised is that I used to get a similar issue very occasionally on ADSL, and also I have occasionally had the phone giving random rings during/after bad weather . I'm avoiding that route if I can as I don't want to end up paying $150 to Chorus if they don't find an issue .

I should have the loaner router this evening .
Tony (4941)
1394264 2015-02-23 23:32:00 Interesting (again). My landline has totally died. No dial tone. Now waiting for Chorus to check that out. Maybe they'll fix everything (yeah, right).

VDSL is going though atm.
Tony (4941)
1394265 2015-02-24 20:17:00 OK, got my landline back this morning.

Can't tell yet whether the VDSL is fixed.

I borrowed a Telecom Thomson TG589vn modem to see what would happen. It appears that it won't let me log on to Actrix - gives me a "not allowed" error message. Any ideas how I can get around that?

With the Zyxel router I have found that if I set a continuous ping the connection stays up. I had it going for about 3 hours last evening. When I terminated it I lost the connection within about 20 minutes.
Tony (4941)
1394266 2015-02-25 05:09:00 Sounds like the Zyxel was getting bored and disconnecting due to inactivity perhaps? Not a common thing these days, it *ought* to stay on permanently, but I don't really like the Zyxel routers so have very little first-hand experience as a result.

The URL in your address bar when you get "Not allowed", what is that? Is it the router telling you that ?
Chilling_Silence (9)
1394267 2015-02-25 08:03:00 Sounds like the Zyxel was getting bored and disconnecting due to inactivity perhaps? Not a common thing these days, it *ought* to stay on permanently, but I don't really like the Zyxel routers so have very little first-hand experience as a result.

The URL in your address bar when you get "Not allowed", what is that? Is it the router telling you that ?I'm sure you are right about the router going to sleep. There is an idle timeout parameter that was at 5 minutes and I reset to 30 and I've now set to 120 minutes, so we'll see what difference that makes. The only thing is I can only change the idle timeout if I change the PPP trigger type from "auto" to "on demand" (see screenshot). If it is auto then it seems to default to 5 mins. I have no idea of the implications of that - whether I'd be better off with auto or better off with a longer idle timeout.

6237

I'll have to re-attach the telecom router to answer the second question - tomorrow.
Tony (4941)
1394268 2015-02-25 08:58:00 Change it to 0 and see what happens. Alex B (15479)
1 2 3 4 5 6 7 8