Re: [Xen-devel] Network still broken, new issue as well , 7468:17a9f111fa93

[Michael Lessard <michael.lessard@xxxxxxxxx>]

On 10/26/05, Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote:

On Wed, Oct 26, 2005 at 08:14:41AM -0400, Michael Lessard wrote:

> On 10/26/05, Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote:
>
>   On Tue, Oct 25, 2005 at 08:10:16PM -0400, Michael Lessard wrote:
>
>   > Bigelow:/etc/xen/scripts# ./blade-network start
>   > /etc/xen/scripts/network-bridge: line 211: /sbin/getcfg: No such file
>   or
>   > directory
>   >
>   > I use Debian Sid ....
>
>   There's a patch for that on the way.  For now, you could just comment
>   out that
>   whole line -- it's SuSE-specific.
>
>   Did the script work anyway?  For me, that error is not a fatal one, and
>   the
>   configuration still succeeds.
>
>   Ewan.
>
> I commend out  the  line,  now  when i start the script no error reported
> but i couldn't ping dom0 from domU, with eth1 bridge too :(

So could you repost the output from brctl show and ifconfig, just as you did
for bug #363 before?  Also, it would be worth having route and iptables -L.

It would also be helpful to know whether you can get packets anywhere -- dom0
to network, network to dom0, domU to network, etc, and if you can figure out
where they are getting lost.

Cheers,

Ewan.

I have two network cards on my computer  : 
eth0 connect to -> FW (DMZ 192.168.100.254)
eth1 connect to -> FW (internal network 192.168.10.254)

On my DOM0 i haved configure network  
eth0 : up (no ip) 
eth1 : 192.168.10.20 

On my DOMU i haved configure network 
eth1 : 192.168.100.1 

ON DOM0 
#brctl show 
xenbr0         
8000.feffffffffff      
no             
vif8.0
# iptables -L 
Chain INPUT (policy ACCEPT)
target     prot opt
source              
destination

Chain FORWARD (policy ACCEPT)
target     prot opt
source              
destination
ACCEPT     all  -- 
anywhere            
anywhere           
PHYSDEV match --physdev-in vif1.0
ACCEPT     all  -- 
anywhere            
anywhere           
PHYSDEV match --physdev-in vif8.0

Chain OUTPUT (policy ACCEPT)
target     prot opt
source              
destination

# ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:08:54:2F:EA:38
          inet
addr:192.168.100.5  Bcast:192.168.100.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:87 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:894 (894.0 b)  TX bytes:16522 (16.1 KiB)
          Interrupt:17 Base address:0xec00

eth1      Link encap:Ethernet  HWaddr 00:08:54:2F:EA:32
          inet
addr:192.168.10.20  Bcast:192.168.10.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7597 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4755 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:963119 (940.5 KiB)  TX bytes:667126 (651.4 KiB)
          Interrupt:18 Base address:0xe800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:76 errors:0 dropped:0 overruns:0 frame:0
          TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5064 (4.9 KiB)  TX bytes:5064 (4.9 KiB)

vif8.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:72 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3024 (2.9 KiB)  TX bytes:0 (0.0 b)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:72 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2016 (1.9 KiB)  TX bytes:0 (0.0 b)


I haved put ip on eth0 to test connectivty from etho on DOM0 and its working ...  
I could ping FW from DOM0 
but i could'nt ping DOM0 from DOMU 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel