[durdom]

Hello, dear sirs!

Sorry, if this question was already asked. It is hard to define the problem for google.

My ISP is giving it's clients some weird settings

e.g.
inet 94.73.223.243
netmask 255.255.255.255
GW 109.226.250.10
(not PPTP or PPPOE, but basic LAN card - IPoE)

on my linux box this works somehow. But router with dd-wrt (pre 24 sp2) doesn't. Returns all packets with
error - not routable.

Is it possible to fix? Evil ISP offers to revert back to dlink firmware.

[durdom]

Thanks for the answer.

I'm using the provider's terminology. They call it: IPoE, IP Unnumbered, Host Route.
To use original Dlink FW is also their advise. Of course, I will not.

The problem narrowed a bit. Yesterday I noticed, that default route is not assigning.
After this command
/sbin/route add default gw 109.226.250.10
everything works (until reboot, of course)

I'm not sure, who's is actually to blame. The ISP's stupid settings or it's just a bug in dd-wrt's scripts.

The situation is:
ISP's giving me
IP 94.73.223.243
Mask 255.255.255.255

route 109.226.250.0/24 through 94.73.223.243
and default GW 109.226.250.10

What's the best place to put custom script? Cron? As far as I see, all scripts are in /tmp. Looks like, they are stored in some archive and are recreating every boot. Right?

[durdom]

I added startup script

/sbin/route add default gw 94.73.223.243

and it didn't help (maybe it is firing before dhcp?)

I can overcome this problem now in many ways, but I wonder what's the most correct one. As far as I understand, it's a bug in dd-wrt's dhcp-deamon (not working with /32 masks)?

[BasCom]

first, deploy routes in setup -> adv routes
2nd: dont set route to the client IP given by ISP.

94.73.223.243 is your client ip, not your gateway ( 109.226.250.10)

wow sm00x you elite, didnt you see that mistake? mr smart.