Tx. I found a workaround with ssh tunnel Tx.
Main Topics
Browse All TopicsSay, when I try connect to CentOS server with VNC viewer to ip: 42.44.6.139 nothing gets logged.But if I ping or ssh it is picked up. I can login via vnc to eth0. VNC server listening on all ports.Please help.
This is my routing
[root@localhost sysconfig]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
dsl-146-152-01. * 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
192.168.10.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth1
default * 0.0.0.0 U 0 0 0 ppp0
and my Firewall:
Saving firewall rules to /etc/sysconfig/iptables: [ OK ]
Chain INPUT (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
8 320 ACCEPT tcp -- any any anywhere anywhere tcp dpt:ssh
0 0 LOG all -- any any anywhere anywhere LOG level warning
0 0 ACCEPT all -- lo any anywhere anywhere
0 0 ACCEPT all -- eth0 any anywhere anywhere
0 0 ACCEPT all -- ppp0 any anywhere anywhere
0 0 ACCEPT all -- any any anywhere anywhere state RELATED,ESTABLISHED
Chain FORWARD (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 6 packets, 756 bytes)
pkts bytes target prot opt in out source destination
and
[root@localhost sysconfig]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:02:E3:4C:A0:05
inet addr:192.168.10.77 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::202:e3ff:fe4c:a005/6
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29066996 errors:1 dropped:0 overruns:0 frame:0
TX packets:29066454 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2074256317 (1.9 GiB) TX bytes:374799651 (357.4 MiB)
Interrupt:201
eth1 Link encap:Ethernet HWaddr 00:06:4F:7D:17:05
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::206:4fff:fe7d:1705/6
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29452 errors:0 dropped:0 overruns:0 frame:0
TX packets:58244 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3449712 (3.2 MiB) TX bytes:4473441 (4.2 MiB)
Interrupt:177 Base address:0xcc00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1868 errors:0 dropped:0 overruns:0 frame:0
TX packets:1868 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3674111 (3.5 MiB) TX bytes:3674111 (3.5 MiB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:42.44.6.139 P-t-P:164.144.152.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:275 errors:0 dropped:0 overruns:0 frame:0
TX packets:589 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:43357 (42.3 KiB) TX bytes:37983 (37.0 KiB)
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hm ssh tunnel works & vnc doesn't? The definitely makes no sense as ip has no special cases based on portnumbers.....
The difference is the you connect with ssh to the local interface and then locally access the outside interface..... (if coming from inside)...
then why not connect to VNC using the local interface.... Now you are using ssh as a special tunnel routing tool
Business Accounts
Answer for Membership
by: nociPosted on 2009-08-20 at 00:36:45ID: 25139987
I dont known what rules are used excatly for LOG...
But ssh is picked up BEFORE the log rule, so the logrule never matches. If there is an -p tcp in the logrule then it won't match icmp (=PING and more).
please if you show iptables configuration dor
iptables -L -nv
and present that output.