Re: [expert] how to set routing at boot? [SOLVED]

2003-07-01 Thread SainTiss
Problem was that the FORWARD_IPV4 variable, which used to be set in the
/etc/sysconfig/network script, got unset somehow...

Everything is fine now

Hans

On Sun, 2003-06-29 at 00:29, SainTiss wrote:
 Ok, anyway, I've tried to change the IP addresses now so that they are
 in different subnets, but that doesn't really seem to help... pinging
 between the 2 client pc's doesn't even work anymore now...
 
 This is the config:
 
 gateway (192.168.0.1 and 192.168.1.1):
 
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse
 Iface
 192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
 eth2
 192.168.0.0 0.0.0.0 255.255.255.0   U 0  00
 eth1
 213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
 eth0
 127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
 lo
 0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
 eth0
 
 client 192.168.0.2:
 
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse
 Iface
 192.168.0.0 0.0.0.0 255.255.255.0   U 0  00
 eth0
 127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
 lo
 0.0.0.0 192.168.0.1 0.0.0.0 UG0  00
 eth0
 
 client 192.168.1.2:
 
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse
 Iface
 192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
 eth0
 127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
 lo
 0.0.0.0 192.168.1.1 0.0.0.0 UG0  00
 eth0
 
 I'd think this is supposed to work, no?
 
 Any ideas as to what is wrong with this setup?
 
 Thanks,
 
 Hans
 
 
 On Sat, 2003-06-28 at 21:59, Steven Broos wrote:
  Quick lesson in subnetworking, because I think the problem isn't your
  IPtables-settings but your network layout.
  
  192.168.0.x is a class C network address. 192.168.0 is the network
  address, and the last number is the host-portion of the address.
  If all PCs have an address beginning with 192.168.0 and a netmask of
  255.255.255.0 they are on the same subnet, and don't need routing.
  If you need to separate your LAN into difefrent subnets, use 192.168.0.x
  and 192.168.1.x etc...
  
  Creating a subnet with mask 255.255.255.255 isn't possible, because that
  way you don't have any broadcast/network-addresses.
  
  If you think this goes into the right direction, please give more
  details about your LAN and ask for more information :-)
  
  regards,
  Steven
  (CCNA)
  
  
  
  
  On Sat, 2003-06-28 at 20:47, SainTiss wrote:
   Well, what I *need* e.g. on the gateway is something like this:
   
   Kernel IP routing table
   Destination Gateway Genmask Flags Metric RefUse
   Iface
   192.168.0.3 0.0.0.0 255.255.255.255 UH0  00
   eth2
   192.168.0.2 0.0.0.0 255.255.255.255 UH0  00
   eth1
   213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
   eth0
   127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
   lo
   0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
   eth0
   
   However, by default those upper 2 rules aren't there, and instead
   there's a rule like this:
   
   192.168.0.0 0.0.0.0 255.255.255.0 U0  0   
   0 eth2
   
   So in other words, by default ALL LAN traffic is routed through eth2,
   while obviously traffic with 192.168.0.2 should be routed via eth1.
   
   Did that make it any clearer?
   
   Thanks,
   
   Hans
   
   On Sat, 2003-06-28 at 20:18, Bill Mullen wrote:
On Sat, 28 Jun 2003, SainTiss wrote:

 I just changed my network configs here, and it seems the routing table
 got messed up...
 
 I know the solution (ie adding some rules and deleting some), but I was
 wondering if there was some file or something where I could specify the
 right rules, so that the table is setup correctly at boot?
 
 what's the default way to do this? I'm guessing some file which is then
 processed by ifup or something, but I'm not sure...

Depends on what's messed up. :)

Most settings draw on the information in the /etc/sysconfig directory, 
specifically the network file and the various ifcfg-interface ones 
in the network-scripts subdirectory. For simpler setups, these are all 
you'll need to adjust, but we have no idea how complicated your normal 
routing table actually is ... care to offer a hint? ;)
  
  
  
  __
  
  Want to buy your Pack or Services from MandrakeSoft? 
  Go to http://www.mandrakestore.com
-- 
In a world without walls and fences, who needs windows and gates?

Is the essence that the light pulse lives longer?

Hans Schippers
1LIC INF

Re: [expert] how to set routing at boot?

2003-06-30 Thread Mark
Hi SainTiss,

I am trying to work out what you are trying to do..

Sounds like your trying to route a live range through a private IP
address range.


 213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
 eth0

