> 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
> conf
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
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
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 prox
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 dhclie
> 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
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 sug
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
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
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:
>
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 &l
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, sta
12 matches
Mail list logo
