iptables conundrum Post: 302915401

Sponsored Content

Special Forums IP Networking iptables conundrum Post 302915401 by Shocco on Tuesday 2nd of September 2014 06:23:57 PM

09-02-2014

Registered User

sorry! the first set of numbers is supposed to be 192.168.222.4, more to add would be that 192.168.222.2 is the gateway and dns of 192.168.222.4

and yes there is a port range. i think thats only the case if it cant connect the the server on 10.10.10.250. but the program i need to use eats all traffic that isnt needed.

so in turn its 10.10.10.250 being the reporting box, 10.10.10.125 being the connection live to the web to hit said reporting box, and 192.168.222.2 being the gateway/dns server of 192.168.222.4.

192.168.222.4 > 192.168.222.2 > 10.10.10.125 > 10.10.10.250

i say this because the last time i had it working it showed 10.10.10.125 as the address for 192.168.222.4(i assume thats masquerading) on the reporting box, and in the inetsim config file it says what ip should be used if inetsim will act as a router for certain traffic

This is a malware traffic analysis box. so it needs to only have this one ip address allowed on this one port so that it can report findings of files run to said box.

the inetsim program also makes its own rules that are pretty annoying. at one point i had it telling me that it was established but wasnt showing activity on the destination server. and now its back to square one. let me know if you need more details. sorry for the typo!

and i have traffic from 10.10.10.250 already accepted, its from 192.168.222.2 that i cant get routed.

Shocco

View Public Profile for Shocco

Find all posts by Shocco

7 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Unix Grep Conundrum - Not for Noobies

Help, I have been stuck on this issue for weeks. I am a unix noobie. I have a very long string and within that string I am trying to get proc file names ie PROCNAME1=SOME_FILENAME_UPDTBASE.SQL There is a space on either side. I can't for the life of me peel out the proc name:...

2. Shell Programming and Scripting

Sed pattern space/looping conundrum

Although my sed skills are gradually developing, thanks in large part to this forum, I'm having a hard time dealing with pattern space and looping, which I suspect is what I'll need a better handle on to figure out my current issue, which is converting a multi line file like this: ...

3. UNIX for Dummies Questions & Answers

umask conundrum

Hi All, i was reading up on a umask question on this forum and have a question on this. the umask value on my home PC running on cygwin is 022. when i create a dir it defaults to permission 755, when i create a file it defaults to 644. Now it starts at 777 for dirs and 666 for files and...

4. Shell Programming and Scripting

Conundrum - Flexible way to strip extension

Hi, First post here. I have something that may prove to be difficult. I have the following files: Example1.0.0.tar.gz Example2.tar Example3.zip Example4.0.0.0.0.0.bzip2 I need to remove the file extensions and store as a variable so they look like this: Example1.0.0 Example2...

5. Shell Programming and Scripting

sudo scripts conundrum

hello; Got a problem running monitoring scripts using sudo ssh.. Mgmt decided to take away root sudoers access.. so most of the scripts ran as: sudo ssh $BOX ... Now I need to run them as: echo $my_pw | sudo -S -l my_user_id $BOX ... I tried this but not working.. Any wisdom/tricks...

6. Red Hat

Physical Volume Create Conundrum

I want to start by saying I already resolved my issue but I want to understand why I am seeing what I am seeing. I have a server with a RAID controller two 500GB drives and six 600GB drives. The two 500GB drives are mirrored and have the OS installed on them. The six 600GB they wanted set as...

7. OS X (Apple)

Help in explaining this echo conundrum.

OSX 10.12.3, default bash terminal. Consider this code and note it is calling 'sh' inside the code... #!/bin/sh echo '1\n2\n2\n3\n5' > /tmp/text hexdump -C /tmp/text /bin/echo '1\n2\n3\n4\n5' > /tmp/text hexdump -C /tmp/text Now view the interactive mode below, note the underlying shell is...

LEARN ABOUT FREEBSD

nos-tun

NOS-TUN(8)						    BSD System Manager's Manual 						NOS-TUN(8)

NAME

     nos-tun -- implement ``nos'' or ``ka9q'' style IP over IP tunnel

SYNOPSIS

     nos-tun -t tunnel -s source -d destination -p protocol_number [source] target

DESCRIPTION

     The nos-tun utility is used to establish an nos style tunnel, (also known as ka9q or IP-IP tunnel) using a tun(4) kernel interface.

     Tunnel is the name of the tunnel device /dev/tun0 for example.

     Source and destination are the addresses used on the tunnel device.  If you configure the tunnel against a cisco router, use a netmask of
     ``255.255.255.252'' on the cisco.	This is because the tunnel is a point-to-point interface in the FreeBSD end, a concept cisco does not
     really implement.

     Protocol number sets tunnel mode.	Original KA9Q NOS uses 94 but many people use 4 on the worldwide backbone of ampr.org.

     Target is the address of the remote tunnel device, this must match the source address set on the remote end.

EXAMPLES

     This end, a FreeBSD box on address 192.168.59.34:

	   nos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45

     Remote cisco on address 192.168.56.45:

	   interface tunnel 0
	   ip address 192.168.61.2 255.255.255.252
	   tunnel mode nos
	   tunnel destination 192.168.59.34
	   tunnel source 192.168.56.45

AUTHORS

     Nickolay N. Dudorov <nnd@itfs.nsk.su> wrote the program, Poul-Henning Kamp <phk@FreeBSD.org> wrote the man-page.  Isao SEKI
     <iseki@gongon.com> added a new flag, IP protocol number.

BUGS

     We do not allow for setting our source address for multihomed machines.

BSD
								  April 11, 1998							       BSD