Solved

Routing problems in Debian virtual machine

Posted on 2008-11-02
12
1,614 Views
Last Modified: 2013-12-06
I have a Debian virtual vmware server. Earlier it was existing on a windows 2003 host system with vmware server 1.7 installed. The trial period of windows 2003 ended and I installed Debian as the host machine instead, now with vmware server 2.0 instead. I had copied the virtual debian server aside and copied it back in again to the new host machine.

Before I did all this I had the virtual server standing in 4 networks(when it was vmware server 1.7 I was using). There was 1 bridged network out to the physical ethernet card, and 3 virtual network. The virtual vmware server routed between all these networks and also acted as a dhcp server for all virtual networks(not the bridged one).

After copying the virtual debian server back to the new host machine with virtual server 2.0 the routing is now working only between the virtual networks and not from a virtual network and through the bridged network to the physical network. The virtual networks are host only networks where vmware dhcp is disabled and the virtual debian server is acting as the dhcp server.  The network that is bridged to the physical network is a normal bridged network.

All works fine, but the routing out to the bridged network and forward to the phyical network. I have tried to turn forwarding on in the host machine as well through /etc/sysctl.conf and running sysctl -p

Routing TO the bridged network card works, but not to other nodes in the physical network that are connected to that bridged card.

It worked in vmware server 1.7 but not vmware server 2.0.

Any one have any ideas?
0
Comment
Question by:itnifl
12 Comments
 

Expert Comment

by:voidzzz
Comment Utility
1. Try the basic troubleshooting by doing ping and trace route to physical network from your virtual OS. Find out where it ends / timed out.
2. have you enable forwarding and route in your virtual machine to physical network ?
3. it's very basic but some times it does solve my problem by restart your network after changes on network related settings.

hope it helps
0
 
LVL 10

Expert Comment

by:kyleb84
Comment Utility
Make sure your hosts on the physical LAN have routes back to the virtual networks via that Router.
0
 
LVL 2

Author Comment

by:itnifl
Comment Utility
Didnt help to make a route back from the physical LAN. It worked before.
I have enabled forwarding on both the virtual debian server that routes between the pysica network and the virtual ones, and also have enabled forwarding on physical debian server that is the host OS for my vmware server.

I have restarted all the virtual nodes, virtual server and the host os several times.

Traceroute only shows what I have been explaining in the text, the package never leaves the gateway if it is from the vmware network to the physical network. It never leaves the gateway if it is from the physical network to the vmware network.

But between different vmware network connected by the routing server, it both traces and pings without problems. They are also logically different.
0
 
LVL 2

Author Comment

by:itnifl
Comment Utility
When I restart the core service when standing at /etc/init.d/ I get the following result:

./vmware-core restart
Stopping VMware services:
   VMware Authentication Daemon                                        done
   VM communication interface socket family:                           done
   Virtual machine communication interface                             done
   Virtual machine monitor                                             done
   Bridged networking on /dev/vmnet0                                   done
   Host network detection                                              done
   Host-only networking on /dev/vmnet1                                 done
   Host-only networking on /dev/vmnet2                                 done
   Host-only networking on /dev/vmnet3                                 done
   DHCP server on /dev/vmnet4                                          done
   Host-only networking on /dev/vmnet4                                 done
   Host-only networking on /dev/vmnet5                                 done
   DHCP server on /dev/vmnet8                                          done
   NAT service on /dev/vmnet8                                          done
   Host-only networking on /dev/vmnet8                                 done
   Virtual ethernet                                                   failed

The lasy one fails. That might have something to do with my problems with the bridging and routing? Anyway, need to fix that problem t, but dont know where to start.
0
 
LVL 8

Expert Comment

by:eager
Comment Utility
Have you run vmware-config.pl?  Does it complete without errors?
0
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 
LVL 2

Author Comment

by:itnifl
Comment Utility
Last time I ran vmware-config.pl it was all ok. Havent run it in a while since I have been editing the names and functions of the virtual svitsjes manually. I have turned off the DHCP service on most of the virtual svitsjes. If I remember corectly it is done in /etc/vmware/locations  (yes, I know that file holds more data, but it wasnt touched). The operation of the virtual svitsjes are normal.
0
 
