Hello. I have installed the SuSE Linux 10 XEN kernel but no domU yet. Now I cannot ping to and from dom0. I get lots of ARP broadcasts from dom0 but dom0 seems to ignore ARP answers. When pinging to dom0 it ignores arp requests. This happens regardless xend is running or not. This happens in the xen kernel only, when booting stock kernel all works as expected. What can I do? Robert _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Stephan Böni
2005-Oct-17 11:16 UTC
Re: [Xen-users] SuSE 10 no network in dom0 - arp problem?
Please mail me your "ifconfig" output. Stephan> -----Ursprüngliche Nachricht----- > Von: Robert Welz [mailto:r_welz@web.de] > Gesendet: Montag, 17. Oktober 2005 12:10 > An: Xen-users@lists.xensource.com > Betreff: [Xen-users] SuSE 10 no network in dom0 - arp problem? > > > Hello. > I have installed the SuSE Linux 10 XEN kernel but no domU yet. Now I > cannot ping to and from dom0. I get lots of ARP broadcasts from dom0 > but dom0 seems to ignore ARP answers. When pinging to dom0 it > ignores > arp requests. This happens regardless xend is running or not. This > happens in the xen kernel only, when booting stock kernel all works > as expected. > > What can I do? > > Robert > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Robert Welz
2005-Oct-17 11:44 UTC
Re: [Xen-users] SuSE 10 no network in dom0 - arp problem?
Here it is: eth0 Protokoll:Ethernet Hardware Adresse 00:0E:0C:72:41:41 inet Adresse:192.168.2.128 Bcast:192.168.2.255 Maske: 255.255.255.0 inet6 Adresse: fe80::20e:cff:fe72:4141/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7 errors:0 dropped:0 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:0 RX bytes:498 (498.0 b) TX bytes:2064 (2.0 Kb) lo Protokoll:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:107 errors:0 dropped:0 overruns:0 frame:0 TX packets:107 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:0 RX bytes:8414 (8.2 Kb) TX bytes:8414 (8.2 Kb) peth0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 Gültigkeitsbereich:Verbindung UP BROADCAST NOARP MULTICAST MTU:1500 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 Sendewarteschlangenlänge:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Basisadresse:0x9000 Speicher:d6800000-d6820000 vif0.0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:28 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:0 RX bytes:2064 (2.0 Kb) TX bytes:588 (588.0 b) xenbr0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF inet6 Adresse: fe80::200:ff:fe00:0/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:27 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:0 RX bytes:1596 (1.5 Kb) TX bytes:378 (378.0 b) Am 17.10.2005 um 13:16 schrieb Stephan Böni:> Please mail me your "ifconfig" output. > > Stephan > > > >> -----Ursprüngliche Nachricht----- >> Von: Robert Welz [mailto:r_welz@web.de] >> Gesendet: Montag, 17. Oktober 2005 12:10 >> An: Xen-users@lists.xensource.com >> Betreff: [Xen-users] SuSE 10 no network in dom0 - arp problem? >> >> >> Hello. >> I have installed the SuSE Linux 10 XEN kernel but no domU yet. Now I >> cannot ping to and from dom0. I get lots of ARP broadcasts from dom0 >> but dom0 seems to ignore ARP answers. When pinging to dom0 it >> ignores >> arp requests. This happens regardless xend is running or not. This >> happens in the xen kernel only, when booting stock kernel all works >> as expected. >> >> What can I do? >> >> Robert >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Robert Welz
2005-Oct-17 12:12 UTC
Re: [Xen-users] SuSE 10 no network in dom0 - arp problem?
Hello. That didn''t help. I see the same arp broadcast storms as before. Robert Am 17.10.2005 um 13:58 schrieb Stephan Böni:> Try ''export LC_MESSAGES=POSIX'' before starting xend. The Xen network > script has problems parsing your ifconfig because its german. > > Stephan > > > >> -----Ursprüngliche Nachricht----- >> Von: Robert Welz [mailto:r_welz@web.de] >> Gesendet: Montag, 17. Oktober 2005 13:45 >> An: Stephan Böni >> Cc: Xen-users@lists.xensource.com >> Betreff: Re: [Xen-users] SuSE 10 no network in dom0 - arp problem? >> >> >> Here it is: >> >> >> eth0 Protokoll:Ethernet Hardware Adresse 00:0E:0C:72:41:41 >> inet Adresse:192.168.2.128 Bcast:192.168.2.255 Maske: >> 255.255.255.0 >> inet6 Adresse: fe80::20e:cff:fe72:4141/64 >> Gültigkeitsbereich:Verbindung >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:7 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 Sendewarteschlangenlänge:0 >> RX bytes:498 (498.0 b) TX bytes:2064 (2.0 Kb) >> >> lo Protokoll:Lokale Schleife >> inet Adresse:127.0.0.1 Maske:255.0.0.0 >> inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine >> UP LOOPBACK RUNNING MTU:16436 Metric:1 >> RX packets:107 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:107 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 Sendewarteschlangenlänge:0 >> RX bytes:8414 (8.2 Kb) TX bytes:8414 (8.2 Kb) >> >> peth0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF >> inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 >> Gültigkeitsbereich:Verbindung >> UP BROADCAST NOARP MULTICAST MTU:1500 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 Sendewarteschlangenlänge:1000 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> Basisadresse:0x9000 Speicher:d6800000-d6820000 >> >> vif0.0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF >> inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 >> Gültigkeitsbereich:Verbindung >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:28 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 Sendewarteschlangenlänge:0 >> RX bytes:2064 (2.0 Kb) TX bytes:588 (588.0 b) >> >> xenbr0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF >> inet6 Adresse: fe80::200:ff:fe00:0/64 >> Gültigkeitsbereich:Verbindung >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:27 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 Sendewarteschlangenlänge:0 >> RX bytes:1596 (1.5 Kb) TX bytes:378 (378.0 b) >> >> >> Am 17.10.2005 um 13:16 schrieb Stephan Böni: >> >> >>> Please mail me your "ifconfig" output. >>> >>> Stephan >>> >>> >>> >>> >>>> -----Ursprüngliche Nachricht----- >>>> Von: Robert Welz [mailto:r_welz@web.de] >>>> Gesendet: Montag, 17. Oktober 2005 12:10 >>>> An: Xen-users@lists.xensource.com >>>> Betreff: [Xen-users] SuSE 10 no network in dom0 - arp problem? >>>> >>>> >>>> Hello. >>>> I have installed the SuSE Linux 10 XEN kernel but no domU >>>> >> yet. Now I >> >>>> cannot ping to and from dom0. I get lots of ARP broadcasts >>>> >> from dom0 >> >>>> but dom0 seems to ignore ARP answers. When pinging to dom0 it >>>> ignores >>>> arp requests. This happens regardless xend is running or not. This >>>> happens in the xen kernel only, when booting stock kernel all works >>>> as expected. >>>> >>>> What can I do? >>>> >>>> Robert >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xensource.com >>>> http://lists.xensource.com/xen-users >>>> >>>> >>>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >>> >>> >> >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Arnd Schmitter
2005-Oct-17 12:20 UTC
AW: [Xen-users] SuSE 10 no network in dom0 - arp problem?
Are you using the default network script shipped with xen ? What''s the configuration of your network bridge ? What say brctl ?> -----Ursprüngliche Nachricht----- > Von: xen-users-bounces@lists.xensource.com [mailto:xen-users- > bounces@lists.xensource.com] Im Auftrag von Robert Welz > Gesendet: Montag, 17. Oktober 2005 14:13 > An: Stephan Böni > Cc: Xen-users@lists.xensource.com > Betreff: Re: [Xen-users] SuSE 10 no network in dom0 - arp problem? > > Hello. > That didn''t help. > > I see the same arp broadcast storms as before. > > Robert > > > Am 17.10.2005 um 13:58 schrieb Stephan Böni: > > > Try ''export LC_MESSAGES=POSIX'' before starting xend. The Xen network > > script has problems parsing your ifconfig because its german. > > > > Stephan > > > > > > > >> -----Ursprüngliche Nachricht----- > >> Von: Robert Welz [mailto:r_welz@web.de] > >> Gesendet: Montag, 17. Oktober 2005 13:45 > >> An: Stephan Böni > >> Cc: Xen-users@lists.xensource.com > >> Betreff: Re: [Xen-users] SuSE 10 no network in dom0 - arp problem? > >> > >> > >> Here it is: > >> > >> > >> eth0 Protokoll:Ethernet Hardware Adresse 00:0E:0C:72:41:41 > >> inet Adresse:192.168.2.128 Bcast:192.168.2.255 Maske: > >> 255.255.255.0 > >> inet6 Adresse: fe80::20e:cff:fe72:4141/64 > >> Gültigkeitsbereich:Verbindung > >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >> RX packets:7 errors:0 dropped:0 overruns:0 frame:0 > >> TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 > >> collisions:0 Sendewarteschlangenlänge:0 > >> RX bytes:498 (498.0 b) TX bytes:2064 (2.0 Kb) > >> > >> lo Protokoll:Lokale Schleife > >> inet Adresse:127.0.0.1 Maske:255.0.0.0 > >> inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine > >> UP LOOPBACK RUNNING MTU:16436 Metric:1 > >> RX packets:107 errors:0 dropped:0 overruns:0 frame:0 > >> TX packets:107 errors:0 dropped:0 overruns:0 carrier:0 > >> collisions:0 Sendewarteschlangenlänge:0 > >> RX bytes:8414 (8.2 Kb) TX bytes:8414 (8.2 Kb) > >> > >> peth0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF > >> inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 > >> Gültigkeitsbereich:Verbindung > >> UP BROADCAST NOARP MULTICAST MTU:1500 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 Sendewarteschlangenlänge:1000 > >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > >> Basisadresse:0x9000 Speicher:d6800000-d6820000 > >> > >> vif0.0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF > >> inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 > >> Gültigkeitsbereich:Verbindung > >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >> RX packets:28 errors:0 dropped:0 overruns:0 frame:0 > >> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 > >> collisions:0 Sendewarteschlangenlänge:0 > >> RX bytes:2064 (2.0 Kb) TX bytes:588 (588.0 b) > >> > >> xenbr0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF > >> inet6 Adresse: fe80::200:ff:fe00:0/64 > >> Gültigkeitsbereich:Verbindung > >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >> RX packets:27 errors:0 dropped:0 overruns:0 frame:0 > >> TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 > >> collisions:0 Sendewarteschlangenlänge:0 > >> RX bytes:1596 (1.5 Kb) TX bytes:378 (378.0 b) > >> > >> > >> Am 17.10.2005 um 13:16 schrieb Stephan Böni: > >> > >> > >>> Please mail me your "ifconfig" output. > >>> > >>> Stephan > >>> > >>> > >>> > >>> > >>>> -----Ursprüngliche Nachricht----- > >>>> Von: Robert Welz [mailto:r_welz@web.de] > >>>> Gesendet: Montag, 17. Oktober 2005 12:10 > >>>> An: Xen-users@lists.xensource.com > >>>> Betreff: [Xen-users] SuSE 10 no network in dom0 - arp problem? > >>>> > >>>> > >>>> Hello. > >>>> I have installed the SuSE Linux 10 XEN kernel but no domU > >>>> > >> yet. Now I > >> > >>>> cannot ping to and from dom0. I get lots of ARP broadcasts > >>>> > >> from dom0 > >> > >>>> but dom0 seems to ignore ARP answers. When pinging to dom0 it > >>>> ignores > >>>> arp requests. This happens regardless xend is running or not. This > >>>> happens in the xen kernel only, when booting stock kernel all works > >>>> as expected. > >>>> > >>>> What can I do? > >>>> > >>>> Robert > >>>> > >>>> _______________________________________________ > >>>> Xen-users mailing list > >>>> Xen-users@lists.xensource.com > >>>> http://lists.xensource.com/xen-users > >>>> > >>>> > >>>> > >>> > >>> _______________________________________________ > >>> Xen-users mailing list > >>> Xen-users@lists.xensource.com > >>> http://lists.xensource.com/xen-users > >>> > >>> > >> > >> > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.344 / Virus Database: 267.12.1/136 - Release Date: 15.10.2005___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Robert Welz
2005-Oct-17 12:30 UTC
Re: AW: [Xen-users] SuSE 10 no network in dom0 - arp problem?
xend suddenly refuses to set up the peth0 etc. I do a clean install now. I will be back here later in some hours. Thank you very much, Robert Welz Am 17.10.2005 um 14:20 schrieb Arnd Schmitter:> Are you using the default network script shipped with xen ? > > What''s the configuration of your network bridge ? What say brctl ? > > > >> -----Ursprüngliche Nachricht----- >> Von: xen-users-bounces@lists.xensource.com [mailto:xen-users- >> bounces@lists.xensource.com] Im Auftrag von Robert Welz >> Gesendet: Montag, 17. Oktober 2005 14:13 >> An: Stephan Böni >> Cc: Xen-users@lists.xensource.com >> Betreff: Re: [Xen-users] SuSE 10 no network in dom0 - arp problem? >> >> Hello. >> That didn''t help. >> >> I see the same arp broadcast storms as before. >> >> Robert >> >> >> Am 17.10.2005 um 13:58 schrieb Stephan Böni: >> >> >>> Try ''export LC_MESSAGES=POSIX'' before starting xend. The Xen >>> network >>> script has problems parsing your ifconfig because its german. >>> >>> Stephan >>> >>> >>> >>> >>>> -----Ursprüngliche Nachricht----- >>>> Von: Robert Welz [mailto:r_welz@web.de] >>>> Gesendet: Montag, 17. Oktober 2005 13:45 >>>> An: Stephan Böni >>>> Cc: Xen-users@lists.xensource.com >>>> Betreff: Re: [Xen-users] SuSE 10 no network in dom0 - arp problem? >>>> >>>> >>>> Here it is: >>>> >>>> >>>> eth0 Protokoll:Ethernet Hardware Adresse 00:0E:0C:72:41:41 >>>> inet Adresse:192.168.2.128 Bcast:192.168.2.255 Maske: >>>> 255.255.255.0 >>>> inet6 Adresse: fe80::20e:cff:fe72:4141/64 >>>> Gültigkeitsbereich:Verbindung >>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>> RX packets:7 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 Sendewarteschlangenlänge:0 >>>> RX bytes:498 (498.0 b) TX bytes:2064 (2.0 Kb) >>>> >>>> lo Protokoll:Lokale Schleife >>>> inet Adresse:127.0.0.1 Maske:255.0.0.0 >>>> inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine >>>> UP LOOPBACK RUNNING MTU:16436 Metric:1 >>>> RX packets:107 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:107 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 Sendewarteschlangenlänge:0 >>>> RX bytes:8414 (8.2 Kb) TX bytes:8414 (8.2 Kb) >>>> >>>> peth0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF >>>> inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 >>>> Gültigkeitsbereich:Verbindung >>>> UP BROADCAST NOARP MULTICAST MTU:1500 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 Sendewarteschlangenlänge:1000 >>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >>>> Basisadresse:0x9000 Speicher:d6800000-d6820000 >>>> >>>> vif0.0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF >>>> inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 >>>> Gültigkeitsbereich:Verbindung >>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>> RX packets:28 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 Sendewarteschlangenlänge:0 >>>> RX bytes:2064 (2.0 Kb) TX bytes:588 (588.0 b) >>>> >>>> xenbr0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF >>>> inet6 Adresse: fe80::200:ff:fe00:0/64 >>>> Gültigkeitsbereich:Verbindung >>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>> RX packets:27 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 Sendewarteschlangenlänge:0 >>>> RX bytes:1596 (1.5 Kb) TX bytes:378 (378.0 b) >>>> >>>> >>>> Am 17.10.2005 um 13:16 schrieb Stephan Böni: >>>> >>>> >>>> >>>>> Please mail me your "ifconfig" output. >>>>> >>>>> Stephan >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> -----Ursprüngliche Nachricht----- >>>>>> Von: Robert Welz [mailto:r_welz@web.de] >>>>>> Gesendet: Montag, 17. Oktober 2005 12:10 >>>>>> An: Xen-users@lists.xensource.com >>>>>> Betreff: [Xen-users] SuSE 10 no network in dom0 - arp problem? >>>>>> >>>>>> >>>>>> Hello. >>>>>> I have installed the SuSE Linux 10 XEN kernel but no domU >>>>>> >>>>>> >>>> yet. Now I >>>> >>>> >>>>>> cannot ping to and from dom0. I get lots of ARP broadcasts >>>>>> >>>>>> >>>> from dom0 >>>> >>>> >>>>>> but dom0 seems to ignore ARP answers. When pinging to dom0 it >>>>>> ignores >>>>>> arp requests. This happens regardless xend is running or not. >>>>>> This >>>>>> happens in the xen kernel only, when booting stock kernel all >>>>>> works >>>>>> as expected. >>>>>> >>>>>> What can I do? >>>>>> >>>>>> Robert >>>>>> >>>>>> _______________________________________________ >>>>>> Xen-users mailing list >>>>>> Xen-users@lists.xensource.com >>>>>> http://lists.xensource.com/xen-users >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Xen-users mailing list >>>>> Xen-users@lists.xensource.com >>>>> http://lists.xensource.com/xen-users >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> >> -- >> No virus found in this incoming message. >> Checked by AVG Anti-Virus. >> Version: 7.0.344 / Virus Database: 267.12.1/136 - Release Date: >> 15.10.2005 >> > > > > > > > > ___________________________________________________________ > Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier > anmelden: http://mail.yahoo.de >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Robert Welz
2005-Oct-17 13:33 UTC
Re: AW: [Xen-users] SuSE 10 no network in dom0 - arp problem?
brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 shouldn''t xenbr0 be bound to eth0? Robert Am 17.10.2005 um 14:20 schrieb Arnd Schmitter:> Are you using the default network script shipped with xen ? > > What''s the configuration of your network bridge ? What say brctl ? > > > >> -----Ursprüngliche Nachricht----- >> Von: xen-users-bounces@lists.xensource.com [mailto:xen-users- >> bounces@lists.xensource.com] Im Auftrag von Robert Welz >> Gesendet: Montag, 17. Oktober 2005 14:13 >> An: Stephan Böni >> Cc: Xen-users@lists.xensource.com >> Betreff: Re: [Xen-users] SuSE 10 no network in dom0 - arp problem? >> >> Hello. >> That didn''t help. >> >> I see the same arp broadcast storms as before. >> >> Robert >> >> >> Am 17.10.2005 um 13:58 schrieb Stephan Böni: >> >> >>> Try ''export LC_MESSAGES=POSIX'' before starting xend. The Xen >>> network >>> script has problems parsing your ifconfig because its german. >>> >>> Stephan >>> >>> >>> >>> >>>> -----Ursprüngliche Nachricht----- >>>> Von: Robert Welz [mailto:r_welz@web.de] >>>> Gesendet: Montag, 17. Oktober 2005 13:45 >>>> An: Stephan Böni >>>> Cc: Xen-users@lists.xensource.com >>>> Betreff: Re: [Xen-users] SuSE 10 no network in dom0 - arp problem? >>>> >>>> >>>> Here it is: >>>> >>>> >>>> eth0 Protokoll:Ethernet Hardware Adresse 00:0E:0C:72:41:41 >>>> inet Adresse:192.168.2.128 Bcast:192.168.2.255 Maske: >>>> 255.255.255.0 >>>> inet6 Adresse: fe80::20e:cff:fe72:4141/64 >>>> Gültigkeitsbereich:Verbindung >>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>> RX packets:7 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 Sendewarteschlangenlänge:0 >>>> RX bytes:498 (498.0 b) TX bytes:2064 (2.0 Kb) >>>> >>>> lo Protokoll:Lokale Schleife >>>> inet Adresse:127.0.0.1 Maske:255.0.0.0 >>>> inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine >>>> UP LOOPBACK RUNNING MTU:16436 Metric:1 >>>> RX packets:107 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:107 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 Sendewarteschlangenlänge:0 >>>> RX bytes:8414 (8.2 Kb) TX bytes:8414 (8.2 Kb) >>>> >>>> peth0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF >>>> inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 >>>> Gültigkeitsbereich:Verbindung >>>> UP BROADCAST NOARP MULTICAST MTU:1500 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 Sendewarteschlangenlänge:1000 >>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >>>> Basisadresse:0x9000 Speicher:d6800000-d6820000 >>>> >>>> vif0.0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF >>>> inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 >>>> Gültigkeitsbereich:Verbindung >>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>> RX packets:28 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 Sendewarteschlangenlänge:0 >>>> RX bytes:2064 (2.0 Kb) TX bytes:588 (588.0 b) >>>> >>>> xenbr0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF >>>> inet6 Adresse: fe80::200:ff:fe00:0/64 >>>> Gültigkeitsbereich:Verbindung >>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>> RX packets:27 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 Sendewarteschlangenlänge:0 >>>> RX bytes:1596 (1.5 Kb) TX bytes:378 (378.0 b) >>>> >>>> >>>> Am 17.10.2005 um 13:16 schrieb Stephan Böni: >>>> >>>> >>>> >>>>> Please mail me your "ifconfig" output. >>>>> >>>>> Stephan >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> -----Ursprüngliche Nachricht----- >>>>>> Von: Robert Welz [mailto:r_welz@web.de] >>>>>> Gesendet: Montag, 17. Oktober 2005 12:10 >>>>>> An: Xen-users@lists.xensource.com >>>>>> Betreff: [Xen-users] SuSE 10 no network in dom0 - arp problem? >>>>>> >>>>>> >>>>>> Hello. >>>>>> I have installed the SuSE Linux 10 XEN kernel but no domU >>>>>> >>>>>> >>>> yet. Now I >>>> >>>> >>>>>> cannot ping to and from dom0. I get lots of ARP broadcasts >>>>>> >>>>>> >>>> from dom0 >>>> >>>> >>>>>> but dom0 seems to ignore ARP answers. When pinging to dom0 it >>>>>> ignores >>>>>> arp requests. This happens regardless xend is running or not. >>>>>> This >>>>>> happens in the xen kernel only, when booting stock kernel all >>>>>> works >>>>>> as expected. >>>>>> >>>>>> What can I do? >>>>>> >>>>>> Robert >>>>>> >>>>>> _______________________________________________ >>>>>> Xen-users mailing list >>>>>> Xen-users@lists.xensource.com >>>>>> http://lists.xensource.com/xen-users >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Xen-users mailing list >>>>> Xen-users@lists.xensource.com >>>>> http://lists.xensource.com/xen-users >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> >> -- >> No virus found in this incoming message. >> Checked by AVG Anti-Virus. >> Version: 7.0.344 / Virus Database: 267.12.1/136 - Release Date: >> 15.10.2005 >> > > > > > > > > ___________________________________________________________ > Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier > anmelden: http://mail.yahoo.de > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Richard Wackerbarth
2005-Oct-17 14:00 UTC
Re: AW: [Xen-users] SuSE 10 no network in dom0 - arp problem?
On Oct 17, 2005, at 8:33 AM, Robert Welz wrote:> brctl show > bridge name bridge id STP > enabled interfaces > xenbr0 8000.feffffffffff > no vif0.0 > > peth0 > > shouldn''t xenbr0 be bound to eth0? > > RobertRobert, I''ll jump in here because I''ve had similar problems and, by explaining my reasoning, I will hopefully be corrected if I am wrong. I believe that the answer is "NO". Given the recent (on the Unix timeline) ability to rename devices, you should look at the overall dom-net architecture rather than the names. peth0 is the (renamed) physical I/O device and it is bound to the virtual "hub" xenbr0. We also attach to that bridge one xen net device "vifX.0" where X is the domain number. The other end of that xen net device is called "eth0" in each of the respective domains. dom0 is handled just like the various domU. An application sends a packet via "eth0". Xen causes that packet to appear on vif0.0 which is bound to xenbr0. Therefore the packet is replicated on peth0 and appears on the actual wire. As I see it, the arp difficulty is a result of the fct that they have "moved" the real MAC address from peth0 to eth0. I think that the xen net device acts as a ppp cross-connect and does not pass arp since it doesn''t need arp to establish routing since there is just one device on the other end of the (virtual) wire. Richard> > > Am 17.10.2005 um 14:20 schrieb Arnd Schmitter: > > >> Are you using the default network script shipped with xen ? >> >> What''s the configuration of your network bridge ? What say brctl ? >> >> >> >> >>> -----Ursprüngliche Nachricht----- >>> Von: xen-users-bounces@lists.xensource.com [mailto:xen-users- >>> bounces@lists.xensource.com] Im Auftrag von Robert Welz >>> Gesendet: Montag, 17. Oktober 2005 14:13 >>> An: Stephan Böni >>> Cc: Xen-users@lists.xensource.com >>> Betreff: Re: [Xen-users] SuSE 10 no network in dom0 - arp problem? >>> >>> Hello. >>> That didn''t help. >>> >>> I see the same arp broadcast storms as before. >>> >>> Robert >>> >>> >>> Am 17.10.2005 um 13:58 schrieb Stephan Böni: >>> >>> >>> >>>> Try ''export LC_MESSAGES=POSIX'' before starting xend. The Xen >>>> network >>>> script has problems parsing your ifconfig because its german. >>>> >>>> Stephan >>>> >>>> >>>> >>>> >>>> >>>>> -----Ursprüngliche Nachricht----- >>>>> Von: Robert Welz [mailto:r_welz@web.de] >>>>> Gesendet: Montag, 17. Oktober 2005 13:45 >>>>> An: Stephan Böni >>>>> Cc: Xen-users@lists.xensource.com >>>>> Betreff: Re: [Xen-users] SuSE 10 no network in dom0 - arp problem? >>>>> >>>>> >>>>> Here it is: >>>>> >>>>> >>>>> eth0 Protokoll:Ethernet Hardware Adresse 00:0E:0C:72:41:41 >>>>> inet Adresse:192.168.2.128 Bcast:192.168.2.255 Maske: >>>>> 255.255.255.0 >>>>> inet6 Adresse: fe80::20e:cff:fe72:4141/64 >>>>> Gültigkeitsbereich:Verbindung >>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>>> RX packets:7 errors:0 dropped:0 overruns:0 frame:0 >>>>> TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 >>>>> collisions:0 Sendewarteschlangenlänge:0 >>>>> RX bytes:498 (498.0 b) TX bytes:2064 (2.0 Kb) >>>>> >>>>> lo Protokoll:Lokale Schleife >>>>> inet Adresse:127.0.0.1 Maske:255.0.0.0 >>>>> inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine >>>>> UP LOOPBACK RUNNING MTU:16436 Metric:1 >>>>> RX packets:107 errors:0 dropped:0 overruns:0 frame:0 >>>>> TX packets:107 errors:0 dropped:0 overruns:0 carrier:0 >>>>> collisions:0 Sendewarteschlangenlänge:0 >>>>> RX bytes:8414 (8.2 Kb) TX bytes:8414 (8.2 Kb) >>>>> >>>>> peth0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF >>>>> inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 >>>>> Gültigkeitsbereich:Verbindung >>>>> UP BROADCAST NOARP MULTICAST MTU:1500 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 Sendewarteschlangenlänge:1000 >>>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >>>>> Basisadresse:0x9000 Speicher:d6800000-d6820000 >>>>> >>>>> vif0.0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF >>>>> inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 >>>>> Gültigkeitsbereich:Verbindung >>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>>> RX packets:28 errors:0 dropped:0 overruns:0 frame:0 >>>>> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 >>>>> collisions:0 Sendewarteschlangenlänge:0 >>>>> RX bytes:2064 (2.0 Kb) TX bytes:588 (588.0 b) >>>>> >>>>> xenbr0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF >>>>> inet6 Adresse: fe80::200:ff:fe00:0/64 >>>>> Gültigkeitsbereich:Verbindung >>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>>> RX packets:27 errors:0 dropped:0 overruns:0 frame:0 >>>>> TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 >>>>> collisions:0 Sendewarteschlangenlänge:0 >>>>> RX bytes:1596 (1.5 Kb) TX bytes:378 (378.0 b) >>>>> >>>>> >>>>> Am 17.10.2005 um 13:16 schrieb Stephan Böni: >>>>> >>>>> >>>>> >>>>> >>>>>> Please mail me your "ifconfig" output. >>>>>> >>>>>> Stephan >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> -----Ursprüngliche Nachricht----- >>>>>>> Von: Robert Welz [mailto:r_welz@web.de] >>>>>>> Gesendet: Montag, 17. Oktober 2005 12:10 >>>>>>> An: Xen-users@lists.xensource.com >>>>>>> Betreff: [Xen-users] SuSE 10 no network in dom0 - arp problem? >>>>>>> >>>>>>> >>>>>>> Hello. >>>>>>> I have installed the SuSE Linux 10 XEN kernel but no domU >>>>>>> >>>>>>> >>>>>>> >>>>> yet. Now I >>>>> >>>>> >>>>> >>>>>>> cannot ping to and from dom0. I get lots of ARP broadcasts >>>>>>> >>>>>>> >>>>>>> >>>>> from dom0 >>>>> >>>>> >>>>> >>>>>>> but dom0 seems to ignore ARP answers. When pinging to dom0 it >>>>>>> ignores >>>>>>> arp requests. This happens regardless xend is running or not. >>>>>>> This >>>>>>> happens in the xen kernel only, when booting stock kernel all >>>>>>> works >>>>>>> as expected. >>>>>>> >>>>>>> What can I do? >>>>>>> >>>>>>> Robert >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Xen-users mailing list >>>>>>> Xen-users@lists.xensource.com >>>>>>> http://lists.xensource.com/xen-users >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Xen-users mailing list >>>>>> Xen-users@lists.xensource.com >>>>>> http://lists.xensource.com/xen-users >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >>> >>> >>> -- >>> No virus found in this incoming message. >>> Checked by AVG Anti-Virus. >>> Version: 7.0.344 / Virus Database: 267.12.1/136 - Release Date: >>> 15.10.2005 >>> >>> >> >> >> >> >> >> >> >> ___________________________________________________________ >> Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier >> anmelden: http://mail.yahoo.de >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > > !DSPAM:4353a87f405001367311775! > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Arnd Schmitter
2005-Oct-17 14:03 UTC
RE: [Xen-users] SuSE 10 no network in dom0 - arp problem?
On my System eth0 is connected to the bridge and working. Maybe there is the Problem. On my Debiansystem I needed to add following line at the beginning of the network script: /etc/xen/scripts/network: #!/bin/sh # ... # LANG="C" ... The Problem above corrected above, is that your locale changes the output from ifconfig. The title of the MAC Address is so changed from HWaddr -> Hardware Addresse. The network script parses the output of ifconfig for HWaddr and so don''t find the right entry. Arnd> -----Ursprüngliche Nachricht----- > Von: xen-users-bounces@lists.xensource.com [mailto:xen-users- > bounces@lists.xensource.com] Im Auftrag von Robert Welz > Gesendet: Montag, 17. Oktober 2005 15:34 > An: Arnd Schmitter > Cc: Xen-users@lists.xensource.com > Betreff: Re: AW: [Xen-users] SuSE 10 no network in dom0 - arp problem? > > brctl show > bridge name bridge id STP > enabled interfaces > xenbr0 8000.feffffffffff > no vif0.0 > > peth0 > > shouldn''t xenbr0 be bound to eth0? > > Robert > > >___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Robert Welz
2005-Oct-17 15:25 UTC
Re: AW: [Xen-users] SuSE 10 no network in dom0 - arp problem?
Am 17.10.2005 um 16:00 schrieb Richard Wackerbarth:> As I see it, the arp difficulty is a result of the fct that they > have "moved" the real MAC address from peth0 to eth0. I think that > the xen net device acts as a ppp cross-connect and does not pass > arp since it doesn''t need arp to establish routing since there is > just one device on the other end of the (virtual) wire.Thanks. Now I now why it does''t work. Will that work if I give peth0 its own ip address and configure my route gateway through peth0? So in which way is xen 3.0 in SuSE 10 usable then? - DomU''s cannot be installed since install source must be network based (NFS or the like). NFS doesn''t work because I have no network. - No softwareupgrade for Dom0. Obviously if no network ... The change from xen 2.0 to xen 3.0 fixed some problems, my serial ports work now for my USV but introduced the network issue. Is there another distro except SuSE which has a working xen 3.0 ? Whats about debian? Robert _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Stephan Böni
2005-Oct-17 16:45 UTC
Re: [Xen-users] SuSE 10 no network in dom0 - arp problem?
Perhaps you should have a look on: http://www.suse.de/~garloff/linux/xen/RPMs-100/ There is a newer Xen3 build for SUSE 10.0. It should solve your netwerk problems. Stephan> -----Ursprüngliche Nachricht----- > Von: Richard Wackerbarth [mailto:richard@nfsnet.org] > Gesendet: Montag, 17. Oktober 2005 16:00 > An: Robert Welz > Cc: Xen-users@lists.xensource.com; Arnd Schmitter > Betreff: Re: AW: [Xen-users] SuSE 10 no network in dom0 - arp problem? > > > > On Oct 17, 2005, at 8:33 AM, Robert Welz wrote: > > > brctl show > > bridge name bridge id STP > > enabled interfaces > > xenbr0 8000.feffffffffff > > no vif0.0 > > > > > peth0 > > > > shouldn''t xenbr0 be bound to eth0? > > > > Robert > > Robert, > I''ll jump in here because I''ve had similar problems and, by > explaining my reasoning, I will hopefully be corrected if I am wrong. > > I believe that the answer is "NO". > Given the recent (on the Unix timeline) ability to rename devices, > you should look at the overall dom-net architecture rather than the > names. > > peth0 is the (renamed) physical I/O device and it is bound to the > virtual "hub" xenbr0. > We also attach to that bridge one xen net device "vifX.0" where X is > the domain number. > The other end of that xen net device is called "eth0" in each of the > respective domains. > > dom0 is handled just like the various domU. An application sends a > packet via "eth0". Xen causes that packet to appear on vif0.0 which > is bound to xenbr0. Therefore the packet is replicated on peth0 and > appears on the actual wire. > > As I see it, the arp difficulty is a result of the fct that > they have > "moved" the real MAC address from peth0 to eth0. I think that > the xen > net device acts as a ppp cross-connect and does not pass arp > since it > doesn''t need arp to establish routing since there is just one device > on the other end of the (virtual) wire. > > Richard > > > > > > > Am 17.10.2005 um 14:20 schrieb Arnd Schmitter: > > > > > >> Are you using the default network script shipped with xen ? > >> > >> What''s the configuration of your network bridge ? What say brctl ? > >> > >> > >> > >> > >>> -----Ursprüngliche Nachricht----- > >>> Von: xen-users-bounces@lists.xensource.com [mailto:xen-users- > >>> bounces@lists.xensource.com] Im Auftrag von Robert Welz > >>> Gesendet: Montag, 17. Oktober 2005 14:13 > >>> An: Stephan Böni > >>> Cc: Xen-users@lists.xensource.com > >>> Betreff: Re: [Xen-users] SuSE 10 no network in dom0 - arp problem? > >>> > >>> Hello. > >>> That didn''t help. > >>> > >>> I see the same arp broadcast storms as before. > >>> > >>> Robert > >>> > >>> > >>> Am 17.10.2005 um 13:58 schrieb Stephan Böni: > >>> > >>> > >>> > >>>> Try ''export LC_MESSAGES=POSIX'' before starting xend. The Xen > >>>> network > >>>> script has problems parsing your ifconfig because its german. > >>>> > >>>> Stephan > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>> -----Ursprüngliche Nachricht----- > >>>>> Von: Robert Welz [mailto:r_welz@web.de] > >>>>> Gesendet: Montag, 17. Oktober 2005 13:45 > >>>>> An: Stephan Böni > >>>>> Cc: Xen-users@lists.xensource.com > >>>>> Betreff: Re: [Xen-users] SuSE 10 no network in dom0 - > arp problem? > >>>>> > >>>>> > >>>>> Here it is: > >>>>> > >>>>> > >>>>> eth0 Protokoll:Ethernet Hardware Adresse 00:0E:0C:72:41:41 > >>>>> inet Adresse:192.168.2.128 > Bcast:192.168.2.255 Maske: > >>>>> 255.255.255.0 > >>>>> inet6 Adresse: fe80::20e:cff:fe72:4141/64 > >>>>> Gültigkeitsbereich:Verbindung > >>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >>>>> RX packets:7 errors:0 dropped:0 overruns:0 frame:0 > >>>>> TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 > >>>>> collisions:0 Sendewarteschlangenlänge:0 > >>>>> RX bytes:498 (498.0 b) TX bytes:2064 (2.0 Kb) > >>>>> > >>>>> lo Protokoll:Lokale Schleife > >>>>> inet Adresse:127.0.0.1 Maske:255.0.0.0 > >>>>> inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine > >>>>> UP LOOPBACK RUNNING MTU:16436 Metric:1 > >>>>> RX packets:107 errors:0 dropped:0 overruns:0 frame:0 > >>>>> TX packets:107 errors:0 dropped:0 overruns:0 > carrier:0 > >>>>> collisions:0 Sendewarteschlangenlänge:0 > >>>>> RX bytes:8414 (8.2 Kb) TX bytes:8414 (8.2 Kb) > >>>>> > >>>>> peth0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF > >>>>> inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 > >>>>> Gültigkeitsbereich:Verbindung > >>>>> UP BROADCAST NOARP MULTICAST MTU:1500 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 Sendewarteschlangenlänge:1000 > >>>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > >>>>> Basisadresse:0x9000 Speicher:d6800000-d6820000 > >>>>> > >>>>> vif0.0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF > >>>>> inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 > >>>>> Gültigkeitsbereich:Verbindung > >>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >>>>> RX packets:28 errors:0 dropped:0 overruns:0 frame:0 > >>>>> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 > >>>>> collisions:0 Sendewarteschlangenlänge:0 > >>>>> RX bytes:2064 (2.0 Kb) TX bytes:588 (588.0 b) > >>>>> > >>>>> xenbr0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF > >>>>> inet6 Adresse: fe80::200:ff:fe00:0/64 > >>>>> Gültigkeitsbereich:Verbindung > >>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >>>>> RX packets:27 errors:0 dropped:0 overruns:0 frame:0 > >>>>> TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 > >>>>> collisions:0 Sendewarteschlangenlänge:0 > >>>>> RX bytes:1596 (1.5 Kb) TX bytes:378 (378.0 b) > >>>>> > >>>>> > >>>>> Am 17.10.2005 um 13:16 schrieb Stephan Böni: > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>> Please mail me your "ifconfig" output. > >>>>>> > >>>>>> Stephan > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>> -----Ursprüngliche Nachricht----- > >>>>>>> Von: Robert Welz [mailto:r_welz@web.de] > >>>>>>> Gesendet: Montag, 17. Oktober 2005 12:10 > >>>>>>> An: Xen-users@lists.xensource.com > >>>>>>> Betreff: [Xen-users] SuSE 10 no network in dom0 - arp problem? > >>>>>>> > >>>>>>> > >>>>>>> Hello. > >>>>>>> I have installed the SuSE Linux 10 XEN kernel but no domU > >>>>>>> > >>>>>>> > >>>>>>> > >>>>> yet. Now I > >>>>> > >>>>> > >>>>> > >>>>>>> cannot ping to and from dom0. I get lots of ARP broadcasts > >>>>>>> > >>>>>>> > >>>>>>> > >>>>> from dom0 > >>>>> > >>>>> > >>>>> > >>>>>>> but dom0 seems to ignore ARP answers. When pinging to dom0 it > >>>>>>> ignores > >>>>>>> arp requests. This happens regardless xend is running > or not. > >>>>>>> This > >>>>>>> happens in the xen kernel only, when booting stock > kernel all > >>>>>>> works > >>>>>>> as expected. > >>>>>>> > >>>>>>> What can I do? > >>>>>>> > >>>>>>> Robert > >>>>>>> > >>>>>>> _______________________________________________ > >>>>>>> Xen-users mailing list > >>>>>>> Xen-users@lists.xensource.com > >>>>>>> http://lists.xensource.com/xen-users > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Xen-users mailing list > >>>>>> Xen-users@lists.xensource.com > >>>>>> http://lists.xensource.com/xen-users > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>> > >>>> > >>>> > >>> > >>> > >>> _______________________________________________ > >>> Xen-users mailing list > >>> Xen-users@lists.xensource.com > >>> http://lists.xensource.com/xen-users > >>> > >>> > >>> -- > >>> No virus found in this incoming message. > >>> Checked by AVG Anti-Virus. > >>> Version: 7.0.344 / Virus Database: 267.12.1/136 - Release Date: > >>> 15.10.2005 > >>> > >>> > >> > >> > >> > >> > >> > >> > >> > >> ___________________________________________________________ > >> Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher > kostenlos - Hier > >> anmelden: http://mail.yahoo.de > >> > >> > >> _______________________________________________ > >> Xen-users mailing list > >> Xen-users@lists.xensource.com > >> http://lists.xensource.com/xen-users > >> > >> > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > !DSPAM:4353a87f405001367311775! > > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Robert Welz
2005-Oct-17 16:58 UTC
Re: [Xen-users] SuSE 10 no network in dom0 - arp problem?
Am 17.10.2005 um 18:45 schrieb Stephan Böni:> Perhaps you should have a look on: http://www.suse.de/~garloff/ > linux/xen/RPMs-100/ > > There is a newer Xen3 build for SUSE 10.0. It should solve your > netwerk problems. > > StephanGreat. I''ll try them tomorrow. Thank you, Robert _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Frank Fiene
2005-Oct-17 18:33 UTC
Re: [Xen-users] SuSE 10 no network in dom0 - arp problem?
Am Montag 17 Oktober 2005 18:45 schrieb Stephan Böni:> Perhaps you should have a look on: > http://www.suse.de/~garloff/linux/xen/RPMs-100/ > > There is a newer Xen3 build for SUSE 10.0. It should solve your > netwerk problems.Dito! We''ve played only with the latest kernel in the Xen workshop with Kurt, Ian, Keir and Gerd (thanks to all four!) at Linux-Kongress in Hamburg, which Kurt has built directly during the workshop. Maybe the old rpm was broken! And everything was fine with SuSE-10.0 as Dom0 and DomU! Frank -- uniorg Solutions GmbH - Märkische Strasse 237 - 44141 Dortmund ffiene@veka.com - Tel:0231-9497-262 -- Ein Unternehmen der uniorg-Gruppe _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Here it is:Please can you try adding "export LANG=C" at the top of the network-bridge and bif-bridge scripts. The local language is breaking the parsing. Thanks, Ian> > eth0 Protokoll:Ethernet Hardware Adresse 00:0E:0C:72:41:41 > inet Adresse:192.168.2.128 Bcast:192.168.2.255 Maske: > 255.255.255.0 > inet6 Adresse: fe80::20e:cff:fe72:4141/64 > Gültigkeitsbereich:Verbindung > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:7 errors:0 dropped:0 overruns:0 frame:0 > TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 Sendewarteschlangenlänge:0 > RX bytes:498 (498.0 b) TX bytes:2064 (2.0 Kb) > > lo Protokoll:Lokale Schleife > inet Adresse:127.0.0.1 Maske:255.0.0.0 > inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:107 errors:0 dropped:0 overruns:0 frame:0 > TX packets:107 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 Sendewarteschlangenlänge:0 > RX bytes:8414 (8.2 Kb) TX bytes:8414 (8.2 Kb) > > peth0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF > inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 > Gültigkeitsbereich:Verbindung > UP BROADCAST NOARP MULTICAST MTU:1500 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 Sendewarteschlangenlänge:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Basisadresse:0x9000 Speicher:d6800000-d6820000 > > vif0.0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF > inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 > Gültigkeitsbereich:Verbindung > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:28 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 Sendewarteschlangenlänge:0 > RX bytes:2064 (2.0 Kb) TX bytes:588 (588.0 b) > > xenbr0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF > inet6 Adresse: fe80::200:ff:fe00:0/64 > Gültigkeitsbereich:Verbindung > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:27 errors:0 dropped:0 overruns:0 frame:0 > TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 Sendewarteschlangenlänge:0 > RX bytes:1596 (1.5 Kb) TX bytes:378 (378.0 b) > > > Am 17.10.2005 um 13:16 schrieb Stephan Böni: > > > Please mail me your "ifconfig" output. > > > > Stephan > > > > > > > >> -----Ursprüngliche Nachricht----- > >> Von: Robert Welz [mailto:r_welz@web.de] > >> Gesendet: Montag, 17. Oktober 2005 12:10 > >> An: Xen-users@lists.xensource.com > >> Betreff: [Xen-users] SuSE 10 no network in dom0 - arp problem? > >> > >> > >> Hello. > >> I have installed the SuSE Linux 10 XEN kernel but no domU > yet. Now I > >> cannot ping to and from dom0. I get lots of ARP broadcasts > from dom0 > >> but dom0 seems to ignore ARP answers. When pinging to dom0 > it ignores > >> arp requests. This happens regardless xend is running or not. This > >> happens in the xen kernel only, when booting stock kernel > all works > >> as expected. > >> > >> What can I do? > >> > >> Robert > >> > >> _______________________________________________ > >> Xen-users mailing list > >> Xen-users@lists.xensource.com > >> http://lists.xensource.com/xen-users > >> > >> > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Robert Welz
2005-Oct-18 07:28 UTC
Re: [Xen-users] SuSE 10 no network in dom0 - arp problem?
Am 17.10.2005 um 20:33 schrieb Frank Fiene:> Am Montag 17 Oktober 2005 18:45 schrieb Stephan Böni: > >> Perhaps you should have a look on: >> http://www.suse.de/~garloff/linux/xen/RPMs-100/ >> >> There is a newer Xen3 build for SUSE 10.0. It should solve your >> netwerk problems. >>I tried build 7398, 7313, 7267 and 6715 without success. No network, no serial ports. Robert _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Robert Welz
2005-Oct-18 07:52 UTC
Re: [Xen-users] SuSE 10 no network in dom0 - arp problem?
Am 18.10.2005 um 09:40 schrieb Nigel Head:> Perhaps a stupid question ... but I''ve forgotten this once, with > Xen 2 and it produced very similar problems ..... > > Do you have the SuSE Firewall running on dom0? If so it probably > prevents the bridge from working as it has a default DROP for > forwarding ... > > I had to patch the Xen2 interface setup script to add the > appropriate rule every time it created a new virtual interface. I > don''t know if this is still the same for X3 as I haven''t tried it yet. > > Regards, > > Nigel.iptables -L tells me default policy ACCEPT for all chains. :( Robert _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users