Routing Problem (was: Re: Startup messages)

PD <[email protected]>
Newsgroups gmane.network.nocat
Message-ID <[email protected]>
Dear Scott,

Thank you for your advice that really solve out problem.

But we still have the other problem that seems to be a routing problem.
We does not know whether this can be insert into initialize.fw file or not.

our network
192.168.105.0/25

main router ----- nocat box ----- AP ----- client
main router : 192.168.105.8
nocat box (fxp0) 192.168.105.16/25
nocat box (dc0) 192.168.105.130/29
ap (wan port) 192.168.105.131/29
ap (ethernet port) 192.168.105.193/26
client using DHCP IP pool 192.168.105.194-254/26

from other terminal that using IP 1 - 126, we can ping to AP wan port, but not 
AP ethernet port and other pc that using IP 194-254.

seems that nocat box did not pass / allow the routing of 192.168.105.192/26

Questions, how to pass 192.168.105.192/26 via nocat ?

I did try to insert "{ipfw} allow 192.168.105.192/26 to any via 
{internaldevice}" into initialize.fw, but still does not solve the problem.

My AP is WRT54G that does not allow wan port and ethernet port within the same 
IP subnet.

Regards

PD
> I've added the following options to my kernel:
>
> options         IPDIVERT
> options         IPFIREWALL
> options         IPFIREWALL_VERBOSE
> options         IPFIREWALL_VERBOSE_LIMIT=5000
> options         DUMMYNET
> options         HZ=1000
>
> Read /usr/src/sys/conf/NOTES for full descriptions of the options.
>
> "options DUMMYNET" allows you to use pipes and queues to shape the traffic.
>  I shape the traffic so the people using our public access points don't use
> too much of our bandwidth.  There is also a section of ipfw man page
> devoted to traffic shapeing and dummynet.
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.