Messages

106

21.7 Legacy Series / Re: DHCPDv6 whining about no IPV6 address on an interface designated NO IPv6

« on: October 20, 2021, 08:24:26 pm »

I've got the debug logs.  Is there a place on the system I can grab the files?  I have the circular logs turned off.

I'd like to get the files and have y'all look at them.

107

21.7 Legacy Series / Re: DHCPDv6 whining about no IPV6 address on an interface designated NO IPv6

« on: October 20, 2021, 05:08:13 pm »

@franco: I wish I knew.

This is ATT Fiber, BGW210-700 Gateway.  I do have an override config for that interface to get the 8 PD's.

What can I supply to help?

108

21.7 Legacy Series / Re: DHCPDv6 whining about no IPV6 address on an interface designated NO IPv6

« on: October 20, 2021, 01:12:36 pm »

It just shows the one interface that has IPv6 turned on.

109

21.7 Legacy Series / Re: DHCPDv6 whining about no IPV6 address on an interface designated NO IPv6

« on: October 20, 2021, 01:09:05 pm »

Not that's shown in the GUI. 

110

21.7 Legacy Series / Re: DHCPDv6 whining about no IPV6 address on an interface designated NO IPv6

« on: October 20, 2021, 05:46:02 am »

Any ideas on this?  It causes dhcpdv6 to die

111

21.7 Legacy Series / [SOLVED]DHCPDv6 whining about no IPV6 address on an interface designated NO IPv6

« on: October 18, 2021, 11:44:32 pm »

2021-10-18T16:39:25   opnsense[32558]   /status_services.php: Warning! dhcpd_dhcp6_configure() found no suitable IPv6 address on opt1   
2021-10-18T16:39:25   opnsense[32558]   /status_services.php: Warning! dhcpd_dhcp6_configure() found no suitable IPv6 address on opt3   
2021-10-18T16:38:43   dhcp6c[52920]   child: exec failed: Bad address   
2021-10-18T16:38:43   opnsense[63681]   plugins_configure newwanip (execute task : webgui_configure_do(,opt5))   
2021-10-18T16:38:43   opnsense[63681]   plugins_configure newwanip (execute task : vxlan_configure_interface())   
2021-10-18T16:38:42   opnsense[63681]   plugins_configure newwanip (execute task : unbound_configure_do(,opt5))   
2021-10-18T16:38:42   opnsense[63681]   /usr/local/etc/rc.newwanipv6: Dynamic DNS: Not updating home.lerctr.org A record because the IP address has not changed.   
2021-10-18T16:38:42   opnsense[63681]   /usr/local/etc/rc.newwanipv6: Dynamic DNS: Not updating home-fw.lerctr.org A record because the IP address has not changed.

What else do I need to supply?

112

21.7 Legacy Series / Re: IPv6 on ATT Fiber

« on: October 10, 2021, 07:15:41 am »

https://forum.netgate.com/topic/153288/multiple-ipv6-prefix-delegation-over-at-t-residential-gateway-for-pfsense-2-4-5/18 <-- this works for us as well (so far at least on one interface).

113

21.7 Legacy Series / Re: Firewall rules only work correctly after an update

« on: October 07, 2021, 03:37:13 am »

I had a similar weirdness.  I have 2 rules in my WAN interface to allow SSH and BACULA in, and one or the other would be active but not both.

I wound up deleting and recreating them both, and it SEEMS to be working now.

114

21.7 Legacy Series / IPv6 on ATT Fiber

« on: September 29, 2021, 03:57:51 am »

I'm trying to follow this article:
https://forums.att.com/conversations/att-internet-email-security/ipv6-wan-address-125-block/60206fe564100a03adc851bc?page=2

and have the following dhcp6c.conf:
# Setup requests for the WAN interface.
interface em4 {
   # Request a single IPv6 address for WAN interface (RG responds with 2600:1702:xxxx:yyy0::48)
   send ia-na 10;
   # Request 8x /64 prefix delegations:
   send ia-pd 0;
   send ia-pd 1;
   send ia-pd 2;
   send ia-pd 3;
   send ia-pd 4;
   send ia-pd 5;
   send ia-pd 6;
   send ia-pd 7;
   send rapid-commit;
   request domain-name-servers;
   request domain-name;
   script "/var/etc/dhcp6c_opt5_script.sh";
   #script "/conf/set_wan_static_v6.sh";
};
# These blocks are required, and I should probably
# assign the prefixes to the LAN interfaces here.
# Since my /60 has not changed since I implemented
# this, I treat them as static and assign them as such.
id-assoc na 10 { };
id-assoc pd 0 {
   prefix-interface em0 {
      sla-id 8;
      sla-len 8;
   };
 };
id-assoc pd 1 { };
id-assoc pd 2 { };
id-assoc pd 3 { };
id-assoc pd 4 { };
id-assoc pd 5 { };
id-assoc pd 6 { };
id-assoc pd 7 { };
#

the em0 interface doesn't seem to get an IPv6 address, and I'm not 100% certain I'm actually getting the PD.

Can anyone help me with:
1) how do I get dhcp6c to log something?
2) what am I missing?
3) getting radvd configured and running.

Thanks, as always.
21.7.3_1

115

20.7 Legacy Series / Re: pfatt and 20.7 don't seem to work

« on: August 20, 2020, 01:37:38 am »

Last week even my 20.1 system stopped getting DHCP from ATT, so I took the OPNatt stuff out and am NOT bypassing the RG at the moment.  If we find a way to get it to work on 20.7 (I upgraded since opnatt wasn't working anyway).

I did lose IPv6 as I can't seem to convince dhcp6c et al to get the PD from the NVG599.

I'll attach the opnatt.sh script I was running on 20.1.9 before ATT (AFAIK) broke it.

let me know what else I can supply.

116

20.7 Legacy Series / Re: pfatt and 20.7 don't seem to work

« on: August 05, 2020, 08:38:13 pm »

In my case I'm using the new OPNatt.sh from MonkWho on 20.1 (I was using the original aus one when this started, and 20.7 broke it), and the current opnatt.sh script from MonkWho works on 20.1 and does NOT work on 20.7.

I can't afford to test 20.7 again as it breaks all my connectivity.

117

20.7 Legacy Series / Re: pfatt and 20.7 don't seem to work

« on: August 05, 2020, 04:16:27 am »

The current opnatt.sh script loads the appropriate netgraph modules.

A fresh install of 20.1.9_1 works, upgrading to 20.7 breaks the DHCP stuff (no address, no connectivity).

118

20.7 Legacy Series / Re: pfatt and 20.7 don't seem to work

« on: August 03, 2020, 05:21:41 pm »

Same here, using the monkwho opnatt.sh script bridging EAPOL. 
I did NOT install RC1 either.

119

20.7 Legacy Series / pfatt and 20.7 don't seem to work

« on: August 01, 2020, 09:02:57 am »

I have 20.1 working great with 20.1.  When I upgrade to 20.7, I don't get DHCP from ATT.

Is there something(TM) changed between the HardenedBSD releases that possibly breaks NetGraph?

I made the grave mistake of NOT having a off machine backup of my config and had to rebuild it from scratch.

I don't want to go through this again trying to get current.

120

20.7 Legacy Series / Re: Why do I have NTP traffic to random IP's?

« on: July 31, 2020, 01:43:43 am »

DNS is *NOT* NTP.

NTP servers synchronize to GPS and other stratum 1 servers.

DNS is purely for Domain Name (Human Readable)-> IP address (and other info).  It has NOTHING to do with time.

Please read up on NTP.

http://www.ntp.org/ntpfaq/NTP-s-def.htm