You should always re-flash the modems your own, I assumed that. Don't touch their stuff. It is essential that you know the network settings of the network you are on, things like the VPI/VCI  (DSL) for the region you are in, connection type, etc., so that you can configure dd-wrt afterwards correctly.  You don't always see the VPI/VCI  in the old proprietary firmware as it maybe hidden (as far as I remember), but you need it anyhow and it has to be the right value. You can look it up at Internet or you can get it from your provider.  There is no reason why a provider would refuse a modem with dd-wrt in it and I never experienced it with several providers in the Toronto area, but you need the right network parameters.

Bob.  

Yes, some cable and DSL modems can be flashed with did-wrt or even openwrt, but before you try, check to see if your provider will allow it. I’m in Canada and even if I own the modem, they will not support it. It will essentially brick the modem because the providers use a proprietary version of the software and it’s not possible to reinstall it once changed. You end up having to buy a new modem. 

I’m not trying to scare you off doing this. Just make sure first. A simple phone call to the providers tech support. 

Roger

VA7LBB 

On Sep 28, 2022, at 13:42, Boudewijn (Bob) Tenty via 44net <44net@mailman.ampr.org> wrote:

 Yes, it will work if dd-wrt is available for the chip-set in it, so you have to flash it with the right version.
It is the first thing I  do if I receive such a modem, re-flash it with dd-wrt if that is not in it. There is
a good change that nowadays dd-wrt is already in it with new modems.  At least, that is what I see here.

Bob

On 2022-09-28 16:08, Lee D Bengston wrote:

Not sure if that will work if the router is also a cable-modem or DSL-modem.

On Wed, Sep 28, 2022, 2:49 PM Boudewijn (Bob) Tenty via 44net <44net@mailman.ampr.org> wrote:

Just flash your router with dd-wrt if it can't pass ipip and the problem is solved.

Bob


On 2022-09-28 14:33, Rob PE1CHL via 44net wrote:
> There is nothing special to do, except that you need to make sure that incoming protocol-4
> traffic on your internet connection arrives at your gateway system.  And with modern internet
> routers as supplied by providers that is often impossible.  You often can forward TCP and UDP
> ports only, not protocols.  And when there is a "DMZ" setting that promises to forward all
> unsolicited incoming traffic to a specified host, more and more often it handles only TCP and UDP
> traffic.
> It can be deceiving that the router often passes replies to outgoing protocol-4 traffic as part
> of its standard NAT function.  That is not enough.  It needs to pass unsolicited incoming traffic
> or else you will not see the RIP packets.
>
> Rob
>
> On 9/28/22 20:24, David Ranch via 44net wrote:
>> Hey Chris, Marius,
>>
>> Ok, thank you for the correction though I clearly remember that "something" additional was required before RIP updates would start flowing over the IPIP tunnel other than the user just defining their gateway IP address for the IPIP tunnel endpoint.  What is "that".
>>
>> --David
>> KI6ZHD
> _______________________________________________
> 44net mailing list -- 44net@mailman.ampr.org
> To unsubscribe send an email to 44net-leave@mailman.ampr.org

--
There is nothing permanent except change
 -Heraclitus

_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org

-- 
There is nothing permanent except change
 
-Heraclitus

_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org

-- 
There is nothing permanent except change
 
-Heraclitus