:strip_icc():strip_exif()/u/12103/7146c68c308d55b9beaa86943249d9e69e2727c7_full.jpg?f=community)
sorrie voor het engels
subject: Replacing Netware 3.12 TCP/IP (RIP) router with Linux 2.2
Recently I've become involved with a project where the goal is to
replace the current old, dusty Novell Netware server which has
routing as a job on the side with a new and shiny Linux router.
I didn't setup the network neither did I ever had anything to do
with the Netware router. I checked out the config of the Netware
box and it was the following:
eth0: ip 10.10.32.11 netmask 255.255.0.0 FORWARD=YES RIP=YES
eth1: ip 10.1.32.11 netmask 255.255.0.0 FORWARD=YES RIP=YES
At first I didn't even think about the RIP part, i thought heck
that's just some old routing protocol that Netware uses, I don't
need that on my Linux 2.2 system.
The local segment on the location of the Netware router is 10.10.0.0
and it's connected to the 10.1.0.0 network which other routers connect
to in their turn, having segments like 10.128.0.0 and 10.4.0.0, etc.
All of them are class B networks. There is also a gateway to the
internet, which IP is 10.1.1.1.
Now when i first swapped the Netware box with my Linux box, just using
route add default gw 10.1.1.1
and ip-forwarding turned on with
echo 1 > /proc/sys/net/ipv4/ip_forward
The linux box was the only one able to reach the internet. So I think
hey what is going on here ? After some thoughts i realized that the
other routers on the LAN (10.0.0.0) all used RIP so they didnt have the
route to my segment (10.10.0.0) in their route table since my Linux box
doesn't use RIP.
After doing some research i found out about routed, a RIP deamon for
Linux. So i cleared all my static routes out of my route table and
ran the deamon. In a few seconds my route table was full of routes,
so all just seemed fine. I did a few traceroutes on the Linux box to
other segments which worked just fine.
Now I tryed out some workstations on my segment but I cannot
seem to reach anything beyond my Linux router. I know there is no
problem with my Kernel, IP Forwarding also works just fine when
done with ipchains. It just seems not to be forwarding the routes
it got trough routed ? Can somebody help me out on this please ?
Could it have something to do with the /etc/gateways file where I
Have no clue on what to do with it.
subject: Replacing Netware 3.12 TCP/IP (RIP) router with Linux 2.2
Recently I've become involved with a project where the goal is to
replace the current old, dusty Novell Netware server which has
routing as a job on the side with a new and shiny Linux router.
I didn't setup the network neither did I ever had anything to do
with the Netware router. I checked out the config of the Netware
box and it was the following:
eth0: ip 10.10.32.11 netmask 255.255.0.0 FORWARD=YES RIP=YES
eth1: ip 10.1.32.11 netmask 255.255.0.0 FORWARD=YES RIP=YES
At first I didn't even think about the RIP part, i thought heck
that's just some old routing protocol that Netware uses, I don't
need that on my Linux 2.2 system.
The local segment on the location of the Netware router is 10.10.0.0
and it's connected to the 10.1.0.0 network which other routers connect
to in their turn, having segments like 10.128.0.0 and 10.4.0.0, etc.
All of them are class B networks. There is also a gateway to the
internet, which IP is 10.1.1.1.
Now when i first swapped the Netware box with my Linux box, just using
route add default gw 10.1.1.1
and ip-forwarding turned on with
echo 1 > /proc/sys/net/ipv4/ip_forward
The linux box was the only one able to reach the internet. So I think
hey what is going on here ? After some thoughts i realized that the
other routers on the LAN (10.0.0.0) all used RIP so they didnt have the
route to my segment (10.10.0.0) in their route table since my Linux box
doesn't use RIP.
After doing some research i found out about routed, a RIP deamon for
Linux. So i cleared all my static routes out of my route table and
ran the deamon. In a few seconds my route table was full of routes,
so all just seemed fine. I did a few traceroutes on the Linux box to
other segments which worked just fine.
Now I tryed out some workstations on my segment but I cannot
seem to reach anything beyond my Linux router. I know there is no
problem with my Kernel, IP Forwarding also works just fine when
done with ipchains. It just seems not to be forwarding the routes
it got trough routed ? Can somebody help me out on this please ?
Could it have something to do with the /etc/gateways file where I
Have no clue on what to do with it.
Steam Profile I5 14600K / 64 GB DDR5 / RTX 4090 / Rift S / HP Omen / Odyssey Neo G9 / Steam Deck OLED / Switch