Do you really have a live Subneted B-class or 8 C-classes, I suspect
that your ISP would have only given you a 213.118.248.0/29  or
213.118.248.0/255.255.255.248 or a range of .1-.6 leaving the .0 for
Network address and .7 for Broadcast.

O.K. where one can configure the extra needed static routes is via the 
 /etc/sysconfig/networking/devices/eth0.route  or the eth1.route etc..
depending which interface you are binding your routes to.

Have a look at the script /etc/sysconfig/network-scripts/ifup-routes
that may give you a hint what's going on.

Cheers
Mark




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [expert] how to set routing at boot?

2003-06-30 Thread richard bown
On Sat, 2003-06-28 at 23:29, SainTiss wrote:
 Ok, anyway, I've tried to change the IP addresses now so that they are
 in different subnets, but that doesn't really seem to help... pinging
 between the 2 client pc's doesn't even work anymore now...
 
 This is the config:
 
 gateway (192.168.0.1 and 192.168.1.1):
 
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse
 Iface
 192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
 eth2
 192.168.0.0 0.0.0.0 255.255.255.0   U 0  00
 eth1
 213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
 eth0
 127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
 lo
 0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
 eth0
 
 client 192.168.0.2:
 
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse
 Iface
 192.168.0.0 0.0.0.0 255.255.255.0   U 0  00
 eth0
 127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
 lo
 0.0.0.0 192.168.0.1 0.0.0.0 UG0  00
 eth0
 
the gateway address should be the address of the router on both machines
 client 192.168.1.2:
 
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse
 Iface
 192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
 eth0
 127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
 lo
 0.0.0.0 192.168.1.1 0.0.0.0 UG0  00
 eth0
   192.168.0.1
   
 I'd think this is supposed to work, no?
 
 Any ideas as to what is wrong with this setup?
 
 Thanks,
 
 Hans
 
 
 On Sat, 2003-06-28 at 21:59, Steven Broos wrote:
  Quick lesson in subnetworking, because I think the problem isn't your
  IPtables-settings but your network layout.
  
  192.168.0.x is a class C network address. 192.168.0 is the network
  address, and the last number is the host-portion of the address.
  If all PCs have an address beginning with 192.168.0 and a netmask of
  255.255.255.0 they are on the same subnet, and don't need routing.
  If you need to separate your LAN into difefrent subnets, use 192.168.0.x
  and 192.168.1.x etc...
  
  Creating a subnet with mask 255.255.255.255 isn't possible, because that
  way you don't have any broadcast/network-addresses.
  
  If you think this goes into the right direction, please give more
  details about your LAN and ask for more information :-)
  
  regards,
  Steven
  (CCNA)
  
  
  
  
  On Sat, 2003-06-28 at 20:47, SainTiss wrote:
   Well, what I *need* e.g. on the gateway is something like this:
   
   Kernel IP routing table
   Destination Gateway Genmask Flags Metric RefUse
   Iface
   192.168.0.3 0.0.0.0 255.255.255.255 UH0  00
   eth2
   192.168.0.2 0.0.0.0 255.255.255.255 UH0  00
   eth1
   213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
   eth0
   127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
   lo
   0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
   eth0
   
   However, by default those upper 2 rules aren't there, and instead
   there's a rule like this:
   
   192.168.0.0 0.0.0.0 255.255.255.0 U0  0   
   0 eth2
   
   So in other words, by default ALL LAN traffic is routed through eth2,
   while obviously traffic with 192.168.0.2 should be routed via eth1.
   
   Did that make it any clearer?
   
   Thanks,
   
   Hans
   
   On Sat, 2003-06-28 at 20:18, Bill Mullen wrote:
On Sat, 28 Jun 2003, SainTiss wrote:

 I just changed my network configs here, and it seems the routing table
 got messed up...
 
 I know the solution (ie adding some rules and deleting some), but I was
 wondering if there was some file or something where I could specify the
 right rules, so that the table is setup correctly at boot?
 
 what's the default way to do this? I'm guessing some file which is then
 processed by ifup or something, but I'm not sure...

Depends on what's messed up. :)

Most settings draw on the information in the /etc/sysconfig directory, 
specifically the network file and the various ifcfg-interface ones 
in the network-scripts subdirectory. For simpler setups, these are all 
you'll need to adjust, but we have no idea how complicated your normal 
routing table actually is ... care to offer a hint? ;)
  
  
  
  __
  
  Want to buy your Pack or Services from MandrakeSoft? 
  Go to http://www.mandrakestore.com
