its probbly the double NAT thats the problem
your getting NATed by the isp
then again by ipcop
external access just opens access to the ipcop box itself (not what you
you want to port forward.
look at the ports being used by whatever it is and forward those to the box
probbly directx ports if its from msn so that may help.
Anybody know of some kind of directx gateway/other things (perhaps
better/other than UPNP)
[mailto:ipcop-user-admin@... Behalf Of Ken
Sent: Friday, 3 March 2006 11:46 AM
Subject: Re: [IPCop-user] Wireless Broadband Problems
>Have you checked for pmtu black holes? I had problems with this.
>>From a windows machine try "ping -f -l 1490 -n 2 <msn site>" at the
>line. Reduce the 1450 by 10's until it works. Use that as your mtu.
>If your first ping gets through (with 1490) then this probably isn't your
>There are other posts in the archive about how to change the mtu on the
>>[mailto:ipcop-user-admin@...] On Behalf Of
>>Sent: Thursday, March 02, 2006 5:42 PM
>>Subject: [IPCop-user] Wireless Broadband Problems
>>I have a small home network - three client computers and
>>IPCop connected using a network hub. I've been using IPCop
>>for about two years on a dialup connection and I have just
>>recently had a wireless broadband service installed.
>>I have been given a static "private" IP Address of
>>172.20.39.78; I have enabled the RED zone on IPCop and most
>>things are working fine.
>>However, I can't seem to successfully access any MSN sites -
>>in particular http://zone.msn.com - to play card games and
>>All that usually happens is that the request times out.
>>Sometimes I get as far as the MSN signon screen but most of
>>the time I don't. I have looked at IPCop's firewall logs but
>>there is no consistency.
>>I did try connecting one of my client computers directly to
>>the box to the outside world and everything seemed to work OK
>>which suggests that it's something to do with IPCop.
>>Although, having said that, I did once (and once only) manage
>>to get one of the clients logged on to zone.msn.com through IPCop.
>>It all seems to point to something that IPCop is unhappy
>>with. I even tried opening external access on all ports
>>(1-65535) on both TCP and UDP but still I couldn't connect.
>>Has anyone any ideas as to what I could try. I'll gladly
>>supply any further information if required.
>>(Current IPCop release - 1.4.10)
>>This SF.Net email is sponsored by xPML, a groundbreaking
>>scripting language that extends applications into web and
>>mobile media. Attend the live webcast and join the prime
>>developer group breaking into this new coding territory!
>>IPCop-user mailing list
Tried that. Maximum I could get without fragmentation was 1472.
Changed IPCop (command ifconfig eth1 mtu 1472) but everything's the same
as it ever was :-(
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
IPCop-user mailing list