This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

external address for NAT doesn't get updated

Hi,
I'm using ASL 5.016 and DSL.
Now I got the following problem: The external address is not updated for the NAT rules.
If I print the NAT rules using
Packet filter->advanced->Current System NAT Rules
I see my last IP-address and not the current IP address.
Any idea?

Thanks, Martin

This thread was automatically locked due to age.

0 Xeno over 21 years ago

HI Martin,

I was not able to reproduce the problem. I tried, but may NAT rules updated fine. Please have a look into middleware logfile. Is there something uncommon at the moment PPPoE reconnects?

cheers
Xeno
Cancel
Vote Up 0 Vote Down

Cancel
0 Martin_Stingl over 21 years ago in reply to Xeno

Hi Xeno,

I attached the part of the middleware logfile. I don't know whether "Confd communication error" lines are real errors or not.
I updated yesterday to 5.017. At that time the new dial-in updated the NAT rules correctly.
Earlier versions did everything okay, too.

Thnak you,
Martin
Cancel
Vote Up 0 Vote Down

Cancel
0 Martin_Stingl over 21 years ago in reply to Martin_Stingl

Hi,

there seems to be a real problem: After today's reconnect there are all NAT rules gone: the chain USR_PRE was empty.
Webmin showed the rules correctly. I've attached the section of the middleware log.

Martin
Cancel
Vote Up 0 Vote Down

Cancel
0 Xeno over 21 years ago in reply to Martin_Stingl

Could you please also post the PPPoE log?

Xeno
Cancel
Vote Up 0 Vote Down

Cancel
0 Martin_Stingl over 21 years ago in reply to Xeno

Hi Xeno,

I attached a zip-file with three files in it:
astaro-ppoe.txt contains the two pppoe-log-parts matching to my earlier posts.
pppoe-2004-08-09[1].21h00m.log and mdw-2004-08-09[1].20h58m.log contains the logfiles of today.
Today happened the following:
At 20:51 the DSL-connection went down. After reconnecting the NAT rules were gone. I killed the pppoe-daemon using a shell login. I had to repeat it because I hadn't waited long enough. At 20:56 I got the new connection and the NAT rules are now there.
Thank you for your help so long,
Martin

47505-astaro.zip
Cancel
Vote Up 0 Vote Down

Cancel
0 KKnecht over 21 years ago

@Martin

i can confirm your first post:
got crazy because a packet filter rule didn't work, then i rememberd this post.
had the same behaviour: NAT rules showed the last IP.

my workaround: Added a host definition 'dynamic hostname' and typed in the dyndns name of the system.

Karsten
Cancel
Vote Up 0 Vote Down

Cancel
0 Timo over 21 years ago in reply to Martin_Stingl

@Martin_Stingl and @KKnecht,

would it be possible for you to send a backup of the firewall to support@astaro.com ?

thanks
Timo
Cancel
Vote Up 0 Vote Down

Cancel
0 Martin_Stingl over 21 years ago in reply to KKnecht

Hello Karsten,

I did use your tip while my NAT rules weren't working. After changing these rules to the dynamic name the chain was filled.
I hope this work-around will solve the problem for next dialin, too.
I also sent a copy of my backup to astaro. I hope they find the bug (or the problem in my configuration...)

Thank you,
Martin
Cancel
Vote Up 0 Vote Down

Cancel
0 Timo over 21 years ago in reply to Martin_Stingl

We imported the backup and let the firewall run over the weekend. But address updated correctly everytime. So it's not reporduceable. Would it be possible to send a login to astaro support at the moment the problem exists?

Timo
Cancel
Vote Up 0 Vote Down

Cancel
0 Martin_Stingl over 21 years ago in reply to Timo

The workaround with the dynamic hostname solved my problem.
Cancel
Vote Up 0 Vote Down

Cancel