-- 
richard bown [EMAIL PROTECTED]


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [expert] how to set routing at boot?

2003-06-30 Thread Bill Mullen
On Sat, 29 Jun 2003, SainTiss wrote:

 Ok, anyway, I've tried to change the IP addresses now so that they are
 in different subnets, but that doesn't really seem to help... pinging
 between the 2 client pc's doesn't even work anymore now...
 
 This is the config:
 
 gateway (192.168.0.1 and 192.168.1.1):
 
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse
 Iface
 192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
 eth2
 192.168.0.0 0.0.0.0 255.255.255.0   U 0  00
 eth1
 213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
 eth0
 127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
 lo
 0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
 eth0
 
 client 192.168.0.2:
 
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse
 Iface
 192.168.0.0 0.0.0.0 255.255.255.0   U 0  00
 eth0
 127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
 lo
 0.0.0.0 192.168.0.1 0.0.0.0 UG0  00
 eth0
 
 client 192.168.1.2:
 
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse
 Iface
 192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
 eth0
 127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
 lo
 0.0.0.0 192.168.1.1 0.0.0.0 UG0  00
 eth0
 
 I'd think this is supposed to work, no?
 
 Any ideas as to what is wrong with this setup?

Well, as for the pinging problem, do you have IP forwarding turned on?

In the /etc/sysconfig/network file:

FORWARD_IPV4=true

Once the network service is restarted, they should see each other again.

If you expect these other systems to have access to the WAN by way of this
machine, however, you'll need to set up NAT, which is done using iptables 
(usually, by way of an iptables configuration front-end such as guarddog, 
firestarter, Bastille, or the Mandrake Control Center's applet, which uses 
the shorewall system). You can also set up your iptables rules manually, 
if you're so inclined, and use the iptables app itself to save them and 
to load them. Check the iptables man page, and such 'net resources as the 
Linux Documentation Project's HOWTOs and the home pages for the netfilter 
project (which includes iptables) and for shorewall.

http://www.tldp.org/HOWTO/HOWTO-INDEX/networking.html
http://www.netfilter.org
http://www.shorewall.net

-- 
Bill Mullen   [EMAIL PROTECTED]   MA, USA   RLU #270075   MDK 8.1  9.0
The engineer is neither optimist nor pessimist. He sees the proverbial
half-full/empty glass and says, The glass is twice as big as there is
any need for it to be.

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


[expert] how to set routing at boot?

2003-06-28 Thread SainTiss
Hi,

I just changed my network configs here, and it seems the routing table
got messed up...

I know the solution (ie adding some rules and deleting some), but I was
wondering if there was some file or something where I could specify the
right rules, so that the table is setup correctly at boot?

what's the default way to do this? I'm guessing some file which is then
processed by ifup or something, but I'm not sure...

Thanks,

Hans

-- 
In a world without walls and fences, who needs windows and gates?

Is the essence that the light pulse lives longer?

Hans Schippers
1LIC INF
UIA 2002-2003


signature.asc
Description: This is a digitally signed message part


Re: [expert] how to set routing at boot?

2003-06-28 Thread Bill Mullen
On Sat, 28 Jun 2003, SainTiss wrote:

 I just changed my network configs here, and it seems the routing table
 got messed up...
 
 I know the solution (ie adding some rules and deleting some), but I was
 wondering if there was some file or something where I could specify the
 right rules, so that the table is setup correctly at boot?
 
 what's the default way to do this? I'm guessing some file which is then
 processed by ifup or something, but I'm not sure...

Depends on what's messed up. :)

Most settings draw on the information in the /etc/sysconfig directory, 
specifically the network file and the various ifcfg-interface ones 
in the network-scripts subdirectory. For simpler setups, these are all 
you'll need to adjust, but we have no idea how complicated your normal 
routing table actually is ... care to offer a hint? ;)

-- 
Bill Mullen   [EMAIL PROTECTED]   MA, USA   RLU #270075   MDK 8.1  9.0
The engineer is neither optimist nor pessimist. He sees the proverbial
half-full/empty glass and says, The glass is twice as big as there is
any need for it to be.

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [expert] how to set routing at boot?

2003-06-28 Thread SainTiss
Well, what I *need* e.g. on the gateway is something like this:

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
192.168.0.3 0.0.0.0 255.255.255.255 UH0  00
eth2
192.168.0.2 0.0.0.0 255.255.255.255 UH0  00
eth1
213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
eth0
127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
lo
0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
eth0

