| Author |
 Topic  |
|
|
arielgrin
Starting Member
Argentina
6 Posts |
 Posted - 26/01/2008 : 03:16:27
|
Hi everybody: I need some help with my connection config.
I'm using PPPoE and want the "always on" connection method.
My PPPoE profile was set to dial on demand, so I changed demanddial to off, and now the profile in the Web GUI shows always on, but still, my ST won't dial automatically.
If I set it to demanddial=on, the ST dials automatically but only afetr I start an IP connection, for example browsing the web, or checking emails.
Can someone help me configure my ST so it dials automatically when it gets synchronized to the ADSL line, I suppose this is the "always on" method.
My firmware version is 4.2.7.16 and it DOES have this demanddial parameter for pppoe ifconfig. Thanks
|
|
|
StingRay
Advanced Member
Australia
1219 Posts |
Posted - 26/01/2008 : 09:03:25
|
Is the firmware the standard international firmware or does your ISP supply a special one?
You can download the firmware from here. Just click home and go to the 510 profile. When you upgrade use the bootp method to wipe all current settings and go back to true factory setup. This will also delete any ISP.DEF that might have been supplied by ISP.
You can also login via telnet and issue the command system reset. Answer yes to all the questions.
Then go to advanced, easy setup and choose PPPoE routed always on. That is the standard template.
I would advise you to save your present config file before you start all this. |
 |
