Freetz questions in english

Hi Faina,

Thanks for response.
The problem is all the write permission is given to both the download directory, and the shared folder. I have EXT3 on NAS.
I have no idea what is the problem.
How can I see syslog?
I searched the whole filsystem within the fritz, (started with /var/logs/ ) but no logs found.

Maybe syslogd is not started by default.

How can I see Transmission logs?

Regards,Robert.

To get the messages from syslog you have to install a syslogd server (e.g. I use kiwi syslogd on a windows pc), but probably if you checked Syslogd in webinterfaces when build up the feetz you can seem the syslogs in the freetz interface. The syslog messages are sent over tcp and not write to a file (I guess)...

Have you enabled the ext3 fs?
 
Hi Faina,

Thanks for the very quick reply.
I use linux PC so having existing syslogd will no problem. But how can I set Fritzbox to send log messages to that machine?
So do I need to compile new firmware with syslog enabled?
I will check the syslog webinterface which you mention.

EXT3 is not enabled, on Firtz because NAS is accessed via CIFS. (by the way NAS has ext3 but not relevant here.)

Do you know Transmission will produce logs to messages?

Regards,
Robert
 
transmission -NAS permission.

Hi RalfFriedl

Thanks for answer.

That's is the problem I can't decide whether is it a bug in the CIFS share or the transmission....
I need to see messages.

I tired lsof but shows only open files, not the moment of directory creation, which is the problematic in this case.

Regards,Robert
 
From what I remember from the other bug report, it was similar when the directories and files were created manually. So you may want to test that first.
 
Hi Faina,

Thanks for the very quick reply.
I use linux PC so having existing syslogd will no problem. But how can I set Fritzbox to send log messages to that machine?
So do I need to compile new firmware with syslog enabled?
I will check the syslog webinterface which you mention.

EXT3 is not enabled, on Firtz because NAS is accessed via CIFS. (by the way NAS has ext3 but not relevant here.)

Do you know Transmission will produce logs to messages?

Regards,
Robert

attachment.php
 

Anhänge

  • syslogd.jpg
    syslogd.jpg
    91.3 KB · Aufrufe: 158
tnx for the fix! now the package builds up :)
.. so I try to work with vpnc:
I needed to "translate" my .pcf into cisco.conf. This link was useful:
http://www.ubuntugeek.com/how-to-set...unty-9-04.html

I am now able to connect to my CISCO router and it give an IP to me, but I got errors from vpnc.
This is the output from freetz:
Code:
/var/mod/root # sh -x /etc/init.d/rc.vpnc start
(...)
+ vpnc --script /etc/default.vpnc/vpnc-script /mod/etc/vpnc.conf
modprobe: module ip_tables not found in modules.dep
modprobe: module ip_conntrack not found in modules.dep
modprobe: module iptable_filter not found in modules.dep
modprobe: module iptable_nat not found in modules.dep
modprobe: module ipt_MASQUERADE not found in modules.dep
iptables v1.4.1.1: can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.4.1.1: can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.4.1.1: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
VPNC started in background (pid: 3268)...
+ exitval=0
+ [ 0 -eq 0 ]
+ echo done.
done.
/var/mod/root # ifconfig
(...)
tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:158.110.123.63  P-t-P:158.110.123.63  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP ALLMULTI MULTICAST  MTU:1412  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:113 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:56 (56.0 B)  TX bytes:6879 (6.7 KiB)

/var/mod/root # route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
158.110.2.151   0.0.0.0         255.255.255.255 UH    0      0        0 dsl
192.168.180.1   0.0.0.0         255.255.255.255 UH    2      0        0 dsl
192.168.180.2   0.0.0.0         255.255.255.255 UH    2      0        0 dsl
192.168.178.201 0.0.0.0         255.255.255.255 UH    2      0        0 dsl
158.110.104.32  158.110.123.67  255.255.255.255 UGH   0      0        0 tun0
79.98.40.244    0.0.0.0         255.255.255.255 UH    2      0        0 dsl
192.168.178.0   0.0.0.0         255.255.255.0   U     0      0        0 lan
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 lan
158.110.0.0     158.110.123.67  255.255.0.0     UG    0      0        0 tun0
0.0.0.0         158.110.123.67  0.0.0.0         UG    0      0        0 tun0
0.0.0.0         0.0.0.0         0.0.0.0         U     2      0        0 dsl
and - possibly do to this errors - I can access my private network only from the fritz!box: any pc attached to the box cannot reach the network any more.
I'm using freetz trunk-Rev.4525
I noticed that iptable is 1.4.1.1 a rather old version; the latest is 1.4.7


Any help appreciated!
 
Zuletzt bearbeitet:
.. so I try to work with vpnc:
I needed to "translate" my .pcf into cisco.conf. This link was useful:
http://www.ubuntugeek.com/how-to-set...unty-9-04.html

I am now able to connect to my CISCO router and it give an IP to me, but I got errors from vpnc.
(...)
and - possibly do to this errors - I can access my private network only from the fritz!box: any pc attached to the box cannot reach the network any more.
I'm using freetz trunk-Rev.4525
I noticed that iptable is 1.4.1.1 a rather old version; the latest is 1.4.7
Solved this way:
Building the firmware with a minimun set of iptables (menu Unstable) and not using NAT, I started my vpnc without errors.

