search for: tnat

...n Apache 2.4 under Centos 7. In particular: - I have a file that's readable to every user and every application, (writeable by only one user), but my CGI scripts cannot read it. - Some of my CGI scripts need temporary storage for some files. They are, for example, some internal log files, tnat get cleaned up over time, but I want to be able to look at them (as root). Where would you suggest they be placed? I've tried /tmp/my_private_files/, and /var/tmp/my_private_files/, but Apache fails to find even the directory. Any suggestions? PS: Centos 6 had no such problems, and the...

...me to use my scripts. So I put in /etc/libvirt/hooks /qemu the right rules to get trafic to my VMs, but I can't set trafic back to external with the right external IP. The -j SNAT --to-source ot -j MASQUERADE dont work, are ignored, and I dont see any packet through these rules in iptables -tnat -L POSTROUTING. I used tcpdump to trace packet on the physical server on virbr0 interface and on eth0 interface. I see the packets on outgoing route. But, the ougoing packets are presented to the external interface with the internal address 10.0.0.x instead of the address specified in the -j S...

...-ctstate RELATED,ESTABLISHED -j ACCEPT iptables -A FORWARD -i br-lan -o br-wan -j ACCEPT , and it seems the packet are NAT'd as a general IP packet (the server receives a lan ip address). Then I tried to add the following NAT rules but it cannot match to any packet. iptables -I POSTROUTING 1 -tnat -j SNAT -p udplite -o br-wan --to [wan_ip] iptables -I PREROUTING 1 -tnat -j DNAT -p udplite -i br-lan --to [lan_ip] The tool I wrote for testing this behavior is hosted at https://github.com/nicholascw/SLOWProxy/tree/develop/gadgets/udpliteping, which is a simple ping-n-pong sketch. -- You are...

...n Apache 2.4 under Centos 7. In particular: - I have a file that's readable to every user and every application, (writeable by only one user), but my CGI scripts cannot read it. - Some of my CGI scripts need temporary storage for some files. They are, for example, some internal log files, tnat get cleaned up over time, but I want to be able to look at them (as root). Where would you suggest they be placed? I've tried /tmp/my_private_files/, and /var/tmp/my_private_files/, but Apache fails to find even the directory. Here's some extra information SELINUX is disabled. I modi...

I''m trying to do a nat redirect (traffic redirected from a router, not originally for the machine). I can see the network traffic, but the iptable rules do not appear to do anything. Is this possible on a virtual domain, and if not what needs to be done? -Jeff ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program.

...Centos 7. In particular: > > - I have a file that's readable to every user and every application, (writeable by only one user), but my CGI scripts cannot read it. > > - Some of my CGI scripts need temporary storage for some files. They are, for example, some internal log files, tnat get cleaned up over time, but I want to be able to look at them (as root). Where would you suggest they be placed? I've tried /tmp/my_private_files/, and /var/tmp/my_private_files/, but Apache fails to find even the directory. > > Here's some extra information > SELINUX is disab...

...n > particular: > > - I have a file that's readable to every user and every application, > (writeable by only one user), but my CGI scripts cannot read it. > > - Some of my CGI scripts need temporary storage for some files. They are, > for example, some internal log files, tnat get cleaned up over time, but I > want to be able to look at them (as root). Where would you suggest they be > placed? I've tried /tmp/my_private_files/, and /var/tmp/my_private_files/, > but Apache fails to find even the directory. > in the /usr/lib/systemd/system/httpd.service...

...> - I have a file that's readable to every user > and every application, (writeable by only one > user), but my CGI scripts cannot read it. > > > > - Some of my CGI scripts need temporary > storage for some files. They are, for example, > some internal log files, tnat get cleaned up > over time, but I want to be able to look at > them (as root). Where would you suggest they > be placed? I've tried /tmp/my_private_files/, > and /var/tmp/my_private_files/, but Apache fails to find even the directory. > > > > Here's some extra...

Hi. The patch I send before was too large so that it was dropped from the maling list. I'm sending again with smaller size. This patch set is the xen paravirtualization of hand written assenbly code. And I expect that much clean up is necessary before merge. We really need the feed back before starting actual clean up as Eddie already said before. Eddie discussed how to clean up and suggested

Hi. The patch I send before was too large so that it was dropped from the maling list. I'm sending again with smaller size. This patch set is the xen paravirtualization of hand written assenbly code. And I expect that much clean up is necessary before merge. We really need the feed back before starting actual clean up as Eddie already said before. Eddie discussed how to clean up and suggested

...the way, I got this behaviour from the very beginning if ACPI was turned off for guest OS (which was default). So I rolled back to NOT specifying CPU topology and allocating only two cores to WinXP. Bad... BUT it started working properly after I did the aforementioned 'optimisation' for tnat WinXP instance. Now I have it with 4 cores assigned. Mystery! Help me please, what did I do wrong way? Best regards, Dmitry Mikhailov Server configuration: 2x Intel(R) Xeon(R) CPU E5420 @ 2.50GHz 2x 2GB DDR-II FBDIMM Intel motherboard with 5000P Chipset Server's Mission: virtualization...

This patchset is for more paravirtualization on ia64/pv_ops. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patchset is for more paravirtualization on ia64/pv_ops. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patchset is for more paravirtualization on ia64/xen domU. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patchset is for more paravirtualization on ia64/xen domU. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S)

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S)

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S)