[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] SSH ping etc not working between dom0 and domU's
Jeroen Torrekens wrote:
-----Original Message-----
From: Ilari Mäkelä [mailto:ilari@xxxxxx]
Sent: woensdag 28 mei 2008 17:21
To: Jeroen Torrekens
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] SSH ping etc not working between dom0 and
domU's
Jeroen Torrekens wrote:
Ilari Mäkelä wrote:
Jeroen Torrekens wrote:
Hi,
I think you might want to check this:
Here is ifconfig from dom0:
eth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet addr:192.168.1.5 Bcast:192.168.1.255
Mask:255.255.255.0
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3422 errors:0 dropped:0 overruns:0 frame:0
TX packets:2133 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:347388 (339.2 KiB) TX bytes:417210 (407.4 KiB)
Interrupt:16 Base address:0x6000
Especially the hardware address.
Jeroen
Hi,
Thanks for the reply. That is the hardware address that was setup
when I installed Debian. If I try to change that hardware address in
/etc/network/interface config file I can't ssh to my dom0 machine
anymore from other computers in my network. I know it looks weird but
if I change it my network on eth0 dies. Now I changed my
configuration a bit and it looks like this now:
This is my network script at the moment, found this one from this
list:
#!/bin/sh
brctl addbr xenbr0
brctl setfd xenbr0 0
brctl sethello xenbr0 0
brctl stp xenbr0 off
ifconfig eth2 0.0.0.0 down
ifconfig eth2 0.0.0.0 up
brctl addif xenbr0 eth2
ifconfig xenbr0 10.0.0.1 netmask 255.255.255.0
sleep 5
brctl addbr xenbr1
brctl setfd xenbr1 0
brctl sethello xenbr1 0
brctl stp xenbr1 off
ifconfig eth3 0.0.0.0 down
ifconfig eth3 0.0.0.0 up
brctl addif xenbr1 eth3
ifconfig xenbr1 10.0.1.2 netmask 255.255.255.0
sleep 5
ifconfig eth2 0.0.0.0
ifconfig eth3 0.0.0.0
exit 0
ifconfig on dom0:
eth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet addr:192.168.1.5 Bcast:192.168.1.255
Mask:255.255.255.0
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:296 errors:0 dropped:0 overruns:0 frame:0
TX packets:267 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:29514 (28.8 KiB) TX bytes:33556 (32.7 KiB)
Interrupt:16 Base address:0x6000
eth2 Link encap:Ethernet HWaddr 00:1C:F0:5B:69:F8
inet6 addr: fe80::21c:f0ff:fe5b:69f8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:90 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7356 (7.1 KiB) TX bytes:1056 (1.0 KiB)
Interrupt:22 Base address:0xe000
eth3 Link encap:Ethernet HWaddr 00:1C:F0:5A:5D:72
inet6 addr: fe80::21c:f0ff:fe5a:5d72/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:253 errors:0 dropped:0 overruns:0 frame:0
TX packets:159 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22429 (21.9 KiB) TX bytes:17327 (16.9 KiB)
Interrupt:17
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:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2360 (2.3 KiB) TX bytes:2360 (2.3 KiB)
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:252 (252.0 b) TX bytes:6114 (5.9 KiB)
vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:174 errors:0 dropped:0 overruns:0 frame:0
TX packets:242 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:14867 (14.5 KiB) TX bytes:21373 (20.8 KiB)
xenbr0 Link encap:Ethernet HWaddr 00:1C:F0:5B:69:F8
inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::21c:f0ff:fe5b:69f8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:99 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6348 (6.1 KiB) TX bytes:552 (552.0 b)
xenbr1 Link encap:Ethernet HWaddr 00:1C:F0:5A:5D:72
inet addr:10.0.1.2 Bcast:10.0.1.255 Mask:255.255.255.0
inet6 addr: fe80::21c:f0ff:fe5a:5d72/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:111 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6642 (6.4 KiB) TX bytes:594 (594.0 b)
and kernel routing table on dom0:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
10.0.0.0 0.0.0.0 255.255.255.0 U 0
0 0 xenbr0
10.0.1.0 0.0.0.0 255.255.255.0 U 0
0 0 xenbr1
192.168.1.0 0.0.0.0 255.255.255.0 U 0
0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0
0 0 eth0
Now I can ping my dom0 from domU's but everything else is still
failing. Can't ping my domU's from dom0 and ssh doesn't work at all.
So there is little progress because ping wasn't working at all before
and now it works from domU to dom0.
Ilari Mäkelä
Could you provide me with the output of 'brctl show' ?
Thanks!
Hi,
This is a bit strange. I changed my hardware address in
/etc/network/interfaces file and booted my computer. Now I can access my
dom0 from my domU with ssh but now I can't access my dom0 from other
computers in my network like I used to before changing that hardware
address. But here is the output you asked:
bridge name bridge id STP enabled interfaces
xenbr0 8000.001cf05b69f8 no eth2
vif1.0
xenbr1 8000.001cf05a5d72 no eth3
vif2.0
Ilari Mäkelä
Why do you change the MAC address of you eth0? And what is the value now?
Just leave it. It is called Hardware Address for a reason; just let it
have its original value.
Well it was just a test, nothing more and I changed it back to the
original one. Wanted to see if that weird hardware address
(FE:FF:FF:FF:FF:FF) had something to do with my problems. Do you have
any more ideas what I should check to get the connection between dom0
and domU's to work?
Ilari Mäkelä
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
