WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Fwd: Re: [Xen-users] Martian Source Networking Errors]

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Fwd: Re: [Xen-users] Martian Source Networking Errors]
From: "Juergen Schinker" <ba1020@xxxxxxxxxxxxxxxxxxx>
Date: Thu, 18 Jan 2007 14:40:15 -0000 (UTC)
Delivery-date: Thu, 18 Jan 2007 06:40:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.9a
------------------------ Ursprüngliche Nachricht -------------------------
Betreff: Re: [Xen-users] Martian Source Networking Errors
Von:     "Juergen Schinker" <ba1020@xxxxxxxxxxxxxxxxxxx>
Datum:   Do, 18.01.2007, 14:10
An:      "Bill Denney" <denney@xxxxxxxxxxxxxx>
--------------------------------------------------------------------------

Am Do, 18.01.2007, 13:55, schrieb Bill Denney:
> Hello,
>
> I've been having trouble with networking a win2003 domU in a SLES 10
> dom0.  dmesg is reporting messages like
>
> Jan 18 02:40:59 xen0 kernel: martian source 169.254.244.56 from
> 169.254.244.56, on dev tun0
> Jan 18 02:40:59 xen0 kernel: ll header:
> ff:ff:ff:ff:ff:ff:00:16:3e:04:63:ba:08:06
>
> when I try to allow the domU to get its own ip address via DHCP, and it
> gets messages like
>
> Jan 18 02:48:50 xen0 kernel: martian source 192.168.200.255 from
> 192.168.200.135, on dev tun0
> Jan 18 02:48:50 xen0 kernel: ll header:
> ff:ff:ff:ff:ff:ff:00:16:3e:04:63:ba:08:00
>
> when I try manually setting the ip address.
>
> With these errors I'm obviously getting no networking.  I've tried both
> enabling and disabling SuSEfirewall2 to no effect.  Any suggestions on
> how to make the kernel not drop these packets but forward them on
> through the bridge correctly?
>
> Thanks,
>
> Bill
>
> Here is the output of ifconfig:
>
> eth2      Link encap:Ethernet  HWaddr 00:19:BB:CA:4A:94
>           inet addr:192.168.200.100  Bcast:192.168.200.255
> Mask:255.255.255.0
>           inet6 addr: fe80::219:bbff:feca:4a94/64 Scope:Link
>           UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:7299 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2846 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:967244 (944.5 Kb)  TX bytes:510310 (498.3 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:31338 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:31338 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:161514340 (154.0 Mb)  TX bytes:161514340 (154.0 Mb)
>
> peth2     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:7294 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2841 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:1007244 (983.6 Kb)  TX bytes:523036 (510.7 Kb)
>           Interrupt:20 Memory:f8000000-f8011100
>
> tun0      Link encap:Ethernet  HWaddr F2:0F:DF:7A:2B:A1
>           inet6 addr: fe80::f00f:dfff:fe7a:2ba1/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:165 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:500
>           RX bytes:29799 (29.1 Kb)  TX bytes:688 (688.0 b)
>
> vif0.2    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:2846 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:7299 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:510310 (498.3 Kb)  TX bytes:967244 (944.5 Kb)
>
> vif19.0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:175 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> xenbr2    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:4262 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:601361 (587.2 Kb)  TX bytes:0 (0.0 b)
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>
thats obvious there are packets comin from where they should't
that means they come from Mars

Windows is generating itself an IP when it can't get one
thats always 169.254...
so Suse says they come fram Mars



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

<Prev in Thread] Current Thread [Next in Thread>