Old age newbie in need of assistance regarding WAN IP
-
@dma_pf
Hi, just tried to ping 8.8.8.8 from within the router whilst it is bridge mode and all packets failed.Unfortunately I have to be away from my system for a few hours now, I will have to put things on hold until tomorrow.
Will post some screen shots then.
Many thanks for assistance.
-
@terryb58 Who's your ISP? If it's UK I will try to guide you.
-
Many thanks for the offer, my ISP is TalkTalk.
I have spent a bit of time on this this morning with some success.
I placed the HG366 router in bridge mode and disabled DHCP.
I then set the WAN port of pfSense to PPPoE and just entered dumb info into the user name password. As the ISP has stated none required but pfSense required an input.
I then added a VLAN 101 and attached to the WAN port.
After a reboot of the router my WAN interface status showed as UP with a public IP address and I then had internet access.
But, after a few minutes I lost internet access and my WAN port was showing as down.
It appeared very hit and miss, perhaps it is the router causing issues. I really need a better one, but I also need to know it will all work before I spend more.
On a side note, if I get a modem with multiple ethernet ports and set the new modem in bridge mode, do the other ethernet ports no longer connect?
TIA
-
@terryb58 the probs could be anything. try to configure DHCP in pfsense. But usually something is blocking, see if any connection blocked from or to your ISP, firewall log (status>system log>firewall) and would you share a screenshot of your states (Diagnostics > States) make sure to cover/blur your info.
-
If the modem auth is set to DHCP/IPoE you should not be using PPPoE. It's only working there by some chance which probably explains the seemingly flaky connection.
You said with DHCP set pfSense gets a public IP but there is no connectivity.
How were you testing that? Does pfSense itself have a connection from Diag > Ping?
Steve
-
Cheers for the assistance, I will have a look tomorrow, beer and football delaying things. :-)
-
When I set the WAN to DHCP, I did get a public IP, however no matter what I tried I could not get internet access. As @AKEGEC has stated, probably something blocking traffic.
Tomorrow is another day to delve further.
I have currently set my WAN IP address as a DMZ in my router and set up Port Forwarding which has enabled access when I am away from home, not ideal but it is working.
Cheers
-
Actually pulling a public IP via DHCP but not being able to connect out is unusual.
It could only be a few things. No default route or an invalid default route maybe.
If you can ping, say, 8.8.8.8 from the firewall itself but not a clinet then it could be an outbound NAT problem. If you can ping 8.8.8.8 buit not google.com it's a DNS issue.
Steve
-
Success.
I tried again this morning, doing the exact same this I have done over & over.
HG366 in bridge mode - DHCP off
pfSense WAN set to DHCP
Rebooted HG633
Status, Gateways, WAN_DHCP - online
Status, Interfaces, igb0 Wan - Public IP
Status, OpenVPN - PIA Connected
Diagnostic Ping 8.8.8.8 - successChecked a web site tab from my browser - no connection.
Tried another as everything should be working - successNot sure why it hadn't worked for the past few days, but it is now.
Many thanks for all the comments and assistance.
Stay Safe.
Edit - I had a VOIP & TV connected to other ports on the HG366 - I disconnected them for this test. May I now assume that having these plugged in to a bridged modem would stop the pfSense, or at least make it flaky?
-
In bridge mode it would only expect one device I imagine. It could have been handing a public to one of those other devices.
It's more likely though that the OpenVPN connection was causing an issue if you're using that as a WAN. Especially if it's the default gateway.
Anyway glad you got up and running. If you're connected over VDSL2 without g.fast then you won't see any benefit to going to a 'modem' with 1G ports. You will never pass >80Mbps anyway.
Steve
