General Questions

Hello,

Because of the out of Sync clock the sixxs-aiccu IPv6 tunnels stops working:

1: I changed the NTP time server (General Setup) to ntp.us.sixxs.net and update Interval to 6 minutes (lowest possible), where can I check if Monowall has updated it's time by this configured 6 minute Timeserver.
2: Why is monowall 'suddenly' running slower / faster with it's clock then the real clock? I'm running on VMware with generic-pc-1.34-vm.zip version. The VMWare host is busy (Processort allway's around 30-40 % load)

Regards, Onedutch

Additional Info:
When the clock is between a max 2 minutes delta on the monowall and sixxs pop the IPv6 tunnel is working properly. After that it starts dropping packages and finally it closes the tunnel. If I check the monowall log I find :
Dec 6 10:23:41 sixxs-aiccu: AICCU running as PID 262
Dec 6 10:23:41 sixxs-aiccu: [AYIYA-start] : Anything in Anything (draft-02)
Dec 6 10:23:41 sixxs-aiccu: [AYIYA-tun->tundev] : (Socket to TUN) started
Dec 6 10:37:24 sixxs-aiccu: [AYIYA-tun->tundev] [192.87.102.107]:5072 : Time is 125 seconds off for ::
Dec 6 10:38:16 sixxs-aiccu: [AYIYA-tun->tundev] [192.87.102.107]:5072 : Time is 133 seconds off for ::

So from 10:23 to 10:37 it looks normal, between 10:37 and 10:38 the difference is out of nowhere 8 second s why....

You can find m0n0 time using /exec.php and for example just type "date".

Clock problems, "time drift" problems could happen with every VM in crowded virtualization environment.

PS: If You are running very heavy traffic trough m0n0 and that is causing CPU issues set System>Advanced>set device polling on.

You can find m0n0 time using /exec.php and for example just type "date".

Have found that allready, the exec page,  it doesn't tell me however when it NTP synced for the last time and if that NTP sync was succesfull. I found a command NTPDATE it doesn't work on the exec page

Clock problems, "time drift" problems could happen with every VM in crowded virtualization environment.

You nailed it, the VM host is crowded, I changed the base priority of the VMWare-vmx.exe process where Monowall is running on. The time drift is history.

Still if somebody could tell me how i could check if monowall is running NTP syncs correctly I would appreciate that. Perhaps the only way is to use wireshark and sniff for NTP traffic.

  other problem is popping up now, IPv6 has a message "No route to host (65)" I will search the forums for a solution.