• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

dsl in linux woes solved:-)

daniel49

Diamond Member
my dsl modem/router is working fine in win xp and fedora core 3 but is struggling in ubuntu. The interface is through eth0.

in ubuntu with the exception of this forum😕 and downloads in synaptic it will not load a webpage.

I have learned the normal way in ubuntu is to enter pppoeconf in terminal and configure it.
I basically get an error message and it says my modem/router is possibly already using another pppoe so it can't use ubuntus.

I know qwest is using pppoa for sure
http://www.qwest.com/dslhelp/modems/gt701/index.html
It is possible to change to pppoe in modem configuration and that may work, or may not, but then it seems to me I would have to reconfigure everytime I went back to windows or fedora.
the link above talks about using a bridge is this maybe what I want to try?
Any ideas appreciated, networking is not one of my stronger points.

edit: ok after mass googling may be seeing a light at the end of the tunnel??
appears to be a problem with the modem and linux which is strange since the gateway is linux>

http://www.linuxquestions.org/questions/printthread.php?s=&threadid=244026
off to hack my files hopefully it will work?
 
ok am making progress the modem apparently does insert your isp# in resolv.conf so substituted the other ip# I assume its the gateways and left the primary dns # there also.

This allowed me to now browse the internet in ubuntu.
as the article indicated, that I linked to upabove, when you reboot though it overwrites resolv.conf with the wrong values again. Took thier suggestion and made a resolv2.conf so on reboot it copies the correct values each time.

Still seems a little sluggish though, you enter an address it thinks about it for 20-30 seconds then bam starts loading as opposed to windows where it doesn't think just loads.

Any tweaks you can think of that might speed that up?
 
ok finally got it solved:

was a combination of the dsl modem/router writing the wrong values to resolv.conf

and some tweaks to firefox:
entered about:config in firefox url window

changed network.http.pipelining to true
changed network.http.proxy.pipelining to true
changed network.http.pipeling.maxrequests value to 25
right clicked and created the new integer of nglayout.initialpaint.delay and set its value to 0

Am getting advertised dsl speeds up and down now
 
Back
Top