Can't seem to get connection

Hello! New user here. I've always felt like an imbecile when it comes to doing anything with networking, and as such always feel as though I'm banging my head against a wall. Due to this, I've always just opted for all-in-one wifi routers. However, I've had fiber for about a year now, and after constantly being disappointed by speeds and lack of vpn support, I've finally decided to go the "DIY" route.

I've purchased a Zimaboard, because everything I've seen about it, made it seem so simple. I plan on swapping my wifi router to be an access point connecting to my Zimaboard with Openwrt, with my ISP modem upstream from there. I also got some smart switches to disperse into hotspots for wired connections.

Upon first installation of Openwrt, everything appeared to be going smooth. It seemed as though I had connection, and was following a couple of tutorials. I was setting up the VLAN and configuring as PPPOE connection, but couldn't figure out the PAP/CHAP, so I called my ISP and they said it was DHCP, not PPPOE. So I changed it back to DHCP, and now cannot connect to the internet at all.

The console says link is ready, but no matter what I try, it doesn't seem to connect. Been through tutorials, troubleshooter and quick start guide. I'm unsure what else to try or how to proceed. I've spent two 4-hour sessions just trying to get a connection, and I'm sure I'm missing something simple. If I can provide more information or if there is another forum or discussion group where I should be posting, please let me know. I don't know where to start, but my head hurts and I just want it to work.

Sorry if this is stupid, nonsensical or in the wrong space.

Thanks for reading.

Please copy the output of the following commands and post it here using the "Preformatted text </> " button:
grafik
Remember to redact passwords, MAC addresses and any public IP addresses you may have:

cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall
1 Like

Hi

Maybe best thing to do is factory reset your device
if i get it right, WAN port is pure DHCP client which is default for fresh OpenWRT
so please, hold the reset button for 10-15 second
you will see a moment when all leds light up
release the button and let the router restart

it will be in "brand new" condition with DHCP client pointing toward ISP

1 Like

Which ISP is it? Some ISPs publish the required settings.

1 Like

Can you share the config from any other device that connects to that ISP?

1 Like
**Network**

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127...'
        option netmask '255...'

config globals 'globals'
        option ula_prefix 'f...'
        option packet_steering '1'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192...'
        option netmask '255...'
        option ip6assign '60'

config interface 'wan'
        option device 'eth1'
        option proto 'dhcp'

config device
        option name 'eth0'

config device
        option name 'eth1'

config device
        option type '8021q'
        option ifname 'eth1'
        option vid '35'
        option name 'eth1.35'


**Wireless**

No wireless capabilities on this device. 


**DHCP**

config dnsmasq
        option domainneeded '1'
        option boguspriv '1'
        option filterwin2k '0'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option nonegcache '0'
        option cachesize '1000'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
        option nonwildcard '1'
        option localservice '1'
        option ednspacket_max '1232'
        option filter_aaaa '0'
        option filter_a '0'

config dhcp 'lan'
        option interface 'lan'
        option start '100'
        option limit '150'
        option leasetime '12h'
        option dhcpv4 'server'
        option dhcpv6 'server'
        option ra 'server'
        list ra_flags 'managed-config'
        list ra_flags 'other-config'

config dhcp 'wan'
        option interface 'wan'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'


**Firewall**

config defaults
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option synflood_protect '1'
        option flow_offloading '1'
        option flow_offloading_hw '1'

config zone
        option name 'lan'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        list network 'lan'

config zone
        option name 'wan'
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option masq '1'
        option mtu_fix '1'
        list network 'wan'

config forwarding
        option src 'lan'
        option dest 'wan'

config rule
        option name 'Allow-DHCP-Renew'
        option src 'wan'
        option proto 'udp'
        option dest_port '68'
        option target 'ACCEPT'
        option family 'ipv4'

config rule
        option name 'Allow-Ping'
        option src 'wan'
        option proto 'icmp'
        option icmp_type 'echo-request'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-IGMP'
        option src 'wan'
        option proto 'igmp'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-DHCPv6'
        option src 'wan'
        option proto 'udp'
        option dest_port '546'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-MLD'
        option src 'wan'
        option proto 'icmp'
        option src_ip 'fe80::/10'
        list icmp_type '130/0'
        list icmp_type '131/0'
        list icmp_type '132/0'
        list icmp_type '143/0'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Input'
        option src 'wan'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        list icmp_type 'router-solicitation'
        list icmp_type 'neighbour-solicitation'
        list icmp_type 'router-advertisement'
        list icmp_type 'neighbour-advertisement'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Forward'
        option src 'wan'
        option dest '*'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-IPSec-ESP'
        option src 'wan'
        option dest 'lan'
        option proto 'esp'
        option target 'ACCEPT'

