> as I said, best is a firewall, however GBE capable pfsense HW starts at
> 1000 NIS + need at least another 200 for an AP,
Hi,
Late reply, but here goes:
You can repurpose (or add capability) to any existing x86/rpi system
in your home, you'll need a wifi USB dongle (if said system isn't
as I said, best is a firewall, however GBE capable pfsense HW starts at
1000 NIS + need at least another 200 for an AP,
this 1k NIS i wanted to save if i could find a satisfying solution
however in HOT 4 router i can't disable or firewall ipv6, so i thought a
simple dhcpv6 server could solve my
All home routers should be able to firewall incoming IPv6 traffic, so
it would be better to just firewall it, instead of disabling.
If you use Hot's modem (hotbox) as a router, then it can do that. At
least in the case of Hotbox2, it does so by default, so you should not
worry about the first
For best control you should go with the option of splitting the ISP router
to only act as modem, and have a FW like PFsense/OpenSense for the rest
(FW,DHCP 4/6, DNS, ).
and have several wireless APs spread across the house, which act only as AP
base stations. It's a bit more expensive, but it
Hello
I've swapped isp (hot/hotnet) and now i have ipv6 support which i can't
turn off.
I have a few issues with ipv6:
1. no NAT so all my devices are accessible from outside
2. can't redirect DNS traffic to my DNS server
I thought about adding a firewall, but this way i need a small fast-enough
Hi Erez,
You should be able to disable DHCP on the router, and pass all logic to a
secondary DHCP server.
You can prepend your DNS server as first among DNS servers on each client (also
make sure that your DNS server can answer for ), you can add one line in
/etc/dhcp/dhclient.conf (for
Baruch Even wrote:
Diego Iastrubni wrote:
The first work around, is to set the DNS server of the clients, not to the
modem but to the DNS servers of the ISP. Since the DHCP lease of the clients
ends after X time, the clients get once again the DNS of the modem, and the
problem comes back.
Meir Kriheli wrote:
It'd be better to leave aliases as is, so updates won't overwrite it (in
case you'll answer y by mistake).
ok, good point.
Another way to disable ipv6 is blacklisting the module. Creating a new
file will be the best:
echo blacklist ipv6 /etc/modprobe.d/blacklist-ipv6
Hi,
In case someone does not know why, I am using this funky bfocus 312 modem
bezeq is giving, configured as a router. In theory all I have to do is to
make my hosts dhcp and I am done. However, this modem supports IPV6, and
our ISPs generally do not, and the DNS servers get broken.
The
Diego Iastrubni wrote:
The first work around, is to set the DNS server of the clients, not to the
modem but to the DNS servers of the ISP. Since the DHCP lease of the clients
ends after X time, the clients get once again the DNS of the modem, and the
problem comes back. How do modify the
ביום רביעי, 9 באוגוסט 2006, 21:22, נכתב על ידי Baruch Even:
In my case there is a directory /etc/dhcp3/dhclient-enter-hooks.d/ any
script inside it is run on dhcp lease renewal. Simply place there a
script to reset the resolv.conf to whatever you want.
what an ugly solution... I like it!
Diego Iastrubni wrote:
ביום רביעי, 9 באוגוסט 2006, 21:22, נכתב על ידי Baruch Even:
alias net-pf-10 ipv6 - old
alias net-pf-10 off - on
and then run update-modules.
This does not work for me.
Maybe you have somewhere a script that forces loading the ipv6 module?
Setting these aliases
Diego Iastrubni wrote:
Hi,
In case someone does not know why, I am using this funky bfocus 312 modem
bezeq is giving, configured as a router. In theory all I have to do is to
make my hosts dhcp and I am done. However, this modem supports IPV6, and
our ISPs generally do not, and the DNS
13 matches
Mail list logo
