Dlink DSL-300G+ DHCP Server query

Has anybody managed to change the default lease time from the 20
second default?

My SonicWall SoHo2 keeps shutting down randomly because it
cannot find the DHCP server.

Have tried changing it using the console, but no joy. It gives no
error but makes no changes.

Rick...

On Fri, 06 Feb 2004 02:25:06 -0600, Rick wrote:

> Has anybody managed to change the default lease time from the 20
> second default?

No, you cannot.

> My SonicWall SoHo2 keeps shutting down randomly because it
> cannot find the DHCP server.
>
> Have tried changing it using the console, but no joy. It gives no
> error but makes no changes.

Indeed. Report it as a bug to Dlink and they might fix it, if enough
of us do.

JAB.

--
Jonathan A. Buzzard Email: jonathan (at) buzzard.me.uk
Northumberland, United Kingdom. Tel: +44 1661-832195

"Rick" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Has anybody managed to change the default lease time from the 20
> second default?
>
> My SonicWall SoHo2 keeps shutting down randomly because it
> cannot find the DHCP server.
>
> Have tried changing it using the console, but no joy. It gives no
> error but makes no changes.
>

You've managed to use the console port???? GIVE DETAILS PLEASE!!!!!!

As for the DHCP leasetime, I took it up with my ISP who (after some to-ing
and fro-ing) suggested I take it up with the manufacturer. I've taken this
up with D-Link about 6 weeks ago.... talked to "tech support" who were going
to investigate it and, if necessary, get me to return the kit... still no
reply!
Incidentally, I re-flashed the Modem with the latest firmware from the
D-Link webby, still no joy!
--
(E-Mail Removed)
Replace the dots and remove nospam for valid email address

On Fri, 6 Feb 2004 09:44:05 -0000, "Paul King"
<(E-Mail Removed)> wrote:

>"Rick" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> Has anybody managed to change the default lease time from the 20
>> second default?
>>
>> My SonicWall SoHo2 keeps shutting down randomly because it
>> cannot find the DHCP server.
>>
>> Have tried changing it using the console, but no joy. It gives no
>> error but makes no changes.
>>
>
>You've managed to use the console port???? GIVE DETAILS PLEASE!!!!!!
>
>As for the DHCP leasetime, I took it up with my ISP who (after some to-ing
>and fro-ing) suggested I take it up with the manufacturer. I've taken this
>up with D-Link about 6 weeks ago.... talked to "tech support" who were going
>to investigate it and, if necessary, get me to return the kit... still no
>reply!
>Incidentally, I re-flashed the Modem with the latest firmware from the
>D-Link webby, still no joy!

Sorry, I should have made myself clearer wrt the console port.
I actually telnetted onto the modem and used the default password
of private.

Have you seen the command set that should be available to us?
If not do a search for "ATMOS Console Commands Reference Manual"
Quite enlightening.

Will call D-Link and complain about their crappy implementation of
ATMOS.

Rick...

Rick <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Fri, 6 Feb 2004 09:44:05 -0000, "Paul King"
> <(E-Mail Removed)> wrote:
>
>
> Sorry, I should have made myself clearer wrt the console port.
> I actually telnetted onto the modem and used the default password
> of private.
>
> Have you seen the command set that should be available to us?
> If not do a search for "ATMOS Console Commands Reference Manual"
> Quite enlightening.
>
> Will call D-Link and complain about their crappy implementation of
> ATMOS.
>

I've got the Ref Manual - but I also noticed in those links on google other
stuff about telnetting to a 604 router by frigging the flash firmware and
re-loading it. Is this what you did, or have you got better instructions on
how to telnet to the 300G+ ?

On Fri, 6 Feb 2004 21:08:24 -0000, "Paul King"
<(E-Mail Removed)> wrote:

>Rick <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> On Fri, 6 Feb 2004 09:44:05 -0000, "Paul King"
>> <(E-Mail Removed)> wrote:
>>
>>
>> Sorry, I should have made myself clearer wrt the console port.
>> I actually telnetted onto the modem and used the default password
>> of private.
>>
>> Have you seen the command set that should be available to us?
>> If not do a search for "ATMOS Console Commands Reference Manual"
>> Quite enlightening.
>>
>> Will call D-Link and complain about their crappy implementation of
>> ATMOS.
>>
>
>I've got the Ref Manual - but I also noticed in those links on google other
>stuff about telnetting to a 604 router by frigging the flash firmware and
>re-loading it. Is this what you did, or have you got better instructions on
>how to telnet to the 300G+ ?
After my experience with a D-Link 504 router the best thing to do with
any D-Link product is to pick it up manually and throw it in the bin .
Grant .

