Project Home
Project Home		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Networking/Discussion/Technology/Unable to get routing with WAP Working/List of Posts
Forum Topic - Unable to get routing with WAP Working: (15 Items)
   
Update
Matt Blackburn
11/03/2010 1:36 PM
post73461
Unable to get routing with WAP Working   
I'm following the direction from here:  http://community.qnx.com/sf/wiki/do/viewPage/projects.networking/wiki/
Wifi_tcpip_config_wiki_page

But I can not get the "routing" to work.

I am bringing up a 3G data connection and the nameservers are being added to /etc/resolv.conf
I then follow the directions above to start my wireless adapter as a hostap and I am able to attach to the the AP that I
 created.  But my data packets are not routed between the wireless client and the 3G network.

I am able to ping off of the router via the 3G network so I'm pretty sure that everything to the "Internet" side is 
working just fine and I believe I have my dhcp.conf file setup correctly based on the examples.

Here is my pppd line:
pppd /dev/serusb1 defaultroute resconf require-ns noipdefault logstatus

Here is my "Network" portion of the dhcp.conf file:
subnet 192.168.253.0 netmask 255.255.255.0{
        range 192.168.253.100 192.168.253.110;
        option routers 192.168.253.1;
        option domain-name "my.net";
        option broadcast-address 192.168.253.255;
        option domain-name-servers 192.168.253.1;
        default-lease-time 600;
        max-lease-time 7200;
}

I have configured my wireless adapter with 192.168.253.1 as the IP address.

Thoughts?
Patrik Lahti
11/03/2010 2:15 PM
post73471
Re: Unable to get routing with WAP Working   
Hi Matt,

If you ping from the wireless client using an IP address (instead of a 
name), does that work?

 From the dhcpd.conf it looks like you may have to setup a nameserver on 
your router.

Cheers!
/P
Matt Blackburn
11/03/2010 2:49 PM
post73475
Re: Unable to get routing with WAP Working   
Nope doesn't work by IP address either.
I tried removing the name-server entry from my dhcp.conf file and still noJoy.

I have tried the connection from 3 different clients as well.  With the same results.
Patrik Lahti
11/03/2010 4:33 PM
post73487
Re: Unable to get routing with WAP Working   
Hi again,

What's the error message from the ping command?

Can the clients ping the router 192.168.253.1?

