DHCP send option not sent

[nemric]

@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 ?

[s4rs]

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 below

Code Select Expand



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



[marjohn56]

Yes please, if you can run up 22.1 and then copy the dhclient over to that and reboot, see if it works... if not then we need to look elsewehere for the issue, but I suspect that it's the client.

@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 ?

[marjohn56]

Are you on OR France as well?

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 below

Code Select Expand



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



[franco]

The old one was https://github.com/opnsense/src/commit/5e4e4f842b714e

Looking at the config it should ignore vlan-parent and vlan-id so that vlan-pcp is still read and used. I've made sure to set net.link.vlan.mtag_pcp=1 on 22.1 for that reason.

One thing to try is to scrub vlan-parent and vlan-id from the configuration, but I worked on compatibility with defunct options including submitting it to FreeBSD so I would rather assume the PCP is not set correctly?


Cheers,
Franco

[s4rs]

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.

[marjohn56]

No, I know it's not the ISP, just wondered if you were OR France.

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.

[nivek1612]

@nemric let me know if you are unsure how to replace the dhclient file. I can help. I just don't want to try on my remote system in case it crashes the router. I will have no way back. Sitting next to it is very easy and risk free. 

[nemric]

Hi,

I will give it a try tomorrow, I need internet today ^^

@marjohn56 my ISP is not OR france (presume it's orange) but like orange I need a VLAN to bypass the box.

[s4rs]

@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 .

I tested the dhclient you attached. While DHCP is working consistently for me with the new client it doesn't fix getting out to the internet. I still lose internet access with 22.1 and when I ping I get this error

Code Select Expand

root@crawford:~ # ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host

while it is getting an IP address routing doesn't seem to be getting setup properly.. Let me know anything else you think I should test.

[nemric]

Yes please, if you can run up 22.1 and then copy the dhclient over to that and reboot, see if it works... if not then we need to look elsewehere for the issue, but I suspect that it's the client.

I finally make the image of 22.1 written on an USB key, see other post ...

What if I write your Dhclient on the USBkey to test it from live boot ? will the test be the same ?
To be honest I don't really want to update, test, reinstall(or not) and so on ^^ but I agree to make some test !

[nemric]

So, I tried to replace dhclient on the USB key and then try to boot on live OS

My Vlan didn't obtain any ip again, the pb seems to be elsewhere :(

[nivek1612]

Hmmm interesting

Did you remember to change the permissions of the dhclient after you copied it to the usb.

[franco]

Maybe, just maybe this is about VLAN parent not being assigned now using hardware features that are not supported/broken? Try to assign the VLAN parent, enable it and see if that yields a response. From what I can see here and assuming dhclient does what it supposedly can the problem might be not there at all.

For reference see: https://github.com/opnsense/core/issues/5521


Cheers,
Franco

[nivek1612]

Hi Franco

So I tried that but no joy.

Added a new interface on igb0 called "VLAN Spoof"

Rebooted after save and apply

Still no IP