RE: Basic routing problem
> I am willing to collect and explain what I did to get it > working but it > may take a little time (a couple of days) to make sure I get > everything > and to go over it so I can understand it again. And just now having a > look at the routing table shows a couple of duplicate and/or > conflicting > routes (but they don't seem to be causing any problems). > > However for starters you might like to read this howto which > explains a > few things which you might need to know: > http://www.faqs.org/docs/Linux-mini/Proxy-ARP-Subnet.html > Let me start here and see where it gets me. Thanks, Peter
Re: Basic routing problem
Peter Coppens wrote: From: Brett [mailto:[EMAIL PROTECTED] You can possibly use ARP to get B to listen for A's packets and route them accordingly. For example I have the following setup: LAN-1 <--> LAN-2 <--> router <--> internet All hosts on LAN-1 can talk to all hosts on LAN-2 and all hosts can access the internet via the router. I have found this to be a very good setup. The link between LAN-1 and LAN-2 is very slow and all the packets get to where they are going without wasting bandwidth. It also doesn't have any of the disadvantages of NAT'ing. > > Thanks for the suggestion. Would you be able to share details on how > you configured your systems? I am willing to collect and explain what I did to get it working but it may take a little time (a couple of days) to make sure I get everything and to go over it so I can understand it again. And just now having a look at the routing table shows a couple of duplicate and/or conflicting routes (but they don't seem to be causing any problems). However for starters you might like to read this howto which explains a few things which you might need to know: http://www.faqs.org/docs/Linux-mini/Proxy-ARP-Subnet.html One thing to remember is that I put my solution together from snippets from usenet, forums, howto's and webpages. So it may not be technically 100% correct but expert help was thin at the time. Brett -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Basic routing problem
Brett, Thanks for the suggestion. Would you be able to share details on how you configured your systems? Tx, Peter > -Original Message- > From: Brett [mailto:[EMAIL PROTECTED] > Sent: Monday, October 10, 2005 5:41 AM > To: debian-user@lists.debian.org > Subject: Re: Basic routing problem > > Hendrik Sattler wrote: > > Peter Coppens wrote: > > > > > >>>I assume you missed to add a route on R for the net of A pointing > >>>to B. > >> > >>Yes...that is probably what is wrong. Problem is I don't > have enough > >>privileges on the router to do that. Seems I am stuck, sigh. > > > > You can do NAT for A on B or install a proxy on B. > > You can possibly use ARP to get B to listen for A's packets and route > them accordingly. > > For example I have the following setup: > LAN-1 <--> LAN-2 <--> router <--> internet > > All hosts on LAN-1 can talk to all hosts on LAN-2 and all hosts can > access the internet via the router. I have found this to be a > very good > setup. The link between LAN-1 and LAN-2 is very slow and all > the packets > get to where they are going without wasting bandwidth. It > also doesn't > have any of the disadvantages of NAT'ing. > > HTH, > Brett > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > >
Re: Basic routing problem
Hendrik Sattler wrote: Peter Coppens wrote: I assume you missed to add a route on R for the net of A pointing to B. Yes...that is probably what is wrong. Problem is I don't have enough privileges on the router to do that. Seems I am stuck, sigh. You can do NAT for A on B or install a proxy on B. You can possibly use ARP to get B to listen for A's packets and route them accordingly. For example I have the following setup: LAN-1 <--> LAN-2 <--> router <--> internet All hosts on LAN-1 can talk to all hosts on LAN-2 and all hosts can access the internet via the router. I have found this to be a very good setup. The link between LAN-1 and LAN-2 is very slow and all the packets get to where they are going without wasting bandwidth. It also doesn't have any of the disadvantages of NAT'ing. HTH, Brett -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Basic routing problem
On Sun, Oct 09, 2005 at 06:48:00AM -0400, Peter Coppens wrote: > > Or maybe you can make B act like a bridge instead of a router > > and put A > > on 192.168.1.0/24. > > I have attempted to use brctl on B to bridge eth0 and wlan0 and > something seems to work...something meaning when I do dhclient on A it > gets an address from R. > > After that I can however still not ping R. I get 'Destination Host > Unreachable'. > > Any suggestions warmly appreciated, > > Thanks, > > Peter More details (as somebody else wrote) would be helpful. A guess: you must set a route on machine A, something like: route add default gw 192.168.2.1 (that means: use B as a gateway to all other hosts) HTH -- Joachim Fahnenmüller -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Basic routing problem
> Or maybe you can make B act like a bridge instead of a router > and put A > on 192.168.1.0/24. I have attempted to use brctl on B to bridge eth0 and wlan0 and something seems to work...something meaning when I do dhclient on A it gets an address from R. After that I can however still not ping R. I get 'Destination Host Unreachable'. Any suggestions warmly appreciated, Thanks, Peter
Re: Basic routing problem
On Sat, Oct 08, 2005 at 05:16:35AM -0400, Peter Coppens wrote: > >Debian (network) fans, > > > >I am strugging with a basic routing problem > > > >I have two machines and a router which is connected to the internet. [..] >Anybody any suggestions what is going on, or any ideas which route or >modules are missing on which machine? [..] Hi Peter, I know that you are more likely to get a response if you provide the output of at least: a) route -vee b) cat /etc/network/interfaces from each machine. I am not running a network yet and so can not directly help you but if I was then I would want to know the output of at least those commands. In other words, I hope someone else may help ;-) You running Sarge? -- Chris. == Reproduction if desired may be handled locally. -- rfc3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Basic routing problem
Peter Coppens wrote: >> I assume you missed to add a route on R for the net of A pointing >> to B. > > Yes...that is probably what is wrong. Problem is I don't have enough > privileges on the router to do that. Seems I am stuck, sigh. You could enable NAT on B; in that case, the router doesn't need to know about A's subnet. Or maybe you can make B act like a bridge instead of a router and put A on 192.168.1.0/24. -- If I have been able to see further, it was only because I stood on the shoulders of giants. -- Isaac Newton Roel Schroeven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Basic routing problem
Peter Coppens wrote: >> I assume you missed to add a route on R for the net of A pointing >> to B. > Yes...that is probably what is wrong. Problem is I don't have enough > privileges on the router to do that. Seems I am stuck, sigh. You can do NAT for A on B or install a proxy on B. HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Basic routing problem
> I assume you missed to add a route on R for the net of A pointing > to B. Yes...that is probably what is wrong. Problem is I don't have enough privileges on the router to do that. Seems I am stuck, sigh. Thanks for the help, Peter > -Original Message- > From: Jörg Schütter [mailto:[EMAIL PROTECTED] > Sent: Saturday, October 08, 2005 1:11 PM > To: debian-user@lists.debian.org > Subject: Re: Basic routing problem > > Hello Peter, > > On Sat, 8 Oct 2005 05:16:35 -0400 > "Peter Coppens" <[EMAIL PROTECTED]> wrote: > > > Debian (network) fans, > > > > I am strugging with a basic routing problem > > > > I have two machines and a router which is connected to the internet. > > > > A <--> B <--> R <-> Internet > > > > - A is connected to B through eth0, static IP 192.168.2.2 > > - B is connected to A through eth0, static IP 192.168.2.1 > > - B is connected to R through wlan0, dynamic IP 192.168.1.102 > > - ip forwarding on B is enabledI think, no ipchain enabled or > > installed. > > > > I have added routes added so that > > > > - A can ping B on 192.168.2.1 and 192.168.1.102 > > - B can ping A, R and the Internet > > > > I can not get A to ping R nor the Internet > > I assume you missed to add a route on R for the net of A pointing > to B. > > > > Anybody any suggestions what is going on, or any ideas > which route or > > modules are missing on which machine? > > > > > Jörg > > -- > Jörg Schütter http://www.schuetter.org/joerg > [EMAIL PROTECTED]http://www.lug-untermain.de/ > > >
Re: Basic routing problem
Hello Peter, On Sat, 8 Oct 2005 05:16:35 -0400 "Peter Coppens" <[EMAIL PROTECTED]> wrote: > Debian (network) fans, > > I am strugging with a basic routing problem > > I have two machines and a router which is connected to the internet. > > A <--> B <--> R <-> Internet > > - A is connected to B through eth0, static IP 192.168.2.2 > - B is connected to A through eth0, static IP 192.168.2.1 > - B is connected to R through wlan0, dynamic IP 192.168.1.102 > - ip forwarding on B is enabledI think, no ipchain enabled or > installed. > > I have added routes added so that > > - A can ping B on 192.168.2.1 and 192.168.1.102 > - B can ping A, R and the Internet > > I can not get A to ping R nor the Internet I assume you missed to add a route on R for the net of A pointing to B. > > Anybody any suggestions what is going on, or any ideas which route or > modules are missing on which machine? > Jörg -- Jörg Schütter http://www.schuetter.org/joerg [EMAIL PROTECTED]http://www.lug-untermain.de/
