Damn, How did I miss that?
it appeared that VMWare's network template script sucks, it did put some
numbers in the route-eth0 file. I emptied the file and now it works :)
Thanks a lot :)
Hetz
On Mon, Feb 14, 2011 at 1:10 PM, Baruch Shpirer <bar...@shpirer.com> wrote:
>
>
> You sure you don’t have some static routing cmds some where?
>
> Changed subnets and forgot to remove them completely?
>
>
>
> Red Hat/Fedora: inside /etc/sysconfig/network-scripts/route-eth0 file
>
> Debian Linux: inside /etc/network/interface file
>
>
>
> Using ip forwarding?
>
>
>
> Baruch
>
>
>
> *From:* linux-il-boun...@cs.huji.ac.il [mailto:
> linux-il-boun...@cs.huji.ac.il] *On Behalf Of *Hetz Ben Hamo
> *Sent:* Monday, February 14, 2011 12:33
> *To:* linux-il
> *Subject:* weird network issue
>
>
>
> Hi,
>
>
>
> I'm getting some really weird error, even though the network on the machine
> works well.
>
> When I'm doing: "service network restart" or "ifup eth0", I'm getting a
> message: RTNETLINK answers: Network is unreachable.
>
>
>
> It is reachable. route's output is perfectly ok, the machine can access the
> net and I can access it from outside. DNS works, ping works etc..
>
>
>
> Looking at /var/log/messages, all I see is:
>
>
>
> Feb 14 13:23:00 testing23 kernel: eth0: intr type 2, mode 0, 1 vectors
> allocated
>
> Feb 14 13:23:00 testing23 kernel: eth0: NIC Link is Up 10000 Mbps
>
>
>
> Here is my ifcfg-eth0 (it's a virtual machine, so the check_link stuff is
> what vmware added)
>
>
>
> DEVICE=eth0
>
> ONBOOT=yes
>
> USERCTL=no
>
> BOOTPROTO=none
>
> NETMASK=255.255.255.224
>
> IPADDR=82.XXX.XXX.203
>
> PEERDNS=no
>
>
>
> check_link_down() {
>
> return 1;
>
> }
>
> HWADDR=00:50:56:a3:00:18
>
> GATEWAY=82.XXX.XXX.193
>
> TYPE=Ethernet
>
>
>
> Any suggestions?
>
>
>
> Thanks,
>
> Hetz
>
>
>
> !DSPAM:4d59062714471211119814!
>
_______________________________________________
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
