For PPPoE users who recieve an ip over wifi but cannot access the web portal

[dimensionerror]

I worked a long time to figure this out, and i'm glad I finally did. A bug in chillispot was preventing me from connecting to the web portal to login. Until chillispot is patched, people who use PPPoE to login to their service provider probably won't be able to run a successful hotspot with chillispot+worldspot.

From reading on chillispot's forum, there seems to be a problem with the way that chillispot handles mtu problems. Chillispot doesn't seem to handle the packets telling a host to resend smaller packets.

Changing your client computer's mtu to 1452 fixes the problem. This isn't feasible for public hotspots. An easy way to work around this is to set up a regular router and have the hotspot router plugged into it.

[dimensionerror]

A guide for changing your mtu in windows xp:
http://www.winguides.com/registry/display.php/280

[WorldSpot]

Thanks for the info. This explains why some people complained it did not work.
Have you tried to set the MTU in dd-wrt? (In basic setup/ optional settings)

[dimensionerror]

Changing the mtu in ddwrt did not work for me. The problem is when the pppoe connection refuses the larger packets and then chillispot ignores the instructions to use a smaller mtu. Since this problem is on the chillispot forum, i think that an update for chillispot will come eventually.

[WorldSpot]

Looks like there are work arounds in this topic

Unfortunately, I don't use pppoe so I can't test anything. Feedback welcome.

[b2amedina]

Does anyone have a clear suggestion as to how to fix this problem. I use PPPoE and get an IP address but can not access any web pages b/c the worldspot login page never comes up.

I have a Buffalo WHR-G54S with DD-WRT SP2 installed on it. I  can access everything correctly wirelessly if I turn off Chilispot or if I use the Sputnik hotspot software.

With Chilispot I it just doesnt work. I tried changing the MTU on the router and on the windows client machine to 1415, 1452, 1492 but it didnt work. I also set tried setting up the Buffalo router using a DHCP address provided by a US Robotics router that uses PPPoE (chained the routers). Again everything worked wired but Wirelessly no cigar.

[WorldSpot]

Maybe it is a dd-wrt bug. Maybe sp3 could help?
Could you please try the coova AP firmware? (http://coova.org)
Sorry if I can't help.

[WorldSpot]

Please try to add this iptables rule:

Code: [Select]

/usr/sbin/iptables -t mangle -A POSTROUTING -p tcp --tcp-flags SYN,RST SYN -m tcpmss --mss 1421:65535 -j TCPMSS --clamp-mss-to-pmtu
In dd-wrt, go in commands, enter the line and click "save firewall"

[WorldSpot]

Latest Coova firmware should have corrected this bug, but it hasn't been confirmed yet.
If someone could confirm, that would be nice.

[jvalla]

Tried Coova but that firmware is waaaay too slow.

[WorldSpot]

Tried Coova but that firmware is waaaay too slow.

Do you talk about the web interface or the hotspot usage?
I find that surfing is faster, and i'm not the only one who noticed that.

[network45]

Mr. Dimension Error,

you mentioned that for solving the PPPOE issue

"An easy way to work around this is to set up a regular router and have the hotspot router plugged into it"

How could this be done, could you if possible please put up a simple network diagram, and how should the hotspot router be confiured, i think i had a similar setup of mine that i had mentioned in

http://worldspot.net/forum/index.php/topic,1168.0.html

Please tell me how to do what you have said above.

regards
ac

[WorldSpot]

Could you please try coovaAP and see if this resolves this pppoe problem?

[spliton210]

Guys, I had this exact same problem with WRT 54GL and Both the DD-WRT v24 and v23sp2 as we use PPPoE here in South Africa. Spent TWP DAYS trying to resolve.

Reflashed with a Linksys firmware and then CoovaAP

Whole system up and running in 30 minutes.

BRILLIANT FIX!

 

[dijnebbh]

RE: For PPPoE users (the WAN side of the router) who receive an IP Address, then cannot access either the web portal, or several websites.

Code: [Select]

/usr/sbin/iptables -t mangle -A POSTROUTING -p tcp --tcp-flags SYN,RST SYN -m tcpmss --mss 1421:65535 -j TCPMSS --clamp-mss-to-pmtu
Worked! Whoo hoo! 

Googled 'Chillispot MTU' and eventually found this post. My users on the public side could not connect to several websites, including Hotmail.

I have confirmed this does fix the bug in DD-WRT's version of Chillispot where the MTU problem in the Chillispot TUN/Virtual adapter, causes some websites to 'hang' forever on 'Waiting for xxxxx.xxx'

This will end up in the DD-WRT Wiki.

It seemed like an MTU problem. Earlier, adjusting the 'physical' LAN port MTU under DD-WRT, made no difference.
It makes sense the TUN adapter has it's own MTU.