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 [;)]
ok i used a older realtek 8129 for the dsl connection, a newer realtek 8139 for the dmz and a 3c905b as internal interface. after i realized the reconnect-problem i changed the realtek 8129 for the dsl connection with a 3c905c, but i had the same problem. today i changed the 3c905c with the realtek 8139. i´ll post the result tomorrow.
ok i used a older realtek 8129 for the dsl connection, a newer realtek 8139 for the dmz and a 3c905b as internal interface. after i realized the reconnect-problem i changed the realtek 8129 for the dsl connection with a 3c905c, but i had the same problem. today i changed the 3c905c with the realtek 8139. i´ll post the result tomorrow.
the 3c905b is my external, one 3c905c is dmz, the other 3c905c is internal - it looks like a bad configuration, hopefully i find the time to change that in the next days...
...are there any known well working combinations of 3 nic's and dmz/int/ext(pppoe) with ASL5.001 ... ??? PLEASE POST! thx
Im having the same problem at the moment. I found out, that maybe Packet Filter could be the problem. Two entries in the list AUTO_INPUT are missing and therefore all replies from the Modem are dropped. The first time after reboot this doesnt seem to be a problem. So I guess its a bug with the automatic update of the Packet Filter rules. On the other hand a entry for protocoll 47 is in AUTO_OUTPUT, that in my opinion should be in AUTO_INPUT, because the source address is the one of the configured DSL-Modem.