On Fri, 6 Feb 2004 21:08:24 -0000, "Paul King"
<(E-Mail Removed)> wrote:

>Rick <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> On Fri, 6 Feb 2004 09:44:05 -0000, "Paul King"
>> <(E-Mail Removed)> wrote:
>>
>>
>> Sorry, I should have made myself clearer wrt the console port.
>> I actually telnetted onto the modem and used the default password
>> of private.
>>
>> Have you seen the command set that should be available to us?
>> If not do a search for "ATMOS Console Commands Reference Manual"
>> Quite enlightening.
>>
>> Will call D-Link and complain about their crappy implementation of
>> ATMOS.
>>
>
>I've got the Ref Manual - but I also noticed in those links on google other
>stuff about telnetting to a 604 router by frigging the flash firmware and
>re-loading it. Is this what you did, or have you got better instructions on
>how to telnet to the 300G+ ?
>
All I did was to telnet to 192.168.0.1 and when asked for the
password, enter "private"
The prompt then changed to 192.168.0.1> and I was in....

However the dhcp server on the modem is a pile of poo.

Session as follows....


192.168.0.1> dhcpserver
192.168.0.1 dhcpserver>
192.168.0.1 dhcpserver> dump
-------------------- DHCP POOL -------------------
*** Dynamic Pool ***
[1] IP=192.168.0.2 MAC=00-40-10-0f-a2-84 lease=0 seconds
satus=DHCPFREE
[2] IP=192.168.0.3 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[3] IP=192.168.0.4 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[4] IP=192.168.0.5 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[5] IP=192.168.0.6 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[6] IP=192.168.0.7 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[7] IP=192.168.0.8 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[8] IP=192.168.0.9 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[9] IP=192.168.0.10 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[10] IP=192.168.0.11 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[11] IP=192.168.0.12 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[12] IP=192.168.0.13 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[13] IP=192.168.0.14 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[14] IP=192.168.0.15 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[15] IP=192.168.0.16 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[16] IP=192.168.0.17 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[17] IP=192.168.0.18 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[18] IP=192.168.0.19 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[19] IP=192.168.0.20 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
[20] IP=192.168.0.21 MAC=00-00-00-00-00-00 lease=0 seconds
satus=DHCPFREE
*** Static Pool ***
[1] IP=81.178.225.15 MAC=00-40-10-0f-a2-84 state= 1
[2] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[3] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[4] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[5] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[6] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[7] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[8] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[9] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[10] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[11] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[12] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[13] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[14] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[15] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[16] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[17] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[18] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[19] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
[20] IP=0.0.0.0 MAC=00-00-00-00-00-00 state= 0
*** Static Pool ***
[1] IP=81.178.225.15 MAC=00-40-10-0f-a2-84 lease=20 seconds
satus=DHCPACK
[2] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[3] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[4] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[5] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[6] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[7] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[8] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[9] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[10] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[11] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[12] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[13] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[14] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[15] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[16] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[17] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[18] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[19] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
[20] IP=0.0.0.0 MAC=00-00-00-00-00-00 lease=INFINITY satus=DHCPFREE
-----------------------------------------------------
192.168.0.1 dhcpserver>


I have been unable to change the static dhcp lease time from the 20
second default.

Rick...

On Fri, 6 Feb 2004 21:08:24 -0000, "Paul King"
<(E-Mail Removed)> wrote:

>Rick <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> On Fri, 6 Feb 2004 09:44:05 -0000, "Paul King"
>> <(E-Mail Removed)> wrote:
>>
>>
>> Sorry, I should have made myself clearer wrt the console port.
>> I actually telnetted onto the modem and used the default password
>> of private.
>>
>> Have you seen the command set that should be available to us?
>> If not do a search for "ATMOS Console Commands Reference Manual"
>> Quite enlightening.
>>
>> Will call D-Link and complain about their crappy implementation of
>> ATMOS.
>>
>
>I've got the Ref Manual - but I also noticed in those links on google other
>stuff about telnetting to a 604 router by frigging the flash firmware and
>re-loading it. Is this what you did, or have you got better instructions on
>how to telnet to the 300G+ ?
>

Just managed to get the following..

logged on; type `@close' to close connection.
192.168.0.1> event p
------ Head of event buffer ------
192.168.0.1> event n
------ Head of event buffer ------
All profile data are reset to default values!
globespan: bad keyword in data file
globespan: bad keyword in data file
globespan: bad keyword in data file
globespan: bad keyword in data file
globespan: bad keyword in data file
globespan: bad keyword in data file
globespan: bad keyword in data file
globespan: bad keyword in data file
globespan: bad keyword in data file
globespan: bad keyword in data file
Line length in profile exceed 255 characters
ppp: 5: 1: Reading saved line
Primary IP: 192.168.0.1
DHCP packet receive to WAN port
DHCP: Receive DHCPREQUEST packet
DHCP: send DHCP NAK!
DHCP: DHCPNAK
Error: trying to send to UDP client
DHCP packet receive to WAN port
DHCP: Receive DHCPREQUEST packet
DHCP: send DHCP NAK!
DHCP: DHCPNAK
Error: trying to send to UDP client
192.168.0.1>


Don't know enough about atmos to understand it, but I suspect that
there is an error in the config somewhere.
I have been looking at the configs in the flashfs system, but found
nothing .

Any suggestions?

Rick wrote:
[snip]

> Any suggestions?

This is what I get:

192.168.0.1> flashfs
192.168.0.1 flashfs> config
Flash configuration: 2 chips
Chip 0 size 1048576 @ 0xc4000000
Chip 0 ID is 45b: (FUJITSU 29LV800BA 1024k bytes), unlocked (0)
Chip 1 size 1048576 @ 0xc4100000
Chip 1 ID is ffff: (UNKNOWN ? 0k bytes), unlocked (0) MISCONFIGURED SIZE
Flash start offset: 0x00020000
Space for all FLASHFS partitions: 0x001e0000

And on the dhcp server

192.168.0.1> dhcpserver
192.168.0.1 dhcpserver> help all
test test
time time <dynamic renew time> <static renew time>
dump dump dhcp pool

Having just got one of these modems myself, I'm frustrated to say the
least. My log files are filled with useless garbage about renew/release etc.

I know zilch about the subject but this list appears to suggest that you
can change renew times? Having tried a few combinations around time 5000
5000 etc, it appears to have no effect at all. Dusty bin awaits, I guess.



Fish

On Sun, 08 Feb 2004 13:02:59 +0000, Fish <(E-Mail Removed)> wrote:

>Rick wrote:
>[snip]
>
>> Any suggestions?
>
>This is what I get:
>
>192.168.0.1> flashfs
>192.168.0.1 flashfs> config
>Flash configuration: 2 chips
>Chip 0 size 1048576 @ 0xc4000000
>Chip 0 ID is 45b: (FUJITSU 29LV800BA 1024k bytes), unlocked (0)
>Chip 1 size 1048576 @ 0xc4100000
>Chip 1 ID is ffff: (UNKNOWN ? 0k bytes), unlocked (0) MISCONFIGURED SIZE
>Flash start offset: 0x00020000
>Space for all FLASHFS partitions: 0x001e0000
>
>And on the dhcp server
>
>192.168.0.1> dhcpserver
>192.168.0.1 dhcpserver> help all
>test test
>time time <dynamic renew time> <static renew time>
>dump dump dhcp pool
>
>Having just got one of these modems myself, I'm frustrated to say the
>least. My log files are filled with useless garbage about renew/release etc.
>
>I know zilch about the subject but this list appears to suggest that you
>can change renew times? Having tried a few combinations around time 5000
>5000 etc, it appears to have no effect at all. Dusty bin awaits, I guess.
>
>
>
>Fish

Yup, I get the same as you. I hadn't noticed that before.

If you change the renew times in the dhcpserver section, it seems to
accept it, but nothing is changed. It still has that crazy 20 second
renew time.

It looks as if there is a serious problem with these modems.

D-Link don't seem interested in fixing it.
My modem was bought second hand, so I am well and truly knackered...

If you have recently bought it, I would take it back for a refund.

Rick....