LVL 8

Expert Comment

by:eager
Comment Utility
Well, it's apparent that starting VMware networking failed.  

I'm using VMware Workstation, but I believe that the log files are the same in VMware server.
Look in /var/log/vnetlib for error messages.  You can also run "sh -x /etc/init.d/vmware restart" and see exactly which commands are failing and attempt to run them manually to see what error messages are issued.

The VMware drivers are built for specific kernel versions.  It's unclear what you mean by copying the virtual server from one machine to another.  If you copy a VMware installation from one system to another, unless they have identical kernels, you need to rebuild the drivers by running vmware-config.pl.  
0
 
LVL 2

Author Comment

by:itnifl
Comment Utility
Masternode:~# more /var/log/vnetlib
/var/log/vnetlib: No such file or directory

Masternode:~# ls /var/log/vmware
hostd-0.log  hostd-3.log  hostd-6.log  hostd-9.log  hostd-trace.log
hostd-1.log  hostd-4.log  hostd-7.log  hostd-index  webAccess
hostd-2.log  hostd-5.log  hostd-8.log  hostd.log

Masternode:~# /etc/init.d/vmware restart
Stopping VMware autostart virtual machines:
   Virtual machines                                                              done
Stopping VMware management services:
   VMware Virtual Infrastructure Web Access
   VMware Server Host Agent                                            done
Stopping VMware services:
   VMware Authentication Daemon                                     done
   VM communication interface socket family:                     done
   Virtual machine communication interface                         done
   Virtual machine monitor                                                    done
   Bridged networking on /dev/vmnet0                                 done
   Host network detection                                                    done
   Host-only networking on /dev/vmnet1                              done
   Host-only networking on /dev/vmnet2                               done
   Host-only networking on /dev/vmnet3                                done
   DHCP server on /dev/vmnet4                                              done
   Host-only networking on /dev/vmnet4                                 done
   Host-only networking on /dev/vmnet5                                 done
   DHCP server on /dev/vmnet8                                               done
   NAT service on /dev/vmnet8                                               done
   Host-only networking on /dev/vmnet8                                 done
   Virtual ethernet                                                                    done
Starting VMware services:
   Virtual machine monitor                                                      done
   Virtual machine communication interface                             done
   VM communication interface socket family:                           done
   Virtual ethernet                                                                     done
   Bridged networking on /dev/vmnet0                                    done
   Host-only networking on /dev/vmnet1 (background)                    done
   Host-only networking on /dev/vmnet2 (background)                    done
   Host-only networking on /dev/vmnet3 (background)                    done
   Host-only networking on /dev/vmnet4 (background)                    done
   DHCP server on /dev/vmnet4                                                        done
   Host-only networking on /dev/vmnet5 (background)                    done
   Host-only networking on /dev/vmnet8 (background)                    done
   DHCP server on /dev/vmnet8                                                       done
   NAT service on /dev/vmnet8                                                        done
   VMware Server Authentication Daemon (background)               done
   Shared Memory Available                                                            done
Starting VMware management services:
   VMware Server Host Agent (background)                               done
   VMware Virtual Infrastructure Web Access
Starting VMware autostart virtual machines:
   Virtual machines                                                                        done
Masternode:~#

It all looks nice. All the networks are working fine. None of the logs tell me anything. I get the error only when I run "vmware-core restart".

I will try to ecplain the setup here little more easy.
1. I have a physical Debian machine with Vmware Server 2.0 Installed(not moved, installed).

2. On that server I have a VIRTUAL Debian server installed that is connected to 4 Virtual networks, one that is bridged to my physical adapeter eth1.

3. Both the physical and the Virtual vmware servers have routing enabled.

4. The Virtual Debian server was moved from a vmware server 1.7 system on a windows 2003 system to this vmware server 2.0 on a Debian system.

5. Routing over the bridged interface between the physical network that the physical server is on and the virtual network that the virtual server is on, worked before. But after setting up the vmware server 2.0 system it doesnt work anymore.

6. Routing works between the different virtual networks that also are assigned different logical IP-networks. But not from those networks out to the physical network over the bridged interface. The can route to the bridged interface, but not through it. The same thing happensfrom the physical not to the bridged interface. Can communicate / ping with the bridged interface, but cannot get any packets routed further.