|
|
arielgrin
Starting Member
Argentina
6 Posts |
Posted - 26/01/2008 : 09:54:53
|
| StingRay: thanks for your reply. I'm using firmware 4.2.7.16 downloaded from speedtouch.net.nz and using pppoe dhcp spoof template also downloaded from here. I modified demanddial=off, restart=on, idle=0 to get an always on connection straight after powering on the ST. Anyway, I can't get ST to connect automatically. If I set demanddial=on, ST will connect automatically, but after I try to surf the web, check email or so. I want the ST to connect automatically immediately after being powered on. Thanks |
|
|
|
StingRay
Advanced Member
Australia
1219 Posts |
Posted - 26/01/2008 : 12:15:37
|
Ok, you didn't spell out the whole thing. No mention of dhcp spoofing.
You need to understand what is happening with spoofing. No IP request is made to the ISP until the pc does a DHCP request. At that point the modem will authenticate. I think this is expected result of spoofing.
First question, why use half bridge when you are using pppoe. Full bridge is far superior and has more robust ability to handle IP changes if your ISP uses dynamic rather than static which is the norm.
Can you use PPPoA. It seems to be more robust with dhcp spoofing.
Let me check the template. Long long time since I used it. |
|
|
|
arielgrin
Starting Member
Argentina
6 Posts |
Posted - 28/01/2008 : 08:19:59
|
Thanks Stingray. I managed to make it work. Setting demanddial to off and restart to on made it.
The problem now is with my router, a Linksys WRT54GL. I think I'm having troubles because my ISP assigns a default gateway that is not in the same subnet as the public IP it assigns me. The strange thing is that it does work with my other Linksys router, a BEFSX41. Do you think this is because WRT54GL firmware is based on linux and BEFSX41 firmware is based on VxWorks?
Do you know if there is a way to make dhcp spoof with WRT54GL? I want the speedtouch to pass the public address to the WRT54GL, I don't want the router to dial, just to handle NAT, that's why I want to use dhcp spoof. |
|
|
|
StingRay
Advanced Member
Australia
1219 Posts |
Posted - 28/01/2008 : 09:32:55
|
You hit it on the head. And I have to confess I never did solve it. But I have tried exactly what you have done. Linux is actually following the correct method. Unfortunately correct doesn't work with the internet because it doesn't bother windows or vxworks etc at all. So the issue is mainly with linux based pc or routers.
I have proved the issue to be true by manually resetting the subnet which worked fine, until the lease expires.
Nor can I find anyplace in the speedtouch where I could alter the subnet delivered to the router. Your ISP is probably using a 255.255.255.255 but the speedtouch actually converts it to /24 ie 255.255.255.0 If we could open it up to 255.255.0.0 or just 255.0.0.0 it could work. Again never could find out where that was set.
Sometimes you can manually set the route table. But really I think that only works if your ISP is giving you a fixed ip.
So.... why do you want the speedtouch to handle authentication?? As I said, using spoofing is normally only used in situation where pppoe is not available to get around the issue of bridging to pppoa. One method used is pptp to pppoa relay. That will also work with the wrt54gl working with dd-wrt. But the authentication is actually taking place on the router.
About the only other solution is one to one NAT. In other words use your speedtouch as a router but all packets are passed so it is pure NAT, not NAPT. You can set this up in the speedtouch. I will need to look up the cli rules for this if you want to go that way. But in 510 you can use defserver, under the NAT. It does a pretty good job of simply forwarding all packets.
IMHO use bridge and PPPoE client. More robust, more efficient. Whatever your reason for not making the wrt54gl do the actual authentication is unlikely to overcome the basic facts that spoofing is poor in dynamic public ip situation.
|
|
|
|
arielgrin
Starting Member
Argentina
6 Posts |
Posted - 31/01/2008 : 02:16:33
|
Hi StingRay: In fact, ST510 is giving a 255.255.0.0 netmask for a 190.3.0.x public IP, but being the gateway 200.3.60.15, it falls outside its range. WRT54GL is getting that netmask, which makes sense since the public IP is a class B one, but fails to create the default route to 200.3.60.15, that is:
Destination Net: 0.0.0.0
Netmask: 0.0.0.0
Default gateway: 200.3.60.15
I guess it fails to do so because of this issue being outside the range of the public IP.
Doing a little more research, I decided to let the WRT54GL do the PPPoE dialing. This way, the WRT54GL is getting a 255.255.255.255 netmask, that's due to the PPPoE not even caring about netmask, as the PPP protocol doesn't negotiate it. So I decided to inspect its route table, and what I found was an additional route being:
Destination network: 200.3.60.15
Netmask: 255.255.255.255
Default gateway: 0.0.0.0
Then I thaught: "Lets go back to DHCP Spoof, but lets add that route to the WRT54GL too and see if that helps the WRT54GL to be able to install the default gateway, since with that route, it should think that the default gateway is now directly connected."
Thankfully, that partially solved it and I'm able to surf the internet with one caveat though. The default route doesn't get installed until I press the "RENEW LEASE" button in the WRT54GL web GUI, although the public IP has already been assigned to the WRT54GL. I'm trying to find a solution for that. I will keep you posted. Thanks again. |
|
|
|
arielgrin
Starting Member
Argentina
6 Posts |
Posted - 31/01/2008 : 03:31:37
|
After a lot more reading and searching, I may conclude that the problem is with the ST firmware, handling the wrong netmask to the WRT54GL. The spoof pool correctly states the netmask to be 255.255.255.255 but gives out a 255.255.0.0 netmask. I'll try to get this changed, though I think it will be really difficult, if not imposible, maybe you can help me with it? Or should I just go with full bridge and let this issue alone?  |
|
|
|
StingRay
Advanced Member
Australia
1219 Posts |
Posted - 31/01/2008 : 10:10:17
|
Full bridge is the way to go.
All the hassles with half-bridge are forced on us sometimes because ISP's don't support PPPoE which should become the world standard at least for domestic type connections. IPOA or EthoA work well for businesses. It is just so much simpler and more robust and reliable.
You are fortunate your ISP offers it... use it...
I think I am repeating myself.
|
|
|
|
arielgrin
Starting Member
Argentina
6 Posts |
Posted - 31/01/2008 : 11:22:20
|
Hey StingRay: as much as I may regret it, I switch my reliable ST for a conexant based modem, switched it to half bridge, for I am so stubborn  and voila! The issue is gone. I will keep on investigating anyway how to make my ST to work so I can get it back on the scene. You've been really helpful, I'm really pleased for your good advise and help. See you soon. |
|
|
|
StingRay
Advanced Member
Australia
1219 Posts |
Posted - 31/01/2008 : 11:52:08
|
| I don't know how a different implementation of the half-bridge can make the slightest difference but I am glad you got it working. Tell me in a week if it is actually reliable. Also see if it is running a 60sec lease. You will find most conexant chip modems use extremely short lease time. |
|
|
| |
Topic |
|
ST510v4 Connection config
