8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a question regarding IPTables packet flow, that I am hoping I can get an answer to.
We have a fairly advanced implementation of IPTables that I am trying to convert into a third party product and I am not quite certain on the packet flow in the current IPTables implementation.
We are... (2 Replies)
Discussion started by: knightfirefx
2 Replies
2. IP Networking
I have two programs, a datagram socket based sender and a datagram socket based receiver. The sender emits a short UDP message to 192.168.0.100:33333 every second. The receiver creates a datagram socket with a default port number (let's say it is 44444), clears the iptables adds the following rule:... (4 Replies)
Discussion started by: michaelrusse
4 Replies
3. Cybersecurity
I am setting up a new squid daemon to run on my server. I want to make sure that everyone inside my network can access squid but I want to make sure everyone on the internet is blocked.
eth0 is connected to my internal LAN via: 192.168.0.5/255.255.255.0
eth1 is connected to the internet via:... (1 Reply)
Discussion started by: nondescriptciti
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
On the IPTABLES, I did iptables --flush. I want to start fresh. Now I only want two things. Allow one ip address to this server. Allow port 443 as incoming from every where. Please advice how to do this.
This is what I did so for.
iptables -I INPUT -i eth0 -s 1.2.3.4 -j ACCEPT... (5 Replies)
Discussion started by: samnyc
5 Replies
5. IP Networking
What should be the iptables rule so that only the subnet 64.61.11.224/255.255.255.248 may access the mysql port 3306 (1 Reply)
Discussion started by: proactiveaditya
1 Replies
6. IP Networking
Trying to create a whitelist to limit bandwidth. My sync speed is 1536/256 kbps.
Simple rules in order:
1. Do not limit (or set to 1536/256) MAC 00:00:00:00:00 (computer is in 192.168.1.0/24).
2. Do not limit (or set to 1536/256) MAC 00:00:00:00:01 (computer is in 192.168.1.0/24).
3. Do not... (1 Reply)
Discussion started by: kripz
1 Replies
7. Linux
Description
i used iptables firewall is a month,running is favorable.it is failed when i connecting to my server on time.the servers' web service and all ports did not connect.i remote login the other server and through intranet address login this server then i restart iptables .but through... (0 Replies)
Discussion started by: proceed
0 Replies
8. IP Networking
Hey guys, I have just started using IP tables and was wondering if anyone could direct me to any good online resources as I am totally new to this. Thanks. (1 Reply)
Discussion started by: 182x
1 Replies
LEARN ABOUT OSX
svk::command::info
SVK::Command::Info(3) User Contributed Perl Documentation SVK::Command::Info(3)
NAME
SVK::Command::Info - Display information about a file or directory
SYNOPSIS
info [PATH | DEPOTPATH]...
OPTIONS
-R [--recursive] : descend recursively
DESCRIPTION
For example, here's the way to display the info of a checkout path:
% svk info ~/dev/svk
Checkout Path: /Users/gugod/dev/svk
Depot Path: //svk/local
Revision: 447
Last Changed Rev.: 447
Last Changed Date: 2006-11-28
Copied From: /svk/trunk, Rev. 434
Merged From: /svk/trunk, Rev. 445
You can see the result has some basic information: the actual depot path, and current revision. Next are advanced information about copy
and merge source for this depot path.
The result of "svk info //svk/local" is almost the same as above, except for the "Checkout Path:" line is not there, because you are not
referring to a checkout path.
Note that the revision numbers on "Copied From:" and "Merged From:" lines are for the source path (//svk/trunk), not the target path
(//svk/local). The example above state that, //svk/local is copied from the revision 434 of //svk/trunk, and //svk/local was merged from
the revision 445 of //svk/trunk. Hence if you do a "svk log -r 434 //svk/local", svk would tell you that //svk/local does not exist at
revision 434.
So far there is no easy way to tell the actual revision number of //svk/local right after a copy or merge.
If the target is a depot path, or the corresponding depot path of the target checkout path is actually a mirroring path, the output of this
command will look like this:
% svk info //svk/trunk
Depot Path: //svk/trunk
Revision: 447
Last Changed Rev.: 445
Mirrored From: svn://svn.clkao.org/svk, Rev. 1744
So you can see this depot path is mirrored from a remote repository, and so far mirrored up to revision 1744.
perl v5.10.0 2008-08-04 SVK::Command::Info(3)