0
 
LVL 8

Expert Comment

by:eager
Comment Utility
Do you have a firewall running on the host or guest systems?  Run "/etc/init.d/iptables stop" and see if you are able to ping the outside network.

By default, ping will use the default interface.  You can force it to use a specific interface by specifying '-I <interface>".  On your guest system, try running ping specifying the interface which is bridged.

Run "route" on the guest system.  It should list the bridged interface as the default destination.

0
 
LVL 2

Author Comment

by:itnifl
Comment Utility
Didnt find iptables as a script under /etc/init.d/ in my Debian host system or vmware system.
But I can paste the rules here, they are very simple, they allow all at the host system:

Masternode:/etc/init.d# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination


And on the guest system(all accept, but with logging):

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
LOG        0    --  anywhere             anywhere            LOG level debug prefix `INPUT-log'

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
LOG        0    --  anywhere             anywhere            LOG level debug prefix `FORWARD-log'

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
LOG        0    --  anywhere             anywhere            LOG level debug prefix `OUTPUT-log'

Listing IP Config for a XP guest system in one of the virtual networks:

Windows IP Configuration


Windows IP Configuration


Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : Nodenet
        IP Address. . . . . . . . . . . . : 192.168.10.5
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.10.1


Pinging the guest debian system that acts as a router between the physical network and all the vm-networks(I am pinging the bridged interface on another logica ip-net then the origin, this has always worked):

C:\Documents and Settings\Atle>ping 192.168.1.100

Pinging 192.168.1.100 with 32 bytes of data:

Reply from 192.168.1.100: bytes=32 time=10ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 10ms, Average = 2ms


Pinging another XP system on another logical vm ip net(via the guest debian router, this has always worked):

C:\Documents and Settings\Atle>ping 172.16.0.3

Pinging 172.16.0.3 with 32 bytes of data:

Reply from 172.16.0.3: bytes=32 time<1ms TTL=127
Reply from 172.16.0.3: bytes=32 time<1ms TTL=127
Reply from 172.16.0.3: bytes=32 time<1ms TTL=127
Reply from 172.16.0.3: bytes=32 time<1ms TTL=127

Ping statistics for 172.16.0.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging a node on the physical network(the packge has to pass the bridged interface voa the guest debian router, this has never worked):

C:\Documents and Settings\Atle>ping 192.168.1.102

Pinging 192.168.1.102 with 32 bytes of data:

Request timed out.
Request timed out.

Ping statistics for 192.168.1.102:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C

Listing all log entries in /var/log that contain OUTPUT and filter the wanted destination (from 192.168.1.102 that I failed to ping earlier):
cd /var/log
grep OUTPUT * | grep DST=192.168.1.102 > All102.txt
more All102.txt
(this is while pinging 192.168.1.102 from a XP guest system continuesly):

syslog.0:Oct 22 05:53:19 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 05:58:20 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 06:03:29 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 06:08:31 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 06:13:32 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 06:18:39 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 06:23:44 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 06:28:39 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 06:33:51 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 06:38:59 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 06:44:01 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 06:49:03 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 06:54:10 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 06:59:16 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 07:04:20 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 07:09:22 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 07:14:20 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 07:19:32 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 07:24:32 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 07:29:40 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70
syslog.0:Oct 22 07:34:41 Deb-i86a kernel: OUTPUT-logIN= OUT=eth5 SRC=192.168.1.100 DST=192.168.1.102 LEN=90 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=70

The date on the system is wrong. Todays date on the system is october 22.

Trying INPUT as well:
Deb-i86a:/var/log# grep INPUT * | grep DST=192.168.1.102 > All102.txt
(no result).


Trying FORWARD as well:
grep FORWARD * | grep DST=192.168.1.102 > All102.txt

syslog:Oct 22 14:14:17 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=551 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=28928
syslog:Oct 22 14:14:22 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=552 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=29184
syslog:Oct 22 14:14:28 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=553 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=29440
syslog:Oct 22 14:14:33 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=554 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=29696
syslog:Oct 22 14:14:39 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=555 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=29952
syslog:Oct 22 14:14:44 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=560 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=30208
syslog:Oct 22 14:14:50 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=561 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=30464
syslog:Oct 22 14:14:55 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=562 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=30720
syslog:Oct 22 14:15:01 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=563 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=30976
syslog:Oct 22 14:15:06 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=565 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=31232
syslog:Oct 22 14:15:12 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=573 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=31488
syslog:Oct 22 14:15:17 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=574 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=31744
syslog:Oct 22 14:15:23 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=577 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=32000
syslog:Oct 22 14:15:28 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=578 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=32256
syslog:Oct 22 14:15:34 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=579 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=32512
syslog:Oct 22 14:15:39 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=580 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=32768
syslog:Oct 22 14:15:45 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=581 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=33024
syslog:Oct 22 14:15:50 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=582 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=33280
syslog:Oct 22 14:15:56 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=583 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=33536
syslog:Oct 22 14:16:01 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=584 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=33792
syslog:Oct 22 14:16:07 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=585 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=34048
syslog:Oct 22 14:16:12 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.102 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=586 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=34304

Looks like there is some action here.
Checking the routes at 192.168.1.102 (IP address on the physical network for the host system):
Masternode:/etc/init.d# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
172.16.100.0    *               255.255.255.0   U     0      0        0 vmnet5
192.168.241.0   *               255.255.255.0   U     0      0        0 vmnet4
192.168.1.0     *               255.255.255.0   U     0      0        0 eth1
172.16.125.0    *               255.255.255.0   U     0      0        0 vmnet8
192.168.10.0    *               255.255.255.0   U     0      0        0 vmnet1
192.168.10.0    *               255.255.255.0   U     0      0        0 vmnet2
10.1.2.0        *               255.255.255.0   U     0      0        0 vmnet3

Looks like there is a oute back?
I will ping my laptop instead(192.168.1.199) and I am taking care that it has a route back:

C:\Windows\system32>route add 10.1.2.0 mask 255.255.255.0 192.168.0.100
 OK!
C:\Windows\system32>route add 192.168.10.0 mask 255.255.255.0 192.168.0.100
 OK!
C:\Windows\system32>route add 172.16.0.0 mask 255.255.255.0 192.168.0.100
 OK!

Not getting reply, checking forward logs again:
grep FORWARD * | grep DST=192.168.1.199 > All199.txt

:Oct 22 14:22:36 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.199 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=673 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=52480
syslog:Oct 22 14:22:42 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.199 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=674 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=52736
syslog:Oct 22 14:22:47 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.199 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=675 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=52992
syslog:Oct 22 14:22:53 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.199 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=676 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=53248
syslog:Oct 22 14:22:58 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.199 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=677 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=53504
syslog:Oct 22 14:23:04 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.199 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=678 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=53760
syslog:Oct 22 14:23:09 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.199 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=679 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=54016
syslog:Oct 22 14:23:15 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.199 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=680 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=54272
syslog:Oct 22 14:23:20 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.199 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=681 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=54528
syslog:Oct 22 14:23:26 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.199 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=682 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=54784
syslog:Oct 22 14:23:31 Deb-i86a kernel: FORWARD-logIN=eth7 OUT=eth5 SRC=192.168.10.5 DST=192.168.1.199 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=683 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=55040

So it looks like theyr going through(the packets)! And cant see NO reason why they are not getting back to the origin.
0
 
LVL 2

Accepted Solution

by:
itnifl earned 0 total points
Comment Utility
Turns out I found the probem. I guess it is not possible to find it by the text here.
Every virtual network connects to the host via virtual NIC's with assigned IP'addresses. Default is that they all are of type xxx.xxx.xxx.1. I had set the guest debian router with the same ip-adresses for each virtual net, crashing with the IP's on the host systems virtual cards. I changed the IP's on the host systems virtual cards to xxx.xxx.xxx.4 and let the guest use xxx.xxx.xxx.1. It solved the problem.

I became aware of this when I tried to enter the host system via samba on 10.1.2.1. It seemed to flicker between the host and the guest. No errors were ever shown. Dont they warn of ip-address conflicts in linux?
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

When we have a dead host and we lose all connections to the ESXi, and we need to find a way to move all VMs from that dead ESXi host.
Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now