config rule
        option name 'Allow-ISAKMP'
        option src 'wan'
        option dest 'lan'
        option dest_port '500'
        option proto 'udp'
        option target 'ACCEPT'


This was a thought I had as well, but shortly after I started this thread I had reached my limit for the day and haven't had time to mess with it since then. I was also thinking about it, and I'm pretty sure my genius left wifi turned on while I was testing. Factory reset was about to be my next option, but I just found instructions for writing OpenWRT straight to the eMMC. I feel as though this may be a better option anyways, so I will try that instead.

Lumos, formerly Northstate. As you can imagine, search results with anything containing "Lumos" is an absolute smorgasbord

By that, you mean like a currently working router? I'm unsure how to acquire this from my TP-Link Archer AX50. All I can find is backup/restore, and that doesn't seem helpful.

You have vlan 35 defined but not used anywhere. If your isp uses this vlan, you need to specify that in the wan config.

config interface 'wan'
        option device 'eth1.35'
        option proto 'dhcp'

You can delete all of this:

2 Likes

True, but searching for "lumos vlan 35" provides some results which appear to be more relevant...

This was in the first three results returned by DDG: VLAN 35 required by ISP

No guarantee that the answer is definitively in that thread, but it may give you some pointers for further troubleshooting.

1 Like

I don't know Lumos (or Northstate) so I can't be 100% positive about what settings you'll need, but I do have DSL (fibre to the cabinet, waiting on fibre to the home) so there might be something of use here...

From my own uninformed tinkering with my own DSL equipment over the years, I suspect some separate pieces of information may have been mixed up.

My own setup:

image

The DSL "modem" talks over VLAN 101 to the ISP, and in turn translates PPPoA into PPPoE. The Router's Ethernet interface is configured with a PPPoE subinterface which contains the ISP's credentials.

Lumos's support pages suggest that they provide a "modem" which you can't (or "aren't allowed to") replace, but you can plug your own router into the "modem".

Assuming that Lumos's support pages are accurate and current (everyone hates writing documentation...) then you might not need to deal with VLAN tags... maybe.

If you're trying to do this:

image

Then remove any references to VLAN 35 from OpenWRT and configure a PPPoE interface for your WAN.

However, if you're trying to do this:

image

Then do as Lumos suggested and set OpenWRT's WAN interface to DHCP.

If you're trying to do this:

image

Then you may need to play around with VLAN configuration.

1 Like

It appears I have only sent you all on a wild goose chase. I setup vlan 35 following the tutorial that led me to attempting to setup PPPOE. I deleted the vlan as well as the config devices you specified. That didn't change anything, so I began messing around with a few other settings and somehow disabled my lan port. I then decided to just go ahead and fresh install. I have not changed anything. I still cannot get any internet connection with my OpenWRT device plugged directly into the Lumos modem. However, if I plug into my OpenWRT device into my current router, it works. I remember coming across a thread with this issue that I will attempt to find momentarily.

Thanks for your response

I never would've thought to add vlan 35 to the search terms! However, due to the revelation above, I may have accidentally mislead you as well. I believe this would apply to your next response. I would like to thank you for your response and pose a couple of questions. To configure as PPPOE, I would need the PAP/CHAP login information, which Lumos told me is incorrect. They said to configure as DHCP, not PPPOE. Is there a way around this? Also, in your last example, it appears to cut out Lumos' modem altogether. Is this correct and/or possible with fiber?

Thanks again!

Quick and dirty test: how is your current router's WAN interface configured? Is it configured to use DHCP, PPPoE, or something else? Whatever configuration it has, can you replicate that configuration on OpenWRT?

Also, is there any chance your ISP is playing stupid games with locking your Internet connection to a specific MAC address? Might the solution be as simple as configuring OpenWRT to lie to your ISP and present your existing router's MAC address instead of its own?

See above. Check your existing router's WAN interface. It's entirely possible that Lumos might be correct.

If all the equipment involved supports it, yes, it's possible. However, the ISP might have implemented measures to prevent customers from using their own kit. Nanny knows best, after all.

2 Likes

[quote="iplaywithtoys, post:15, topic:164616, full:true"]
Also, is there any chance your ISP is playing stupid games with locking your Internet connection to a specific MAC address? Might the solution be as simple as configuring OpenWRT to lie to your ISP and present your existing router's MAC address instead of its own?[/quote]

This was the answer. Copied the MAC over, disconnected existing router, restarted everything and it worked like a charm. Thank you so so so so much for all of your help!

I will mark this as the answer even though it wasn't the solution to the original issue.

May all your days be glorious.

::EDIT:: Apparently I can't figure out the quoting, but that's a problem for another day.

1 Like

You're welcome. Glad it's all working now.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.