16
22.1 Legacy Series / Re: ipv6 issues
« on: March 06, 2022, 04:03:38 pm »BNG - What is that? Sorry this level of IPv6 is new to me.
Broadband Network Gateway
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
BNG - What is that? Sorry this level of IPv6 is new to me.
@Stephen maybe you want to upgrade to 22.1.1 first and try again.
@Mastah ... basically you do something like this...
# opnsense-core plugins
# cd /usr/plugins/dns/ddclient
(make your modifications to src/ directory files)
# make upgrade
(install new code to test your changes in the system)
@mueller let me get back on the issue of the log file
Cheers,
Franco
well, it is a least supposed to support google domains but will it accept the generated credential from my google domain accounts NO. Claims userid contains invalid characters
Anyone managed to get it to work with Google domains
Running 22.1.r2 and I'm having some difficulty getting it to run:Code: [Select]2022-01-24T16:48:55-06:00
root /usr/local/etc/rc.d/os-udpbroadcastrelay: WARNING: failed to start osudpbroadcastrelay
Are there any known compatibility issues known at this moment?
I did edit the migration notes a bit and pushed them to the server so they are being displayed during upgrade with the extended information.
https://github.com/opnsense/changelog/commit/3eab5a51434
Cheers,
Franco
Can anyone that is knowledgeable with the new plugin point me to the direction of getting godaddy to work with it? I played around with manually editing the config, and haven't gotten it to work so far.
No I am in the US and my carrier is Verizon FIOS. I don't think its a carrier issue since 22.1 fails in my lab just like it does with my provider.
I am having Internet access issues post 22.1 upgrade. I did a tcpdump on the WAN interface when connecting to my ISP. A DHCP address is being offered and accepted but I get no traffic. Can't ping, nothing is getting out. Strange..
If you are getting a WAN v4 address, then it's not the client causing you issues. Try some deeper diagnostics from the WAN interface, ping 8.8.8.8 for example, if that works then try a ping to www.google.com, that will prove if the dns ( unbound ) is working. My test system which is running 22.1 is working fine, and it's a simple dual stack setup.
Pinging the GW fails. Interface info and failure belowCode: [Select]
igb0_vlan10: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: WAN
options=4000400<LRO,NOMAP>
ether d4:a9:28:14:e8:98
inet6 fe80::d6a9:28ff:fe14:e898%igb0_vlan10 prefixlen 64 scopeid 0x6
inet 108.20.117.101 netmask 0xffffff00 broadcast 108.20.117.255
groups: vlan
vlan: 10 vlanproto: 802.1q vlanpcp: 0 parent interface: igb0
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
Guest (igb0_vlan200) -> v4: 192.168.200.30/27
LAN (igb0_vlan100) -> v4: 192.168.1.254/24
PIAWG (wg0) -> v4: 10.7.154.210/8
WAN (igb0_vlan10) -> v4/DHCP4: 108.20.117.101/24
PING 108.20.117.1 (108.20.117.1): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
@nemric - Seems the version from 21.7 is working OK, at least on my test device so I'm attaching it here. No guarentees, but try it. At least you have a local device and can revert. @nivek1612 is concerned he might lose everyhing if he tries, so would you try it and let us know? Remember to set the permissions to 0555 after copying the attached to /sbin .
Hi, I'm not sure to understand what you ask me for.
I'm running 21.7 now, and my vlan100 get an ip from ISP and everything works fine
The file you want me to try is for 22.1 ?
I am having Internet access issues post 22.1 upgrade. I did a tcpdump on the WAN interface when connecting to my ISP. A DHCP address is being offered and accepted but I get no traffic. Can't ping, nothing is getting out. Strange..