However, by default those upper 2 rules aren't there, and instead
there's a rule like this:

192.168.0.0 0.0.0.0 255.255.255.0 U0  0   
0   eth2

So in other words, by default ALL LAN traffic is routed through eth2,
while obviously traffic with 192.168.0.2 should be routed via eth1.

Did that make it any clearer?

Thanks,

Hans

On Sat, 2003-06-28 at 20:18, Bill Mullen wrote:
 On Sat, 28 Jun 2003, SainTiss wrote:
 
  I just changed my network configs here, and it seems the routing table
  got messed up...
  
  I know the solution (ie adding some rules and deleting some), but I was
  wondering if there was some file or something where I could specify the
  right rules, so that the table is setup correctly at boot?
  
  what's the default way to do this? I'm guessing some file which is then
  processed by ifup or something, but I'm not sure...
 
 Depends on what's messed up. :)
 
 Most settings draw on the information in the /etc/sysconfig directory, 
 specifically the network file and the various ifcfg-interface ones 
 in the network-scripts subdirectory. For simpler setups, these are all 
 you'll need to adjust, but we have no idea how complicated your normal 
 routing table actually is ... care to offer a hint? ;)
-- 
In a world without walls and fences, who needs windows and gates?

Is the essence that the light pulse lives longer?

Hans Schippers
1LIC INF
UIA 2002-2003


signature.asc
Description: This is a digitally signed message part


Re: [expert] how to set routing at boot?

2003-06-28 Thread Steven Broos
Quick lesson in subnetworking, because I think the problem isn't your
IPtables-settings but your network layout.

192.168.0.x is a class C network address. 192.168.0 is the network
address, and the last number is the host-portion of the address.
If all PCs have an address beginning with 192.168.0 and a netmask of
255.255.255.0 they are on the same subnet, and don't need routing.
If you need to separate your LAN into difefrent subnets, use 192.168.0.x
and 192.168.1.x etc...

Creating a subnet with mask 255.255.255.255 isn't possible, because that
way you don't have any broadcast/network-addresses.

If you think this goes into the right direction, please give more
details about your LAN and ask for more information :-)

regards,
Steven
(CCNA)




On Sat, 2003-06-28 at 20:47, SainTiss wrote:
 Well, what I *need* e.g. on the gateway is something like this:
 
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse
 Iface
 192.168.0.3 0.0.0.0 255.255.255.255 UH0  00
 eth2
 192.168.0.2 0.0.0.0 255.255.255.255 UH0  00
 eth1
 213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
 eth0
 127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
 lo
 0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
 eth0
 
 However, by default those upper 2 rules aren't there, and instead
 there's a rule like this:
 
 192.168.0.0 0.0.0.0 255.255.255.0 U0  0   
 0 eth2
 
 So in other words, by default ALL LAN traffic is routed through eth2,
 while obviously traffic with 192.168.0.2 should be routed via eth1.
 
 Did that make it any clearer?
 
 Thanks,
 
 Hans
 
 On Sat, 2003-06-28 at 20:18, Bill Mullen wrote:
  On Sat, 28 Jun 2003, SainTiss wrote:
  
   I just changed my network configs here, and it seems the routing table
   got messed up...
   
   I know the solution (ie adding some rules and deleting some), but I was
   wondering if there was some file or something where I could specify the
   right rules, so that the table is setup correctly at boot?
   
   what's the default way to do this? I'm guessing some file which is then
   processed by ifup or something, but I'm not sure...
  
  Depends on what's messed up. :)
  
  Most settings draw on the information in the /etc/sysconfig directory, 
  specifically the network file and the various ifcfg-interface ones 
  in the network-scripts subdirectory. For simpler setups, these are all 
  you'll need to adjust, but we have no idea how complicated your normal 
  routing table actually is ... care to offer a hint? ;)


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [expert] how to set routing at boot?

2003-06-28 Thread richard bown
HI
try adding to rc.local at the end of the file
/sbin/route add -host 192.168.0.2 eth1
/sbin/route add -host 192.168.0.3 eth2
HTH 
Richard

