Based on the suggestions by
This is my configuration file:
firewall { all-ping enable broadcast-ping disable ipv6-receive-redirects disable ipv6-src-route disable ip-src-route disable log-martians enable name WAN_IN { default-action drop description "packets from Internet to LAN & WLAN" enable-default-log rule 1 { action accept description "allow established sessions" log disable protocol all state { established enable invalid disable new disable related enable } } rule 2 { action drop description "drop invalid state" log disable protocol all state { established disable invalid enable new disable related disable } } } name WAN_LOCAL { default-action drop description "packets from Internet to the router" enable-default-log rule 1 { action accept description "allow established session to the router" log disable protocol all state { established enable invalid disable new disable related enable } } rule 2 { action drop description "drop invalid state" log enable protocol all state { established disable invalid enable new disable related disable } } } receive-redirects disable send-redirects enable source-validation disable syn-cookies enable } interfaces { ethernet eth0 { address dhcp description WAN firewall { in { name WAN_IN } local { name WAN_LOCAL } } } ethernet eth1 { address 192.168.1.1/24 description LAN-eth1 } ethernet eth2 { address 192.168.2.1/24 description LAN-eth2 } loopback lo { } } service { dhcp-server { disabled false shared-network-name LAN-eth1 { authoritative disable subnet 192.168.1.0/24 { default-router 192.168.1.1 dns-server 192.168.1.1 lease 86400 start 192.168.1.2 { stop 192.168.1.254 } } } shared-network-name LAN-eth2 { authoritative disable subnet 192.168.2.0/24 { lease 86400 start 192.168.2.100 { stop 192.168.2.150 } } } } dns { forwarding { cache-size 150 listen-on eth1 listen-on eth2 } } gui { https-port 443 } nat { rule 5000 { description "masquerade for WAN" log disable outbound-interface eth0 type masquerade } } ssh { port 22 protocol-version v2 } } system { host-name ubnt login { user ubnt { authentication { encrypted-password $1$zKNoUbAo$gomzUbYvgyUMcD436Wo66. } level admin } } ntp { server 0.ubnt.pool.ntp.org { } server 1.ubnt.pool.ntp.org { } server 2.ubnt.pool.ntp.org { } server 3.ubnt.pool.ntp.org { } } syslog { global { facility all { level notice } facility protocols { level debug } } } time-zone America/New_York } /* Warning: Do not remove the following line. */ /* === vyatta-config-version: "config-management@1:dhcp-relay@1:dhcp-server@4:firewall@4:ipsec@3:nat@3:qos@1:quagga@2:system@4:ubnt-pptp@1:vrrp@1:webgui@1:webproxy@1:zone-policy@1" === */ /* Release version: v1.0.2.4507738.121107.1250 */
Even though the WRT-54G is intended to be on eth2 in the end, it is currently connected to eth1. I have now set up the router like so:
Basic Setup
I assume they are because everything seems to be working, but are the Gateway and DNS addresses correct?
Advanced Routing
With this setup, I *am* able to connect to the internet when I am on WiFi, letting the router give me an address. However, if I use a network cable, I cannot get on the internet but I can get into the router settings. Another thing that's odd is that Windows is telling me the IP address of the laptop when connected via WiFi is not in the 192.168.20.X range as I would expect, but rather 192.168.1.X:
Wireless LAN adapter Wi-Fi: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::4a8:915d:b851:f967%2 IPv4 Address. . . . . . . . . . . : 192.168.1.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1