Interesting. Thanks Chris.
-A
On Tue, May 13, 2014 at 6:19 AM, Chris Buechler wrote:
> On Sat, May 10, 2014 at 9:58 PM, Aaron C. de Bruyn
> wrote:
> >
> > Slightly OT, but why would they have ARP cache timeouts of four hours?
> What
> > benefit do you get with such high cache times as oppos
On Sat, May 10, 2014 at 9:58 PM, Aaron C. de Bruyn wrote:
>
> Slightly OT, but why would they have ARP cache timeouts of four hours? What
> benefit do you get with such high cache times as opposed to the obvious
> support calls you will get when equipment is swapped around?
>
That's Cisco's defa
On Sat, May 10, 2014 at 10:58 PM, Aaron C. de Bruyn wrote:
> Good to know.
>
> Slightly OT, but why would they have ARP cache timeouts of four hours?
> What benefit do you get with such high cache times as opposed to the
> obvious support calls you will get when equipment is swapped around?
>
> -
I have the same behavior with Videotron here in canada.
a power off for 2-3 minutes does the trick everytime.
On Sat, May 10, 2014 at 10:58 PM, Aaron C. de Bruyn wrote:
> Good to know.
>
> Slightly OT, but why would they have ARP cache timeouts of four hours?
> What benefit do you get with suc
Good to know.
Slightly OT, but why would they have ARP cache timeouts of four hours?
What benefit do you get with such high cache times as opposed to the
obvious support calls you will get when equipment is swapped around?
-A
On Sat, May 10, 2014 at 7:55 PM, Moshe Katz wrote:
> On Fri, May 9
On Fri, May 9, 2014 at 10:56 PM, Aaron C. de Bruyn wrote:
> Spent about an hour beating my head against the wall with this issue,
> hopefully this will save others some time.
>
> We had a stand-alone pfSense router.
> We just purchased two machines from ixsystems and were preparing them to
> be a
On 10.05.2014 04:56 Aaron C. de Bruyn wrote:
> We figured we would just get the two new boxes up.
[...]
> I called Comcast and had them remotely reboot the modem. Everything
> immediately came up and started working perfectly.
Hi Aaron,
this is no unexpected behavior.
Arp table on the router or
Yeah--I had gone over all the 'usual' stuff. DHCP disabled, firewall
settings disabled, Smart Packet Detection disabled.
-A
On Sat, May 10, 2014 at 4:28 AM, Ryan Coleman wrote:
> You may want to make sure the DHCP server is disabled on the modem
> completely. I’ve noticed that caused issues i
> You may want to make sure the DHCP server is disabled on the modem
completely.
It's a cable modem that I guess is in bridge mode, and they don't let me
mess with settings. Anyway, I think the DHCP server is in their headend
somewhere.
I'm just glad it's not like the old days when Comcast
You may want to make sure the DHCP server is disabled on the modem completely.
I’ve noticed that caused issues in the past for me.
The default user/pass is cusadmin/highspeed on those modems.
On May 10, 2014, at 2:19, Aaron C. de Bruyn wrote:
> Yeah--I figured it was related to the MAC address
Yeah--I figured it was related to the MAC address.
It'd be nice to know why the Comcast equipment does that--I've never run in
to it with other providers.
-A
On Fri, May 9, 2014 at 9:01 PM, compdoc wrote:
> > I called Comcast and had them remotely reboot the modem.
>
> Whenever I connect a di
It happens occasionally with their older SMC modems, but it seems to happen
frequently with the Netgear modems.
If you don't reboot the modem, it usually picks up on the changes within
5-15 minutes. Sometimes longer.
-A
On Fri, May 9, 2014 at 8:30 PM, Ryan Coleman wrote:
> I’m not running CA
> I called Comcast and had them remotely reboot the modem.
Whenever I connect a different network card to my home Comcast modem, I have
to power cycle the modem for it come up. I think it keys off the MAC address
of the old card, and won't accept the new one until then. I get a new IP
address ea
I’m not running CARP but I am doing many things like yours on my Comcast
Business account…
I’ve never had that happen - and I think my modem only reboots when I lose
power (it’s on the UPS but not on battery - by design).
Which modem did they install? I suspect it’s a firmware “feature” of that
Spent about an hour beating my head against the wall with this issue,
hopefully this will save others some time.
We had a stand-alone pfSense router.
We just purchased two machines from ixsystems and were preparing them to be
a failover pair of pfSense routers and then decommission the smaller old
15 matches
Mail list logo