On Sat, 2003-06-28 at 20:59, Steven Broos wrote:
 Quick lesson in subnetworking, because I think the problem isn't your
 IPtables-settings but your network layout.
 
 192.168.0.x is a class C network address. 192.168.0 is the network
 address, and the last number is the host-portion of the address.
 If all PCs have an address beginning with 192.168.0 and a netmask of
 255.255.255.0 they are on the same subnet, and don't need routing.
 If you need to separate your LAN into difefrent subnets, use 192.168.0.x
 and 192.168.1.x etc...
 
 Creating a subnet with mask 255.255.255.255 isn't possible, because that
 way you don't have any broadcast/network-addresses.
 
 If you think this goes into the right direction, please give more
 details about your LAN and ask for more information :-)
 
 regards,
 Steven
 (CCNA)
 
 
 
 
 On Sat, 2003-06-28 at 20:47, SainTiss wrote:
  Well, what I *need* e.g. on the gateway is something like this:
  
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse
  Iface
  192.168.0.3 0.0.0.0 255.255.255.255 UH0  00
  eth2
  192.168.0.2 0.0.0.0 255.255.255.255 UH0  00
  eth1
  213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
  eth0
  127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
  lo
  0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
  eth0
  
  However, by default those upper 2 rules aren't there, and instead
  there's a rule like this:
  
  192.168.0.0 0.0.0.0 255.255.255.0 U0  0   
  0   eth2
  
  So in other words, by default ALL LAN traffic is routed through eth2,
  while obviously traffic with 192.168.0.2 should be routed via eth1.
  
  Did that make it any clearer?
  
  Thanks,
  
  Hans
  
  On Sat, 2003-06-28 at 20:18, Bill Mullen wrote:
   On Sat, 28 Jun 2003, SainTiss wrote:
   
I just changed my network configs here, and it seems the routing table
got messed up...

I know the solution (ie adding some rules and deleting some), but I was
wondering if there was some file or something where I could specify the
right rules, so that the table is setup correctly at boot?

what's the default way to do this? I'm guessing some file which is then
processed by ifup or something, but I'm not sure...
   
   Depends on what's messed up. :)
   
   Most settings draw on the information in the /etc/sysconfig directory, 
   specifically the network file and the various ifcfg-interface ones 
   in the network-scripts subdirectory. For simpler setups, these are all 
   you'll need to adjust, but we have no idea how complicated your normal 
   routing table actually is ... care to offer a hint? ;)
 
 
 
 __
 
 Want to buy your Pack or Services from MandrakeSoft? 
 Go to http://www.mandrakestore.com
-- 
richard bown [EMAIL PROTECTED]


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [expert] how to set routing at boot?

2003-06-28 Thread Steven Broos
geddemn
forget about my post.  Didn't read your mail with my full attention (as
most of the time) and again made a stupid post :-)
Anyway, you can considder buying a switch or a hub, using one PC as
router/firewall between the switch and your cable connection, and
connect the other PC's with the switch.
I think that would be easier and would increase performance...

Steven


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [expert] how to set routing at boot?

2003-06-28 Thread SainTiss
Hi,

hmm, what are you saying here?

I'd basically want all pc's to be in the same subnet, yes...

So I should delete all routing rules wrt the LAN?

Thanks,

Hans

On Sat, 2003-06-28 at 21:59, Steven Broos wrote:
 Quick lesson in subnetworking, because I think the problem isn't your
 IPtables-settings but your network layout.
 
 192.168.0.x is a class C network address. 192.168.0 is the network
 address, and the last number is the host-portion of the address.
 If all PCs have an address beginning with 192.168.0 and a netmask of
 255.255.255.0 they are on the same subnet, and don't need routing.
 If you need to separate your LAN into difefrent subnets, use 192.168.0.x
 and 192.168.1.x etc...
 
 Creating a subnet with mask 255.255.255.255 isn't possible, because that
 way you don't have any broadcast/network-addresses.
 
 If you think this goes into the right direction, please give more
 details about your LAN and ask for more information :-)
 
 regards,
 Steven
 (CCNA)
 
 
 
 
 On Sat, 2003-06-28 at 20:47, SainTiss wrote:
  Well, what I *need* e.g. on the gateway is something like this:
  
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse
  Iface
  192.168.0.3 0.0.0.0 255.255.255.255 UH0  00
  eth2
  192.168.0.2 0.0.0.0 255.255.255.255 UH0  00
  eth1
  213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
  eth0
  127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
  lo
  0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
  eth0
  
  However, by default those upper 2 rules aren't there, and instead
  there's a rule like this:
  
  192.168.0.0 0.0.0.0 255.255.255.0 U0  0   
  0   eth2
  
  So in other words, by default ALL LAN traffic is routed through eth2,
  while obviously traffic with 192.168.0.2 should be routed via eth1.
  
  Did that make it any clearer?
  
  Thanks,
  
  Hans
  
  On Sat, 2003-06-28 at 20:18, Bill Mullen wrote:
   On Sat, 28 Jun 2003, SainTiss wrote:
   
