RE: Routing problems

2003-11-12 Thread Vince Hoffman
Hi Dimitris,

snip lots of relevaent info

 
 The 10.X.X.X subnet will never need to use any of the
 services of the 193.X.X.X subnet or the 193.R.R.R
 router. It will always access internet via its own
 10.R.R.R router, which only routes packets towards the
 internet and never towards the 193.X.X.X subnet. Thus,
 what's the need to do any of the above? 
 
Well a packet originating on the 193.x.x.x network will have a return
address on the 193.x.x.x network even after its been routed via the freebsd
box, (unless you nat, which if your adsl router is a rubbish as mine was you
may have to as i couldnt add static routes to mine, but thats another
issue.) and so the 10.R.R.R router wont know where to forward to if it has
no route to 10.x.x.x (or at least the sending host on that network.)

 Please note that I am rather inexperienced in routing
 and please forgive me if I make terrible mistakes. :-)

and excuse me if i do too :) I've plenty of experience, but no formal
training.
 
 Thanks for the responce
 Jim Xochellis
 
 
 
 Do You Yahoo!?
 ?p??t?ste t? d??e?? @yahoo.gr d?es? sa? st? http://www.otenet.gr
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to 
 [EMAIL PROTECTED]
 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Routing problems

2003-11-12 Thread Dimitris Xochellis
Hi Vince, Hi list,

 --- Vince Hoffman [EMAIL PROTECTED]
wrote:

  
  The 10.X.X.X subnet will never need to use any of
 the
  services of the 193.X.X.X subnet or the 193.R.R.R
  router. It will always access internet via its own
  10.R.R.R router, which only routes packets towards
 the
  internet and never towards the 193.X.X.X subnet.
 Thus,
  what's the need to do any of the above? 
  
 Well a packet originating on the 193.x.x.x network
 will have a return
 address on the 193.x.x.x network even after its been
 routed via the freebsd
 box, (unless you nat, which if your adsl router is a
 rubbish as mine was you
 may have to as i couldnt add static routes to mine,
 but thats another
 issue.) and so the 10.R.R.R router wont know where
 to forward to if it has
 no route to 10.x.x.x (or at least the sending host
 on that network.)
 

Currently, I have solved all my problems, (it seems
so) without adding any routes to the 10.R.R.R router.
I have just added the 193.x.x.x interface to it and I
gave it an address in that interface. This seems to be
sufficient enough!

What I have learned from this problems is that a
router  can only route packets that are coming from
interfaces that it knows. Thus it either has to be a
member of the  source subnet or we have to
appropriately translate the addresses via NAT. Am I
right?

Although I have not followed your advice I am very
grateful to you, because you helped me think towards
the right direction. I will also keep in mind what you
have said in case I face problems in the future...

Thanks a lot
Jim Xochellis



Do You Yahoo!?
   @yahoo.grhttp://www.otenet.gr
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Routing problems

2003-11-11 Thread Vince Hoffman

- Original Message -
From: Dimitris Xochellis [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 11, 2003 6:43 PM
Subject: Routing problems


 Dear list members,

 I have two subnets (10.X.X.X and 193.X.X.X) on the
 same physical network (ethernet). Subnet 10.X.X.X has
 its own 10.R.R.R router, which is forwarding packets
 to the internet (via DSL),  Subnet 193.X.X.X has also
 its own 193.R.R.R router which is also forwarding
 packets to the internet (via a very slow analogical
 connection), The 193.R.R.R router is a FreeBSD(i386)
 4.7 - RELEASE box.

 What I need, is to forward some of the packets
 (depending on the final destination) of the 193.X.X.X
 subnet to the 10.R.R.R router via the 193.R.R.R
 router.

 193.X.X.X --- 193.R.R.R --- internet
   |
   v
 10.X.X.X --- 10.R.R.R --- internet

 I am using two ethernet cards on the 193.R.R.R and its
 network configuration follows:

 network_interfaces=rl0 rl1 lo0
 ifconfig_rl0=inet 193.R.R.R  netmask 255.255.255.240
 ifconfig_rl1=inet 10.A.A.A  netmask 255.255.255.0

 hostname=router.of.subnet
 defaultrouter=10.R.R.R
 gateway_enable=YES

 The result is that the 193.R.R.R router can access
 both subnets but cannot forward packet from the one to
 the other. The situation does not get any better even
 if I add the following lines:

 static_routes=adsl
 route_ adsl =-net  target_subnet  10.R.R.R

 In all cases we have static routes and routed is
 disabled.

 My questions are:
 1) Is it appropriate/feasible to use routing in this
 case, where we don't have physically separated
 subnets? If not, what should be used instead?
 2) Any hints, corrections or pointers to the docs?


I'm no routing guru but from the setup described the only host on the
10.X.X.X network
that has a route to the 193.X.X.X network is the freebsd router (193.R.R.R
and 10.A.A.A). So either add a route on
the adsl router something like
route add -net 193.X.X.X  netmask 255.255.255.240 10.A.A.A
or put a static route on each host on the 10.X.X.X network with 10.A.A.A as
the default route for 193.R.R.R

 Thanks in Advance
 Jim Xohellis



 
 Do You Yahoo!?
@yahoo.grhttp://www.otenet.gr
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
[EMAIL PROTECTED]


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Routing problems

2003-11-11 Thread Dimitris Xochellis
Hi List, hi Vince,

 --- Vince Hoffman [EMAIL PROTECTED]
