Re: IP weirdness
Well, in that case, Lutz, we'll all just blame you then. :-)
DJ
Lutz Hamann wrote:
Explanation accepted, Dave !
And I should know it - because I am one of those (admins) :-)
I always use the $TTL 86400 (default) in our z/OS BIND9-
implementations
ciao Lutz
-
Lutz Hamann
BETA Systems Software AG
z/OS System Engineering
-
Dave Jones
<[EMAIL PROTECTED]
are.com> To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: IP weirdness
08.08.2005 14:32
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
You're welcome, Lutz.
There was a discussion over the weekend on the VM-ESA list about why it
takes so long for DNS updates to propagate. It has to do with the TTL
(time to live) values set by various DNS administrators.
Have a good week.
DJ
Lutz Hamann wrote:
Thank you, Dave ...
I could never imagine that those DNS-updates take more than
2 days :-) But let's wait ...
But at least I can acces the site via their IP-address.
ciao Lutz
-
Lutz Hamann
BETA Systems Software AG
z/OS System Engineering
-
Dave Jones
<[EMAIL PROTECTED]
are.com>
To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port
cc
<[EMAIL PROTECTED]
IST.EDU>
Subject
Re: IP weirdness
08.08.2005 14:12
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
Hi, Lutz.
www.vm.ibm.com has moved from 204.146.134.198 to 204.146.134.18.
DNS updates are working their way through the Internet, so it's not just
a German/European problem.
DJ
Lutz Hamann wrote:
Thank you for your explanation and the URL, Vic.
I'd like to check it - if www.vm.ibm.com goes online again :-)
It seems to be off-line since last Friday or Saturday :-(
Does anybody know the reason - or is it only specific German/European
problem ?
ciao Lutz
-
Lutz Hamann
BETA Systems Software AG
z/OS System Engineering
-
Vic Cross
<[EMAIL PROTECTED]
au>
To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port
cc
<[EMAIL PROTECTED]
IST.EDU>
Subject
Re: IP weirdness
06.08.2005 16:24
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
On Saturday 06 August 2005 04:38, Neale Ferguson wrote:
NF> I have a guest LAN that connects a number of guests.
NF> All but one of the guests can talk to each other, except one
NF> (I'll call X) which can only talk to the default gateway. If I ping
the
NF> others from X I get no response. The same goes when I go from the any
NF> other of the guests except R to X.
NF> We are z/VM 4.4 0404. Guest X is SLES9 SP2, Guest R is SLES7, other
NF> guests are Debian.
There are a few VMLAN fixes out since 0404RSU. From recent experience
I'd
suggest you get right up to date and try again (the qeth driver on the
guests
other than X might need an update as well, although it strikes me as odd
that
the SLES 7 system works talking to the SLES 9 SP2 given that its qeth is
probably older than the Debians'...).
The z/VM team maintains an excellent resource that talks about (among
other
things) z/VM maintenance levels in support of virtual networking:
http://www.vm.ibm.com/virtualnetwork
Look for the "Virtual Switch and Guest LAN CP Maintenance levels" link.
NF> The other weirdness I see is that all the guests have a subnet mask
of
NF> 255.255.255.192 but Q LAN DETAILS reports everyone as 255.255.255.0.
No need to be concerned about this. At earlier levels the display shows
the
natural network mask (i.e. as if you weren't subnetting) instead of the
actual subnet mask in use. On z/VM 5.1 the subnet mask display is
removed
(replaced by the MAC address, like the multicast display).
Chee
Re: IP weirdness
Explanation accepted, Dave !
And I should know it - because I am one of those (admins) :-)
I always use the $TTL 86400 (default) in our z/OS BIND9-
implementations
ciao Lutz
-
Lutz Hamann
BETA Systems Software AG
z/OS System Engineering
-
Dave Jones
<[EMAIL PROTECTED]
are.com> To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: IP weirdness
08.08.2005 14:32
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
You're welcome, Lutz.
There was a discussion over the weekend on the VM-ESA list about why it
takes so long for DNS updates to propagate. It has to do with the TTL
(time to live) values set by various DNS administrators.
Have a good week.
DJ
Lutz Hamann wrote:
> Thank you, Dave ...
>
> I could never imagine that those DNS-updates take more than
> 2 days :-) But let's wait ...
>
> But at least I can acces the site via their IP-address.
>
>
> ciao Lutz
>
>
> -
> Lutz Hamann
> BETA Systems Software AG
> z/OS System Engineering
> -
>
>
>
> Dave Jones
> <[EMAIL PROTECTED]
> are.com>
To
> Sent by: Linux on LINUX-390@VM.MARIST.EDU
> 390 Port
cc
> <[EMAIL PROTECTED]
> IST.EDU>
Subject
>Re: IP weirdness
>
> 08.08.2005 14:12
>
>
> Please respond to
> Linux on 390 Port
> <[EMAIL PROTECTED]
> IST.EDU>
>
>
>
>
>
>
> Hi, Lutz.
>
> www.vm.ibm.com has moved from 204.146.134.198 to 204.146.134.18.
>
> DNS updates are working their way through the Internet, so it's not just
> a German/European problem.
>
>
> DJ
>
> Lutz Hamann wrote:
>
>>Thank you for your explanation and the URL, Vic.
>>
>>I'd like to check it - if www.vm.ibm.com goes online again :-)
>>It seems to be off-line since last Friday or Saturday :-(
>>
>>Does anybody know the reason - or is it only specific German/European
>>problem ?
>>
>>
>> ciao Lutz
>>
>>-
>>Lutz Hamann
>>BETA Systems Software AG
>>z/OS System Engineering
>>-
>>
>>
>>
>> Vic Cross
>> <[EMAIL PROTECTED]
>> au>
>
> To
>
>> Sent by: Linux on LINUX-390@VM.MARIST.EDU
>> 390 Port
>
> cc
>
>> <[EMAIL PROTECTED]
>> IST.EDU>
>
> Subject
>
>> Re: IP weirdness
>>
>> 06.08.2005 16:24
>>
>>
>> Please respond to
>> Linux on 390 Port
>> <[EMAIL PROTECTED]
>> IST.EDU>
>>
>>
>>
>>
>>
>>
>>On Saturday 06 August 2005 04:38, Neale Ferguson wrote:
>>NF> I have a guest LAN that connects a number of guests.
>>
>>NF> All but one of the guests can talk to each other, except one
>>NF> (I'll call X) which can only talk to the default gateway. If I ping
>
> the
>
>>NF> others from X I get no response. The same goes when I go from the any
>>NF> other of the guests except R to X.
>>
>>NF> We are z/VM 4.4 0404. Guest X is SLES9 SP2, Guest R is SLES7, other
>>NF> guests are Debian.
>>
>>There are a few VMLAN fixes out since 0404RSU. From recent experience
>
> I'd
>
>>suggest you get right up to date and try again (the qeth driver on the
>>guests
>>other than X might need an update as well, although it strikes me as odd
>>that
>>the SLES 7 system works talking to the SLES 9 SP2 given that its qeth is
>>probably older than the Debians'...).
>>
>>The z/VM team maintains an
Re: IP weirdness
You're welcome, Lutz.
There was a discussion over the weekend on the VM-ESA list about why it
takes so long for DNS updates to propagate. It has to do with the TTL
(time to live) values set by various DNS administrators.
Have a good week.
DJ
Lutz Hamann wrote:
Thank you, Dave ...
I could never imagine that those DNS-updates take more than
2 days :-) But let's wait ...
But at least I can acces the site via their IP-address.
ciao Lutz
-
Lutz Hamann
BETA Systems Software AG
z/OS System Engineering
-
Dave Jones
<[EMAIL PROTECTED]
are.com> To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: IP weirdness
08.08.2005 14:12
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
Hi, Lutz.
www.vm.ibm.com has moved from 204.146.134.198 to 204.146.134.18.
DNS updates are working their way through the Internet, so it's not just
a German/European problem.
DJ
Lutz Hamann wrote:
Thank you for your explanation and the URL, Vic.
I'd like to check it - if www.vm.ibm.com goes online again :-)
It seems to be off-line since last Friday or Saturday :-(
Does anybody know the reason - or is it only specific German/European
problem ?
ciao Lutz
-
Lutz Hamann
BETA Systems Software AG
z/OS System Engineering
-
Vic Cross
<[EMAIL PROTECTED]
au>
To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port
cc
<[EMAIL PROTECTED]
IST.EDU>
Subject
Re: IP weirdness
06.08.2005 16:24
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
On Saturday 06 August 2005 04:38, Neale Ferguson wrote:
NF> I have a guest LAN that connects a number of guests.
NF> All but one of the guests can talk to each other, except one
NF> (I'll call X) which can only talk to the default gateway. If I ping
the
NF> others from X I get no response. The same goes when I go from the any
NF> other of the guests except R to X.
NF> We are z/VM 4.4 0404. Guest X is SLES9 SP2, Guest R is SLES7, other
NF> guests are Debian.
There are a few VMLAN fixes out since 0404RSU. From recent experience
I'd
suggest you get right up to date and try again (the qeth driver on the
guests
other than X might need an update as well, although it strikes me as odd
that
the SLES 7 system works talking to the SLES 9 SP2 given that its qeth is
probably older than the Debians'...).
The z/VM team maintains an excellent resource that talks about (among
other
things) z/VM maintenance levels in support of virtual networking:
http://www.vm.ibm.com/virtualnetwork
Look for the "Virtual Switch and Guest LAN CP Maintenance levels" link.
NF> The other weirdness I see is that all the guests have a subnet mask
of
NF> 255.255.255.192 but Q LAN DETAILS reports everyone as 255.255.255.0.
No need to be concerned about this. At earlier levels the display shows
the
natural network mask (i.e. as if you weren't subnetting) instead of the
actual subnet mask in use. On z/VM 5.1 the subnet mask display is
removed
(replaced by the MAC address, like the multicast display).
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For LINUX-390 subscribe / signoff / archive access instructions,
send em
Re: IP weirdness
Thank you, Dave ...
I could never imagine that those DNS-updates take more than
2 days :-) But let's wait ...
But at least I can acces the site via their IP-address.
ciao Lutz
-
Lutz Hamann
BETA Systems Software AG
z/OS System Engineering
-
Dave Jones
<[EMAIL PROTECTED]
are.com> To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: IP weirdness
08.08.2005 14:12
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
Hi, Lutz.
www.vm.ibm.com has moved from 204.146.134.198 to 204.146.134.18.
DNS updates are working their way through the Internet, so it's not just
a German/European problem.
DJ
Lutz Hamann wrote:
> Thank you for your explanation and the URL, Vic.
>
> I'd like to check it - if www.vm.ibm.com goes online again :-)
> It seems to be off-line since last Friday or Saturday :-(
>
> Does anybody know the reason - or is it only specific German/European
> problem ?
>
>
> ciao Lutz
>
> -
> Lutz Hamann
> BETA Systems Software AG
> z/OS System Engineering
> -
>
>
>
> Vic Cross
> <[EMAIL PROTECTED]
> au>
To
> Sent by: Linux on LINUX-390@VM.MARIST.EDU
> 390 Port
cc
> <[EMAIL PROTECTED]
> IST.EDU>
Subject
>Re: IP weirdness
>
> 06.08.2005 16:24
>
>
> Please respond to
> Linux on 390 Port
> <[EMAIL PROTECTED]
> IST.EDU>
>
>
>
>
>
>
> On Saturday 06 August 2005 04:38, Neale Ferguson wrote:
> NF> I have a guest LAN that connects a number of guests.
>
> NF> All but one of the guests can talk to each other, except one
> NF> (I'll call X) which can only talk to the default gateway. If I ping
the
> NF> others from X I get no response. The same goes when I go from the any
> NF> other of the guests except R to X.
>
> NF> We are z/VM 4.4 0404. Guest X is SLES9 SP2, Guest R is SLES7, other
> NF> guests are Debian.
>
> There are a few VMLAN fixes out since 0404RSU. From recent experience
I'd
> suggest you get right up to date and try again (the qeth driver on the
> guests
> other than X might need an update as well, although it strikes me as odd
> that
> the SLES 7 system works talking to the SLES 9 SP2 given that its qeth is
> probably older than the Debians'...).
>
> The z/VM team maintains an excellent resource that talks about (among
other
> things) z/VM maintenance levels in support of virtual networking:
>
> http://www.vm.ibm.com/virtualnetwork
>
> Look for the "Virtual Switch and Guest LAN CP Maintenance levels" link.
>
> NF> The other weirdness I see is that all the guests have a subnet mask
of
> NF> 255.255.255.192 but Q LAN DETAILS reports everyone as 255.255.255.0.
>
> No need to be concerned about this. At earlier levels the display shows
> the
> natural network mask (i.e. as if you weren't subnetting) instead of the
> actual subnet mask in use. On z/VM 5.1 the subnet mask display is
removed
> (replaced by the MAC address, like the multicast display).
>
> Cheers,
> Vic Cross
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IP weirdness
Hi, Lutz.
www.vm.ibm.com has moved from 204.146.134.198 to 204.146.134.18.
DNS updates are working their way through the Internet, so it's not just
a German/European problem.
DJ
Lutz Hamann wrote:
Thank you for your explanation and the URL, Vic.
I'd like to check it - if www.vm.ibm.com goes online again :-)
It seems to be off-line since last Friday or Saturday :-(
Does anybody know the reason - or is it only specific German/European
problem ?
ciao Lutz
-
Lutz Hamann
BETA Systems Software AG
z/OS System Engineering
-
Vic Cross
<[EMAIL PROTECTED]
au>To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: IP weirdness
06.08.2005 16:24
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
On Saturday 06 August 2005 04:38, Neale Ferguson wrote:
NF> I have a guest LAN that connects a number of guests.
NF> All but one of the guests can talk to each other, except one
NF> (I'll call X) which can only talk to the default gateway. If I ping the
NF> others from X I get no response. The same goes when I go from the any
NF> other of the guests except R to X.
NF> We are z/VM 4.4 0404. Guest X is SLES9 SP2, Guest R is SLES7, other
NF> guests are Debian.
There are a few VMLAN fixes out since 0404RSU. From recent experience I'd
suggest you get right up to date and try again (the qeth driver on the
guests
other than X might need an update as well, although it strikes me as odd
that
the SLES 7 system works talking to the SLES 9 SP2 given that its qeth is
probably older than the Debians'...).
The z/VM team maintains an excellent resource that talks about (among other
things) z/VM maintenance levels in support of virtual networking:
http://www.vm.ibm.com/virtualnetwork
Look for the "Virtual Switch and Guest LAN CP Maintenance levels" link.
NF> The other weirdness I see is that all the guests have a subnet mask of
NF> 255.255.255.192 but Q LAN DETAILS reports everyone as 255.255.255.0.
No need to be concerned about this. At earlier levels the display shows
the
natural network mask (i.e. as if you weren't subnetting) instead of the
actual subnet mask in use. On z/VM 5.1 the subnet mask display is removed
(replaced by the MAC address, like the multicast display).
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IP weirdness
Thank you for your explanation and the URL, Vic.
I'd like to check it - if www.vm.ibm.com goes online again :-)
It seems to be off-line since last Friday or Saturday :-(
Does anybody know the reason - or is it only specific German/European
problem ?
ciao Lutz
-
Lutz Hamann
BETA Systems Software AG
z/OS System Engineering
-
Vic Cross
<[EMAIL PROTECTED]
au>To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: IP weirdness
06.08.2005 16:24
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
On Saturday 06 August 2005 04:38, Neale Ferguson wrote:
NF> I have a guest LAN that connects a number of guests.
NF> All but one of the guests can talk to each other, except one
NF> (I'll call X) which can only talk to the default gateway. If I ping the
NF> others from X I get no response. The same goes when I go from the any
NF> other of the guests except R to X.
NF> We are z/VM 4.4 0404. Guest X is SLES9 SP2, Guest R is SLES7, other
NF> guests are Debian.
There are a few VMLAN fixes out since 0404RSU. From recent experience I'd
suggest you get right up to date and try again (the qeth driver on the
guests
other than X might need an update as well, although it strikes me as odd
that
the SLES 7 system works talking to the SLES 9 SP2 given that its qeth is
probably older than the Debians'...).
The z/VM team maintains an excellent resource that talks about (among other
things) z/VM maintenance levels in support of virtual networking:
http://www.vm.ibm.com/virtualnetwork
Look for the "Virtual Switch and Guest LAN CP Maintenance levels" link.
NF> The other weirdness I see is that all the guests have a subnet mask of
NF> 255.255.255.192 but Q LAN DETAILS reports everyone as 255.255.255.0.
No need to be concerned about this. At earlier levels the display shows
the
natural network mask (i.e. as if you weren't subnetting) instead of the
actual subnet mask in use. On z/VM 5.1 the subnet mask display is removed
(replaced by the MAC address, like the multicast display).
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IP weirdness
On Saturday 06 August 2005 04:38, Neale Ferguson wrote: NF> I have a guest LAN that connects a number of guests. NF> All but one of the guests can talk to each other, except one NF> (I'll call X) which can only talk to the default gateway. If I ping the NF> others from X I get no response. The same goes when I go from the any NF> other of the guests except R to X. NF> We are z/VM 4.4 0404. Guest X is SLES9 SP2, Guest R is SLES7, other NF> guests are Debian. There are a few VMLAN fixes out since 0404RSU. From recent experience I'd suggest you get right up to date and try again (the qeth driver on the guests other than X might need an update as well, although it strikes me as odd that the SLES 7 system works talking to the SLES 9 SP2 given that its qeth is probably older than the Debians'...). The z/VM team maintains an excellent resource that talks about (among other things) z/VM maintenance levels in support of virtual networking: http://www.vm.ibm.com/virtualnetwork Look for the "Virtual Switch and Guest LAN CP Maintenance levels" link. NF> The other weirdness I see is that all the guests have a subnet mask of NF> 255.255.255.192 but Q LAN DETAILS reports everyone as 255.255.255.0. No need to be concerned about this. At earlier levels the display shows the natural network mask (i.e. as if you weren't subnetting) instead of the actual subnet mask in use. On z/VM 5.1 the subnet mask display is removed (replaced by the MAC address, like the multicast display). Cheers, Vic Cross -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
IP weirdness
I have a guest LAN that connects a number of guests. One of the guests is acting as a router (R) and is the default gateway for all the other guests. All but one of the guests can talk to each other, except one (I'll call X) which can only talk to the default gateway. If I ping the others from X I get no response. The same goes when I go from the any other of the guests except R to X. If I do a tcpdump 'host X' -vv on the guest X is trying to ping I see nothing (call this guest Y). However, if I do a tcpdump -i eth0 -vv I see stuff which looks like a ping but seems to be missing the IP header information: 14:04:40.907445 00:00:40:01:89:1a > 45:00:00:54:6b:91, ethertype Unknown (0xc0a8 ), length 84: 0x: 8255 c0a8 8257 6692 054b 0017 42f3 .U...W..f..K..B. 0x0010: a9ff 000a bc0b 0809 0a0b 0c0d 0e0f 1011 0x0020: 1213 1415 1617 1819 1a1b 1c1d 1e1f 2021 ...! 0x0030: 2223 2425 2627 2829 2a2b 2c2d 2e2f 3031 "#$%&'()*+,-./01 0x0040: 3233 3435 3637 234567 So it appears the Guest LAN is able to deliver stuff but none of the guests are recognizing that the payload is for them. X's routing table: 192.168.130.64 0.0.0.0 255.255.255.192 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.130.68 0.0.0.0 UG0 0 0 eth0 X's config: eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:11 inet addr:192.168.130.87 Bcast:192.168.130.127 Mask:255.255.255.192 inet6 addr: fe80::200:0:100:11/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:8192 Metric:1 RX packets:1333 errors:0 dropped:0 overruns:0 frame:0 TX packets:1041 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:96699 (94.4 Kb) TX bytes:126565 (123.5 Kb) Y's routing table: 192.168.130.64 0.0.0.0 255.255.255.192 U 0 0 0 eth0 0.0.0.0 192.168.130.68 0.0.0.0 UG0 0 0 eth0 Y's config: eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:12 inet addr:192.168.130.85 Bcast:192.168.130.127 Mask:255.255.255.192 inet6 addr: fe80::ff:fe00:12/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:8192 Metric:1 RX packets:5442 errors:0 dropped:0 overruns:0 frame:0 TX packets:5311 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:371571 (362.8 KiB) TX bytes:995318 (971.9 KiB) The other weirdness I see is that all the guests have a subnet mask of 255.255.255.192 but Q LAN DETAILS reports everyone as 255.255.255.0. Y: Adapter Owner: YNIC: 0340 Name: UNASSIGNED Device: 0342 Unit: 002 Role: DATA VLAN: ANY Assigned by user Unicast IP Addresses: 192.168.130.85 Mask: 255.255.255.0 Multicast IP Addresses: 224.0.0.1MAC: 01-00-5E-00-00-01 Y's NIC: Adapter 0340 Type: QDIO Name: UNASSIGNED Devices: 3 Port 0 MAC: 02-00-00-00-00-12 LAN: SYSTEM LNXLAN3 MFS: 8192 RX Packets: 11242 Discarded: 0 Errors: 0 TX Packets: 10587 Discarded: 6 Errors: 0 RX Bytes: 959602 TX Bytes: 2280553 Connection Name: HALLOLE State: Session Established Device: 0340 Unit: 000 Role: CTL-READ Device: 0341 Unit: 001 Role: CTL-WRITE Device: 0342 Unit: 002 Role: DATA VLAN: ANY Assigned by user Unicast IP Addresses: 192.168.130.85 Mask: 255.255.255.0 Multicast IP Addresses: 224.0.0.1MAC: 01-00-5E-00-00-01 X: Adapter Owner: XNIC: 0340 Name: UNASSIGNED Device: 0342 Unit: 002 Role: DATA VLAN: ANY Assigned by user Unicast IP Addresses: 192.168.130.87 Mask: 255.255.255.0 FE80::200:0:100:11/64 Multicast IP Addresses: 224.0.0.1MAC: 01-00-5E-00-00-01 224.0.0.251 MAC: 01-00-5E-00-00-FB 224.0.1.22 MAC: 01-00-5E-00-01-16 239.255.255.253 MAC: 01-00-5E-7F-FF-FD FF02::1 MAC: 33-33-00-00-00-01 FF02::1:FF00:11 MAC: 33-33-FF-00-00-11 X's NIC: Adapter 0340 Type: QDIO Name: UNASSIGNED Devices: 3 Port 0 MAC: 02-00-00-00-00-11 LAN: SYSTEM LNXLAN3 MFS: 8192 RX Packets: 1407 Discarded: 0 Errors: 0 TX Packets: 1116 Discarded: 0 Errors: 0 RX Bytes: 99629TX Bytes: 101257 Connection Name: HALLOLE State: Session Established Device: 0340 Unit: 000 Role: CTL-READ Device: 0341 Unit: 001 Role: CTL-WRITE Device: 0342 Unit: 002 Role: DATA VLAN: ANY Assigned by user Unicast IP Addresses: 192.168.130.87 Mask: 255.255.255.0