I just changed my network configs here, and it seems the routing table
got messed up...

I know the solution (ie adding some rules and deleting some), but I was
wondering if there was some file or something where I could specify the
right rules, so that the table is setup correctly at boot?

what's the default way to do this? I'm guessing some file which is then
processed by ifup or something, but I'm not sure...
   
   Depends on what's messed up. :)
   
   Most settings draw on the information in the /etc/sysconfig directory, 
   specifically the network file and the various ifcfg-interface ones 
   in the network-scripts subdirectory. For simpler setups, these are all 
   you'll need to adjust, but we have no idea how complicated your normal 
   routing table actually is ... care to offer a hint? ;)
 
 
 
 __
 
 Want to buy your Pack or Services from MandrakeSoft? 
 Go to http://www.mandrakestore.com
-- 
In a world without walls and fences, who needs windows and gates?

Is the essence that the light pulse lives longer?

Hans Schippers
1LIC INF
UIA 2002-2003


signature.asc
Description: This is a digitally signed message part


Re: [expert] how to set routing at boot?

2003-06-28 Thread SainTiss
Well, that would work of course, but it's rather ugly don't you think?

I'm looking for the way MDK does these things by default.. Must be
somewhere in /etc/sysconfig

Hans

On Sat, 2003-06-28 at 23:12, richard bown wrote:
 HI
 try adding to rc.local at the end of the file
 /sbin/route add -host 192.168.0.2 eth1
 /sbin/route add -host 192.168.0.3 eth2
 HTH 
 Richard
 
 On Sat, 2003-06-28 at 20:59, Steven Broos wrote:
  Quick lesson in subnetworking, because I think the problem isn't your
  IPtables-settings but your network layout.
  
  192.168.0.x is a class C network address. 192.168.0 is the network
  address, and the last number is the host-portion of the address.
  If all PCs have an address beginning with 192.168.0 and a netmask of
  255.255.255.0 they are on the same subnet, and don't need routing.
  If you need to separate your LAN into difefrent subnets, use 192.168.0.x
  and 192.168.1.x etc...
  
  Creating a subnet with mask 255.255.255.255 isn't possible, because that
  way you don't have any broadcast/network-addresses.
  
  If you think this goes into the right direction, please give more
  details about your LAN and ask for more information :-)
  
  regards,
  Steven
  (CCNA)
  
  
  
  
  On Sat, 2003-06-28 at 20:47, SainTiss wrote:
   Well, what I *need* e.g. on the gateway is something like this:
   
   Kernel IP routing table
   Destination Gateway Genmask Flags Metric RefUse
   Iface
   192.168.0.3 0.0.0.0 255.255.255.255 UH0  00
   eth2
   192.168.0.2 0.0.0.0 255.255.255.255 UH0  00
   eth1
   213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
   eth0
   127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
   lo
   0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
   eth0
   
   However, by default those upper 2 rules aren't there, and instead
   there's a rule like this:
   
   192.168.0.0 0.0.0.0 255.255.255.0 U0  0   
   0 eth2
   
   So in other words, by default ALL LAN traffic is routed through eth2,
   while obviously traffic with 192.168.0.2 should be routed via eth1.
   
   Did that make it any clearer?
   
   Thanks,
   
   Hans
   
   On Sat, 2003-06-28 at 20:18, Bill Mullen wrote:
On Sat, 28 Jun 2003, SainTiss wrote:

 I just changed my network configs here, and it seems the routing table
 got messed up...
 
 I know the solution (ie adding some rules and deleting some), but I was
 wondering if there was some file or something where I could specify the
 right rules, so that the table is setup correctly at boot?
 
 what's the default way to do this? I'm guessing some file which is then
 processed by ifup or something, but I'm not sure...

Depends on what's messed up. :)

Most settings draw on the information in the /etc/sysconfig directory, 
specifically the network file and the various ifcfg-interface ones 
in the network-scripts subdirectory. For simpler setups, these are all 
you'll need to adjust, but we have no idea how complicated your normal 
routing table actually is ... care to offer a hint? ;)
  
  
  
  __
  
  Want to buy your Pack or Services from MandrakeSoft? 
  Go to http://www.mandrakestore.com
-- 
In a world without walls and fences, who needs windows and gates?

