Craig White spoke forth with the blessed manuscript:
> ----
> I don't think that you have to do it that way.
I don't. I don't trust the ability of the actiontec's software to configure
the fw properly. I don't want to use it as the FW.
>
> I typically can put all of the devices I need in the 4 ports on the
> Actiontec and assign them the public_ip address or if I needed more, I
> suppose I could add a hub to one of the Actiontec ports.
>
What 4 ports on the actiontec? I have 1. Also see above comment.
> I am guessing that what you are calling the WAN address is simply
> another public_ip address
In a real static netblock situation from a real ISP, your router will have an
external public IP address (typically static). This is the wan interface of
the router. The qwest setup doesn't do this (well it does, but you can't get
at the external address. Which would be fine, if the actiontec would let me
run a non-routable address range on its lan interface, and then a static route
to my net block.
>
> As for tunneling pppoa - that doesn't make sense to me. The Actiontec
> handles the pppoa connection and is the gateway device for all the other
> systems that have a public_ip - thus, there is no reason to fool with
> pppoa on any of the systems.
I don't want to run PPPoA on a desktop/laptop/whatever, I want my fw to get
the WAN address.
>
> As for bridging, I thought someone said that Qwest doesn't support
> bridging any longer. The Cisco 678 is capable of bridging though.
The actiontec is "capable" of it, but it does it in a horrid way which is
totally broken.
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)