You will need to leave 53 on UDP available unless you set up your
own DNS entries on the PC. You will only need to open the ports
that the particular program requires but opening them all might
do it. netmeetinf has been a problem. There was some discusion
about the brain dead protocol that embeds the IP address of
machines involved and that won't be translated by the M10 so it
may still not work.

If you do succeed let us know. I don't have MS windows so I
can't run Netmeeting or most MS product to test.

If none of this makes sense let me know and I try to clean it up
;)

>From the yet to be written FAQ

If your favorite program won't work with the M10 it is probably
because the M10 acts as a basic firewall. This means it prevents
certain types of unauthorized connections. You will need to
authorize the connections by opening what are called pinholes in
the firewall. To add pinholes, in your browser access the M10
and click on pinhole. You have to add
External Start Port
External End Port
Protocol
Internal IP address
Internal Port

You type the numbers in, select the protocol from the drop down
list then click add. To remove and entry click Delete. Then
click home and click save. Click restart. (I find that it is
best to switch the modem off for 30 seconds and then back on
again) To allow anything to connect to your computer you need
to have 2 entries.

External Start External End Proto IP Address Internal
Port
1 65535 TCP 192.168.1.1 1
1 65535 UDP 192.168.1.1 1

If you wish to use the M10 as a DNS server try

External Start External End Proto IP Address Internal
Port
1 65535 TCP 192.168.1.1 1
1 52 UDP 192.168.1.1 1
54 65535 UDP 192.168.1.1 54

--kit

Dion Holmes wrote:
>
> The IP on the M10 is 210.55.116.42
> The Ip being presented to the web sites in question was
> 203.96.111.199
> the implication is that the machine that is 203.96.111.199 is
> taking the
> packets and doing something akin to NAT on them. Or possible
> some other sort
> of Proxy service. The server at the far end is seeing the
> packets as if they are coming from the 203.96.111.199 machine.
>
> Kit,
>
> We have been trying to link up between our ISDN and ADSL in order to get
> Netmeeting, or VDO Phone operating. So far we have found that when
> connecting via IP addresses we can only connect from the ADSL to the ISDN.
> When we attempt to contact the ADSL from the ISDN we get a message "party
> not online" or words to that effect any way.
>
> Do you think this could in part be due to the sort of IP masquerading that
> you have seen? Just a thought at present, but it would tend to explain the
> problem. If it is the problem it could also make video conferencing via
> the ADSL pretty hard until some sort of static IP system is made available
> which is a shame because we now have all this bandwidth to play with. Just
> the thing for decent video.
> Regards,
>
> Dion Holmes.
>
> Dynalink Modems Tech Support
> 20-22 Andrew Young Street
> PALMERSTON NORTH
>
> 0800 653 962 Mon-Fri 9am-4pm
>
> Visit our website at http://www.dynalink.co.nz
> Checkout the Online Tech Support at http://www.dynalink.co.nz/support
>
> To unsubscribe: send mail to majordomo@freebsddiary.cx
> with "unsubscribe adsl" in the body of the message

To unsubscribe: send mail to majordomo@freebsddiary.cx
with "unsubscribe adsl" in the body of the message
Received on Sun Aug 15 19:20:01 1999