Is the essence that the light pulse lives longer?

Hans Schippers
1LIC INF
UIA 2002-2003


signature.asc
Description: This is a digitally signed message part


Re: [expert] how to set routing at boot?

2003-06-28 Thread SainTiss
that would probably be a good solution, but I've got quite a lot of
(longish) cables here, and installing a hub would mean I won't be able
to use those anymore (coax and such), so I'd really prefer avoiding the
install of a switch/hub...

Hans

On Sat, 2003-06-28 at 22:46, Steven Broos wrote:
 geddemn
 forget about my post.  Didn't read your mail with my full attention (as
 most of the time) and again made a stupid post :-)
 Anyway, you can considder buying a switch or a hub, using one PC as
 router/firewall between the switch and your cable connection, and
 connect the other PC's with the switch.
 I think that would be easier and would increase performance...
 
 Steven
 
 
 
 __
 
 Want to buy your Pack or Services from MandrakeSoft? 
 Go to http://www.mandrakestore.com
-- 
In a world without walls and fences, who needs windows and gates?

Is the essence that the light pulse lives longer?

Hans Schippers
1LIC INF
UIA 2002-2003


signature.asc
Description: This is a digitally signed message part


Re: [expert] how to set routing at boot?

2003-06-28 Thread richard bown

Well it will work, the big problem is two adjacent addresses on two
different interfaces.
personally I would have split the subnet in two so that a netmask of
x.x.x.0/27 could be used.
I had to do similar thing when running a radio ip hub here, where users
were linked on different interfaces with each interface using a
different frequency..
If there is only 1 machine on each interface it dos'nt matter about
broadcast addresses, as there's only 1 machine to broadcast to.
So the only way to route is with host routing.
Also if adding to rc.local dont forget to delete the default routing

/sbin/route del -net 192.168.0.0 netmask 255.255.255.0 eth2

Richard
On Sat, 2003-06-28 at 22:00, SainTiss wrote:
 Well, that would work of course, but it's rather ugly don't you think?
 
 I'm looking for the way MDK does these things by default.. Must be
 somewhere in /etc/sysconfig
 
 Hans
 
 On Sat, 2003-06-28 at 23:12, richard bown wrote:
  HI
  try adding to rc.local at the end of the file
  /sbin/route add -host 192.168.0.2 eth1
  /sbin/route add -host 192.168.0.3 eth2
  HTH 
  Richard
  
  On Sat, 2003-06-28 at 20:59, Steven Broos wrote:
   Quick lesson in subnetworking, because I think the problem isn't your
   IPtables-settings but your network layout.
   
   192.168.0.x is a class C network address. 192.168.0 is the network
   address, and the last number is the host-portion of the address.
   If all PCs have an address beginning with 192.168.0 and a netmask of
   255.255.255.0 they are on the same subnet, and don't need routing.
   If you need to separate your LAN into difefrent subnets, use 192.168.0.x
   and 192.168.1.x etc...
   
   Creating a subnet with mask 255.255.255.255 isn't possible, because that
   way you don't have any broadcast/network-addresses.
   
   If you think this goes into the right direction, please give more
   details about your LAN and ask for more information :-)
   
   regards,
   Steven
   (CCNA)
   
   
   
   
   On Sat, 2003-06-28 at 20:47, SainTiss wrote:
Well, what I *need* e.g. on the gateway is something like this:

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
192.168.0.3 0.0.0.0 255.255.255.255 UH0  00
eth2
192.168.0.2 0.0.0.0 255.255.255.255 UH0  00
eth1
213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
eth0
127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
lo
0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
eth0

However, by default those upper 2 rules aren't there, and instead
there's a rule like this:

192.168.0.0 0.0.0.0 255.255.255.0 U0  0   
0   eth2

So in other words, by default ALL LAN traffic is routed through eth2,
while obviously traffic with 192.168.0.2 should be routed via eth1.

Did that make it any clearer?

Thanks,

Hans

On Sat, 2003-06-28 at 20:18, Bill Mullen wrote:
 On Sat, 28 Jun 2003, SainTiss wrote:
 
  I just changed my network configs here, and it seems the routing table
  got messed up...
  
  I know the solution (ie adding some rules and deleting some), but I was
  wondering if there was some file or something where I could specify the
  right rules, so that the table is setup correctly at boot?
  
  what's the default way to do this? I'm guessing some file which is then
  processed by ifup or something, but I'm not sure...
 
 Depends on what's messed up. :)
 
 Most settings draw on the information in the /etc/sysconfig directory, 
 specifically the network file and the various ifcfg-interface ones 
 in the network-scripts subdirectory. For simpler setups, these are all 
 you'll need to adjust, but we have no idea how complicated your normal 
 routing table actually is ... care to offer a hint? ;)
   
   
   
   __
   
   Want to buy your Pack or Services from MandrakeSoft? 
   Go to http://www.mandrakestore.com