Can the clients ping the router's IP address on the "Internet" side 
(router's PPP interface)?

Can you post output of the following commands taken on the router:
sysctl net.inet.ip.forwarding
netstat -rn
ifconfig
arp -na

And from client:
cat /etc/resolv.conf
netstat -rn
ifconfig
arp -na

I think you should keep the name server line in dhcp.conf, the question 
is maybe what name server you should have in there. Are you running an 
name server inside the router? If not, then the name server line should 
change to point to the name server you're getting from the 3G network.

Cheers!
/P
Matt Blackburn
11/04/2010 10:15 AM
post73534
Re: Unable to get routing with WAP Working   
Here is the information you requested.  I ran the command as you indicated in your last response, but I was to busy to 
clean it up, trying to run between meetings and all.
I can not ping the external side of the PPP connection, 10.0.0.1 from any of my clients.  Right now the clients are a 
DROID X and a MAC, the information was gathered from the MAC client and the QNX 641 target.

Sure hope this helps.
Attachment: Compressed file AP_Router_Output.zip 1.7 KB
Patrik Lahti
11/04/2010 11:55 AM
post73572
Re: Unable to get routing with WAP Working   
Thanks for sending the info,

This looks suspicious:

rum0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ssid MYAP apbridge

I don't have a setup to try on at the moment, but IIRC that shouldn't 
say apbridge when you're trying to run router...

/P

On 10-11-04 10:15 AM, Matt Blackburn wrote:
> Here is the information you requested.  I ran the command as you
> indicated in your last response, but I was to busy to clean it up,
> trying to run between meetings and all.
> I can not ping the external side of the PPP connection, 10.0.0.1 from
> any of my clients. Right now the clients are a DROID X and a MAC, the
> information was gathered from the MAC client and the QNX 641 target.
>
> Sure hope this helps.
>
>
>
> _______________________________________________
>
> Technology
> http://community.qnx.com/sf/go/post73534
>
Matt Blackburn
11/04/2010 12:11 PM
post73582
Re: Unable to get routing with WAP Working   
I wondered the same thing, but I configure the interface as follows:

ifconfig rum0 mediaopt hostap ssid "MYSSID" 192.168.253.1 netmask 255.255.255.0

So I'm not 100% sure why it says "Bridge"..
Patrik Lahti
11/04/2010 12:30 PM
post73590
Re: Unable to get routing with WAP Working   
Maybe try 'ifconfig rum0 -apbridge' and see if that clears it?

(shot in the dark)
Matt Blackburn
11/08/2010 8:10 AM
post73816
Re: Unable to get routing with WAP Working   
Got pretty busy at the end of the week so wasn't able to try this until just now.
ifconfig rum0 -apbridge Did not produce the desired defaults.
Matt Blackburn
11/08/2010 9:17 AM
post73837
Re: Unable to get routing with WAP Working   
Based on my reading if I do the -apbridge then I need to use pf or something like that.  I have tried packet filtering 
(NAT) as well to no success.  I"m beginning to wonder if there is a problem with the "rum" driver.
Matt Blackburn
11/08/2010 11:20 AM
post73868
Re: Unable to get routing with WAP Working   
Ok I have tried with "Packet Filtering" (pf) to sort of "Reverse" the situation.
en0->rum0 with rum0 associated to an WiFi AP in the area.  Packets are routed just fine.
en0->ppp0 with ppp0 connected to a 3G network.  Packets are routed just fine.

The only issue I seem to have is rum0->ppp0 with the rum being a AP.

At this point I'm beginning to question the stability of:  devnp-rum.so.

Any thoughts.
Patrik Lahti
11/08/2010 11:38 AM
post73878
Re: Unable to get routing with WAP Working   
You can use pf to make routing work out of apbridge, but the fundamental 
problem seems to be the driver stuck in apbridge.

/P

On 10-11-08 11:20 AM, Matt Blackburn wrote:
> Ok I have tried with "Packet Filtering" (pf) to sort of "Reverse" the
> situation.
> en0->rum0 with rum0 associated to an WiFi AP in the area. Packets are
> routed just fine.
> en0->ppp0 with ppp0 connected to a 3G network. Packets are routed just fine.
>
> The only issue I seem to have is rum0->ppp0 with the rum being a AP.
>
> At this point I'm beginning to question the stability of: devnp-rum.so.
>
> Any thoughts.
>
>
>
> _______________________________________________
>
> Technology
> http://community.qnx.com/sf/go/post73868
>
Matt Blackburn
11/08/2010 12:32 PM
post73902
Re: Unable to get routing with WAP Working   
Please correct me if I am wrong here but if I was struck in "Bridge" mode then wouldn't I be getting addresses assigned 
to me from the "Far" end?  Basically look like I was on the Far end network rather than the local network to my board?
Patrik Lahti
11/08/2010 1:30 PM
post73923
Re: Unable to get routing with WAP Working   
Maybe I misunderstood but I thought you had a DHCP server running 
directly on the rum0? (I'm saying, if it is in bridge mode but isn't 
bridged to anything then there are no other interfaces which would come 
into play)

On 10-11-08 12:32 PM, Matt Blackburn wrote:
> Please correct me if I am wrong here but if I was struck in "Bridge"
> mode then wouldn't I be getting addresses assigned to me from the "Far"
> end? Basically look like I was on the Far end network rather than the
> local network to my board?
>
>
>
> _______________________________________________
>
> Technology
> http://community.qnx.com/sf/go/post73902
>
Matt Blackburn
11/08/2010 1:35 PM
post73925
Re: Unable to get routing with WAP Working   
No I think we are on the same page.  I had a dhcp server running against rum0 but I also tried it w/o a server too.

My solution is to "Not" have a bridge, so I agree that -apbridge is correct, but just not working.

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems