[ QUOTE ] so i tried this: asl-pc's bios let the system restart every night and dsl-modem is plugged with a timer switch @ same time [:)] hm - i'am kidding
[/ QUOTE ] You may be kidding, but I have been thinking that very same thought. The idea of putting a power plug timer on my ADSL modem, so that it will power off for a few minutes around 06:00 every morning, is my current backup plan for when I go away for several days, so that I can still get assured remote access to my home system. The ASL box I am not concerned about, it has never hung on me yet.
I've forgotten to add a "!?" behind the "kidding" [:)]
But theres something i didn't understand: With IPCOP or Wingate something like this never happend before...
But i had this problem in the past with a d-link wlan ap/router - the problem was simple: this unit managed 255 connection maximum and "forgot" to close any external port - it depends on duty if it goes down -
But a linux based system has to cover that - or iam wrong???
Maybe - the error can happen @ the modem, but there has to be a way to fix it by software: -
- any at-string to reset or
- a power off @ cat-cable or something like this - cause a reset of asl works too!
OK, i looked for so many reasons, and theres quite a good chance that we have a MTU-Problem.
I try to explain my idea:
My system does not reconnect, when my services hard on duty. All local funktions like nat, masq and so on put a few bytes 4 headers to the packets - if i got packets with 1492 - it's possible that theres not enough space for additional information. So i will check it out with smaller packets, at first 1412... and enlarge them every day a lil' bit if it works... Lets see what happens.
If I'am totally wrong - let me know... Try and error is a hard way, but a good teacher [;)]
Jens
Hm. I guess i'am wrong... more than 1 3com nic might be the problem...
Don't thing it's Dyndns because i turned of Dyndns and the Problem still occures. But the other Point is very interesting, the 3COM Nics... I have two of them. Thank god it's sunday and there must be two Intel-Nics in my room... i'l try reinstalling.
Some News on this: 1. I keep DynDNS @ ASL off, it doesn't support Wildcards prior the Domain - so i don't care if it's the reason or not, there are more than enough better IP-Update-Scripts available - with tons of options... 2. A friend of mine administrates some Debian and Suse Linux-Servers and he told me, that they had a similar problem. Linux get's in trouble, when 2 or more 3com nic uses the same driver - and they had trouble with older realtec too - so Intel might be a good solution. 3. MTU 1492 for T-DSL is OK. 4. It would be a good idear to use NIC's of different brands or different types (of drivers), thats what i try out in the next days. 5. Enjoy sunshine - leave your PC - It's sunday [;)]
