I am writing for the first time in this forum but it is the need of help directing me here so Hello to everybody.
Since April I have running SLES 12 Virtualized Server and problem is simple Destination Host Unreachable
Sniffing for source:
rcnetwork status
wicked.service - wicked managed network interfaces
Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled)
Active: active (exited) since Fri 2015-08-07 15:40:02 BST; 33min ago
Process: 1671 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS)
Main PID: 1671 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/wicked.service
Aug 07 15:40:02 cloud wicked[1671]: lo up
Aug 07 15:40:02 cloud wicked[1671]: br0 up
Aug 07 15:40:02 cloud wicked[1671]: bond0 enslaved
Aug 07 15:40:02 cloud wicked[1671]: eth0 enslaved
Aug 07 15:40:02 cloud wicked[1671]: eth1 enslaved
netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 177.172.0.1 0.0.0.0 UG 0 0 0 br0
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
10.0.1.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr1
177.172.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
54 is www
ip route get 177.172.0.54
177.172.0.54 dev br0 src 177.172.0.10
cache
ping 177.172.0.54
PING 177.172.0.54 (177.172.0.54) 56(84) bytes of data.
From 177.172.0.10 icmp_seq=1 Destination Host Unreachable
Where are these commands being executed? I’m guessing some kind of host,
but maybe they’re on the guest. Also, which box is the SLES 12 box, the
host or the guest (or both)? Is the ‘www’ server one of these, or is just
another system attempting to be accessed?
Have you tried simplifying networking to see if thing scan ever work? For
example, removing the bond0 device?
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
It is on server and the virtualized partitions
The system is connected by two eth cards bonded together and to top of that is bridge so I have two private and public network for whole the system.
All network works just fine but it was not simple to get it working, yes i tried to use only bridge but it did not work as I expected, bond was the solution.
Reads are coming from host system and the host and virtual systems are the same SLES 12 based on KVM and qemu together.
The idea is to run apache on host system where problem gets its appearance.
It is on server and the virtualized partitions
The system is connected by two eth cards bonded together and to top of that is bridge so I have two private and public network for whole the system.
All network works just fine but it was not simple to get it working, yes i tried to use only bridge but it did not work as I expected, bond was the solution.
Reads are coming from host system and the host and virtual systems are the same SLES 12 based on KVM and qemu together.
The idea is to run apache on host system where problem gets its appearance.
Marek[/QUOTE]
I have taken down bond0 and no change found.
On novell websites I found info in ICMP codes suggestions
problem with ARP header problem so I check it out.
[QUOTE=MKTS;29095]I have taken down bond0 and no change found.
On novell websites I found info in ICMP codes suggestions
problem with ARP header problem so I check it out.
Regs
Marek[/QUOTE]
solution I hope this will help for others with the same problem
ip neighbor
177.172.0.1 dev br0 lladdr e4:f4:c6:8b:14:37 REACHABLE
10.0.0.51 dev virbr0 lladdr 52:54:00:19:0c:93 STALE
10.0.0.41 dev virbr0 lladdr 52:54:00:fe:d1:c1 STALE
10.0.0.31 dev virbr0 lladdr 52:54:00:ad:bb:8b STALE
177.172.0.54 dev br0 FAILED
ip addr add 177.172.0.54 brd + dev br0
ping 177.172.0.54
PING 177.172.0.54 (177.172.0.54) 56(84) bytes of data.
64 bytes from 177.172.0.54: icmp_seq=1 ttl=64 time=0.028 ms
64 bytes from 177.172.0.54: icmp_seq=2 ttl=64 time=0.024 ms
