News: This forum is now permanently frozen.
Pages: [1]
Topic: monowall behind router using pppoa doesnt route properly in half bridge mode  (Read 3130 times)
« on: June 08, 2008, 11:41:36 »
xbipin *
Posts: 2

basically my problem is i have a dlink ADSL router and recently i have changed its firmware to that of routertech, now my isp only supports pppoa so i cant create a full bridge which is possible in pppoe. recently the routertech team got a firmware upgrade that supports pppoa half bridge mode in which on boot once it gets the wan ip it passes it over the the first lan client, in my case the monowall running on alix 2c3, now the firmware is designed in such a way that it gives out a short lease of 60sec or whatever is defined and till the time it gets the wan ip it gives monowall a lan ip but monowall doesnt seem to follow the ip lease timing and doesnt poll for new ip on lease timeout and if its dont manually then monowall gets the wanip but doesnt seem to know how to route to the isps default gateway so all monowall lan clients dont get internet access.
i did some research and found out the this problem has been discussed and is almost 4 years old and the solution is simple:
monowall doesnt know how to set a default route to the ISP gateway (to fix all it has to do is set the route first).

the link to the older post is here:
http://m0n0.ch/wall/list/showmsg.php?id=109/30

Regards,
Bipin
« Reply #1 on: June 09, 2008, 11:14:02 »
markb ****
Posts: 331

My personal experience with ADSL routers in Bridge or half bridge mode is not good.  I have spent many hours with different models trying to get it to work, with limited success.   The best solution I found was to get a Dratek Vigor 100. It very simply is a PPPoE - PPPoA dsl modem.  It will let you use the PPPoE settings on the WAN page on Mono and convert it to PPPoA.  When I got one, all I did was change the default IP address and password (Need to do the latter through a telnet session) plug it in and hey presto it work like a charm.
« Reply #2 on: June 23, 2008, 19:03:49 »
Manuel Kasper
Administrator
*****
Posts: 364

Why m0n0wall's DHCP client fails to re-obtain a lease after the first one times out I don't know (would need a tcpdump from the WAN interface to see if it's really m0n0wall's fault), but m0n0wall does have some special-case code in its dhclient-script that should handle DHCP leases issued by half-bridge DSL modems (where default gateway = assigned IP address). Can you give us some WAN interface status output after it has obtained the "right" lease?

From /sbin/dhclient-script (in 1.3b11):

Code:
    if [ x"$new_ip_address" = x"$new_routers" ]; then
        route delete default >/dev/null 2>&1
        route add default -interface -link $interface >/dev/null 2>&1
    fi
« Reply #3 on: May 21, 2010, 18:22:25 »
xe2sdc *
Posts: 2

Manuel I'm fighting with m0n0... I'm running 1.32 on alix and switched to a different ISP.
I have to run in half-bridge setup since my new ISP supports only pppoa and my modem (dlink 320B) doesn't support tunneling pppoa over pptp. I've found that while m0n0 picks up the right IP address from the modem, it doesn't setup the default route. I have to add the default route using exec.php ...

I'm trying to fix this issue but have little if no experience in playing "that deep" with m0n0.

Right now I've been able to replace the dhclient-script at runtime and obtain details on values of variables, trying to find why m0n0 doesn't run the "magic" code you already put in the script... :-)

Do you have some direction on how to dig deep this issue?

Thank you Manuel!
« Last Edit: May 21, 2010, 18:25:13 by xe2sdc »
« Reply #4 on: May 22, 2010, 00:07:05 »
xe2sdc *
Posts: 2

I've tweaked dhclient-script a little and found that

new_ip_address = 109.234.63.xx
new_routers = 192.168.1.1

The condition you mentioned in the script won't ever trigger within my specific environment.
I think you have to check if new_ip is within the same network of the new_routers. In case it is true, no need to add more routes. In case (just like mine) new_routers falls outside new_ip network, clean default route and add it with the above mentioned commands.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines