From: Mark on
d_s_klein wrote:
[snip]
> I took it apart, found the chip-set maker (it was an embedded X86 with
> two MII ports; one MII went to a 1-port PHY, the other MII went to a
> 4- port switch)

I guess this 1-port PHY was for WAN interface. So from software point of
view (ie. Linux in your case), there are two network interfaces, eth0 and
eth1 for ex., where eth0 is WAN and eth1 is 4 ports switch?

--
Mark

From: d_s_klein on
On Mar 31, 5:38 pm, "Mark" <mark_cruzNOTFORS...(a)hotmail.com> wrote:
> d_s_klein wrote:
>
> [snip]
>
> > I took it apart, found the chip-set maker (it was an embedded X86 with
> > two MII ports; one MII went to a 1-port PHY, the other MII went to a
> > 4- port switch)
>
> I guess this 1-port PHY was for WAN interface. So from software point of
> view (ie. Linux in your case), there are two network interfaces, eth0 and
> eth1 for ex., where eth0 is WAN and eth1 is 4 ports switch?
>
> --
> Mark

From my point of view it was a router - a module I plugged in to do a
task.

I doubt that the "no-mmu x86" in the controlling IC was running
Linux. It did the job; I didn't care.

RK
From: David Brown on
Mark wrote:
> d_s_klein wrote:
> [snip]
>> I took it apart, found the chip-set maker (it was an embedded X86 with
>> two MII ports; one MII went to a 1-port PHY, the other MII went to a
>> 4- port switch)
>
> I guess this 1-port PHY was for WAN interface. So from software point of
> view (ie. Linux in your case), there are two network interfaces, eth0
> and eth1 for ex., where eth0 is WAN and eth1 is 4 ports switch?
>

For a great many of these devices, the switch is actually a managed
switch. So while the default firmware typically configures the four
"lan" ports as a simple switch, with better firmware you can configure
them as separate VLANs (i.e., eth1.0, eth1.1, etc. in Linux).
From: David Brown on
Big Boy wrote:
> Hello Group
>
> We are facing a project, where we need to incorporate a router and a 4 port
> ethernetswitch into a design.
> The switch part, we have covered, but the routerpart seems to post some sort
> of challenge.
>
> The requirements are:
>
> Always the same IP adress on the WAN side
> On the LAN side we need either DHCP or static IP's and NAT
> Portforwarding
>
> Does anyone here know of some small embedded module, for this use, or could
> point us in the direction of a chip-set or referencedesign? We thought about
> simply buying an industrial router, but spaceconstraints and a
> "minimum-cables" policy from the customer forces us to integrate this
> function on our PCB.
>
> It is part of a Computer system based on a ETX Module, but as far as I see,
> this function is completely separate from the computer it self, and could be
> contained on a PCB of its own, inside the box.
>
> Any thoughts or pointers would be gladly appreciated.
>
> Best regards
>
>

If you are only looking for small quantities, go for an off-the-shelf
firewall/NAT/wireless router. If you want more control than the default
firmware, install something like OpenWRT. We use LinkSys WRT54GL
devices with OpenWRT - they are not the most modern of routers, but do a
perfectly good job. And with OpenWRT, you can configure the port
forwarding, VLANs, etc., exactly as you want.