|
|
 |  |
Re: Secondary IP Port Mapping BugFrom: Men & Mice Support Date: Thursday, December 7, 2000
Time: 3:55:50 pmAs far as I know, this has not been addressed. We don't officially
support use of QuickDNS on a machine with multiple addresses.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!
At 12:37 PM -0500 12/7/00, Gary Gleason wrote:
>Chris -
>
>To revisit an old thread, does QuickDNS Pro 3.0 fix this bug (see previous
>mail below)?
>
>Regards,
>Gary
>
>Tim Bodine wrote:
>
>> Gary (and Chris),
>>
>> This sounds much more like a bug in QuickDNS rather than IPNR.
>> IPNetRouter only tells Apple's OT/mentat network stacks how to
>> configure themselves. If this interferes with QuickDNS, it is much
>> more likely that QuickDNS is making some assumptions about Apple's
>> networking stacks and their capabilities (eg assuming that OT cannot
>> be configured while QuickDNS is running) that are not true. Many
>> other Mac networking applications make this erroneous assumption, not
>> just QuickDNS.
>>
>> Apple only exposed the TCP/IP control panel interface for
>> configuration of their networking stacks but not all of the
>> capabilities of IP with mentat. IPNetRouter provides you with a way
>> to configure mentat to do what it is designed to do. We do not
>> insert our own networking stacks to make this happen.
>>
>> Its much more likely that IPNetRouter is just uncovering a QuickDNS
>> incompatibility between what OT can do when access is provided to its
>> APIs via IPNetRouter--not a problem that can be corrected in
>> IPNetRouter. I'm sure Peter will correct me if I'm wrong about this.
>>
>> Regards,
>> --Tim
>>
>> >Men & Mice Support wrote:
>> >
>> > > At 11:52 PM -0400 9/16/00, Gary Gleason wrote:
>> > > >Hi,
>> > > >
>> > > >We're running QuickDNS Pro 2.2.1 and IPNetRouter 1.5.2 (and nothing
>> > > >else) on a PM 6100/60 with OS 8.1. This is a dual ethernet setup with
>> >
>> > > >ADSL on the built-in ethernet and with an internal LAN with NAT on an
>> >
>> > > >Apple NuBus adapter card. Our ISP has assigned us consecutive
>> >addresses
>> > > >40, 41, etc. in x.y.z.0/26. We want to multihome 41 and 42 and then
>> >port
>> > > >map them to our internal web server. Everything works fine, except
>> >...
>> > > >
>> > > >... as soon as I add a 41 or 42 port mapping entry into IPNetRouter,
>> > > >QuickDNS stops responding to *any* external requests. Internal
>> >requests
>> > > >are still serviced normally. Removing the port mapping entries
>> >doesn't
>> > > >reactivate QuickDNS but quitting IPNetRouter does. Is there any way
>> >to
>> > > >work around this?
>> > >
>> > > I believe this has been mentioned before (either here or elsewhere)
>> > > as a bug in IPNetRouter - you should be able to fix it by moving
>> > > QuickDNS to another machine and port-mapping port 53 to it.
>> > > ____________________________________________________________________
>> > > Chris Buxton Men & Mice
>> > > cbuxton@menandmice.com We Make DNS Easy!
>> >
>> >Chris -
>> >
>> >Your suggested fix works fine. I couldn't find any referrence to this on
>> >the
>> >IPNetRouter site or archives, though, so will post this there in case
>> >anyone
>> >else runs into the problem.
>> >
>> >Thanks,
>> >Gary
>
>--
>Gary Gleason
>SoftLink Corporation
>8108 Park Crest Drive
>Silver Spring, MD 20910
>(301) 585-4345
>
>"For appreciation, always a little time."
> - Maude
|

Return to Digital Point Solutions' Home Page |