Re: [Xen-users] network-route and vif-route setup help

["Md Mooktakim Ahmed" <mma@xxxxxxxxxxxxx>]

I got my connection back. It doesn't work.

-bash-3.00# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:3E:7D:2B:63
          inet addr:82.165.37.144  Bcast:82.165.37.144  Mask:255.255.255.255
          inet6 addr: fe80::216:3eff:fe7d:2b63/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:756 (756.0 b)

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)

and ip r:
-bash-3.00# ip r
169.254.0.0/16 dev eth0  scope link

if i try to add my own default route:
-bash-3.00# ip route replace default via 10.255.255.1
RTNETLINK answers: Network is unreachable

and even if i use dom0 as default route:
-bash-3.00# ip route replace default via 82.165.27.12
RTNETLINK answers: Network is unreachable


I just don't know what to do now.

On Tue, March 28, 2006 11:13 pm, Md Mooktakim Ahmed wrote:
> I just tried what you said below. I'm not sure if its working though. I tried 
> bridging
> one more time and still disconnected from the network. waiting for 1and1 to 
> reconnect me.
>  But i can access serial console.
>
>
> So what i see is this, ifconfig says:
> [root@cyclops ~]# ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:40:CA:80:5B:80 inet addr:82.165.27.12
> Bcast:82.165.27.12  Mask:255.255.255.255
> inet6 addr: fe80::240:caff:fe80:5b80/64 Scope:Link UP BROADCAST 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 txqueuelen:1000
> RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> Interrupt:23 Base address:0xe000
>
>
> 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:48 errors:0 dropped:0 overruns:0 frame:0
> TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:4360 (4.2 KiB)  TX bytes:4360 (4.2 KiB)
>
>
> vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF inet addr:82.165.27.12
> Bcast:82.165.27.12  Mask:255.255.255.255
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING 
> MULTICAST
> MTU:1500  Metric:1
> RX packets:10 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:5 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:588 (588.0 b)  TX bytes:0 (0.0 b)
>
>
>
> 82.165.27.12 is my main IP. vif1.0 seems to have been assigned the same ip.
> which probably makes sense because of what ip r says: [root@cyclops ~]# ip r
> 82.165.37.144 dev vif1.0  scope link  src 82.165.27.12
> 169.254.0.0/16 dev eth0  scope link
> default via 10.255.255.1 dev eth0
>
> 37.144 is my domU ip. not sure exactly whats going on. but it probably means 
> vif1.0 is
> connected on 144? no idea.
>
> and what i have in my domU config: vif = [ 'ip=82.165.37.144' ] ip = 
> "82.165.37.144"
> netmask="255.255.255.255" gateway="10.255.255.1" #gateway="82.165.27.12"
>
>
> the question is here do i use my isp's gateway? (10.*) the one for dom0? OR 
> do i use
> dom0 itself? since we are routing i should use dom0? I tried both. the 
> ifconfig and ip r
> output is the same.
>
> and lastly i used centos for domU too. so my 
> /etc/sysconfig/network-scripts/ifcfg-eth0
> is:
> DEVICE=eth0
> ONBOOT=yes
> BOOTPROTO=static
> IPADDR=82.165.37.144
> NETMASK=255.255.255.255
> GATEWAY=10.255.255.1
>
>
> Is everything correct here?
> I will send another email detailing if it worked when my connection was 
> reinstated.
>
>
> Ralf Steenbock:
>
>
>> I had the same problems with my new provider a few days ago. For me it
>> is working when I set
>>
>> echo 1 >/proc/sys/net/ipv4/ip_forward echo 1 > 
>> /proc/sys/net/ipv4/conf/eth0/proxy_arp
>>
>> in /etc/xen/scripts/network-route. /etc/xen/scripts/vif-route is unchanged. 
>> domUs have
>> to be configured with the public IPs you got from your provider like the 
>> following:
>>
>> vif = [ 'ip=your.public.domu.ip' ] ip="your.public.domu.ip"
>> netmask="your.domu.net.mask" gateway="your.providers.gateway.ip"
>>
>> After restarting you should see a line like the following in the output
>> of "ip r" in your dom0:
>>
>> your.public.domu.ip dev vif1  scope link  src your.public.dom0.ip
>>
>> I hope that I did not forget anything.
>> Good luck
>>
>>
>> Ralf
>>
>


-- 
Website: http://www.mooktakim.com
email: mma@xxxxxxxxxxxxx


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