wrote: 
 
 - Original Message -
 From: Dimitris Xochellis [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Tuesday, November 11, 2003 6:43 PM
 Subject: Routing problems
 
 
  Dear list members,
 
  I have two subnets (10.X.X.X and 193.X.X.X) on the
  same physical network (ethernet). Subnet 10.X.X.X
 has
  its own 10.R.R.R router, which is forwarding
 packets
  to the internet (via DSL),  Subnet 193.X.X.X has
 also
  its own 193.R.R.R router which is also forwarding
  packets to the internet (via a very slow
 analogical
  connection), The 193.R.R.R router is a
 FreeBSD(i386)
  4.7 - RELEASE box.
 
  What I need, is to forward some of the packets
  (depending on the final destination) of the
 193.X.X.X
  subnet to the 10.R.R.R router via the 193.R.R.R
  router.
 
  193.X.X.X --- 193.R.R.R --- internet
|
v
  10.X.X.X --- 10.R.R.R --- internet
 
  I am using two ethernet cards on the 193.R.R.R and
 its
  network configuration follows:
 
  network_interfaces=rl0 rl1 lo0
  ifconfig_rl0=inet 193.R.R.R  netmask
 255.255.255.240
  ifconfig_rl1=inet 10.A.A.A  netmask
 255.255.255.0
 
  hostname=router.of.subnet
  defaultrouter=10.R.R.R
  gateway_enable=YES
 
  The result is that the 193.R.R.R router can access
  both subnets but cannot forward packet from the
 one to
  the other. The situation does not get any better
 even
  if I add the following lines:
 
  static_routes=adsl
  route_ adsl =-net  target_subnet  10.R.R.R
 
  In all cases we have static routes and routed is
  disabled.
 
  My questions are:
  1) Is it appropriate/feasible to use routing in
 this
  case, where we don't have physically separated
  subnets? If not, what should be used instead?
  2) Any hints, corrections or pointers to the docs?
 
 
 I'm no routing guru but from the setup described the
 only host on the 10.X.X.X network
 that has a route to the 193.X.X.X network is the
 freebsd router (193.R.R.R and 10.A.A.A). 

That is correct.

 So either add a route on
 the adsl router something like
 route add -net 193.X.X.X  netmask 255.255.255.240
 10.A.A.A
 or put a static route on each host on the 10.X.X.X
 network with 10.A.A.A as
 the default route for 193.R.R.R
 

The 10.X.X.X subnet will never need to use any of the
services of the 193.X.X.X subnet or the 193.R.R.R
router. It will always access internet via its own
10.R.R.R router, which only routes packets towards the
internet and never towards the 193.X.X.X subnet. Thus,
what's the need to do any of the above? 

Please note that I am rather inexperienced in routing
and please forgive me if I make terrible mistakes. :-)

Thanks for the responce
Jim Xochellis



Do You Yahoo!?
   @yahoo.grhttp://www.otenet.gr
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: routing problems (experience needed)

2003-09-07 Thread Harald Schmalzbauer
On Saturday 06 September 2003 12:19, Peter Ulrich Kruppa wrote:
 Hi,

 I am trying to substitute our school's old Win NT4 Server by a
 SAMBA/FreeBSD. The SAMBA PDC itself works like a charm, but
 without the NT machine it can't be located from the different
 subnets - and so is quite useless.

 This is our network design:


  Internet

  ^

   ___+_

   | DSL Router|  172.16.2.254

   ---+-

   ___+

   |   Switch +--+

   -+-+-+-+-+--  |
 _  | | | | |+---+

 | PROXY FBSD|--+ | | | || 172.16.2.1

 -| | | |    +_
 172.16.2.11  | | | +-| SAMBA PDC|   | NT4 PDC|

  | | |   ------+--
  | | |   172.16.2.253  |
  | | | 172.16.1.1

 different subnets: |
  172.16.3. |
  172.16.4. |
  172.16.5. 172.16.2.
etc. subnet
  (with routers and  (with switches)
   switches)


 As I said: connections between the different subnets break as
 soon as the NT4 Server is plugged off.
 What can be done:
 1) Change all machines to mask 255.255.0.0
- or would this end up in bad perfomance?
(We have about 35 workstations all over the house and the
 number is growing)

I'm guessing your sunet currently is /24.
Don't consider any perfomance issues unless you have at least 100 workstations

 2) Set up some kind of router (we have got some old P75 left)?

Well, if machine FOO=172.16.3.x/24 want's to communicate with machine 
BAR=172.16.4.x/24 you WILL need a router in any case.

If you just want to have machined FOO and BAR communicate with 
PDC=172.16.2.x/24 you could do some ARP tricks but I guess you have a router 
in each subnet.


Now your problem is with WIndowsNameService (WINS)
You have to setup samba as a WINS server with local master and domain master 
set. Then your clients need to get the DPC's IP as WINS Server. You can do 
that with ISC's DHCP by adding the following option netbios-name-servers 
your.pdc-ip.or.name;
Per definition in each subnet had to be another local master but I can 
remember that if there are enough machines in each subnet, so that there is 
alwas a masterbrowser online, it works without.

Hope this helps,

-Harry


 3) Something completely different?

 Thanks for all kinds of ideas and hints.

 Uli.


   +---+

   |Peter Ulrich Kruppa|
   |
 | Wuppertal |
 |  Germany  |

 +---+
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]


pgp0.pgp
Description: signature