I have a machine connected to the local network via eth0 as
192.168.1.39. This machine also has an ISDN connection for dialling
remote machines. The ISDN connection uses RawIP, and assigns a static
IP to the dialled machine (192.168.1.5)
I'm wondering how to go about making the dialled machine visible on
the internal network.
The routing I have tried is as follows:

On 192.168.1.39
host 192.168.1.5 -> isdn0
network 192.168.1.0 -> eth0
default via 192.168.1.1 (GW) -> eth0

I have two gateways set up on the other machines on the internal net.
192.168.1.1 (DSL router) and 192.168.1.39 (ISDN machine)

This, however, doesn't allow me to see the 192.168.1.5 machine from
anything other than 192.168.1.39.

Any suggestions?

On Thu, 09 Oct 2003 09:38:21 +0100, gk <g777k@hotmail.com> wrote:
> I have a machine connected to the local network via eth0 as
> 192.168.1.39. This machine also has an ISDN connection for dialling
> remote machines. The ISDN connection uses RawIP, and assigns a static
> IP to the dialled machine (192.168.1.5)
> I'm wondering how to go about making the dialled machine visible on
> the internal network.
> The routing I have tried is as follows:
>
> On 192.168.1.39
> host 192.168.1.5 -> isdn0
> network 192.168.1.0 -> eth0
> default via 192.168.1.1 (GW) -> eth0
>
> I have two gateways set up on the other machines on the internal net.
> 192.168.1.1 (DSL router) and 192.168.1.39 (ISDN machine)
>
> This, however, doesn't allow me to see the 192.168.1.5 machine from
> anything other than 192.168.1.39.

Do you have ip_forward enabled (does cat /proc/sys/net/ipv4/ip_forward
return 1)?

Is your local IP for isdn0 192.168.1.39 (same as eth0 IP), which I think
is necessary to be able to proxy arp?

I know that pppd has a proxyarp option, but not sure how isdn works.
Perhaps you could enable proxy arp for the isdn connecting by doing:

echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp

Are you running any firewall?

By "visible" are you referring ping/traceroute, or samba/Network
Neighborhood? The remote will not see broadcasts from main network, only
traffic to its own IP.

--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/

Hi David, thanks for the reply.. As well as the replies below, I've
changed the machine on the isdn connection to 192.168.2.5 because I
have a feeling that packets routed to the old IP were getting snatched
by the internet net (192.168.1.x/255.255.255.0) route.

On Fri, 10 Oct 2003 01:16:21 +0000 (UTC), efflandt@xnet.com (David
Efflandt) wrote:

>
>Do you have ip_forward enabled (does cat /proc/sys/net/ipv4/ip_forward
>return 1)?

Yes

>
>Is your local IP for isdn0 192.168.1.39 (same as eth0 IP), which I think
>is necessary to be able to proxy arp?
>

no, I had isdn0 set to 192.168.1.6

>I know that pppd has a proxyarp option, but not sure how isdn works.
>Perhaps you could enable proxy arp for the isdn connecting by doing:
>
> echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
>

ok... gonna try this.

>Are you running any firewall?

no, security on the isdn is handled by only accepting calls from a
specific number/MSN

>By "visible" are you referring ping/traceroute, or samba/Network
>Neighborhood? The remote will not see broadcasts from main network, only
>traffic to its own IP.

I'm using ping to test if the machine is contactable.