I am a recent Frontier install and migrating from another provider. I was given a NVG44B against ADSL2+ bonded. I'm frustrated and unhappy with the device, less so with the service although that's been a headache too.
First topic:
I need a bridge. I see instructions how to configure the 443B in other posts. However, I prefer to test bridging with second device whether a second 443B or something else. As a consumer, finding one I can buy outright is proving difficult.
First question:
Who sells a compatible device to us consumers?
Second topic:
The 443B appears to have an internal DNS (UDP 53) intercept resolver that is, frankly, a PoS that I cannot turn off. On Incoming (i.e., Internet initiated) DNS queries, the resolver intercepts and drops those queries to my DNS primaries on the LAN side of the 443B thereby blinding my DNS secondaries on the WAN side (i.e., the DNS secondaries cannot query the primary for SOA records). Outgoing DNS queries seem to overwhelm the 443B intercept resolver and DNSSec is probably a no-go. TCP 53 is fine.
It is unclear whether putting the 443B into bridge mode bypasses the 443B's intercept but for testing I prefer to use a device I own and to have alternative devices.
No, I am not doing NAT.Yes, my LAN side devices are not pointed to the 443B's resolver (i.e., the 443B appears to intercept queries). Yes, I have internet routable IPs on the LAN side of the 443B. Yes, I provide my own Internet services: DNS, SMTP, IMAP, etc. and have done so for decades. I also have three 6in4 tunnels. I also do Internet protocol research. Therefore, I need a device that simply bridges and does little else although QoS/CoS would be nice. If Necessary, I'll do my own routing if the 443B can be turned into nothing more than a modem.
Second question:
I read the 443B cannot be configured into a "true bridge" but I cannot find a discussion where the 443B falls down in that regard. In what areas does the 443B fall down as a bridge?
TIA
↧