Hi,
I don't understand why you're still 213.137.187.32, you should be able to forget about this IP and just use your new 16 IP address range.
Your ISP should have given you a default gateway for your new IP range.
This should simplify your setup and hopefully make it more stable.
We run a very similar setup, and only ever have to reboot our machines when we patch them.
Hope this helps,
Paul ----- Original Message ----- From: "Razvan Cristian Oprea"
To: Sent: Saturday, April 13, 2002 2:19 PM Subject: [SLE] SuSE as router problem - help needed Hello everyone,
I started using SuSE Linux for a while now as a workstation OS and I was pleased with the experience provided. However, I insisted in replacing the Win2000 router at work with SuSE and I encountered some problems I hope you can give me some advice for.
We have one static IP address: 213.137.187.32 , netmask 255.255.255.0 with the default gateway 213.137.187.1. We requested another 16 IP addresses from our ISP and they allocated the subnet: 62.234.73.48/28. I understand this means 16 useable addresses, from x.x.x.49 to x.x.x.64, with the network mask 255.255.255.240. We have to route all the addresses in the subnet through the old P address of 213.137.187.32.
This is what I did: I have first put one network card, set the eth0 to 213.137.187.32, then eth0:0 to 62.234.73.49, enabled IP forwarding, set
Paul,
Thank you so much for your response and interest in my problem. However I'm
glad if you have found my configuration flawless, but yet I'm sad that such
a small problem as is routing a subnet through another IP address apart from
that subnet, can render a Linux router instable.
In any case, if you can think of a solution concerning things or
configuration issues that I might have done better, olease let me know.
Many thanks,
Razvan
----- Original Message -----
From: "Paul Miles"
default gateway to 213.137.187.1, put the nameservers' IP addresses (all in Yast2), and then I added the following lines to /etc/init.d/boot.local:
/sbin/ifconfig eth0 213.137.187.32 netmask 255.255.255.0 broadcast 213.137.187.255 /sbin/ifconfig eth0:0 62.234.73.49 netmask 255.255.255.240 broadcast 62.234.73.65 /sbin/route add -host 213.137.187.32 dev eth0 /sbin/route add -host 62.234.73.49 dev eth0:0 /sbin/route add default gw 213.137.187.1
For all the computers in the network, running Win98, I have put the default gateway 62.234.73.49 and the correct nameservers.
Everything worked perfectly, but, from time to time, randomly, the router ceased to function and the only solution to put the network up on its feet was to reboot the machine, or, as I learned later, to issue: /etc/init.d/network start. In that second, the network was up again.
I thought that perhaps if I put two network cards inside the router the situation will change, but no way (this time having eth0 and eth1). The router stops to function at times (once a day let's say) and I have to issue the above-mentioned command. I assume I'm doing something wrong, since the Win2000 machine did not have all this problems, and I would feel sorry to have the Windoze in control again. The network card was initially a Realtek 8139 and with the 2 network cards version, a Realtek 8139 and an onboard SiS 730. I have replaced the 8-ports Genius hub with a 3Com switch. I have also aquired 3 brand name network cards (Intel, 3Com and SMC EtherPowerII (which costed roughly about $48 a piece), but I'm not so sure changing the network cards will really make a difference in terms of stability.
All and any advices and/or opinions would be highly appreciated... after all, it's all about proving the advantage of a Linux solution vs. standard Windows one...
Thank you, Razvan Oprea
Note: The IP addresses mentioned were slightly modified vs the real ones, so that the net mask, broadcast and everything remain the same - for instance, it's not 62, it could be 63 - hope no one will feel offended by this.