On Tue, Jul 24, 2012 at 2:54 PM, Adam Thompson <[email protected]> wrote: > You're followed the right steps, I think, but pfSense has detected the > firewire port on the motherboard as an ethernet device (this is legit)
Interesting. This little mobo has only one slot, one nic on board, but 2 firewire headers. Do I understand correctly that a firewire connection between the pfsense box and firewire on another computer is the equivalent of regular nics and cable? Thanks, Kent and auto-detection isn't working properly. > Either skip auto-detection and use the device name you show in your post > (rl0) or disable the firewire port if possible and try again. > -Adam > > Kent Tenney <[email protected]> wrote: > >>Howdy, >> >>Is my understanding of installation wrong? >>If the following should work, troubleshooting suggestions? >> >>Thanks, >>Kent >> >>I'm trying to build a new pfSense box: >>- small 32bit mobo w/ one nic card, one on board >>- boot w/ pfSense 2.01 CD >>- set up vlans? no >>- a for WAN auto >>- connect via small switch to a test box >> - "vr0: link state changed to up" >> <enter> >>- a for LAN autodetect >>- connect laptop to the small switch >> "rl0: link state changed to up" >> <enter> >>- <enter> (nothing if finished) >> >>WAN -> fwe0 >>LAN -> fwip0 >> >>"do you want to proceed?" >><y> >> >>WAN (wan) -> fwe0 -> NONE (DHCP) >>LAN (lan) -> fwip0 -> 192.168.1.1 >> >>On my laptop: >>- sudo dhclient -r >>- sudo dhclient eth0 >> >>Nothing. >> >>- sudo ifconfig eth0 192.168.1.10 netmask 255.255.255.0 >> >>- ping 192.168.1.1 >> >>Nothing >>_______________________________________________ >>List mailing list >>[email protected] >>http://lists.pfsense.org/mailman/listinfo/list >> > _______________________________________________ > List mailing list > [email protected] > http://lists.pfsense.org/mailman/listinfo/list _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
