Pfsense can`t keep connection alive to provider

stephenw10

@kalle13 said in Pfsense can`t keep connection alive to provider:

kernel igb1: link state changed to DOWN

Looks like the WAN interface actually goes down, loses link.
Try switching the cable. Swapping the NIC assigned as WAN. Putting in an unmanaged switch between the WAN and the modem.

Make sure you have WAN_DHCP set as the default gateway in System > Routing > Gateway not automatic. Remove the v6 gateway if you're not using it.

Steve

Kalle13

Thanks for your fast reply Steve.

I will realize all of your proposals but one afte another. So I can see which one (maybe) caused the problem.

I will start with the default gateway option.
Both, IPv4 and 6 were on automatic. I set the IPv4 to WAN_DHCP and IPv6 to nothing.

I will let you guys know if it worked or not.

Kalle

johnpoz

Also setting 1000 to anything than auto is always going to be a BAD idea!! Gig is meant to be auto! Auto-negotiation is required by 802.3ab at 1GE...

I would be curious if what is meant by gui when set to 1000BaseT or 1000BaseT full-duplex... Since gig can not run non full duplex.. So that shouldn't even be listed. And possible when set vs auto that gig is the only thing advertised in the autoneg?

Interfaces for gig really need to auto to determine who is master and slave for timing, etc..

You shouldn't be messing with that setting unless you want your gig interface to run at something lower than gig. If its suppose to be gig and doesn't neg to that - then you have something wrong that needs to be addressed!!

Have to look into the docs to see if that is called out directly - but they shouldn't really allow you to set 1000 anything other than autoneg.

stephenw10

Yes, I've always found that a bit odd. The gui just reports what ifconfig sees. Quite why the driver has those modes is beyond me:

[2.4.4-RELEASE][root@5100.stevew.lan]/root: ifconfig -m igb0
igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
	options=2400b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6>
	capabilities=753fbb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,NETMAP,RXCSUM_IPV6,TXCSUM_IPV6>
	ether 00:90:0b:76:8e:51
	hwaddr 00:90:0b:76:8e:51
	inet6 fe80::290:bff:fe76:8e51%igb0 prefixlen 64 scopeid 0x1 
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
	media: Ethernet autoselect
	status: no carrier
	supported media:
		media autoselect
		media 1000baseT
		media 1000baseT mediaopt full-duplex
		media 100baseTX mediaopt full-duplex
		media 100baseTX
		media 10baseT/UTP mediaopt full-duplex
		media 10baseT/UTP

Steve

johnpoz

Anyway to remove them from the gui - its just going to lead to stuff like this user did because they don't know any better..

But curious if setting that mode just actually removes the 100 and 10 from the neg process?

stephenw10

Probably going to need to ask Intel that. Or at least someone much more familiar with the code than me.

Steve

Kalle13

@johnpoz

I had switched it back to default (autoselect) since a few weeks.

Kalle13

I have done 4 from the things of the other posts. Now I've got no connection and so no internet. I am completly lost!

This I've tried:

switched the cable
setted tha WAN as dafult gateway
swapped the NICs

After I swapped the NICs I am not able to get an IP address now. My WAN adress shows 0.0.0.0. After some searching I recognized that I am not the only one with this issue and read some hints. This is what I did:

reset the router
switched from bridge mode to normal mode and back
-> in normal mode I got good and fast internet
spoofed the MAC adress from the router
restarted the pfsense several times after the router was finally up

I the status from the NIC it says :"Status : up" and "DHCP: down"

The DHCP protokoll says this 7 times in a row with diffenerent intervalls:
dhclient 76735 DHCPDISCOVER on igb0 to 255.255.255.255.255 port 67 interval 9

The system-generic protokoll has 3 entries:

php-fpm - /status_interfaces.php: the command '/sbin/dhclient -c /var/etc/dhclient_wan.conf igb0 > /tmp/igb0_output 2 > /tmp/igb0_error_output' gave exitcode '15' and the result was "
php-fpm - /status_interfaces.php: the command '/sbin/dhclient -c /var/etc/dhclient_wan.conf igb0 > /tmp/igb0_output 2 > /tmp/igb0_error_output' gave exitcode '1' and the result was "
php-fpm - /status_interfaces.php: the comand '/usr/local/sbin/dhclient {$ipv} -d -r -lf '/var/db/dhclient.igb0' -cf '/var/rtc/dhclient_wan.conf' -sf '/usr/local/sbin/pfsense-dhclient-script" gave exit code '1' back, the result was "Internet Consortium DH CP Client .... Listening on BPF/igb0/54:67:44:45:gg:34 Sending on BPF/igb0/... Canˋt attache interface {} to bpf device /dev/bpf0:Device not configured ....

stephenw10

Yes, if you changed the WAN MAC you might need to restart your modem device or even cal your ISP and ask them to reset it.
There should be no reason a different NIC would not get a DHCP address unless the server is refusing it.

Steve

Kalle13

Did my MAC change when I spoof the MAC of my router in my pfsense?
My router reseted several times due to the switching between the normal and bridge mode.

My new attempt is: f**k this router, I buy a used 6360 FritzBox cable and see if this works.

But if this is not going to be working I am calling my ISP to reset their modem.

Kalle13

Nothing of the following worked:

bought another cable router (Fritzbox) -> no success
called my ISP -> they resetted their hardware -> no success

I am now finished reinstalling pfsense and nothing changed. I canˋt get a IPv4 adress via DHCP.
I am desperate now. Does anyone has some tipps for me?

stephenw10

Run a packet capture on the WAN see what's happening. Is it actually sending dhcp requests? Is it seeing replies?

It still gets an IP if you put the modem back in router mode I assume?

Steve

Kalle13

@stephenw10 I did that yesterday (with wireshark). The pfsense sends the request but after that there is no offer from the ISP.

That´s right. In normal mode it get`s an IP.

Kalle

chrismacmahon

What gets this working again?

Rebooting the cable router (Fritzbox), or rebooting pfSense?

Kalle13

The mystery is is solved!
Heureka!
After days of working and searching.

It was a problem on the ISP side. I think, but don`t know it for sure, that they had a problem with the DHCP server. Maybe.
Today they worked on it. After some time it worked.

Thanks for you all for your help!
This case is closed.

stephenw10

Hmm, well why does the ISP not respond I wonder...

Can you try a pcap from a switch mirror port in the connection? That would prove it's actually being send.

Is it spoofing the MAC correctly?

Steve

Kalle13

Sadly I do not know. I did not talked to the IT people. I only had a ticket for my failure. So the only that I have is, that they where working on it and now it's working. That`s all.

I don't understand what you say. What should I do?
I watch my connection with wireshark.
I did the spoofing one time but after it did not succeed I witched it back to default.

Kalle

stephenw10

When you run tcpdump on the interface in pfSense you see eveything the driver is sending but that might not necessarily make it onto the wire.
By using a switch in between, mirroring the port and capturing on there you see what traffic is actually going back and forth.

Steve