-- 
richard bown [EMAIL PROTECTED]


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [expert] how to set routing at boot?

2003-06-28 Thread SainTiss
Ok, anyway, I've tried to change the IP addresses now so that they are
in different subnets, but that doesn't really seem to help... pinging
between the 2 client pc's doesn't even work anymore now...

This is the config:

gateway (192.168.0.1 and 192.168.1.1):

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
eth2
192.168.0.0 0.0.0.0 255.255.255.0   U 0  00
eth1
213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
eth0
127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
lo
0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
eth0

client 192.168.0.2:

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
192.168.0.0 0.0.0.0 255.255.255.0   U 0  00
eth0
127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
lo
0.0.0.0 192.168.0.1 0.0.0.0 UG0  00
eth0

client 192.168.1.2:

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
eth0
127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
lo
0.0.0.0 192.168.1.1 0.0.0.0 UG0  00
eth0

I'd think this is supposed to work, no?

Any ideas as to what is wrong with this setup?

Thanks,

Hans


On Sat, 2003-06-28 at 21:59, Steven Broos wrote:
 Quick lesson in subnetworking, because I think the problem isn't your
 IPtables-settings but your network layout.
 
 192.168.0.x is a class C network address. 192.168.0 is the network
 address, and the last number is the host-portion of the address.
 If all PCs have an address beginning with 192.168.0 and a netmask of
 255.255.255.0 they are on the same subnet, and don't need routing.
 If you need to separate your LAN into difefrent subnets, use 192.168.0.x
 and 192.168.1.x etc...
 
 Creating a subnet with mask 255.255.255.255 isn't possible, because that
 way you don't have any broadcast/network-addresses.
 
 If you think this goes into the right direction, please give more
 details about your LAN and ask for more information :-)
 
 regards,
 Steven
 (CCNA)
 
 
 
 
 On Sat, 2003-06-28 at 20:47, SainTiss wrote:
  Well, what I *need* e.g. on the gateway is something like this:
  
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse
  Iface
  192.168.0.3 0.0.0.0 255.255.255.255 UH0  00
  eth2
  192.168.0.2 0.0.0.0 255.255.255.255 UH0  00
  eth1
  213.118.248.0   0.0.0.0 255.255.252.0   U 0  00
  eth0
  127.0.0.0   0.0.0.0 255.0.0.0   U 0  00
  lo
  0.0.0.0 213.118.248.1   0.0.0.0 UG0  00
  eth0
  
  However, by default those upper 2 rules aren't there, and instead
  there's a rule like this:
  
  192.168.0.0 0.0.0.0 255.255.255.0 U0  0   
  0   eth2
  
  So in other words, by default ALL LAN traffic is routed through eth2,
  while obviously traffic with 192.168.0.2 should be routed via eth1.
  
  Did that make it any clearer?
  
  Thanks,
  
  Hans
  
  On Sat, 2003-06-28 at 20:18, Bill Mullen wrote:
   On Sat, 28 Jun 2003, SainTiss wrote:
   
I just changed my network configs here, and it seems the routing table
got messed up...

I know the solution (ie adding some rules and deleting some), but I was
wondering if there was some file or something where I could specify the
right rules, so that the table is setup correctly at boot?

what's the default way to do this? I'm guessing some file which is then
processed by ifup or something, but I'm not sure...
   
   Depends on what's messed up. :)
   
   Most settings draw on the information in the /etc/sysconfig directory, 
   specifically the network file and the various ifcfg-interface ones 
   in the network-scripts subdirectory. For simpler setups, these are all 
   you'll need to adjust, but we have no idea how complicated your normal 
   routing table actually is ... care to offer a hint? ;)
 
 
 
 __
 
 Want to buy your Pack or Services from MandrakeSoft? 
 Go to http://www.mandrakestore.com
-- 
In a world without walls and fences, who needs windows and gates?

Is the essence that the light pulse lives longer?

Hans Schippers
1LIC INF
UIA 2002-2003


signature.asc
Description: This is a digitally signed message part