Hello,
I think that I am having some problems regarding networking, or maybe I
misunderstood something. I have the following config:
Dom0 with a bridge to dom1 and dom3.
# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 3268 4 r-----
91.7
dom1 1 512 1 -b----
1.4
dom3 2 512 1 -b----
1.2
ifconfig in dom0 shows:
eth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65
inet addr:16.127.73.174 Bcast:16.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::725a:b6ff:fe94:b865/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3227 errors:0 dropped:0 overruns:0 frame:0
TX packets:625 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:540854 (540.8 KB) TX bytes:136930 (136.9 KB)
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:104 errors:0 dropped:0 overruns:0 frame:0
TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8864 (8.8 KB) TX bytes:8864 (8.8 KB)
peth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65
inet addr:16.127.73.175 Bcast:16.127.75.255 Mask:255.255.252.0
inet6 addr: fe80::725a:b6ff:fe94:b865/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:16059 errors:0 dropped:0 overruns:0 frame:0
TX packets:762 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1667649 (1.6 MB) TX bytes:146238 (146.2 KB)
Memory:d7400000-d7420000
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 PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2625 errors:0 dropped:5 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 B) TX bytes:223204 (223.2 KB)
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 PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2624 errors:0 dropped:4 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 B) TX bytes:222610 (222.6 KB)
ifconfig in dom1:
eth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65
inet addr:16.127.73.174 Bcast:16.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::725a:b6ff:fe94:b865/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3227 errors:0 dropped:0 overruns:0 frame:0
TX packets:625 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:540854 (540.8 KB) TX bytes:136930 (136.9 KB)
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:104 errors:0 dropped:0 overruns:0 frame:0
TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8864 (8.8 KB) TX bytes:8864 (8.8 KB)
peth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65
inet addr:16.127.73.175 Bcast:16.127.75.255 Mask:255.255.252.0
inet6 addr: fe80::725a:b6ff:fe94:b865/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:16059 errors:0 dropped:0 overruns:0 frame:0
TX packets:762 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1667649 (1.6 MB) TX bytes:146238 (146.2 KB)
Memory:d7400000-d7420000
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 PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2625 errors:0 dropped:5 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 B) TX bytes:223204 (223.2 KB)
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 PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2624 errors:0 dropped:4 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 B) TX bytes:222610 (222.6 KB)
ifcofig in dom3:
eth0 Link encap:Ethernet HWaddr 00:16:3e:52:f4:b5
inet addr:16.127.73.79 Bcast:16.127.75.255 Mask:255.255.252.0
inet6 addr: fec0::f:216:3eff:fe52:f4b5/64 Scope:Site
inet6 addr: 2002:107f:493a:f:216:3eff:fe52:f4b5/64 Scope:Global
inet6 addr: fe80::216:3eff:fe52:f4b5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15553 errors:0 dropped:0 overruns:0 frame:0
TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1105617 (1.1 MB) TX bytes:2959 (2.9 KB)
Interrupt:245
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:0 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:0 (0.0 B) TX bytes:0 (0.0 B)
I can ping between dom1 and dom3, but dom1 <-> dom0 doesnt work neither
dom3<->dom0.
I think I have something misconfigured .. or something is blocking the
packets to arrive in dom0.
Any Ideas?
Thank you !!
--
David Cemin
mobile: +55 51 93523097
home: +55 51 32763785
email: davidcemin@gmail.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On 11/22/2010 12:03 PM, David Cemin wrote:> Hello, > > I think that I am having some problems regarding networking, or maybe I > misunderstood something. I have the following config: > > Dom0 with a bridge to dom1 and dom3. > > # xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 3268 4 r----- > 91.7 > dom1 1 512 1 -b---- > 1.4 > dom3 2 512 1 -b---- > 1.2 > > > ifconfig in dom0 shows: > eth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65Virtual device copied from "real" peth0.> peth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65Real eth0 device> vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ffConnects dom1''s eth0> vif2.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ffConnect''s dom3''s eth0> ifconfig in dom1: > > eth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65Connects to dom0''s vif1.0> peth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65 > vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > vif2.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ffThese should not be here. They should only exist on dom0.> ifcofig in dom3: > > eth0 Link encap:Ethernet HWaddr 00:16:3e:52:f4:b5Connects to vif2.0 on dom0. hth, -- Digimer E-Mail: digimer@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 11/22/2010 12:14 PM, Digimer wrote:> On 11/22/2010 12:03 PM, David Cemin wrote: >> Hello, >> >> I think that I am having some problems regarding networking, or maybe I >> misunderstood something. I have the following config: >> >> Dom0 with a bridge to dom1 and dom3. >> >> # xm list >> Name ID Mem VCPUs State >> Time(s) >> Domain-0 0 3268 4 r----- >> 91.7 >> dom1 1 512 1 -b---- >> 1.4 >> dom3 2 512 1 -b---- >> 1.2 >> >> >> ifconfig in dom0 shows: >> eth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65 > > Virtual device copied from "real" peth0. > >> peth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65 > > Real eth0 device > >> vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > > Connects dom1''s eth0 > >> vif2.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > > Connect''s dom3''s eth0 > >> ifconfig in dom1: >> >> eth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65 > > Connects to dom0''s vif1.0 > >> peth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65 >> vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff >> vif2.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > > These should not be here. They should only exist on dom0. > >> ifcofig in dom3: >> >> eth0 Link encap:Ethernet HWaddr 00:16:3e:52:f4:b5 > > Connects to vif2.0 on dom0. > > hth, >Looks like all of your MAC addresses are the same, too. They should be different. -- Digimer E-Mail: digimer@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thank you for your quick answer,
So, I manage to force a mac inside my dom1. Heres my config:
# cat /etc/xen/dom1
kernel = "/boot/vmlinuz-2.6.32.25-xen" #CHANGE IT TO YOUR VMLINUZ
ramdisk = "/boot/initrd.img-2.6.32.25-xen" #CHANGE IT TO YOUR INITRD
memory = 512
name = "dom1"
vif = [''mac=00:16:3e:63:29:ab,bridge=xenbr0'']
#vif = [''bridge=xenbr0'']
#disk
[''file:/xen/domains/dom1/diskimage.img,xvda1,w'',''file:/xen/domains/dom1/swapimage.img,xvda2,w'']
disk =
[''phy:/dev/lvm-vol/dom1,xvda1,w'',''phy:/dev/lvm-vol/dom1swp,xvda2,w'']
#DHCP - remove the ip, gateway and netmask lines, and include:# dhcp
"dhcp"
#ip = "ip add"
#gateway = "ip add"
#netmask = "255.255.0.0"
dhcp = "dhcp"
root = "/dev/xvda1 ro"
serial= "/dev/hvc0"
extra = ''4''
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
ifconfig inside dom0:
# ifconfig
eth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65
inet addr:16.127.73.174 Bcast:16.255.255.255 Mask:255.0.0.0
inet6 addr: fec0::f:725a:b6ff:fe94:b865/64 Scope:Site
inet6 addr: 2002:107f:493a:f:725a:b6ff:fe94:b865/64 Scope:Global
inet6 addr: fe80::725a:b6ff:fe94:b865/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5348 errors:0 dropped:0 overruns:0 frame:0
TX packets:1144 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:936544 (936.5 KB) TX bytes:204687 (204.6 KB)
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:120 errors:0 dropped:0 overruns:0 frame:0
TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10272 (10.2 KB) TX bytes:10272 (10.2 KB)
peth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65
inet addr:16.127.73.175 Bcast:16.127.75.255 Mask:255.255.252.0
inet6 addr: fe80::725a:b6ff:fe94:b865/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:5944 errors:0 dropped:0 overruns:0 frame:0
TX packets:1304 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1059860 (1.0 MB) TX bytes:215651 (215.6 KB)
Memory:d7400000-d7420000
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 PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4275 errors:0 dropped:6 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 B) TX bytes:351516 (351.5 KB)
ifconfig inside dom1:
root@xen-hypervisor:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:3e:63:29:ab
inet addr:16.127.73.171 Bcast:16.127.75.255 Mask:255.255.252.0
inet6 addr: fec0::f:216:3eff:fe63:29ab/64 Scope:Site
inet6 addr: 2002:107f:493a:f:216:3eff:fe63:29ab/64 Scope:Global
inet6 addr: fe80::216:3eff:fe63:29ab/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7457 errors:0 dropped:0 overruns:0 frame:0
TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:525254 (525.2 KB) TX bytes:2295 (2.2 KB)
Interrupt:245
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:0 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:0 (0.0 B) TX bytes:0 (0.0 B)
I dont have any peth0 or vif inside dom1s ifconfig. So now maybe the
connection to dom1 inside dom0 is wrong(vif1.0 Link encap:Ethernet
HWaddr fe:ff:ff:ff:ff:ff )
And I am having the same mac on peth0 and eth0 .. where do I configure it ..
inside xend-config.sxp ?
Thank you again
2010/11/22 Digimer <linux@alteeve.com>
> On 11/22/2010 12:03 PM, David Cemin wrote:
>
>> Hello,
>>
>> I think that I am having some problems regarding networking, or maybe I
>> misunderstood something. I have the following config:
>>
>> Dom0 with a bridge to dom1 and dom3.
>>
>> # xm list
>> Name ID Mem VCPUs State
>> Time(s)
>> Domain-0 0 3268 4 r-----
>> 91.7
>> dom1 1 512 1 -b----
>> 1.4
>> dom3 2 512 1 -b----
>> 1.2
>>
>>
>> ifconfig in dom0 shows:
>> eth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65
>>
>
> Virtual device copied from "real" peth0.
>
>
> peth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65
>>
>
> Real eth0 device
>
>
> vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
>>
>
> Connects dom1''s eth0
>
>
> vif2.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
>>
>
> Connect''s dom3''s eth0
>
>
> ifconfig in dom1:
>>
>> eth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65
>>
>
> Connects to dom0''s vif1.0
>
> peth0 Link encap:Ethernet HWaddr 70:5a:b6:94:b8:65
>> vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
>> vif2.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
>>
>
> These should not be here. They should only exist on dom0.
>
>
> ifcofig in dom3:
>>
>> eth0 Link encap:Ethernet HWaddr 00:16:3e:52:f4:b5
>>
>
> Connects to vif2.0 on dom0.
>
> hth,
>
> --
> Digimer
> E-Mail: digimer@alteeve.com
> AN!Whitepapers: http://alteeve.com
> Node Assassin: http://nodeassassin.org
>
--
David Cemin
mobile: +55 51 93523097
home: +55 51 32763785
email: davidcemin@gmail.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On 11/22/2010 12:41 PM, David Cemin wrote:> And I am having the same mac on peth0 and eth0 .. where do I configure > it .. inside xend-config.sxp ? > > Thank you againpeth0 and eth0 do share a MAC address, that is okay (as they are one in the same). The domU machines though all need unique MAC addresses. You should use ''00:16:3e:xx:xx:xx''. -- Digimer E-Mail: digimer@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yes, I´ve done that:
root@xen-hypervisor:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:3e:63:29:ab
But it appears that the link to dom1 inside dom0 is wrong:
vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
Am I right? If yes, it is configurable through xend-config.sxp ?
Thank you!
best regards,
--
David
2010/11/22 Digimer <linux@alteeve.com>
> On 11/22/2010 12:41 PM, David Cemin wrote:
>
>> And I am having the same mac on peth0 and eth0 .. where do I configure
>> it .. inside xend-config.sxp ?
>>
>> Thank you again
>>
>
> peth0 and eth0 do share a MAC address, that is okay (as they are one in the
> same). The domU machines though all need unique MAC addresses. You should
> use ''00:16:3e:xx:xx:xx''.
>
>
> --
> Digimer
> E-Mail: digimer@alteeve.com
> AN!Whitepapers: http://alteeve.com
> Node Assassin: http://nodeassassin.org
>
--
David Cemin
mobile: +55 51 93523097
home: +55 51 32763785
email: davidcemin@gmail.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On 11/22/2010 12:52 PM, David Cemin wrote:> Yes, I´ve done that: > > root@xen-hypervisor:~# ifconfig > eth0 Link encap:Ethernet HWaddr 00:16:3e:63:29:ab > > But it appears that the link to dom1 inside dom0 is wrong: > > vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > > Am I right? If yes, it is configurable through xend-config.sxp ? > > Thank you!Sorry, vifX.Y devices are ''fe:ff:ff:ff:ff:ff''. So long as the eth0 inside each domU is unique, you are ok. Do you have any firewalls running? What does ''iptables-save'' show on dom[013]? -- Digimer E-Mail: digimer@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
dom0: # iptables-save # Generated by iptables-save v1.4.4 on Mon Nov 22 16:06:31 2010 *filter :INPUT ACCEPT [1324:790913] :FORWARD ACCEPT [3389:341110] :OUTPUT ACCEPT [1656:273098] -A FORWARD -m state --state RELATED,ESTABLISHED -m physdev --physdev-out vif2.0 -j ACCEPT -A FORWARD -m physdev --physdev-in vif2.0 -j ACCEPT -A FORWARD -m state --state RELATED,ESTABLISHED -m physdev --physdev-out vif1.0 -j ACCEPT -A FORWARD -m physdev --physdev-in vif1.0 -j ACCEPT COMMIT # Completed on Mon Nov 22 16:06:31 2010 dom1: root@xen-hypervisor:~# iptables-save # Generated by iptables-save v1.4.4 on Mon Nov 22 18:03:46 2010 *filter :INPUT ACCEPT [4002:941999] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [198:10662] COMMIT # Completed on Mon Nov 22 18:03:46 2010 dom3: root@xen-hypervisor:~# iptables-save # Generated by iptables-save v1.4.4 on Mon Nov 22 18:05:16 2010 *filter :INPUT ACCEPT [504:496131] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [217:11648] COMMIT # Completed on Mon Nov 22 18:05:16 2010 Thank you! -- David 2010/11/22 Digimer <linux@alteeve.com>> On 11/22/2010 12:52 PM, David Cemin wrote: > >> Yes, I´ve done that: >> >> root@xen-hypervisor:~# ifconfig >> eth0 Link encap:Ethernet HWaddr 00:16:3e:63:29:ab >> >> But it appears that the link to dom1 inside dom0 is wrong: >> >> vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff >> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link >> >> Am I right? If yes, it is configurable through xend-config.sxp ? >> >> Thank you! >> > > Sorry, vifX.Y devices are ''fe:ff:ff:ff:ff:ff''. So long as the eth0 inside > each domU is unique, you are ok. > > Do you have any firewalls running? What does ''iptables-save'' show on > dom[013]? > > > -- > Digimer > E-Mail: digimer@alteeve.com > AN!Whitepapers: http://alteeve.com > Node Assassin: http://nodeassassin.org >-- David Cemin mobile: +55 51 93523097 home: +55 51 32763785 email: davidcemin@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 11/22/2010 01:04 PM, David Cemin wrote:> dom0: > # iptables-save > # Generated by iptables-save v1.4.4 on Mon Nov 22 16:06:31 2010 > *filter > :INPUT ACCEPT [1324:790913] > :FORWARD ACCEPT [3389:341110] > :OUTPUT ACCEPT [1656:273098] > -A FORWARD -m state --state RELATED,ESTABLISHED -m physdev --physdev-out > vif2.0 -j ACCEPT > -A FORWARD -m physdev --physdev-in vif2.0 -j ACCEPT > -A FORWARD -m state --state RELATED,ESTABLISHED -m physdev --physdev-out > vif1.0 -j ACCEPT > -A FORWARD -m physdev --physdev-in vif1.0 -j ACCEPT > COMMIT > # Completed on Mon Nov 22 16:06:31 2010Try this, as a test: /etc/init.d/iptables stop /etc/init.d/ip6tables stop See if you can ping. -- Digimer E-Mail: digimer@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
its not firewall I suppose. I have uninstalled iptables and I could not ping as well .. I have no Ideas anymore .. 2010/11/22 Digimer <linux@alteeve.com>> On 11/22/2010 01:04 PM, David Cemin wrote: > >> dom0: >> # iptables-save >> # Generated by iptables-save v1.4.4 on Mon Nov 22 16:06:31 2010 >> *filter >> :INPUT ACCEPT [1324:790913] >> :FORWARD ACCEPT [3389:341110] >> :OUTPUT ACCEPT [1656:273098] >> -A FORWARD -m state --state RELATED,ESTABLISHED -m physdev --physdev-out >> vif2.0 -j ACCEPT >> -A FORWARD -m physdev --physdev-in vif2.0 -j ACCEPT >> -A FORWARD -m state --state RELATED,ESTABLISHED -m physdev --physdev-out >> vif1.0 -j ACCEPT >> -A FORWARD -m physdev --physdev-in vif1.0 -j ACCEPT >> COMMIT >> # Completed on Mon Nov 22 16:06:31 2010 >> > > Try this, as a test: > > /etc/init.d/iptables stop > /etc/init.d/ip6tables stop > > See if you can ping. > > > -- > Digimer > E-Mail: digimer@alteeve.com > AN!Whitepapers: http://alteeve.com > Node Assassin: http://nodeassassin.org >-- David Cemin mobile: +55 51 93523097 home: +55 51 32763785 email: davidcemin@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''ll try to drop the packets with wireshark .. maybe I can see something .. 2010/11/22 David Cemin <davidcemin@gmail.com>> its not firewall I suppose. I have uninstalled iptables and I could not > ping as well .. > > I have no Ideas anymore .. > > 2010/11/22 Digimer <linux@alteeve.com> > >> On 11/22/2010 01:04 PM, David Cemin wrote: >> >> dom0: >>> # iptables-save >>> # Generated by iptables-save v1.4.4 on Mon Nov 22 16:06:31 2010 >>> *filter >>> :INPUT ACCEPT [1324:790913] >>> :FORWARD ACCEPT [3389:341110] >>> :OUTPUT ACCEPT [1656:273098] >>> -A FORWARD -m state --state RELATED,ESTABLISHED -m physdev --physdev-out >>> vif2.0 -j ACCEPT >>> -A FORWARD -m physdev --physdev-in vif2.0 -j ACCEPT >>> -A FORWARD -m state --state RELATED,ESTABLISHED -m physdev --physdev-out >>> vif1.0 -j ACCEPT >>> -A FORWARD -m physdev --physdev-in vif1.0 -j ACCEPT >>> COMMIT >>> # Completed on Mon Nov 22 16:06:31 2010 >>> >> >> Try this, as a test: >> >> /etc/init.d/iptables stop >> /etc/init.d/ip6tables stop >> >> See if you can ping. >> >> >> -- >> Digimer >> E-Mail: digimer@alteeve.com >> AN!Whitepapers: http://alteeve.com >> Node Assassin: http://nodeassassin.org >> > > > > -- > David Cemin > mobile: +55 51 93523097 > home: +55 51 32763785 > email: davidcemin@gmail.com >-- David Cemin mobile: +55 51 93523097 home: +55 51 32763785 email: davidcemin@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I only see packets in dom0 interface with the IPs from dom1 and dom3 when I try to ping dom1 <->dom3 .. when I try either witn dom1 to dom0 or with dom3 to dom0 I got nothing ... Any Ideas? Thank you! 2010/11/22 David Cemin <davidcemin@gmail.com>> I''ll try to drop the packets with wireshark .. maybe I can see something > .. > > 2010/11/22 David Cemin <davidcemin@gmail.com> > > its not firewall I suppose. I have uninstalled iptables and I could not >> ping as well .. >> >> I have no Ideas anymore .. >> >> 2010/11/22 Digimer <linux@alteeve.com> >> >>> On 11/22/2010 01:04 PM, David Cemin wrote: >>> >>> dom0: >>>> # iptables-save >>>> # Generated by iptables-save v1.4.4 on Mon Nov 22 16:06:31 2010 >>>> *filter >>>> :INPUT ACCEPT [1324:790913] >>>> :FORWARD ACCEPT [3389:341110] >>>> :OUTPUT ACCEPT [1656:273098] >>>> -A FORWARD -m state --state RELATED,ESTABLISHED -m physdev --physdev-out >>>> vif2.0 -j ACCEPT >>>> -A FORWARD -m physdev --physdev-in vif2.0 -j ACCEPT >>>> -A FORWARD -m state --state RELATED,ESTABLISHED -m physdev --physdev-out >>>> vif1.0 -j ACCEPT >>>> -A FORWARD -m physdev --physdev-in vif1.0 -j ACCEPT >>>> COMMIT >>>> # Completed on Mon Nov 22 16:06:31 2010 >>>> >>> >>> Try this, as a test: >>> >>> /etc/init.d/iptables stop >>> /etc/init.d/ip6tables stop >>> >>> See if you can ping. >>> >>> >>> -- >>> Digimer >>> E-Mail: digimer@alteeve.com >>> AN!Whitepapers: http://alteeve.com >>> Node Assassin: http://nodeassassin.org >>> >> >> >> >> -- >> David Cemin >> mobile: +55 51 93523097 >> home: +55 51 32763785 >> email: davidcemin@gmail.com >> > > > > -- > David Cemin > mobile: +55 51 93523097 > home: +55 51 32763785 > email: davidcemin@gmail.com >-- David Cemin mobile: +55 51 93523097 home: +55 51 32763785 email: davidcemin@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users