Karlnet
[Top] [All Lists]

Re: [Karlnet] RE: Moderate Bug in Configurator 5 related toNATwithDHCP

To: "Karlnet Mailing List" <karlnet@WISPNotes.com>
Subject: Re: [Karlnet] RE: Moderate Bug in Configurator 5 related toNATwithDHCP
From: jna@tcpbbs.net
Reply-to: Karlnet Mailing List <karlnet@WISPNotes.com>
Date: Sat, 26 Jun 2004 02:57:30 -0500
List-post: <mailto:karlnet@WISPNotes.com>
What are you using to view the SNMP info like you have in that cap?

John

----- Original Message ----- 
From: "Caleb Carroll" <karlnet@pathcom.ca>
To: <karlnet@WISPNotes.com>
Cc: <support@karlnet.com>
Sent: Wednesday, June 23, 2004 3:54 PM
Subject: RE: [Karlnet] RE: Moderate Bug in Configurator 5 related toNAT
withDHCP


> Hi Ed,
>
> The problem that we are having is a real world problem.  We first noticed
this problem after upgrading our network to v4.45 firmware.  Some of our
customers turn off their KN-100's when they are not home or turn them off
overnight.  Because our IP address space is limited, when these customers
that turn their KN-100 back on, the KN-100 often recieves a different IP
address from what it had before it was switched off.  This shouldn't cause
any problems.  Without my "work-around" for this problem, the KN-100 will
have 2 IP addresses.  The first IP address is taken from the "Public IP
Address" field in the NAT setup.  The second IP address (the correct IP
address) is recieved from the DHCP server.  Again, this is all detailed at:
https://carroll.pathcom.ca/serials/Configurator445_bug.html
>
> *********** REPLY SEPARATOR  ***********
>
> On 2004-06-23 at 3:56 PM KarlNet Support wrote:
>
> >Caleb,
> >
> >I am sorry you feel the request is not being taken seriously. Your
comments
> >and feedback have always been important to us and we have always
performed
> >a
> >best effort to assist however we can.
> >
> >Please explain a few things to me please.
> >
> >1. What is the old IP and the new IP and exactly what is happening in
step
> >2
> >and how would this ever happen in a real world scenario?
> >
> >The way I understand it you are manually deleting the DHCP address on the
> >server side. How would the client know this has occurred? Also when you
say
> >you force the KBridge to get another assignment I assume you are
performing
> >this activity from the DHCP server? How is the new lease being created
and
> >what are the values for the lease?
> >
> >Forgive me if I am misunderstanding something. Thanks,
> >
> >
> >Ed
> >
> >KarlNet Technical Support
> >http://www.karlnet.com/Support/SupportKnowledgeBase.htm
> >614-822-5275
> >
> >-----Original Message-----
> >From: karlnet-bounces@WISPNotes.com
> >[mailto:karlnet-bounces@WISPNotes.com]On Behalf Of Caleb Carroll
> >Sent: Wednesday, June 23, 2004 1:38 PM
> >To: karlnet@WISPNotes.com
> >Subject: [Karlnet] RE: Moderate Bug in Configurator 5 related to NAT
> >withDHCP
> >
> >
> >
> >Is anyone going to take this seriously?  Is anyone going to fix this?
> >
> >*********** REPLY SEPARATOR  ***********
> >
> >On 2004-06-23 at 1:26 PM KarlNet Support wrote:
> >
> >>Caleb,
> >>
> >>I think there is a change being made here in the DHCP assignment. So if
> >the
> >>change is made and the save is recording it then the issue would be
there
> >>after reboot.
> >>
> >>Ed
> >>
> >>KarlNet Technical Support
> >>http://www.karlnet.com/Support/SupportKnowledgeBase.htm
> >>614-822-5275
> >>
> >>-----Original Message-----
> >>From: Caleb Carroll [mailto:karlnet@pathcom.ca]
> >>Sent: Wednesday, June 23, 2004 1:09 PM
> >>To: karlnet@WISPNotes.com
> >>Cc: support@karlnet.com
> >>Subject: RE: Moderate Bug in Configurator 5 related to NAT with DHCP
> >>
> >>
> >>Ed,
> >>
> >>Thanks for at least providing confirmation that your engineers
acknowledge
> >>the problem.  Do they have any idea of how to fix the problem?
> >>
> >>My line of thinking is that if you read a KN's configuration then save
the
> >>KN's configuration without making any changes then the configuration
after
> >>re-boot should be the same.
> >>
> >>Karlnet's NAT implementation is dodgy.  I can't think of any reason to
> >have
> >>the fields "Public IP Address" & "Public IP Mask" in either Incoming or
> >>Outgoing NAT setup if your Public IP address is DHCP assigned.
> >>
> >>*********** REPLY SEPARATOR  ***********
> >>
> >>On 2004-06-23 at 12:09 PM KarlNet Support wrote:
> >>
> >>>Caleb,
> >>>
> >>>OK after talking with the engineers they say this is the issue. In step
3
> >>>the Configuration is being changed, at this point the dual IP's are
> >>>actually
> >>>being saved to the unit. So when logging back in on step 4 you are
> >reading
> >>>the configuration with the dual IP information. I am sure it is
debatable
> >>>that the other IP should be removed, however once the dual IP situation
> >>has
> >>>been created, saving to the unit is guaranteeing the issue to be there
> >>upon
> >>>reboot. Have you tried rebooting it without performing a save? Does the
> >>>issue still occur?
> >>>
> >>>
> >>>
> >>>Ed
> >>>
> >>>KarlNet Technical Support
> >>>http://www.karlnet.com/Support/SupportKnowledgeBase.htm
> >>>614-822-5275
> >>>
> >>>-----Original Message-----
> >>>From: Caleb Carroll [mailto:karlnet@pathcom.ca]
> >>>Sent: Tuesday, June 22, 2004 4:30 PM
> >>>To: KarlNet Support
> >>>Subject: RE: Moderate Bug in Configurator 5 related to NAT with DHCP
> >>>
> >>>
> >>>Hi Ed,
> >>>
> >>>This is a fairly serious problem.  I understand what you are trying to
> >say
> >>>but you're barking up the wrong tree...  If you follow my instructions,
> >>>Step
> >>>#4 says "Open the configuration of the RG/KN"... This is exactly what
you
> >>>are suggesting I try to do to verify this (log in again).  So, Yes; the
> >>>problem remains after logging in again.
> >>>
> >>>I NEVER make a bug report unless I am 100% certain that there is a
> >>problem.
> >>>I am getting frustrated because every time I report something, your
> >>>engineers ask me to answer all sorts of ridiculous questions that have
no
> >
> >>>bearing whatsoever on the problem at hand.
> >>>
> >>>
> >>>*********** REPLY SEPARATOR  ***********
> >>>
> >>>On 2004-06-22 at 3:35 PM KarlNet Support wrote:
> >>>
> >>>>Caleb,
> >>>>
> >>>>If you do not login to the unit after making the change the
information
> >>>>will
> >>>>not be updated automatically as the configuration is only read from
the
> >>>>unit
> >>>>upon login. Try to login again and see if both IP addresses remain.
> >>>Thanks,
> >>>>
> >>>>Ed
> >>>>
> >>>>KarlNet Technical Support
> >>>>http://www.karlnet.com/Support/SupportKnowledgeBase.htm
> >>>>614-822-5275
> >>>>
> >>>>-----Original Message-----
> >>>>From: Caleb Carroll [mailto:karlnet@pathcom.ca]
> >>>>Sent: Wednesday, June 16, 2004 12:04 PM
> >>>>To: support@karlnet.com
> >>>>Subject: Moderate Bug in Configurator 5 related to NAT with DHCP
> >>>>
> >>>>
> >>>>
> >>>>Configurator 5.00-xxxx is retaining the Public IP Address & Public IP
> >>Mask
> >>>>settings when the IP Host is set to "Obtain an IP address from DHCP
> >>>>Server".
> >>>>
> >>>>The easiest way to demonstrate this problem is by following the steps
> >>>>outlined below:
> >>>>
> >>>>1) Use Configurator to open the configuration of a KN-100 or RG-1100
> >>>>2) On your DHCP server.  Delete the lease for your KN/RG and then
create
> >>a
> >>>>temporary lease reserve (force the KN or RG to grab a different IP
> >>>>address).
> >>>>3) Go back to Configurator - Don't make any configuration changes!
Just
> >>>>select "Save Config" from the file menu.
> >>>>4) Open the configuration of the KN/RG, 4) Click on the "Monitor" tab
> >>>>5a) Click on "Local IP Address" - there will be 2 IP addresses listed
> >>>>5b) Click on "IP Route" - the default route will be marked "Invalid"
> >>>>
> >>>>See screenshots here:
> >>>>https://carroll.pathcom.ca/serials/Configurator445_bug.html
> >>>>
> >>>>
> >>>>---
> >>>>Incoming mail is certified Virus Free.
> >>>>Checked by AVG anti-virus system (http://www.grisoft.com).
> >>>>Version: 6.0.705 / Virus Database: 461 - Release Date: 6/12/2004
> >>>>
> >>>>---
> >>>>Outgoing mail is certified Virus Free.
> >>>>Checked by AVG anti-virus system (http://www.grisoft.com).
> >>>>Version: 6.0.707 / Virus Database: 463 - Release Date: 6/15/2004
> >>>
> >>>
> >>>
> >>>---
> >>>Incoming mail is certified Virus Free.
> >>>Checked by AVG anti-virus system (http://www.grisoft.com).
> >>>Version: 6.0.707 / Virus Database: 463 - Release Date: 6/15/2004
> >>>
> >>>---
> >>>Outgoing mail is certified Virus Free.
> >>>Checked by AVG anti-virus system (http://www.grisoft.com).
> >>>Version: 6.0.710 / Virus Database: 466 - Release Date: 6/23/2004
> >>
> >>
> >>
> >>---
> >>Incoming mail is certified Virus Free.
> >>Checked by AVG anti-virus system (http://www.grisoft.com).
> >>Version: 6.0.710 / Virus Database: 466 - Release Date: 6/23/2004
> >>
> >>---
> >>Outgoing mail is certified Virus Free.
> >>Checked by AVG anti-virus system (http://www.grisoft.com).
> >>Version: 6.0.710 / Virus Database: 466 - Release Date: 6/23/2004
> >
> >
> >
> >_______________________________________________
> >Karlnet mailing list
> >Karlnet@WISPNotes.com
> >http://lists.wispnotes.com/mailman/listinfo/karlnet
> >
> >---
> >Incoming mail is certified Virus Free.
> >Checked by AVG anti-virus system (http://www.grisoft.com).
> >Version: 6.0.710 / Virus Database: 466 - Release Date: 6/23/2004
> >
> >---
> >Outgoing mail is certified Virus Free.
> >Checked by AVG anti-virus system (http://www.grisoft.com).
> >Version: 6.0.710 / Virus Database: 466 - Release Date: 6/23/2004
>
>
>
> _______________________________________________
> Karlnet mailing list
> Karlnet@WISPNotes.com
> http://lists.wispnotes.com/mailman/listinfo/karlnet

_______________________________________________
Karlnet mailing list
Karlnet@WISPNotes.com
http://lists.wispnotes.com/mailman/listinfo/karlnet

<Prev in Thread] Current Thread [Next in Thread>