Routing



  • I have a laptop with an rfc1918 0.2 ip and a gw of 0.1 using wrt54g ddwrt.  I also have a Symantec 5420 with a headless/embedded config with the internal net using eth1 at 1.1.  I have tried to get to the mgmt. if at 1.1 via all possible/routes ways to no avail.  my wish is to use my laptop thru the wlan (dd-wrt) to connect to the pfsense appliance using 1.1.  how can I use my 0.2->01 wlan laptop to connect to the internal lan 1.1 pfsense mgmt. interface? to config the pfsense router?

    send me a bone of some sort, pls?

    am I not asking the correct question?


  • Netgate Administrator

    What you would normally do here is re-configure the WRT54 to be an AP point only and then connect it to the pfSense LAN interface. Then your laptop would receive it's IP via DHCP from pfSense even if connected wirelessly.

    http://www.dd-wrt.com/wiki/index.php/Wireless_Access_Point

    Steve



  • Problem is I want to maintain my current internet connection, which is my DDWRT wap, while I configure the pfsense box in case I need to research any issues that I might encounter.  I thought vlan or aliasing with a static route would be easy enough but does not work…


  • Netgate Administrator

    Hmm, perhaps I've misunderstood what you are doing. I assume the Symantec box is running pfSense?
    How is it connected to the wrt54? Which interface?

    Steve



  • it's on the internal eth1 of eth0-6 minus 1 of course…. as these are not config'd with private ip's.  I have added static routes on the router and static leases on the router as well and also on my w7 box to no avail and no pingy/route to host on the pfsense box via option 7 to ping the router from hyperterm... I even edited rc.conf with a static route on pfsense to the gatewae but no joy... I have finally switched ip's on the router to the same subnet and figured that I will forego the disconnected down time from ip changes from the pfsense box and then set everything up from the front end down to where the other devices should be.... it was mostly a learning curve that I wanted to tackle but the curve crossed and now I have to re-evaluate the and configure the thing later.... thanks for your responses... I am sure it is something very simple I missed as I have some knowledge about a lot but not a lot about one thing and I ain't so sure I wanna be a "sme".  I could get it working traditionally but I thought I could learn something to the other to work.... ohh... well!

    thanks!



  • I have tried all of the ifs internally on the LAN but what I wanted to do was route wlan traffic from my laptop to the pfsense box to config the pfsense box while keeping my inet connection…. that's all.....


  • Netgate Administrator

    There should be no good reason why you can't access the pfSense webgui from your laptop connected via wifi. Here's what I would do.
    Connect the pfSense WAN interface to one of the switch ports on the WRT54. Set the pfSense WAN to use DHCP, it will then receive an IP from the WRT54. Set a firewall rule on the pfSense WAN interface to allow access to the webgui on WAN, so: source any, destination WAN address, port 443 (or 80 if your using http). Done, you should now be able to access it via a wifi connection to the WRT54.

    It sounds like you're trying something more complex, is there some reason for that? As you say it's good experience to try some thing new.

    Steve


Log in to reply