1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

PPPoE fails when using Wireless in Client mode

Discussion in 'HyperWRT Firmware' started by cventour, Apr 24, 2006.

  1. cventour

    cventour LI Guru Member

    Hello ,

    I have a WRT54GL v1.1 running on tofu 13c.

    At initial setup I put my PPPoE user/pass and Internet works ok. When I switch wireless to Client mode , Internet stops working. Syslog says that pppd is starting but nothing happens. GUI says that pppoe is disconnected and trying to connect give me a message that says that the router could not get an IP from the ISP.

    If I go back to AP mode or Wireless Bridge everything works ok again.

    I also want to assign an IP address to the wireless if (eth1) . I tried ifconfig but after I enter the command it hangs there and does not come back with the shell prompt. I have to press Ctrl-C to work again.


    Any ideas?

    Thank you.
     
  2. Thibor

    Thibor Super Moderator Staff Member Member

    when you put your router into Client mode, turn off the WAN port as the wireless is used as the WAN interface
     
  3. cventour

    cventour LI Guru Member

    Is it possible to use the wireless as a simple client ? I need to keep my original WAN port but I also want to connect to another AP (different subnet) , where I want to access some other services (FTP, file transfers etc)

    Is it possible to be done through command line ?
     
  4. Thibor

    Thibor Super Moderator Staff Member Member

    you can do it on the command line i think
     
  5. cventour

    cventour LI Guru Member

    oh sh*t ... more command line ? Would it be iptables commands only or not ?

    btw, I suggest that this should be added in the following versions for example having an option a. Wireless Client as WAN , b. Wireless Client ...

    Just half a cent of though (I am too n00b to give you two :) )
     
  6. Thibor

    Thibor Super Moderator Staff Member Member

    I don't think so, if that's what you want...write your own. tbh, i think the idea of using wireless to reach a remote ap, whilst maintaining your own wan link is a little advanced for the needs of the average Hyperwrt user, since this is the first time the topic has been broached.
     

Share This Page