Setup is
WAN < ====== > (enp2s0) ROUTER / OPENVPN SERVER (enp1s0 <========= > LAN
enp2s0 IP: 192.168.1.1
enp1s0 IP: 192.168.254.1
OPENVPN SERVER CONFIG:
[oconf=]#################################################
# Sample OpenVPN 2.0 config file for #
# multi-client server. #
# #
# This file is for the server side #
# of a many-clients <-> one-server #
# OpenVPN configuration. #
# #
# OpenVPN also supports #
# single-machine <-> single-machine #
# configurations (See the Examples page #
# on the web site for more info). #
# #
# This config should work on Windows #
# or Linux/BSD systems. Remember on #
# Windows to quote pathnames and use #
# double backslashes, e.g.: #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
# #
# Comments are preceded with '#' or ';' #
#################################################
# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d
# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one. You will need to
# open up this port on your firewall.
port 1194
# TCP or UDP server?
;proto tcp
proto udp
# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun
topology subnet
# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one. On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap
# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key). Each client
# and the server must have their own cert and
# key file. The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys. Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca /etc/openvpn/ca.crt
cert /etc/openvpn/U1010SERVER.crt
key /etc/openvpn/U1010SERVER.key # This file should be kept secret
# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys.
dh /etc/openvpn/dh2048.pem
# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.6.0.0 255.255.255.0
# Maintain a record of client <-> virtual IP address
# associations in this file. If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt
# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface. Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0. Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients. Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100
# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses. You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge
# Push routes to the client to allow it
# to reach other private subnets behind
# the server. Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"
push "route 192.168.254.0 255.255.255.0"
# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).
# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.
# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
# ifconfig-push 10.9.0.1 10.9.0.2
# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
;learn-address ./script
# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
;push "redirect-gateway def1 bypass-dhcp"
# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
;push "dhcp-option DNS 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"
push "dhcp-option DNS 192.168.254.1"
# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
;client-to-client
# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn
# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120
# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
# openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
tls-auth /etc/openvpn/ta.key 0 # This file is secret
key-direction 0
# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC # Blowfish (default)
cipher AES-128-CBC # AES
;cipher DES-EDE3-CBC # Triple-DES
auth SHA256
# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
comp-lzo
# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100
# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
user nobody
group nogroup
# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun
# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log
# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it. Use one
# or the other (but not both).
;log openvpn.log
log-append /var/log/openvpn.log
# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 6
# Silence repeating messages. At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20[/oconf]
OPENVPN CLIENT CONFIG
[oconf=]##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server. #
# #
# This configuration can be used by multiple #
# clients, however each client should have #
# its own cert and key files. #
# #
# On Windows, you might want to rename this #
# file so it has a .ovpn extension #
##############################################
# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client
# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun
# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one. On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap
# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
;proto tcp
proto udp
# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
;remote 192.168.100.253 1194
;remote 124.106.81.31 1194
remote 192.168.254.1 1194
;remote u1010.duckdns.org 1194
# Choose a random host from the remote
# list for load-balancing. Otherwise
# try hosts in the order specified.
;remote-random
# Keep trying indefinitely to resolve the
# host name of the OpenVPN server. Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite
# Most clients don't need to bind to
# a specific local port number.
nobind
# Downgrade privileges after initialization (non-Windows only)
;user nobody
;group nobody
# Try to preserve some state across restarts.
persist-key
persist-tun
# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here. See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]
# Wireless networks often produce a lot
# of duplicate packets. Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings
# SSL/TLS parms.
# See the server config file for more
# description. It's best to use
# a separate .crt/.key file pair
# for each client. A single ca
# file can be used for all clients.
# ca /Users/kss1x/Library/openvpn/ca.crt
# cert /Users/kss1x/Library/openvpn/KSS1XMAC.crt
# key /Users/kss1x/Library/openvpn/KSS1XMAC.key
ca ca.crt
cert KSS1XMAC.crt
key KSS1XMAC.key
# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server". This is an
# important precaution to protect against
# a potential attack discussed here:
# http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the nsCertType
# field set to "server". The build-key-server
# script in the easy-rsa folder will do this.
;ns-cert-type server
# If a tls-auth key is used on the server
# then every client must also have the key.
tls-auth ta.key 1
# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
;cipher x
cipher AES-128-CBC
auth SHA256
key-direction 1
# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo
# Set log file verbosity.
verb 3
# Silence repeating messages
;mute 20
[/oconf]
ROUTER / OPENVPN ROUTE
Code: Select all
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.1 0.0.0.0 UG 0 0 0 enp2s0
10.6.0.0 192.168.254.1 255.255.255.0 UG 0 0 0 enp1s0
10.6.0.0 * 255.255.255.0 U 0 0 0 tun1
10.6.1.0 192.168.254.1 255.255.255.0 UG 0 0 0 enp1s0
10.6.1.0 * 255.255.255.0 U 0 0 0 tun0
10.8.0.0 10.8.0.5 255.255.255.0 UG 0 0 0 tun2
10.8.0.5 * 255.255.255.255 UH 0 0 0 tun2
link-local * 255.255.0.0 U 1000 0 0 enp1s0
192.168.1.0 * 255.255.255.0 U 0 0 0 enp2s0
192.168.100.0 10.8.0.5 255.255.255.0 UG 0 0 0 tun2
192.168.102.0 10.8.0.5 255.255.255.0 UG 0 0 0 tun2
192.168.254.0 * 255.255.255.0 U 0 0 0 enp1s0Code: Select all
enp1s0 Link encap:Ethernet HWaddr 18:d6:c7:03:23:5e
inet addr:192.168.254.1 Bcast:192.168.254.255 Mask:255.255.255.0
inet6 addr: fe80::1ad6:c7ff:fe03:235e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16292 errors:0 dropped:5 overruns:0 frame:0
TX packets:20013 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1917068 (1.9 MB) TX bytes:15745946 (15.7 MB)
enp2s0 Link encap:Ethernet HWaddr 88:d7:f6:3d:78:a2
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::8ad7:f6ff:fe3d:78a2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29048 errors:0 dropped:0 overruns:0 frame:0
TX packets:20630 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:23367920 (23.3 MB) TX bytes:2395403 (2.3 MB)
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:65536 Metric:1
RX packets:808 errors:0 dropped:0 overruns:0 frame:0
TX packets:808 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:62990 (62.9 KB) TX bytes:62990 (62.9 KB)
tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.6.1.1 P-t-P:10.6.1.1 Mask:255.255.255.0
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
tun1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.6.0.1 P-t-P:10.6.0.1 Mask:255.255.255.0
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:980 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:72775 (72.7 KB) TX bytes:0 (0.0 B)
tun2 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.6 P-t-P:10.8.0.5 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)ROUTER / OPENVPN IPTABLES (filter and nat)
Code: Select all
Chain INPUT (policy ACCEPT 6370 packets, 6772K bytes)
pkts bytes target prot opt in out source destination
302 20546 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0
3 246 ACCEPT udp -- enp2s0 * 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:1194
0 0 ACCEPT udp -- enp2s0 * 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:1195
0 0 ACCEPT udp -- enp1s0 * 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:1194
0 0 ACCEPT udp -- enp1s0 * 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:1195
0 0 ACCEPT all -- tun+ * 0.0.0.0/0 0.0.0.0/0
438 29065 SSH_ROUTER tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:2222
Chain FORWARD (policy ACCEPT 2872 packets, 416K bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- tun+ * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT all -- tun+ enp1s0 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
0 0 ACCEPT all -- tun+ enp2s0 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
0 0 ACCEPT all -- enp1s0 tun+ 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
0 0 ACCEPT all -- enp2s0 tun+ 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
Chain OUTPUT (policy ACCEPT 4848 packets, 426K bytes)
pkts bytes target prot opt in out source destination
Chain SSH_ROUTER (1 references)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- * * 122.3.87.161 0.0.0.0/0
0 0 ACCEPT all -- * * 124.106.81.31 0.0.0.0/0
0 0 ACCEPT all -- * * 10.6.1.0/24 0.0.0.0/0
0 0 ACCEPT all -- * * 10.6.0.0/24 0.0.0.0/0
438 29065 ACCEPT all -- * * 192.168.254.0/24 0.0.0.0/0
0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0
Chain PREROUTING (policy ACCEPT 1161 packets, 87578 bytes)
pkts bytes target prot opt in out source destination
Chain INPUT (policy ACCEPT 286 packets, 20681 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 396 packets, 26249 bytes)
pkts bytes target prot opt in out source destination
Chain POSTROUTING (policy ACCEPT 396 packets, 26249 bytes)
pkts bytes target prot opt in out source destination
133 12419 MASQUERADE all -- * enp2s0 192.168.254.0/24 0.0.0.0/0
0 0 MASQUERADE all -- * enp2s0 10.6.0.0/24 0.0.0.0/0
0 0 MASQUERADE all -- * enp2s0 10.6.1.0/24 0.0.0.0/0
on my Mac using Tunnelblick:
MAC CLIENT IFCONFIG (utun0 as the VPN interface)
Code: Select all
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=27<RXCSUM,TXCSUM,VLAN_MTU,TSO4>
ether 34:15:9e:23:1e:80
nd6 options=1<PERFORMNUD>
media: autoselect
status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:26:bb:0a:71:92
inet 192.168.43.99 netmask 0xffffff00 broadcast 192.168.43.255
nd6 options=1<PERFORMNUD>
media: autoselect
status: active
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 34:15:9e:ff:fe:23:1e:80
nd6 options=1<PERFORMNUD>
media: autoselect <full-duplex>
status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
ether 02:26:bb:0a:71:92
media: autoselect
status: inactive
[color=#FF0000]utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
inet 10.6.0.4 --> 10.6.0.4 netmask 0xffffff00[/color] Code: Select all
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.43.1 UGSc 13 0 en1
10.6/24 10.6.0.4 UGSc 2 0 utun0
10.6.0.4 10.6.0.4 UH 1 0 utun0
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 5 21263 lo0
169.254 link#5 UCS 0 0 en1
192.168.43 link#5 UCS 1 0 en1
192.168.43.1/32 link#5 UCS 1 0 en1
192.168.43.1 8:23:b2:e3:ab:ca UHLWIir 12 110 en1 1180
192.168.43.99/32 link#5 UCS 0 0 en1
192.168.43.255 ff:ff:ff:ff:ff:ff UHLWbI 0 3 en1
192.168.254 10.6.0.1 UGSc 1 0 utun0
224.0.0 link#5 UmCS 2 0 en1
224.0.0.1 1:0:5e:0:0:1 UHmLWI 0 49 en1
224.0.0.251 1:0:5e:0:0:fb UHmLWI 0 0 en1
255.255.255.255/32 link#5 UCS 0 0 en1
Internet6:
Destination Gateway Flags Netif Expire
::1 ::1 UHL lo0
fe80::%lo0/64 fe80::1%lo0 UcI lo0
fe80::1%lo0 link#1 UHLI lo0
ff01::%lo0/32 ::1 UmCI lo0
ff01::%en0/32 link#4 UmCI en0
ff02::%lo0/32 ::1 UmCI lo0
ff02::%en0/32 link#4 UmCI en0
Code: Select all
kss1xmac:~ kss1x$ ping -c 5 10.6.0.4
PING 10.6.0.4 (10.6.0.4): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
--- 10.6.0.4 ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
kss1xmac:~ kss1x$ ping -c 5 192.168.254.1
PING 192.168.254.1 (192.168.254.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
--- 192.168.254.1 ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
kss1xmac:~ kss1x$ ping -c 5 192.168.254.254
PING 192.168.254.254 (192.168.254.254): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Code: Select all
No. Time Source Destination Protocol port Length Info
12 36.643792576 10.6.0.4 10.6.0.4 ICMP 12 84 Echo (ping) request id=0x5a2b, seq=0/0, ttl=64 (no response found!)
Frame 12: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 10.6.0.4
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
13 37.629393082 10.6.0.4 10.6.0.4 ICMP 13 84 Echo (ping) request id=0x5a2b, seq=1/256, ttl=64 (no response found!)
Frame 13: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 10.6.0.4
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
14 38.645193443 10.6.0.4 10.6.0.4 ICMP 14 84 Echo (ping) request id=0x5a2b, seq=2/512, ttl=64 (no response found!)
Frame 14: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 10.6.0.4
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
16 39.639983712 10.6.0.4 10.6.0.4 ICMP 16 84 Echo (ping) request id=0x5a2b, seq=3/768, ttl=64 (no response found!)
Frame 16: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 10.6.0.4
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
18 40.632837625 10.6.0.4 10.6.0.4 ICMP 18 84 Echo (ping) request id=0x5a2b, seq=4/1024, ttl=64 (no response found!)
Frame 18: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 10.6.0.4
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
49 122.063250260 10.6.0.4 192.168.254.1 ICMP 49 84 Echo (ping) request id=0x602b, seq=0/0, ttl=64 (no response found!)
Frame 49: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 192.168.254.1
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
50 122.999950926 10.6.0.4 192.168.254.1 ICMP 50 84 Echo (ping) request id=0x602b, seq=1/256, ttl=64 (no response found!)
Frame 50: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 192.168.254.1
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
51 124.002003315 10.6.0.4 192.168.254.1 ICMP 51 84 Echo (ping) request id=0x602b, seq=2/512, ttl=64 (no response found!)
Frame 51: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 192.168.254.1
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
52 125.006362913 10.6.0.4 192.168.254.1 ICMP 52 84 Echo (ping) request id=0x602b, seq=3/768, ttl=64 (no response found!)
Frame 52: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 192.168.254.1
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
53 126.040136811 10.6.0.4 192.168.254.1 ICMP 53 84 Echo (ping) request id=0x602b, seq=4/1024, ttl=64 (no response found!)
Frame 53: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 192.168.254.1
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
62 188.237146466 10.6.0.4 192.168.254.254 ICMP 62 84 Echo (ping) request id=0x622b, seq=0/0, ttl=64 (no response found!)
Frame 62: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 192.168.254.254
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
63 189.285430100 10.6.0.4 192.168.254.254 ICMP 63 84 Echo (ping) request id=0x622b, seq=1/256, ttl=64 (no response found!)
Frame 63: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 192.168.254.254
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
64 190.275569018 10.6.0.4 192.168.254.254 ICMP 64 84 Echo (ping) request id=0x622b, seq=2/512, ttl=64 (no response found!)
Frame 64: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 192.168.254.254
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
65 191.258359198 10.6.0.4 192.168.254.254 ICMP 65 84 Echo (ping) request id=0x622b, seq=3/768, ttl=64 (no response found!)
Frame 65: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 192.168.254.254
Internet Control Message Protocol
No. Time Source Destination Protocol port Length Info
66 192.251237194 10.6.0.4 192.168.254.254 ICMP 66 84 Echo (ping) request id=0x622b, seq=4/1024, ttl=64 (no response found!)
Frame 66: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Raw packet data
Internet Protocol Version 4, Src: 10.6.0.4, Dst: 192.168.254.254
Internet Control Message Protocol
would appreciate help on this.