Hi, I have the following Problem: My Rootserver stands at a hoster, I run a debian sarge and installed Xen 3 there latetly. I booted the xen Kernel - everything ok. However: when I started xend, the server instantly stopped responding. My Hosters Support said, that was due to a sort of mac spoofing protection in the switch, which disabled the Port, to which my server is connected, because there arrived an unknown Mac Address from my Server at the switchport. ( btw: at that point, I had not configured any domU''s )>From the Xen Docs I understand that the bridge gets the mac from eth0which is then diabled. So - I dont understand where the ''spoofed'' Mac is coming from. I''m thinking if it would be a solution, du configure the Bridge''s and all virtual interfaces''s Mac by hand with eht0''s Mac ? ( what would be the best way to do it ?) I am cueless. ( I dont want to use NAT: I have two IPs ( only one NIC )for the Server and want the dom0 and one domU to run on one IP each. ) Tia _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I have the following Problem: My Rootserver stands at a hoster ( german 1und1 ), I run a debian sarge and installed Xen 3 there latetly. I booted the xen Kernel - everything ok. However: when I started xend, the server instantly stopped responding. My Hosters Support said, that was due to a sort of mac spoofing protection in the switch, which disabled the Port, to which my server is connected, because there arrived an unknown Mac Address from my Server at the switchport. ( btw: at that point, I had not configured any domU''s )>From the Xen Docs I understand that the bridge gets the mac from eth0which is then diabled. So - I dont understand where the ''spoofed'' Mac is coming from - at least as long I have no domU running. I am clueless. ( I dont want to use NAT: I have two IPs ( only one NIC )for the Server and want the dom0 and one domU to run on one IP each. ) Tia _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I have the following Problem: My Rootserver stands at a hoster ( german 1und1 ), I run a debian sarge and installed Xen 3 there latetly. I booted the xen Kernel - everything ok. However: when I started xend, the server instantly stopped responding. My Hosters Support said, that was due to a sort of mac spoofing protection in the switch, which disabled the Port, to which my server is connected, because there arrived an unknown Mac Address from my Server at the switchport. ( btw: at that point, I had not configured any domU''s )>From the Xen Docs I understand that the bridge gets the mac from eth0which is then diabled. So - I dont understand where the ''spoofed'' Mac is coming from - at least as long I have no domU running. I am clueless. ( I dont want to use NAT: I have two IPs ( only one NIC )for the Server and want the dom0 and one domU to run on one IP each. ) Tia _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Friday 19 May 2006 7:06 am, Heiko.Garrelfs wrote:> ( btw: at that point, I had not configured any domU''s ) > > From the Xen Docs I understand that the bridge gets the mac from eth0 > which is then diabled. > > So - I dont understand where the ''spoofed'' Mac is coming from - at least > as long I have no domU running.maybe the bridge is generating some STP (spanning tree protocol) events at setting up time. the hoster''s switch interprets it as if you''ve put your own switch at the given port (it would be a correct interpretation, btw). try to disable STP (brctl stp br0 off) before adding peth0 to it.> ( I dont want to use NAT: I have two IPs ( only one NIC )for the Server > and want the dom0 and one domU to run on one IP each. )make sure that you''re allowed to put two machines at that port. if you don''t use NAT or routing you''ll have to use two MACs at a single port. maybe you''ll have to ask them to register your new MAC to add it to their bridging table. -- Javier _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for this answer, I had not thought about stp before. But as far as I understand, STP is turned off by default in the network-bridge script ( ca line 160 in function create_bridge() Is there another place to disable it ? Javier Guerra wrote: Javier Guerra wrote:> On Friday 19 May 2006 7:06 am, Heiko.Garrelfs wrote: >> ( btw: at that point, I had not configured any domU''s ) >> >> From the Xen Docs I understand that the bridge gets the mac from eth0 >> which is then diabled. >> >> So - I dont understand where the ''spoofed'' Mac is coming from - at least >> as long I have no domU running. > > maybe the bridge is generating some STP (spanning tree protocol) events at > setting up time. the hoster''s switch interprets it as if you''ve put your own > switch at the given port (it would be a correct interpretation, btw). try to > disable STP (brctl stp br0 off) before adding peth0 to it. > >> ( I dont want to use NAT: I have two IPs ( only one NIC )for the Server >> and want the dom0 and one domU to run on one IP each. ) > > make sure that you''re allowed to put two machines at that port. if you don''t > use NAT or routing you''ll have to use two MACs at a single port. maybe > you''ll have to ask them to register your new MAC to add it to their bridging > table. > > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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
Hi all, I''ve successfully running XEN under SuSE 10.1 with CentOS/Debian/SuSE 10.1/RedHat AS4 Domains. All are woking fine but the SLES9 Domain won''t show a network interface under yast. I even followed http://lists.xensource.com/archives/html/xen-users/2006-05/msg00135.html http://lists.xensource.com/archives/html/xen-users/2006-05/msg00135.html But neither of them worked. I''ve installed SLES 9 via "Installation into directory" and copied the modules from the master domains (as already done on the other domains). Even the xennet module is showing. Any idea? Thanks for your help Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi all, I''ve successfully running XEN under SuSE 10.1 with CentOS/Debian/SuSE 10.1/RedHat AS4 Domains. All are woking fine but the SLES9 Domain won''t show a network interface under yast. I even followed http://lists.xensource.com/archives/html/xen-users/2006-05/msg00135.html http://lists.xensource.com/archives/html/xen-users/2006-05/msg00135.html But neither of them worked. I''ve installed SLES 9 via "Installation into directory" and copied the modules from the master domains (as already done on the other domains). Even the xennet module is showing. Any idea? Thanks for your help Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, May 18, 2006 at 08:51:28PM +0200, Heiko.Garrelfs wrote:> My Rootserver stands at a hoster ( german 1und1 ), I run a debian sarge > and installed Xen 3 there latetly. > I booted the xen Kernel - everything ok. > However: when I started xend, the server instantly stopped responding. > My Hosters Support said, that was due to a sort of mac spoofing > protection in the switch, which disabled the Port, to which my server is > connected, because there arrived an unknown Mac Address from my Server > at the switchport. > > ( btw: at that point, I had not configured any domU''s ) > > From the Xen Docs I understand that the bridge gets the mac from eth0 > which is then diabled. > > So - I dont understand where the ''spoofed'' Mac is coming from - at least > as long I have no domU running.I don''t know where the packets are coming from either. But see below.> ( I dont want to use NAT: I have two IPs ( only one NIC )for the Server > and want the dom0 and one domU to run on one IP each. )Have you tried the routed network configuration? That should avoid the problem of spoofed MAC addresses, since it doesn''t use the bridging code, and should configure Dom-0 to use proxy ARP so that all your IP addresses will be accessible to the outside using your original MAC address. --Michael Vrable _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
As far as I know xen uses IANA reserved address in the form of 00:16:3E:XX:XX:XX. Try configuring dom0 with vif=[''''] and use dhcp. You will that MAC address will have the above "manufacturer" address.> On Thu, May 18, 2006 at 08:51:28PM +0200, Heiko.Garrelfs wrote: > > My Rootserver stands at a hoster ( german 1und1 ), I run a debian sarge > > and installed Xen 3 there latetly. > > I booted the xen Kernel - everything ok. > > However: when I started xend, the server instantly stopped responding. > > My Hosters Support said, that was due to a sort of mac spoofing > > protection in the switch, which disabled the Port, to which my server is > > connected, because there arrived an unknown Mac Address from my Server > > at the switchport. > > > > ( btw: at that point, I had not configured any domU''s ) > > > > From the Xen Docs I understand that the bridge gets the mac from eth0 > > which is then diabled. > > > > So - I dont understand where the ''spoofed'' Mac is coming from - at least > > as long I have no domU running. > > I don''t know where the packets are coming from either. But see below. > > > ( I dont want to use NAT: I have two IPs ( only one NIC )for the Server > > and want the dom0 and one domU to run on one IP each. ) > > Have you tried the routed network configuration? That should avoid the > problem of spoofed MAC addresses, since it doesn''t use the bridging > code, and should configure Dom-0 to use proxy ARP so that all your IP > addresses will be accessible to the outside using your original MAC > address. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
From: "Jan Albrecht" <jan.albrecht@gmail.com>> I''ve successfully running XEN under SuSE 10.1 with CentOS/Debian/SuSE > 10.1/RedHat AS4 Domains. > All are woking fine but the SLES9 Domain won''t show a network > interface under yast. > I even followed > http://lists.xensource.com/archives/html/xen-users/2006-05/msg00135.html > http://lists.xensource.com/archives/html/xen-users/2006-05/msg00135.html > But neither of them worked. > I''ve installed SLES 9 via "Installation into directory" and copied the > modules from the master domains (as already done on the other > domains). Even the xennet module is showing.Hi, I''ve several working SuSE 9.3 running. In YaST you won''t see a card, but you could add a static interface an it works. HTH Daniel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Daniel Bauer wrote:> From: "Jan Albrecht" <jan.albrecht@gmail.com> > >> I''ve successfully running XEN under SuSE 10.1 with CentOS/Debian/SuSE >> 10.1/RedHat AS4 Domains. >> All are woking fine but the SLES9 Domain won''t show a network >> interface under yast. >> I even followed >> http://lists.xensource.com/archives/html/xen-users/2006-05/msg00135.html >> http://lists.xensource.com/archives/html/xen-users/2006-05/msg00135.html >> But neither of them worked. >> I''ve installed SLES 9 via "Installation into directory" and copied the >> modules from the master domains (as already done on the other >> domains). Even the xennet module is showing. > > > Hi, > > I''ve several working SuSE 9.3 running. In YaST you won''t see a card, > but you could add a static interface an it works.Hm, I tried that, but it didn''t worked. Even a "ifconfig -a" does not show any devices besides "lo" and "sit0". Any other idea? Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
From: "Jan Albrecht" <jan.albrecht@gmail.com>> Daniel Bauer wrote: >> From: "Jan Albrecht" <jan.albrecht@gmail.com> >>> I''ve successfully running XEN under SuSE 10.1 with >>> CentOS/Debian/SuSE >>> 10.1/RedHat AS4 Domains. >>> All are woking fine but the SLES9 Domain won''t show a network >>> interface under yast. >>> I even followed >>> http://lists.xensource.com/archives/html/xen-users/2006-05/msg00135.html >>> http://lists.xensource.com/archives/html/xen-users/2006-05/msg00135.html >>> But neither of them worked. >>> I''ve installed SLES 9 via "Installation into directory" and copied >>> the >>> modules from the master domains (as already done on the other >>> domains). Even the xennet module is showing. >> >> >> I''ve several working SuSE 9.3 running. In YaST you won''t see a card, >> but you could add a static interface an it works. > > Hm, I tried that, but it didn''t worked. Even a "ifconfig -a" does not > show any devices besides "lo" and "sit0". > > Any other idea?no sorry, I also don''t see a interface in YaST, but I add one without any hardware information (hwinfo is static-0 in YaST). YaST doesn''t detect a NIC. Daniel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users