I am having CentOS and Xen running on it this machine is able to do a ssh to other machines on the network but the client machines are not able to connect to it via ssh message comes is no route to host I have disabled firewalls and still to be sure enough I added following rule iptables -A INPUT -p TCP -m tcp --sport 22 -j ACCEPT following is the output of iptables -L [root@localhost ~]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere 192.168.122.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain OUTPUT (policy ACCEPT) target prot opt source destination But still the route to this machine does not exist this machine is able to ping other machine on my network but the other mchines can not ping if you see above rules then I have not disabled ICMP echo on Xen Machine can any one help. -- http://www.abhitech.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Dec 1, 2009 at 5:58 PM, Tapas Mishra <tapas@abhitech.com> wrote:> But still the route to this machine does not exist this machine is > able to ping other machine on my network but the other mchines can not > pingIs this "machine" the dom0, or domU? If it''s domU, what bridge do you put it on? is it virbr0? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, please change sport to dport iptables -A INPUT -p TCP -m tcp --sport 22 -j ACCEPT to iptables -A INPUT -p TCP -m tcp --dport 22 -j ACCEPT to make it work. please use iptables-save to list your settings Best regards, Udo Attila Fischer _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Well right now my problem for ssh is resolved the nameserver which it is showing me in /etc/resolv.conf is is not correct and inspite of setting it maually it is getting changed in both xen and normal kernel on the machine on which I am using Xen -- http://www.abhitech.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
It is very surprising that the same Xen machine about which I reported the problem internet etc had been working nicely and it was able to ping gateway and other machines on the network and after I did a simple reboot and neither it is able to ping it from the network internet was working very fine on the machine which I had reported right now nothing here are few outputs These questions answers might help:> - Is the client and this dom0 located on the same network?Yes the client machine is a Debian Laptop IP is 192.168.1.65/24 and the Xen machine is 192.168.1.85/24 both in same subnet 192.168.1.0> - does the problem happen when using normal kernel (i.e. not Xen)?Yes the problem is happening when using the normal kernel also I checked /etc/resolv.conf and the nameserver entry there is wrong it should be 4.2.2.6 but each time I manually edit it is still taking it from ADSL router.> - what is the value of /proc/sys/net/ipv4/icmp_echo_ignore_allit is 0> - what is the output of "netstat -nr"? Can dom0 ping the client?The output of netstat -nr is wrong it is not routing to the gateway as it should do> dom0 ping the gateway/router?No it is not doing previous email I was able to do from the machine I reported problem so I guess some thing else has gone wronge All the machines are in same subnet _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Yes the problem is happening when using the normal kernel also > I checked /etc/resolv.conf > and the nameserver entry there is wrong it should be 4.2.2.6 but each > time I manually edit it is still taking it from ADSL router.Do you have NetworkManager running? If so, stop it and disable it: If you are running CentOS you should be able to change the ifcfg-eth* scripts in /etc/sysconfig/network-scripts to not automatically set DNS according to the gateway. In the ifcfg-ethX (where X is the interface number that your server is connected to the network, eg eth0) file you can add PEERDNS=no to stop it from overwriting the DNS entries. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I did changed the PEERDNS entry and when I did a service network restart for some time the machine started giving reply of ping which I was able to see on the other machine but it is giving an error Bringing up interface eth0:RTNETLINK answers :File exists I do not wish to remove network manager gnome is it necessary I did chkconfig NetworkManager off and then restarted the network service machine started giving reply of ping for some time but then it stopped giving reply of ping.> > Do you have NetworkManager running? If so, stop it and disable it: > > If you are running CentOS you should be able to change the ifcfg-eth* > scripts in /etc/sysconfig/network-scripts to not automatically set DNS > according to the gateway. > > In the ifcfg-ethX (where X is the interface number that your server is > connected to the network, eg eth0) file you can add PEERDNS=no to stop > it from overwriting the DNS entries. >-- http://www.abhitech.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I have resolved this probblem here is what I did I added to /etc/sysconfig/network-scripts/ifcfg-eth0 PEERDNS=no DNS1=XXX.XXX.XXX.XXX (that is my gateway) But still I am wondering why did it happned ssh and everything else including internet is working fine on the Xen machine On Tue, Dec 1, 2009 at 7:00 AM, Tait Clarridge <tait@clarridge.ca> wrote:> >> Yes the problem is happening when using the normal kernel also >> I checked /etc/resolv.conf >> and the nameserver entry there is wrong it should be 4.2.2.6 but each >> time I manually edit it is still taking it from ADSL router. > > Do you have NetworkManager running? If so, stop it and disable it: > > If you are running CentOS you should be able to change the ifcfg-eth* > scripts in /etc/sysconfig/network-scripts to not automatically set DNS > according to the gateway. > > In the ifcfg-ethX (where X is the interface number that your server is > connected to the network, eg eth0) file you can add PEERDNS=no to stop > it from overwriting the DNS entries. >-- http://www.abhitech.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I am now back to the original problem where the Xen machine is able to
ping other machines on network
here is the output from of the Xen machine the issue started with ssh
[root@localhost ~]# netstat -tualp | grep 22
tcp 0 0 localhost.localdomain:2208 *:*
LISTEN 2594/hpiod
tcp 0 0 192.168.122.1:domain *:*
LISTEN 2829/dnsmasq
tcp 0 0 localhost.localdomain:2207 *:*
LISTEN 2599/python
tcp 0 0 192.168.1.84:58022
qw-in-f83.1e100.net:http ESTABLISHED 4056/firefox
udp 0 0 192.168.122.1:domain *:*
2829/dnsmasq
So it is clear that port 22 is not open here but I have not enabled
firewall and not disabled ICMP echo still it is not able reply back I
am able to have outgoing ssh/ping from Xen machine but any incoming
ssh/ping is notworking while if you read above replies in the thread I
was able to this Xen machine from my LAN but then it was not able to
access internet
Once again I am doing it from start here is what iptables on this machine say
[root@localhost ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT udp -- anywhere anywhere udp dpt:domain
ACCEPT tcp -- anywhere anywhere tcp dpt:domain
ACCEPT udp -- anywhere anywhere udp dpt:bootps
ACCEPT tcp -- anywhere anywhere tcp dpt:bootps
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere 192.168.122.0/24 state
RELATED,ESTABLISHED
ACCEPT all -- 192.168.122.0/24 anywhere
ACCEPT all -- anywhere anywhere
REJECT all -- anywhere anywhere
reject-with icmp-port-unreachable
REJECT all -- anywhere anywhere
reject-with icmp-port-unreachable
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
[root@localhost ~]#
Now what ?
On Tue, Dec 1, 2009 at 7:40 AM, Tapas Mishra <tapas@abhitech.com>
wrote:> I have resolved this probblem here is what I did
> I added to /etc/sysconfig/network-scripts/ifcfg-eth0
> PEERDNS=no
> DNS1=XXX.XXX.XXX.XXX (that is my gateway)
>
> But still I am wondering why did it happned
> ssh and everything else including internet is working fine on the Xen
machine
> On Tue, Dec 1, 2009 at 7:00 AM, Tait Clarridge <tait@clarridge.ca>
wrote:
>>
>>> Yes the problem is happening when using the normal kernel also
>>> I checked /etc/resolv.conf
>>> and the nameserver entry there is wrong it should be 4.2.2.6 but
each
>>> time I manually edit it is still taking it from ADSL router.
>>
>> Do you have NetworkManager running? If so, stop it and disable it:
>>
>> If you are running CentOS you should be able to change the ifcfg-eth*
>> scripts in /etc/sysconfig/network-scripts to not automatically set DNS
>> according to the gateway.
>>
>> In the ifcfg-ethX (where X is the interface number that your server is
>> connected to the network, eg eth0) file you can add PEERDNS=no to stop
>> it from overwriting the DNS entries.
>>
>
>
>
> --
>
> http://www.abhitech.com
>
--
http://www.abhitech.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I had a similar problem a couple days ago. I had this network layout: DHCP Server <-> Switch <-> Host Somehow, I could ssh from the DHCP server to a DomU at the host, but not on the other way around. A friend of mine suggested checking the routing table at the Host''s Dom0, and it was: root@aramis:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 10.0.0.1 0.0.0.0 UG 100 0 0 eth0 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 peth0 0.0.0.0 10.0.0.1 0.0.0.0 UG 100 0 0 peth0 Where 10.0.0.1 is the DHCP server''s IP address. eth0 is the host''s network interface that''s connected to the switch. It seemed strange, so I''ve started toying around and deleted the entries for the peth0: route del -net 0.0.0.0 dev peth0 route del -net 10.0.0.0 dev peth0 And lo and behold, now the DomU could access the Internet (ping google, etc). Thinking of it now, I didn''t remove/disable the network managers (I''m using Ubuntu), so that may be the source of the problem. I hope this helps, Paolo On Tue, Dec 1, 2009 at 1:55 PM, Tapas Mishra <tapas@abhitech.com> wrote:> > I am now back to the original problem where the Xen machine is able to > ping other machines on network > here is the output from of the Xen machine the issue started with ssh > [root@localhost ~]# netstat -tualp | grep 22 > tcp 0 0 localhost.localdomain:2208 *:* > LISTEN 2594/hpiod > tcp 0 0 192.168.122.1:domain *:* > LISTEN 2829/dnsmasq > tcp 0 0 localhost.localdomain:2207 *:* > LISTEN 2599/python > tcp 0 0 192.168.1.84:58022 > qw-in-f83.1e100.net:http ESTABLISHED 4056/firefox > udp 0 0 192.168.122.1:domain *:* > 2829/dnsmasq > > > So it is clear that port 22 is not open here but I have not enabled > firewall and not disabled ICMP echo still it is not able reply back I > am able to have outgoing ssh/ping from Xen machine but any incoming > ssh/ping is notworking while if you read above replies in the thread I > was able to this Xen machine from my LAN but then it was not able to > access internet > Once again I am doing it from start here is what iptables on this machine say > > [root@localhost ~]# iptables -L > Chain INPUT (policy ACCEPT) > target prot opt source destination > ACCEPT udp -- anywhere anywhere udp dpt:domain > ACCEPT tcp -- anywhere anywhere tcp dpt:domain > ACCEPT udp -- anywhere anywhere udp dpt:bootps > ACCEPT tcp -- anywhere anywhere tcp dpt:bootps > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > ACCEPT all -- anywhere 192.168.122.0/24 state > RELATED,ESTABLISHED > ACCEPT all -- 192.168.122.0/24 anywhere > ACCEPT all -- anywhere anywhere > REJECT all -- anywhere anywhere > reject-with icmp-port-unreachable > REJECT all -- anywhere anywhere > reject-with icmp-port-unreachable > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > [root@localhost ~]# > > Now what ? > On Tue, Dec 1, 2009 at 7:40 AM, Tapas Mishra <tapas@abhitech.com> wrote: > > I have resolved this probblem here is what I did > > I added to /etc/sysconfig/network-scripts/ifcfg-eth0 > > PEERDNS=no > > DNS1=XXX.XXX.XXX.XXX (that is my gateway) > > > > But still I am wondering why did it happned > > ssh and everything else including internet is working fine on the Xen machine > > On Tue, Dec 1, 2009 at 7:00 AM, Tait Clarridge <tait@clarridge.ca> wrote: > >> > >>> Yes the problem is happening when using the normal kernel also > >>> I checked /etc/resolv.conf > >>> and the nameserver entry there is wrong it should be 4.2.2.6 but each > >>> time I manually edit it is still taking it from ADSL router. > >> > >> Do you have NetworkManager running? If so, stop it and disable it: > >> > >> If you are running CentOS you should be able to change the ifcfg-eth* > >> scripts in /etc/sysconfig/network-scripts to not automatically set DNS > >> according to the gateway. > >> > >> In the ifcfg-ethX (where X is the interface number that your server is > >> connected to the network, eg eth0) file you can add PEERDNS=no to stop > >> it from overwriting the DNS entries. > >> > > > > > > > > -- > > > > http://www.abhitech.com > > > > > > -- > > http://www.abhitech.com > > _______________________________________________ > 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
Hmmm well what is happening here is that right now before you mailed I just rebooted the concerned machine and on the other machine when the target machine came up for some seconds I was able to see the reply of Xen machine and once the gnome display came everything is a mess as I report here in thread. On Tue, Dec 1, 2009 at 8:04 AM, Paolo <paolovictor@gmail.com> wrote:> I had a similar problem a couple days ago. I had this network layout: > > DHCP Server <-> Switch <-> Host > > Somehow, I could ssh from the DHCP server to a DomU at the host, but > not on the other way around. A friend of mine suggested checking the > routing table at the Host''s Dom0, and it was: > > root@aramis:~# route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 0.0.0.0 10.0.0.1 0.0.0.0 UG 100 0 0 eth0 > 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 peth0 > 0.0.0.0 10.0.0.1 0.0.0.0 UG 100 0 0 peth0 > > Where 10.0.0.1 is the DHCP server''s IP address. eth0 is the host''s > network interface that''s connected to the switch. > > It seemed strange, so I''ve started toying around and deleted the > entries for the peth0: > > route del -net 0.0.0.0 dev peth0 > route del -net 10.0.0.0 dev peth0 > > And lo and behold, now the DomU could access the Internet (ping > google, etc). Thinking of it now, I didn''t remove/disable the network > managers (I''m using Ubuntu), so that may be the source of the problem. > > I hope this helps, > Paolo > > On Tue, Dec 1, 2009 at 1:55 PM, Tapas Mishra <tapas@abhitech.com> wrote: >> >> I am now back to the original problem where the Xen machine is able to >> ping other machines on network >> here is the output from of the Xen machine the issue started with ssh >> [root@localhost ~]# netstat -tualp | grep 22 >> tcp 0 0 localhost.localdomain:2208 *:* >> LISTEN 2594/hpiod >> tcp 0 0 192.168.122.1:domain *:* >> LISTEN 2829/dnsmasq >> tcp 0 0 localhost.localdomain:2207 *:* >> LISTEN 2599/python >> tcp 0 0 192.168.1.84:58022 >> qw-in-f83.1e100.net:http ESTABLISHED 4056/firefox >> udp 0 0 192.168.122.1:domain *:* >> 2829/dnsmasq >> >> >> So it is clear that port 22 is not open here but I have not enabled >> firewall and not disabled ICMP echo still it is not able reply back I >> am able to have outgoing ssh/ping from Xen machine but any incoming >> ssh/ping is notworking while if you read above replies in the thread I >> was able to this Xen machine from my LAN but then it was not able to >> access internet >> Once again I am doing it from start here is what iptables on this machine say >> >> [root@localhost ~]# iptables -L >> Chain INPUT (policy ACCEPT) >> target prot opt source destination >> ACCEPT udp -- anywhere anywhere udp dpt:domain >> ACCEPT tcp -- anywhere anywhere tcp dpt:domain >> ACCEPT udp -- anywhere anywhere udp dpt:bootps >> ACCEPT tcp -- anywhere anywhere tcp dpt:bootps >> >> Chain FORWARD (policy ACCEPT) >> target prot opt source destination >> ACCEPT all -- anywhere 192.168.122.0/24 state >> RELATED,ESTABLISHED >> ACCEPT all -- 192.168.122.0/24 anywhere >> ACCEPT all -- anywhere anywhere >> REJECT all -- anywhere anywhere >> reject-with icmp-port-unreachable >> REJECT all -- anywhere anywhere >> reject-with icmp-port-unreachable >> >> Chain OUTPUT (policy ACCEPT) >> target prot opt source destination >> [root@localhost ~]# >> >> Now what ? >> On Tue, Dec 1, 2009 at 7:40 AM, Tapas Mishra <tapas@abhitech.com> wrote: >> > I have resolved this probblem here is what I did >> > I added to /etc/sysconfig/network-scripts/ifcfg-eth0 >> > PEERDNS=no >> > DNS1=XXX.XXX.XXX.XXX (that is my gateway) >> > >> > But still I am wondering why did it happned >> > ssh and everything else including internet is working fine on the Xen machine >> > On Tue, Dec 1, 2009 at 7:00 AM, Tait Clarridge <tait@clarridge.ca> wrote: >> >> >> >>> Yes the problem is happening when using the normal kernel also >> >>> I checked /etc/resolv.conf >> >>> and the nameserver entry there is wrong it should be 4.2.2.6 but each >> >>> time I manually edit it is still taking it from ADSL router. >> >> >> >> Do you have NetworkManager running? If so, stop it and disable it: >> >> >> >> If you are running CentOS you should be able to change the ifcfg-eth* >> >> scripts in /etc/sysconfig/network-scripts to not automatically set DNS >> >> according to the gateway. >> >> >> >> In the ifcfg-ethX (where X is the interface number that your server is >> >> connected to the network, eg eth0) file you can add PEERDNS=no to stop >> >> it from overwriting the DNS entries. >> >> >> > >> > >> > >> > -- >> > >> > http://www.abhitech.com >> > >> >> >> >> -- >> >> http://www.abhitech.com >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >-- http://www.abhitech.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I think the problem has something to do with NetworkManager since I noticed rebooting the machine many times that after bringing eth0 and eth1 up when NetworkManager daemon starts the machine is not able to reply to ICMP Echo while the machine brings eth0 up it starts replying till the time NetworkManager is not on but to my surprise I have disabled the Network Manager just see the output here [root@localhost ~]# chkconfig NetworkManager --list NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off On Tue, Dec 1, 2009 at 9:38 PM, Tapas Mishra <tapas@abhitech.com> wrote:> Hmmm well what is happening here is that right now before you mailed I > just rebooted the concerned machine and on the other machine when the > target machine came up for some seconds I was able to see the reply of > Xen machine and once the gnome display came everything is a mess as I > report here in thread. > > On Tue, Dec 1, 2009 at 8:04 AM, Paolo <paolovictor@gmail.com> wrote: >> I had a similar problem a couple days ago. I had this network layout: >> >> DHCP Server <-> Switch <-> Host >> >> Somehow, I could ssh from the DHCP server to a DomU at the host, but >> not on the other way around. A friend of mine suggested checking the >> routing table at the Host''s Dom0, and it was: >> >> root@aramis:~# route -n >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric Ref Use Iface >> 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 >> 0.0.0.0 10.0.0.1 0.0.0.0 UG 100 0 0 eth0 >> 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 peth0 >> 0.0.0.0 10.0.0.1 0.0.0.0 UG 100 0 0 peth0 >> >> Where 10.0.0.1 is the DHCP server''s IP address. eth0 is the host''s >> network interface that''s connected to the switch. >> >> It seemed strange, so I''ve started toying around and deleted the >> entries for the peth0: >> >> route del -net 0.0.0.0 dev peth0 >> route del -net 10.0.0.0 dev peth0 >> >> And lo and behold, now the DomU could access the Internet (ping >> google, etc). Thinking of it now, I didn''t remove/disable the network >> managers (I''m using Ubuntu), so that may be the source of the problem. >> >> I hope this helps, >> Paolo >> >> On Tue, Dec 1, 2009 at 1:55 PM, Tapas Mishra <tapas@abhitech.com> wrote: >>> >>> I am now back to the original problem where the Xen machine is able to >>> ping other machines on network >>> here is the output from of the Xen machine the issue started with ssh >>> [root@localhost ~]# netstat -tualp | grep 22 >>> tcp 0 0 localhost.localdomain:2208 *:* >>> LISTEN 2594/hpiod >>> tcp 0 0 192.168.122.1:domain *:* >>> LISTEN 2829/dnsmasq >>> tcp 0 0 localhost.localdomain:2207 *:* >>> LISTEN 2599/python >>> tcp 0 0 192.168.1.84:58022 >>> qw-in-f83.1e100.net:http ESTABLISHED 4056/firefox >>> udp 0 0 192.168.122.1:domain *:* >>> 2829/dnsmasq >>> >>> >>> So it is clear that port 22 is not open here but I have not enabled >>> firewall and not disabled ICMP echo still it is not able reply back I >>> am able to have outgoing ssh/ping from Xen machine but any incoming >>> ssh/ping is notworking while if you read above replies in the thread I >>> was able to this Xen machine from my LAN but then it was not able to >>> access internet >>> Once again I am doing it from start here is what iptables on this machine say >>> >>> [root@localhost ~]# iptables -L >>> Chain INPUT (policy ACCEPT) >>> target prot opt source destination >>> ACCEPT udp -- anywhere anywhere udp dpt:domain >>> ACCEPT tcp -- anywhere anywhere tcp dpt:domain >>> ACCEPT udp -- anywhere anywhere udp dpt:bootps >>> ACCEPT tcp -- anywhere anywhere tcp dpt:bootps >>> >>> Chain FORWARD (policy ACCEPT) >>> target prot opt source destination >>> ACCEPT all -- anywhere 192.168.122.0/24 state >>> RELATED,ESTABLISHED >>> ACCEPT all -- 192.168.122.0/24 anywhere >>> ACCEPT all -- anywhere anywhere >>> REJECT all -- anywhere anywhere >>> reject-with icmp-port-unreachable >>> REJECT all -- anywhere anywhere >>> reject-with icmp-port-unreachable >>> >>> Chain OUTPUT (policy ACCEPT) >>> target prot opt source destination >>> [root@localhost ~]# >>> >>> Now what ? >>> On Tue, Dec 1, 2009 at 7:40 AM, Tapas Mishra <tapas@abhitech.com> wrote: >>> > I have resolved this probblem here is what I did >>> > I added to /etc/sysconfig/network-scripts/ifcfg-eth0 >>> > PEERDNS=no >>> > DNS1=XXX.XXX.XXX.XXX (that is my gateway) >>> > >>> > But still I am wondering why did it happned >>> > ssh and everything else including internet is working fine on the Xen machine >>> > On Tue, Dec 1, 2009 at 7:00 AM, Tait Clarridge <tait@clarridge.ca> wrote: >>> >> >>> >>> Yes the problem is happening when using the normal kernel also >>> >>> I checked /etc/resolv.conf >>> >>> and the nameserver entry there is wrong it should be 4.2.2.6 but each >>> >>> time I manually edit it is still taking it from ADSL router. >>> >> >>> >> Do you have NetworkManager running? If so, stop it and disable it: >>> >> >>> >> If you are running CentOS you should be able to change the ifcfg-eth* >>> >> scripts in /etc/sysconfig/network-scripts to not automatically set DNS >>> >> according to the gateway. >>> >> >>> >> In the ifcfg-ethX (where X is the interface number that your server is >>> >> connected to the network, eg eth0) file you can add PEERDNS=no to stop >>> >> it from overwriting the DNS entries. >>> >> >>> > >>> > >>> > >>> > -- >>> > >>> > http://www.abhitech.com >>> > >>> >>> >>> >>> -- >>> >>> http://www.abhitech.com >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >> > > > > -- > > http://www.abhitech.com >-- http://www.abhitech.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Do you have NetworkManager running? If so, stop it and disable it:I disabled Network Manager the machine is giving response to other machine on LAN in same subnet but not able to connect to internet while it was doing so before uninstalling Network Manager.> If you are running CentOS you should be able to change the ifcfg-eth* > scripts in /etc/sysconfig/network-scripts to not automatically set DNS > according to the gateway.I have set in the file as following which are the entries I am using static IP only DEVICE=eth0 BOOTPROTO=none BROADCAST=192.168.1.255 HWADDR=00:24:01:15:06:DD IPADDR=192.168.1.84 NETMASK=255.255.255.0 NETWORK=192.168.1.0 ONBOOT=yes GATEWAY=192.168.1.250 TYPE=Ethernet USERCTL=no IPV6INIT=no PEERDNS=no DNS1=4.2.2.6> In the ifcfg-ethX (where X is the interface number that your server is > connected to the network, eg eth0) file you can add PEERDNS=no to stop > it from overwriting the DNS entries. >I have done it as per your suggestion now the machine under question is not able to communicate on Internet. -- http://www.abhitech.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I have done it as per your suggestion now the machine under question > is not able to communicate on Internet.I forgot to say mention that ssh and ping from within the network are working and before removing Network Manager it was able to access internet but not LAN now LAN is able to access this Xen machine but internet not working. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users