To share the vpn tunnel with the connected pc's, I entered the following via telnet:

iptables -A FORWARD -o tun0 -j ACCEPT
iptables -A FORWARD -i tun0 -j ACCEPT
iptables -t nat -A POSTROUTING -o tun0 -j MASQUERADE
 
new build

I build Freetz (trunk/Rev5338 ) including VPNC
I already configured VPNC and I am able to connect to remote server.

But I cannot share my VPN session, because of a iptables error:
Code:
Loading table list...
iptables v1.4.1.1: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
In the make I already included iptables_nat but seems that something else is missing??!
 
Hi,

Have you tried to load the NAT modules first? You probably need to:
Code:
modprobe iptable_nat
modprobe ip_nat
modprobe ipt_MASQUERADE

# modprobe ip_nat_ftp   - if needed
# modprobe ip_nat_h323  - if needed
# modprobe ip_nat_irc   - if needed
# modprobe ip_nat_pptp  - if needed
# modprobe ip_nat_tftp  - if needed

It depends on your box (kernel type) what modules have to be loaded in advance. If you have a replaced kernel, you can also enable KMOD in the kernel to allow autoloading of the required modules. You need - of course - the according modules included in your firmware when you make it (unstable branch - iptables section libipt_MASQUERADE, iptable_nat, ip_nat, ipt_MASQUERADE, ...)
 
Zuletzt bearbeitet:
I selected ALL the option in unstable branch - iptables section
but have still the same error.
modprobe returns also an error:

Code:
/var/mod/root # modprobe iptable_nat
modprobe: can't load module iptable_nat (kernel/net/ipv4/netfilter/iptable_nat.ko): unknown symbol in module, or unknown parameter

How do I enable KMOD in the kernel to allow autoloading ?

BTW, I rebuild an older version (freetz-devel-5020) and it works!
 
Zuletzt bearbeitet:
This is strange. What kind of Fritz!Box do you have, and do you use the original kernel or have made you your own kernel with the "replace kernel" option?

If so, please check the selected kernel options, if the NAT modules are included in your build (make kernel-menuconfig etc...)

However - you have now a running firmware. If you do not need newer features, maybe you better stay with that version...
 
This is strange. What kind of Fritz!Box do you have, and do you use the original kernel or have made you your own kernel with the "replace kernel" option?

If so, please check the selected kernel options, if the NAT modules are included in your build (make kernel-menuconfig etc...)

Yes, I have the original kernel and no, I have not selected "replace kernel" opt.
The nat modules seem to be included!! I really do not understand...:mad:

However - you have now a running firmware. If you do not need newer features, maybe you better stay with that version...

Yes, you're absolutely right, ...but I like to experiment and to have the latest versions! ;)

tnx for your help!!:)
 
Anyway - there is no signature in your account. What kind of Box are we talking about? ist a 71xx or 72xx or 73xx series??? They are very different in regard of Memory, Kernel version etc. Even the 7270 has two distinct versions (v2 / v3) with a different kernel configuration. It may help, if you add some information about the hardware...
 
sorry, I forget to reply this question!
I have a
FRITZ!Box Fon WLAN 7270 Firmware version 54.04.81 English

FREETZ_AVM_VERSION_7270_04_80=y
FREETZ_TYPE_FON_WLAN_7270=y
FREETZ_TYPE_FON_WLAN_7270_16MB=y
FREETZ_AVM_VERSION_STRING="7270_04.80"
FREETZ_TYPE_LANG_EN=y
FREETZ_TYPE_LANG_STRING="en"
 
Can you please post the ouput of "cat /dev/debug" after you tried to modprobe the iptable modules?

Regards
Oliver
 
sorry, I am not *near* my fritz now! I have access via https to AVM interface but seems not possible to access via telnet! (is there a way to do this?)
I'll be able to post what you requested only in the evening...
 
No, not with AVM interface. Only with Freetz (Rudi-Shell).
 
I make a new build, freetz-devel-5409
After
modprobe ip_table nat
this is the (tail) output of
cat /dev/debug:

Code:
ip_tables: (C) 2000-2006 Netfilter Core Team
ip_conntrack version 2.4 (256 buckets, 2048 max) - Zd bytes per conntrack
iptable_nat: Unknown symbol ip_xfrm_me_harder
[4294948979]maxrun: 1
[4294950257]maxrun: 1
 
I got the problem and we will discuss how to solve it...

Regards
Oliver
 
Holen Sie sich 3CX - völlig kostenlos!
Verbinden Sie Ihr Team und Ihre Kunden Telefonie Livechat Videokonferenzen

Gehostet oder selbst-verwaltet. Für bis zu 10 Nutzer dauerhaft kostenlos. Keine Kreditkartendetails erforderlich. Ohne Risiko testen.

3CX
Für diese E-Mail-Adresse besteht bereits ein 3CX-Konto. Sie werden zum Kundenportal weitergeleitet, wo Sie sich anmelden oder Ihr Passwort zurücksetzen können, falls Sie dieses vergessen haben.