[plug] Still not able to route to adsl

bob bob at fots.org.au
Sat May 1 16:40:17 WST 2004


I have not been able to crack this one since I posted regarding this on 
Wednesday. I would really like some clues on how to get this working - 
please :)

To refresh those that are interested's memories here is what I am trying to 
achieve and some of what I have tried

ADSL (NB1300+4)
        |
        eth1 (192.168.1.x dhcp'd from ADSL)
Gateway/firewall  (debian)
        eth0 (192.168.0.x)
        |
hosts on LAN

I can not ping  ADSL from "hosts on LAN". I can ping  ADSL from 
Gateway/firewall.

ADSL appears not to be able to see 192.168.0/24 either, however it can see 
external 192.168.1/24 (ie the dhcp's IP it gives to eth1 on the  
Gateway/firewall)

If I set a route to 192.168.1/24 on the "hosts on LAN" and plug the ADSL 
into the switch I can see the device. I find though that the link fails 
after a short period of use - I suspect this may be to do with having two 
routes to the one device, one direct and the other via the Gateway/firewall

Isolating the ADSL from the rest of the network and plugging a host into it 
directly appears to work fine. (ie there is no hardware problem - at least 
for some simple configurations)

There is one factor muddying the water in that there is currently a ppp 
dialup coming off the Gateway/firewall ... this works, in fact it is what 
the email will travel by. However I think it may be able to be ruled out as 
a direct problem as a reboot [1] with the dialup disabled produced little 
visible difference.

Yes, there is an iptables firewall... I tried an iptables -clear to see if 
that got rid of the problem... nope - don't worry, I remembered to restore 
it :).

I have tried every setting on the ADSL that looks halfway sensible without 
success. I have set routes to 192.168.0/24 on the device, I have tried both 
static and dhcp IP#s on the Gateway/firewall eth1 (dhcp was suggested as a 
possible solution). I have managed to make the ADSL stop responding to the 
world 4 times so far - fortunate the reset works eh :). 

I have set default routes on the Gateway/firewall to the ADSL 192.168.1/24 
addr, to the assigned ISP for the ADSL and to the ISP's gateway addr. None 
made any difference.

Needless to say looking back into my network from spark, trying to see if 
the port forwarding works, doesn't work either

I have found a site that details how to setup the NB1300 as a half-bridge 
(it manages the connection but then hands the assigned IP# over to the 
Gateway/firewall so it deals directly with the internet) but I would prefer 
not to go that direction (what's the point of buying a router in that 
case?)

There is heaps of other things I've tried but I won't bore you with too much 
detail :), just say that I am at my wits end here and would really 
appreciate a point in the right direction.

Thanks.

[1] note to self: Two default routes + restarting networking = kernel panic

-- 
You will stop at nothing to reach your objective, but only because your
brakes are defective.




More information about the plug mailing list