@Flea77 

 

TBH from what I see , the Omada range is not that easy to configure with a public IP subnet. Maybe you could post your actual Omada WAN config ?

 

Who is the ISP ? 

 

 

I dont have access to the config right now, I should have it Tuesday afternoon. The ISP is BVCOG. I have used their stuff before, I have two other locations that are served by their fiber, one of which is using a Mikrotik router they provided and set up, the other is using a TPLink, I seem to remember an ER605.

  @Flea77 

 

Thinking about this a bit more, I think you've got a major problem with the Omada range. To use the public IP addresses on the LAN you need to be able to disable NAT . AFAIK that's not possible on any of the Omada range.

MisterW wrote

  @Flea77 

 

Thinking about this a bit more, I think you've got a major problem with the Omada range. To use the public IP addresses on the LAN you need to be able to disable NAT . AFAIK that's not possible on any of the Omada range.

  @MisterW 

I'm confused, who is using a public IP address on a LAN connection?

  @Flea77 

 

Sorry for not being able to reply earlier, I was travelling most of yesterday.

 

As regards public IP's , the whole idea of a multiple IP block is that you can use some of the public IPs on devices in your LAN, for instance a web or email server that needs to be public facing. The main network IP is still used via NAT for other devices that don't require a public IP.

 

The settings you've been given seem (to me) to be those applicable for a client using one of the public IPs on your LAN.

You currently have the WAN interface on the 7206 set for static IP with the default gateway set to  173.195.163.129  , is that correct ?

I don't see how 173.195.163.129  can be correct for the default gateway for the WAN interface, it has to be the ISP gateway and thus can't possibly be in your allocated subnet.

 

Are you sure the WAN interface should be static IP ?, its more usual for it to be DHCP or PPPoE. These protocols allow for the IP address and default gateway to be automatically assigned by the ISP. 

MisterW wrote

  @Flea77 

 

Sorry for not being able to reply earlier, I was travelling most of yesterday.

 

As regards public IP's , the whole idea of a multiple IP block is that you can use some of the public IPs on devices in your LAN, for instance a web or email server that needs to be public facing. The main network IP is still used via NAT for other devices that don't require a public IP.

  @MisterW I understand, although the way I have always done what you suggested is to connect a switch to the incoming line from the ISP, then port 1 on the switch would go to a typical router and be used with NAT for the normal LAN, port 2 on the switch would go to the Ethernet port on my web server, port 3 on the switch would go to the Ethernet port on my FTP server, etc. I have never attempted to route static IPs through a router. Different methods for different people I guess.

 

 

MisterW wrote

  @Flea77 

 

The settings you've been given seem (to me) to be those applicable for a client using one of the public IPs on your LAN.

You currently have the WAN interface on the 7206 set for static IP with the default gateway set to  173.195.163.129  , is that correct ?

I don't see how 173.195.163.129  can be correct for the default gateway for the WAN interface, it has to be the ISP gateway and thus can't possibly be in your allocated subnet.

 

Are you sure the WAN interface should be static IP ?, its more usual for it to be DHCP or PPPoE. These protocols allow for the IP address and default gateway to be automatically assigned by the ISP. 

 

I am sure as I have used this ISP at two other locations, both of which also have static IP addresses, one on a Mikrotik router and one on a TPLink router. I also have the email from their network engineer giving me the static IP address information to put in the router. Lastly, with that given static IP information, my laptop works with their fiber perfectly when plugged directly from their media converter into the laptop's Ethernet port, so obviously the connection and information work.

  @Flea77 

 

I am sure as I have used this ISP at two other locations, both of which also have static IP addresses,

Were those single IP or IP block connections ? and what was/is the default gateway for those ?

 

Lastly, with that given static IP information, my laptop works with their fiber perfectly when plugged directly from their media converter into the laptop's Ethernet port, so obviously the connection and information work.

 

That's confusing me too

 

While I do not have the information for those connections I can tell you that as far as I remember all of BVCOG's connections are static and they are all blocks of IP addresses. And for the laptop, it is interesting that I could clone the MAC from the laptop into the router, plug the cable from the media converter into the laptop-it works, into the router-it doesnt, into the latop-it works, into the router-it doesnt. Of course waiting a little while between connections to let the devices sync. I have never seen that behavior before. Good news is on Tuesday I will have one of their network engineers who actually uses TPLink both in his home and office there on-site with me and we will have replacement routers and media converters so one way or the other we should get some answers.

I'd be interested in the results from the engineer visit.

  @Flea77 

 

Just re-reading from the beginning...

 

Lights show no activity on WAN4 or the fiber converter Ethernet port. Weird.

 

Is there absolutely no activity or just a brief burst ?

 

Do you have WAN online detection enabled ? If so try disabling it