Hi,
I need advice.
I'd like to get a wired-only router that *only* routes. Is this possible now?
All it needs to do is:
a. run pppoe for the fttp connection
b. route static ipv4 (/29)
c. route "static" [1] ipv6
[1] when it connects, for ipv6 it gets a /64 for ND (neighbour discovery) and a /48
for PD (prefix delegation). The machines on the dmz with ipv6-only get their
ipv6 with SLAAC. The router I'd expect to run some type of dhcpcd, issuing the
/48 to the slaac ipv6 machines.
The ipv4 &6 are "static" in the sense that they linked to my account - in other words
they are not returned to the ISP's pool if the connection goes offline.
I don't want the router to do anything else like traffic shaping or firewalling or
dect phone or any of the other bells and whistles typical of all the routers i've seen.
It doesn't even need sshd, or a webby frontend. I'd be happy with just console access
via console cable. Firewalling is done within each of the connecting machines, which
have their own rules.
It only requires 2x NICs @1GB, though 2.5GB would be good.
The connection, currently, is 110/21 via FTTP, termination is ethernet.
thanks,
I need advice.
I'd like to get a wired-only router that *only* routes. Is this possible now?
All it needs to do is:
a. run pppoe for the fttp connection
b. route static ipv4 (/29)
c. route "static" [1] ipv6
[1] when it connects, for ipv6 it gets a /64 for ND (neighbour discovery) and a /48
for PD (prefix delegation). The machines on the dmz with ipv6-only get their
ipv6 with SLAAC. The router I'd expect to run some type of dhcpcd, issuing the
/48 to the slaac ipv6 machines.
The ipv4 &6 are "static" in the sense that they linked to my account - in other words
they are not returned to the ISP's pool if the connection goes offline.
I don't want the router to do anything else like traffic shaping or firewalling or
dect phone or any of the other bells and whistles typical of all the routers i've seen.
It doesn't even need sshd, or a webby frontend. I'd be happy with just console access
via console cable. Firewalling is done within each of the connecting machines, which
have their own rules.
It only requires 2x NICs @1GB, though 2.5GB would be good.
The connection, currently, is 110/21 via FTTP, termination is ethernet.
thanks,